6364366
|
While upgrading from Application Server 7.0
Update 5 to Application Server 7.0 Update 9, an incorrect upgrade version
is displayed before the upgrade starts. The text reads ”Upgrading Sun Java System Application
Server from 7.0.0_05 to 7.0.0_07’ instead of ”Upgrading Sun Java System Application
Server from 7.0.0_05 to 7.0.0_08.’
Solution
None
|
4403166
|
On Microsoft Windows, package/path/application
names longer than 255 characters will fail to deploy applications.
On Microsoft Windows only, long package/path names are not supported
because of the JDK™ limitation. During deployment, the deployment tool
will try to extract class file from the archive. If the expanded name is more
than 255 characters, the extraction will fail.
-
Example of a long application name:
J2EE application
name as servlet_jsh_HttpServletRequestWrapper.ear
-
Example of a long package name:
The servlet is
located in the following package:
servlet_jsh_HttpServletRequestWrapper_1\servlet_jsh_HttpServletRequestWrapper_servlet_war\WEB-INF\classes\tests\javax_servlet_http\HttpServletRequestWrapperHttpServletRequestWrapperConstructorTestServlet.class
-
Example of a long path name:
Sun Java System Application Server is
installed as drive \:> Sun \ApplicationServer
Solution
Consider the following solutions:
-
Make a shorter directory structure during installation. For
example, drive:>App\ instead of the default drive:\>Sun\Apsserver7.
-
Use the create_instance command to rename
the instance to something shorter. For example, /instance1/domain1/ could
be changed to /i/d.
-
Have shorter package names, path names, and application names.
|
4687768
|
On Solaris setup-SDK/JDK, an error occurs when
installing in command-line mode on a machine without Xwindows.
It is not possible to run the Sun Java System Application Server installer, even
in command-line mode, on a hardened Solaris system which does not contain
X Windows libraries. The installer will throw java.lang.UnsatisfiedLinkError while instantiating AWT objects used by SetupSDK/Webstart Wizard’s
installer framework.
Solution
-
Install X Windows support packages temporarily, removing them
after installing the Sun Java System Application Server product.
-
Install the Sun Java System Application Server packages using the pkgadd command and create the initial domain using asadmin commands.
|
4719600
|
Warning messages occur during installation.
During installation, some invalid error messages might occur. For example:
WARNING: Couldn’t flush system prefs: java.util.prefs.BackingStoreException:
Couldn’t get file lock.WARNING: Could not lock System prefs.Unix error
code -223460600.
Solution
Ignore these warnings or, alternatively, you can create a system preferences
directory (typically /etc/.java/.systemPrefs). This is
normally done by the JDK install script.
|
4737663
|
On Solaris, if you install both the package-based
install and regular install, there is conflict.
If you install both the package-based install (Solaris 9 bundled) and
the mainstream installer version of the product, there are potential conflicts.
The Sun Java System broker for both of these installations will be shared, so if you
don’t uniquely name the domains and instances, you might see the following
message when starting the second instance with the same domain/instance name:
SEVERE: JMS5024: JMS service startup failed.SEVERE: CORE5071:
An error occurred during initialization
In particular, the default domain and instance names are the same for
both of these installations.
Solution
Follow the instructions in the “JMS Administration” chapter
of the Sun Java System Application Server Administrator’s
Guide.
|
4742038
|
Sun Java System Application Server does not start if the install
directory contains non alpha-numeric characters.
Sun Java System Application Server startup fails if the install directory contains
characters such as #, spaces, or any other non alpha-numeric characters. In
this case, the server log files are not created. The Sun Java System Application Server install
directory can contain only the following characters: alphanumerics, - (dash)
or _ (underscore). This also applies to entering existing Java 2 SDK directory
during installation.
Solution
During installation, specify a directory where names contain only alphanumeric,
dash, or underscore characters.
|
4742828
|
Silent installer is not checking user permissions.
Although interactive installers (GUI or command-line) check for appropriate
user permissions (admin user for Microsoft Windows platforms, and root user
for Solaris package-based installation), this check is not done during silent
installation. As a result, installation will fail later in the process because
you will not have sufficient permissions to install packages (Solaris) or
create services (Microsoft Windows).
Solution
Make sure that silent installation is being run as the appropriate user.
|
4741190
|
For Solaris, Installer accepts JDK_LOCATION
value even if the location contains an earlier version (earlier than JDK 1.2).
Sun Java System Application Server 7 requires a Java 2 SDK version greater than
or equal to 1.4.0_02. However, on Solaris, if a user chooses to reuse an existing
Java 2 SDK (less than version 1.2), the installer might not display a warning
message. The installation might complete successfully, but the Sun Java System Application Server might
not function properly. This is caused by having an existing JAVA_HOME in your
environment.
Solution
Before starting the installation program, unset JAVA_HOME as follows:
(On ksh): unset JAVA_HOME(On csh): unsetenv
JAVA_HOME
|
4742171
|
Installing a development installation over an
existing evaluation installation in silent mode does not report an error.
Affects installers running in silent mode. If user attempts to install
over an existing evaluation installation of Sun Java System Application Server 7 (in the
same directory), silent installation does not report any errors and proceeds
normally. Existing evaluation installation files are preserved.
Solution
Uninstall existing evaluation installations before installing a new
development installation in the same location.
|
4742552
|
Selecting Application Server and Sun Java System Studio
4 Enterprise Edition for Java components in the same installation session
in command-line and silent mode does not work correctly.
Affects development and operations installations. While running installation
in command-line or silent mode, you can choose to install both Application
Server and Support for Sun Java System Studio 4 Enterprise Edition for Java components
during the same installation session (in GUI mode, these components are mutually
exclusive). The installer does not process component dependency correctly
and tries to install the Administration Client component instead of the selected Sun Java System Application Server component.
Solution
Simulating GUI mode, first install the Sun Java System Application Server component
in command-line or silent mode, then run another installation and install
the Support for Sun Java System Studio.
|
N/A
|
On Solaris, if the Sun Java System Application Server installer
upgrades an existing Sun Java System Message Queue 3.0 to 3.0.1, the resulting installation
will be removed during Sun Java System Application Server uninstallation.
Affects Solaris development and operations installer. If an installed Sun Java System Message
Queue 3.0 is detected on the system, you are given the option of automatically
upgrading this installation to version 3.0.1. If this option is chosen, the
resulting Sun Java System Message Queue 3.0.1 installation will be uninstalled during Sun Java System Application Server uninstallation.
Solution
To preserve the Sun Java System Message Queue installation after the Sun Java System Application Server is
uninstalled:
-
Exit the installer when offered the automatic upgrade choice.
-
Upgrade Sun Java System Message Queue to version 3.0.1 according to Sun Java System Message
Queue documentation.
-
Run Sun Java System Application Server installation again.
|
4746410
|
On Solaris, when installing the Sun Java System Application Server in
non-default locations, the package-based installer on Solaris does not check
disk space in the correct locations.
When attempting to install the Sun Java System Application Server on Solaris (using
the package-based installer) in non-default locations, the installation program
does not check for disk space in the specified target directory. Instead,
it checks for disk space only in the default location (/opt).
Solution
Before starting the installation, make sure that you have adequate disk
space (85 MB) in /opt even if you do not plan to install
in /opt. In addition, make sure you have adequate disk
space (85 MB) in the target directory.
|
4748404
|
On Microsoft Windows XP, cannot incrementally
install sample applications and PointBase 4.2 components.
This issue affects the Windows XP platform. If you try to incrementally
install Sample Applications and/or PointBase 4.2 components over an installed Sun Java System Application Server component,
the installer does not correctly detect the existing Sun Java System Application Server installation
and reports Application Server Not Found. Installation
does not proceed.
Solution
Install sample applications and PointBase 4.2 components together with
the Sun Java System Application Server component. If the Sun Java System Application Server is already
installed on the system, uninstall it and run installation again, this time
selecting all necessary components.
|
4748455
|
Directory error occurs during generic silent
install.
This issue affects silent installation on all platforms. If the installer
finds a problem with a given installation directory, the generic error message Invalid Installation Directory is reported.This error message covers
the following situations:
-
Selected directory is not writable.
-
Selected directory string is empty or contains space characters.
Solution
Check the supplied installation directory value for both issues to determine
the cause of error.
|
4749033
|
On Microsoft Windows XP, cannot uninstall standalone
admin client installation using uninstaller.
This issue affects a standalone admin client installation on the Windows
XP platform. If user tries to uninstall a standalone admin client through
the provided uninstaller, uninstallation tries to uninstall an incorrect set
of components and hang.
Solution
Uninstall a standalone admin client manually. Files located in the install_dir directory should be deleted. The related Program
Group folder (Start->Programs->Sun Microsystems->Sun Java System Application
Server) should also be removed. There are no related Microsoft Windows registry
entries for a standalone admin client component; these steps will fully revert
the system in the state before admin client installation.
|
4749666
|
Samples documentation is not published to initial
server instance if Sample Application component has been incrementally installed.
This issue affects the development and operations installer on all platforms.
If sample applications are installed in a separate installation session over
an installed Sun Java System Application Server, the sample documentation will not be published
to the initial server instance and will not be accessible through the http://hostname:port/samples URL. However, documentation is installed
on the file system and can be accessed locally at this location: file:///install_root/samples/index.html
Solution
Access samples documentation locally.
|
4754256
|
On Solaris, Sun Java System Message Queue configuration
files are not preserved during Sun Java System Message Queue upgrade performed by the
installer.
If an existing Sun Java System Message Queue 3.0 package has been detected on
the system, the installer offers to upgrade this installation to version 3.0.1
which can be used by the Sun Java System Application Server. During this upgrade operation,
the existing 3.0 Solaris packages is removed, resulting in the removal of
the following configuration files:
/etc/imq/passwd/etc/imq/accesscontrol.properties
If these files have been modified, those modifications will be lost
and the resulting Sun Java System Message Queue 3.0.1 installation will contain the
default configuration values.
Solution
Create a backup copy of any user-modified files and restore the backup
copies of the files after the upgrade has been completed. For more details,
consult Sun Java System Message Queue 3.0 Installation Guide.
|
4754824
|
On Solaris, an installer error message occurs
while running installation from a CD.
When a volume is inserted into the CD-ROM drive, Solaris volume management
assigns it the next symbolic name. For example, if two CD-ROMs match the default
regular expression, they are named cdrom0 and cdrom.
Any that match the added regular expression would be named starting with cdrom2. This is documented on vold.conf man page.
Every time you install the Sun Java System Application Server from the CD, the CD-ROM mount
point appends a number after the label name. The first time the CD is mounted
everything goes well. On subsequent mounts, the following error message occurs
when the installer starts:
IOException:java.io.FileNotFoundException: /cdrom/appserver7
No such file or directory) while loading default flavormap.properties file
URL:file:/cdrom/appserver7#4/AppServer7/pkg/jre/lib/flavormap.properties
Solution
Installer functionality is not affected in any way. However, the following
workaround exists:
-
Become the superuser by entering the command su and
the root password at the command prompt, or log in as root. The command prompt
changes to the pound sign (#).
-
If the /cdrom directory does not already
exist, enter the following command to create it:
#
mkdir /cdrom
-
Mount the CD-ROM drive.
NOTE: The vold process
manages the CD-ROM device and performs the mounting. The CD-ROM might automatically
mount onto the /cdrom/cdrom0 directory.
If running File Manager, a separate File Manager window displays the
CD-ROM contents.
-
If the /cdrom/cdrom0 directory is empty
because the CD-ROM was not mounted, or if File Manager did not open a window
displaying the contents of the CD-ROM, verify that the vold daemon
is running by entering:
# ps -e | grep vold | grep
-v grep
-
If vold is running, the system displays
the process identification number of vold. If the system
does not display anything, kill the daemon by typing the following:
# ps -ef | grep vold | grep -v grep
-
Stop the vold process by entering:
# kill -15 process_ID_number
-
Mount the CDROM manually:
# mount
-F hsfs -r ro /dev/dsk/cxtyd0sz /cdrom/cdrom0
where x is the CD-ROM drive controller number, y is the CD-ROM drive
SCSI ID number, and z is the slice of the partition on which the CD-ROM is
located.
You have now mounted the CD-ROM drive. Refer to Installing and Setting
Up CD One on Solaris for procedures on installation.
|
4755165
|
On Microsoft Windows, Installer functionality
is affected if administrator user credentials are supplied only when running
setup.exe.
This issue affects all installations on Microsoft Windows platforms.
If a user is logged in without administrator privileges, he/she will be prompted
to enter administrator user credentials while attempting to run setup.exe. If the correct credentials are entered, the installer checks for
user privileges will be satisfied and installation will proceed. However,
some installer functionality will be affected:
Solution
Log in as user with administrator privileges when performing installation.
|
4757687
|
On Solaris, incremental installation of the Sun Java System Application Server component
on the system with previously installed Administration Client component might
result in an unusable installation.
This issue affects Solaris package-based installation on a Solaris platform.
If user tries to install the Sun Java System Application Server component on the system
where a standalone Administration Client component has already been installed,
and selects a different installation directory from the one originally used
for Administration Client installation, the resulting Sun Java System Application Server installation
will be unusable even though the installation outcome is reported as successful.
This is because the Administration Client Solaris packages will be detected
as already installed on the system, and they will not be installed as the
part of the Sun Java System Application Server installation. As a result, files critical
for product functionality will be missing.
Solution
Uninstall the standalone Administration Client before attempting to
install the Sun Java System Application Server on the same Solaris system.
Alternatively, an incremental installation can be attempted, but the
same installation directory that has been used for the Administration Client
installation should be used for the subsequent Sun Java System Application Server installation.
|
4762118
|
On Solaris, installation fails if a selected
custom configuration directory is a subdirectory of the selected installation
directory and is called ’etc’.
This issue affects Solaris package-based installation on a Solaris platform.
If the following combination of custom directory locations has been selected,
installation fail due to inconsistent group ownership information for the
same directory:
The pkgadd log file in the /var/sadm/install/logs directory will contain following error message:
pkgadd: ERROR: duplicate pathname /install_dir/etcpkgadd: ERROR: unable to process pkgmap
Solution
Select a custom configuration directory other than install_dir/etc.
|
4724612
|
On Solaris SPARC and Linux, PointBase shell
scripts fail if run by someone other than the installing user.
This issue affects only the evaluation installation. All PointBase shell
scripts are set to execute permission only for the installing user.
Solution
If users other than the person who installed the product need to execute
these scripts, change the permissions to 0755.
|
4762694
|
On Solaris, the Sun Java System Message Queue package
SUNWiqsup is not removed during Message Queue upgrade process.
This is only an issue on Solaris. The Sun Java System Application Server 7 installation
process involves installing Sun Java System Message Queue version 3.0.1. On Solaris,
if Sun Java System Message Queue version 3.0 is detected, it is first uninstalled (after
user confirmation) and the 3.0.1 version is installed.
There is a minor cleanup issue where the Solaris installer does not
remove one of the Solaris packages (SUNWiqsup) for Sun Java System Message
Queue 3.0 as part of this upgrade process. The presence of this package is
harmless and does not affect Sun Java System Message Queue or Sun Java System Application Server 7.
Solution
Manually remove the SUNWiqsup package using the following
command (as root):
# pkgrm SUNWiqsup
|
4890289
|
On Window 2000 Pro, the uninstaller is not able
to find the JDK to run uninstallation.
On Windows 2000 Pro, uninstallation fails with the following message:
The uninstaller could not locate a suitable j2sdk to run the
uninstalltion program. Run the uninstalltion again with the -javahome option
set to the directory in which j2sdk 1.4.0_02 or greater is installed. Press
Enter to exit.
Solution
Use the -javahome JDK location.
|
5017630
|
When upgrading on Windows, an error is displayed
and the upgrade fails if SNMP is running.
Solution
Stop the SNMP Service before upgrading:
-
From the Control Panel, choose Administrative Tools.
-
Choose Services.
-
Scroll down to the SNMP Service and stop it.
|
5018162
|
On Linux, two Message Queue packages are installed
if you are doing a full installation and if a qualified Message Queue is already
installed.
Solution
Due to a bug in the Linux rpm utility in 4.2.1.xx,
the installed Sun Java System Message Queue (identified as imq) rpm is not recognized. Because of this problem, the Sun Java System Application
Server installer will install a second version of the Sun Java System Message Queue rpm. To work around this, either install the 4.2.0.69 version of rpm on your system or uninstall Message Queue before installing
the application server.
Typically 4.2.1.xx version of rpm is present in Red
Hat Enterprise Linux Advanced Server 3.0 unless the rpm package
was upgraded on prior versions of the Linux system.
|
5034338
|
On Linux, upgraded packages are not removed
by the uninstaller.
Solution
Remove the packages manually by typing:
rpm -e --nodeps SUNWas* packages
|
5050621
|
On Linux and Solaris platforms, if Sun Java System Application
Server 7 Update 3 was installed as a part of Sun Java Enterprise 2004Q2, and
you then upgrade the Sun Java System Application Server, a problem appears. The subsequent
attempt to create a new server instance and to install Sun Java System Identity
Server 2004Q2 with SSL enabled Directory Server will fail and the newly created
server instance will crash with a SIGSEGV error upon restart.
Solution
For the instance of the application server created after upgrading Sun Java System Application
Server, edit the server instance’s server.xml file
and enter the correct location for the jss3.jar in server-classpath as follows:
For the Linux platform:
Change the following lines:
<java-config java-home="/usr/jdk/entsys-j2se"
server-classpath="/usr/share/lib/mps/secv1/jss3.jar <---
To:
<java-config java-home="/usr/jdk/entsys-j2se"
server-classpath="//opt/sun/private/share/lib/jss3.jar <----
To prevent this problem from occurring in future, modify the following
template files as well:
${APPSERVER_INSTALL_DIR}/lib/install/template/server.xml.template.admin
${APPSERVER_INSTALL_DIR}/lib/install/template/server.xml.template
In these template files, change the lines:
<java-config java-home="%%%JAVA_HOME%%%"
server-classpath="/usr/share/lib/mps/secv1/jss3.jar
To:
<java-config java-home="%%%JAVA_HOME%%%"
server-classpath="/opt/sun/private/share/lib/jss3.jar
|
5050621(Continued)
|
For the Solaris platform:
Modify the server.xml file:
-
Open the server.xml file for editing. The
file is found at: app_server_instance_dir/config/server.xml.
-
Add the location of the jss3.jar in server-classpath: server-classpath =/usr/share/lib/mps/secv1/jss3.jar
Edit the startserv script’s LD_LIBRARY_PATH:
-
Open the startserv script for editing.
The script is found at app_server_instance_dir/bin/startserv.
-
Add /usr/lib/mps/secv1 to the LD_LIBRARY_PATH.
To prevent this problem from occurring in future, modify the following
template files as well:
-
install_dir/lib/install/template/server.xml.template.admin
-
install_dir/lib/install/template/server.xml.template
-
install_dir/lib/install/template/start
In these template files, change the lines:
<java-config java-home="%%%JAVA_HOME%%%"server-classpath="/usr/lib/mps/secv1/jss3.jar
To:
<java-config java-home="%%%JAVA_HOME%%%"server-classpath="/usr/lib/mps/secv1/jss3.jar
|
N/A
|
Installing Sun Java System Application Server on Windows
may give the following message:
“Error writing native components to disk.
Aborting wizard”
Solution
-
If you have a file named C:\Documents,
it interferes when processing the system property user.home (typically
points to C:\Documents and Settings\your_name).
Remove or rename C:\Documents.
-
Additionally, the environment variable TEMP must
be set and must point to an existing writable directory.
|
5063872
|
The app_server_install/samples/common.properties file is overwritten with null values when
you upgrade Sun Java System Application Server 7 using the upgrade installer.
Solution
Back up the common.properties file before you upgrade
to the latest Sun Java System Application Server 7, or add the values to common.properties manually after upgrading.
Sample common.properties file for the Microsoft Windows
platform:
com.sun.aas.javaRoot=C\:/Sun/AppServer7/jdkadmin.host=<machinename>admin.port=4848com.sun.aas.imqLib=C\:/Sun/AppServer7/imq/libcom.sun.aas.installRoot=C\:/Sun/AppServer7admin.user=admin#admin
password will not be saved as default. User can enter it and save it manually.#admin.password=sunone.instance=server1com.sun.aas.webServicesLib=C\:/Sun/AppServer7/share/libcom.sun.aas.pointbaseRoot=C\:/Sun/AppServer7/pointbasesunone.instance.port=<port>sunone.instance=server1admin.user=adminadmin.port=4848
Sample common.properties file for the Linux platform:
com.sun.aas.pointbaseRoot=/export/appserver7ur5/pointbasecom.sun.aas.webServicesLib=/export/appserver7ur5/share/libcom.sun.aas.imqLib=/opt/imq/libcom.sun.aas.installRoot=/export/appserver7ur5com.sun.aas.javaRoot=/usr/java/j2sdk1.4.2_04#admin
password will not be saved as default. User can enter it and save it manually.#admin.password=admin.host=<machinename>sunone.instance=server1sunone.instance.port=80admin.user=adminadmin.port=4848
|
5063872(Continued)
|
Sample common.properties file for the Solaris platform:
com.sun.aas.pointbaseRoot=/opt/SUNWappserver7/pointbasecom.sun.aas.webServicesLib=/usr/share/libcom.sun.aas.imqLib=/usr/share/lib/imqcom.sun.aas.installRoot=/opt/SUNWappserver7com.sun.aas.javaRoot=/usr/j2se#admin
password will not be saved as default. User can enter it and save it manually.#admin.password=admin.host=<machinename>sunone.instance=server1sunone.instance.port=81admin.user=adminadmin.port=4848
|
6172916
|
Sun Java System Application Server fails to start after
you use the upgrade installer to upgrade the Sun Java System Application Server.
On the Solaris platform, the following error appears:
SEVERE (14394): JMS5024: JMS service startup failed. CORE5071:
An error occured during initialization
On the Linux platform, the following error appears:
cp: cannot stat \Q/etc/opt/imq/passwd’: No such file
or directorycp: cannot stat \Q/etc/opt/imq/accesscontrol.properties’:
No such file or directoryError backing up!
This problem appears because the upgrade installer does not check which
version of Message Queue is installed. It automatically installs Sun Java System Message
Queue 3.0.1 SP3, which is shipped with Sun Java System Application Server 7.
If Sun Java System Message Queue 3.5 is installed on the machine, the
upgrade installer downgrades it to Message Queue 3.0.1SP3.
On the Microsoft Windows platform, the problem only occurs if Sun Java
System Message Queue 3.5 is installed in the same directory in which the Sun Java System Application
Server installer installs. No error appears.
Solution
If you have not yet run the upgrade installer:
-
After downloading the product and untarring the binaries,
go to the untarred_location/sun-appserver7/upgrade directory.
-
Open the package-list file and remove all
the package names associated with Message Queue:
-
On the Microsoft Windows platform: imq.zip
-
On the Solaris Sparc and x86 platforms: SUNWiqdoc, SUNWiqfs, SUNWiqjx, SUNWiqr, SUNWiqu, SUNWiquc, SUNWiqum,
and SUNWiqlpl
-
On the Linux platform: imq.
If you already upgraded using upgrade installer:
For package-based installations on the Solaris Sparc and x86 platforms:
-
At the command prompt, remove the Message Queue instances
by typing rm -rf /var/imq/instances.
-
Use pkgrm to remove the following packages:
SUNWiqdoc, SUNWiqfs, SUNWiqjx, SUNWiqr, SUNWiqu, SUNWiquc, SUNWiqum, and SUNWiqlpl
-
Use pkgadd to reinstall the correct versions
of the packages you removed in the previous step.
|
6172916(Continued)
|
For Linux RPM installations:
-
Remove the Message Queue instance by typing rm -rf
/var/imq/instances.
-
Remove the Message Queue installation by typing rpm
-e imq.
-
Install the correct version of Message Queue by typing rpm
-i rpm_location/imq-xxx.rpm where xxx is
the correct version of Message Queue.
For Microsoft Windows installations, and for zip, tar, and evaluation
installations on all platforms:
-
Remove the Message Queue installation by typing rmdir app_server_install_dir/imq.
-
Unzip the correct version of Message Queue from its downloaded
location and run the installer.
|
6211610
|
For Solaris SPARC and x86 platforms, when upgrading
from Sun Java System System Application Server Platform Edition 7 Solaris 9 OS Update
3 and above (the Application Server component in the Solaris 9 Operating System),
information about existing domains is lost during the upgrade.
Solution
Before upgrading, back up the file /etc/appserver/domains.bin.
Once you complete the upgrade, restore the backed-up copy of the file.
|
6283084
|
The text in the Application Server 7.0, Update
7, Software License Agreement shows Update 6 instead of Update 7.
|