6407877
|
Incorrect migration occurs while migrating
from Web Server 6.0 to 7.0 if the installed.pkg file is not found.
In Web Server 6.0 to 7.0 migration, if the installed.pkg file
is missing, Web Server incorrectly migrates the NSServlet entries
in the magnus.conf file.
|
6490124
|
6.x -> 7.0: Migrated scheduled events still
points to 6.x paths in the server.xml file.
|
6502529
|
6.1->7.0: Migration does not handle relative
path set for search-collection-dir correctly.
During instance migration, specifying a relative path for the target
path into which the search collections should be copied, results in the search
collection directory being created with respect to the config-store.
When the instance is instantiated, the indexes are created without properly
migrating the search collections.
|
6502769
|
6.x->7.0: Migration ignores any "document-root"
NameTrans specified in the obj.conf file.
|
6498806
|
On Windows, Web Server Admin Console does not
appropriately warn users during migration.
Administration Server does not detect if the selected new configuration
or the service name already exists on Windows and hence does not appropriately
warn the users to select a different configuration name or suggest a different
configuration name as default.
|
6500509
|
Web Server 7.0 migration tool is unable to successfully
migrate from Web Server 6.1 if it has Root Certs installed in it.
|
6559918
|
Unclear error message if CLI and Administration
Server versions are incompatible.
While upgrading Web Server 7.0 installation to Web Server 7.0 Update 2 , make sure that the
entire setup CLI, Administration Server and all the Administration Nodes are
also upgraded to Web Server 7.0 Update 2. This is because, Web Server 7.0 administration
interfaces will not work correctly with Web Server 7.0 Update 2 administration interfaces.
|
6595795
|
The Admin console does not add the required functions in the
obj.conf file for a migrated instance.
When a JVM disabled
Web Server 6.0 instance is migrated to Web Server 7.0 and when the migrated
instance is enabled with the JVM option using the Admin console, the process
does not add the following necessary lines in obj.conf file.
NameTrans fn="ntrans-j2ee" name="j2ee"
PathCheck fn="find-index-j2ee"
ObjectType fn="type-j2ee"
Error fn="error-j2ee"
|
6641844
|
On Windows, server fails to start after upgrading from Web Server
7 that is part of the Java ES 5 release to Web Server 7.0 Update 2 release
using the patch.
Workaround
On Windows, to upgrade the Web Server that is part of Java ES 5 or Java ES
5 Update 1 release to Web Server 7.0 Update 2 release, ensure the following
security patches are installed on the system.
-
125923-05 or later
-
NSS_NSPR_JSS 3.11.8
-
NSPR 4.6.8
-
NSS 3.11.8
-
JSS 4.2.5
|
6644314
|
Security
patch 121656-16 is a mandatory perquisite for Sun Java System Web Server 7.0
Update 2 Linux patch on Java ES 5/U1. However, the security patch exhibits
cyclic dependency, hence making it impossible to apply any of the patches.
Workaround
In order to avoid this scenario,
use the --force option. For example:
rpm -F --force <list
of rpms to be applied>
|
6640206
|
On non-windows
platforms (Solaris, Linux and HP-UX), if you have installed Web Server 7.0
or 7.0 update 1 without sample applications and if you upgrade to Web Server
7.0 update 2, you will see the following error message:
A
problem occurred during upgrade. To troubleshoot the problem, review the installation
log at: <install-dir>/setup/Sun_Java_System_Web_Server_install.log
Note –
This error does not impact the upgrade.
|