6602615 

After upgrading from localized version of Application Server 7.1 Update 5 to Application Server 7.1 Update 7, the upgraded instance fails to start on Soalris 10 Update 3 and above. 

There is a conflict between the Message Queue (MQ) versions bundled with Solaris and the version bundled with Application Server. 

Solution:

1. Remove the following MQ packages using the pkgrm command:

   • Base packages: SUNWiqdoc, SUNWiqfs, SUNWiqjx, SUNWiqr, SUNWiqu, SUNWiquc, SUNWiqum, and SUNWiqlpl

   • ja packages: SUNWjiqu, SUNWjiquc

   • zh packages: SUNWciqu, SUNWciquc

2. Install the corresponding OS-bundled base, ja, and zh packages.

6606419 

Upgrade from localized version of Application Server 7.1 Update 5 to Application Server 7.1 Update 7 fails. 

The installer fails to delete the directory, SUNWhadb/4.

Solution:

Do one of the following: 

• Delete SUNWhadb/4 before running ./setup.

• Run the ./setup command for the second time, if you have already run the ./setup command once and experienced a failed upgrade.

6606417 

Upgrade from localized version of Application Server Enterprise Edition 7.1 Update 5 to Application Server Enterprise Edition 7.1 Update 7 does not change the SUNWhadb/4 symbolic links.

Solution: 

Changed the symbolic link to 4.4.2-30. 

6606979 

Upgrade to localized version of Application Server Enterprise Edition 7.1 Update 7 displays English index.html 

Solution: 

Perform the following steps: 

1. Change directory to <AppServer_install_dir>/domains/domain1/server1/docroot.

2. Rename index.html to index.html_en.

3. Copy AppServer_install_dir/lib/install/templates/index.html to AppServer_install_dir/domains/domain1/server1/docroot.

6245916

When upgrading from localized Application Server 7.1 Update 2 to Update 3/Update 4/Update 7 in Japanese and Simplified Chinese locales, the localized welcome page and index.html is displayed from Update 2.

The localized version of Application Server 7.1 Update 7 contain localized files from Application Server 7.1 Update 2. 

Solution

After upgrading to Update 7, refer to the English welcome page and index page located at:

Appserver_Install_Dir/docs/about.html

Appserver_Install_Dirlib/install/templates/index.html

To register Sun Java System Application Server, use the following URLS: 

Japanese: https://www.sun.com/software/product_registration?locale=ja_JP

Simplified Chinese: https://www.sun.com/software/product_registration?locale=zh_CN

To view the latest index.html (in English) for an existing domain, instead of the old localized version, copy the index.html to the docroot folder:

copy Appserver_Install_Dir/lib/install/templates/index.html to

Appserver_domain_root/domains/domain1/admin-server/docroot

Before creating a new domain, replace the localized index.html with the English index.html:

Copy Appserver_Install_Dir/lib/install/templates/index.html to

Appserver_Install_Dir/lib/install/templates/{ja,zh_CN}/index.html

Ensure that you back up your current Japanese or Chinese index.html file. 

6222700

When upgrading from localized Application Server 7.1 Update 2 to Update 3/Update 4/Update 7 in Japanese and Simplified Chinese locales, the default page of server1 instance is displayed in English.

6245424

After uninstalling localized versions of Application Server Update 7, the localized packages/RPMs will remain.

Solution

Remove the localized packages/RPMs first and then run the uninstall program. Perform the following procedure on package-based Solaris installations. 

1. Remove the following packages:

   pkgrm SUNWjaspx SUNWjasdmo SUNWjiquc SUNWjiqu SUNWjaso

   pkgrm SUNWjjmail SUNWjjaf SUNWjasaco SUNWjascmo SUNWjaspx

   pkgrm SUNWcaspx SUNWcasdmo SUNWciquc SUNWciqu SUNWcaso

   pkgrm SUNWcjmail SUNWcjaf SUNWcasaco SUNWcascmo SUNWcaspx

2. Run the Application Server uninstall program.

3. Remove the Application Server installation directory.

   rm -rf Appserver_Install_Dir

   Perform the following procedure on RPM-based Linux installations.

4. Remove the following RPMs:

   rpm -e SUNWjasaco-7.1.0-02.src.rpm

   rpm -e SUNWjascmo-7.1.0-02.src.rpm

   rpm -e SUNWjasdmo-7.1.0-02.src.rpm

   rpm -e SUNWjaso-7.1.0-02.src.rpm

   rpm -e SUNWjaspx-7.1.0-02.src.rpm

   rpm -e SUNWjjaf-7.1.0-02.src.rpm

   rpm -e SUNWjjmail-7.1.0-02.src.rpm

   rpm -e SUNWasaco-zh_CN-7.1.0-02.src.rpm

   rpm -e SUNWascmo-zh_CN-7.1.0-02.src.rpm

   rpm -e SUNWasdmo-zh_CN-7.1.0-02.src.rpm

   rpm -e SUNWaso-zh_CN-7.1.0-02.src.rpm

   rpm -e SUNWaspx-zh_CN-7.1.0-02.src.rpm

   rpm -e SUNWjaf-zh_CN-7.1.0-02.src.rpm

   rpm -e SUNWjmail-zh_CN-7.1.0-02.src.rpm

5. Run the Application Server uninstall program.

6. Remove the Application Server installation directory.

   rm -rf Appserver_Install_Dir

   Perform the following procedure on Windows installations:

7. Run the Application Server uninstall program.

8. Delete Appserver_Install_Dir.

6208875

Upgrade installation Failed:java.io.FileNotFoundException

File-based upgrade of HADB on Solaris SPARC, Solaris x86, and Linux will encounter problems in certain scenarios, as described here: 

Installation fails with the following exception: 

java.io.FileNotFoundException: /sun/appserver7/./SUNWhadb/4 (Is a directory)

Upgrade scenarios: 7.1RTM/7.1ER1/7.1UR1 file-based upgrade to 7.1UR2. 

Solution

Rename the file-based-installing-directory/SUNWhadb/4 softlink to another name, such as, SUNWhadb/3. Restart the upgrade.

6217112

Incremental installation is not working on Windows platforms.

Sample applications can be installed along with Application Server. They cannot be incrementally installed. 

Solution

Select to install sample applications at the beginning of installation. During incremental installations, do not select the sample applications option. 

5006942

On Windows, the services created have the start type set by default to “Automatic” after an upgrade.

Solution

1. Open the Windows services.

2. Change the start type of the servers to “Manual.”

6217097

File-based upgrade performed as a non-root user seems to fail if the Application Server binaries for the upgrade were not downloaded as non-root user.

Solution

The downloaded binaries need to be owned by the non-root user. The downloaded archive must be unzipped by the user who will do the installation or upgrade. Otherwise this is known to lead to permissions issues while the JDK is being upgraded.