WebSphere Application Server APAR # PQ41324

  Defect # 86280
   
  WebSphere Release: 3.0.2.2

 Description:
  (Naming exception) Cannot connect administration console after
  applying fix pack 2 to V3.02.  Additional symptoms are that if
  security is enabled, that the administrative server will not start.
  This problem affects installations in which the node name is set
  to upper case.

  The administrative server's node name defaults to the server system's host name.
  This name gets set in the administrative repository the first time
  the administrative server is initialized.  A change was introduced in v3.02.2
  so that the default node name is folded to lower case to ease case
  dependencies when connecting from remote Administration clients.
  However, this change created a problem for existing configurations
  on systems on which the host name is typically stored as upper case
  (example: AS/400).  Prior to V3.02.2, the name would have been stored
  in the case returned by the operating system.  If the node name was 
  stored in upper case, then after applying fix pack 2 (v3.02.2), any
  attempt to connect from a remote administration console will fail because
  the case will never match when a search for the node home is made.
  
  This same problem will prevent the administration server from starting
  if security is enabled.

  One harmless side affect of this problem is that if the adminserver is
  able to start, an additional node (lower case name) will be created.
  Once the fix is applied, this entry is otherwise ignored.  It can be
  safely deleted.
  
How to apply:
- create a directory to store the jar file (e.g. c:\WebSphere\AppServer\efix)
- copy pq41324.jar to the directory
- add the directory/jar file to the beginning of the admin server's classpath
  in admin.config:
com.ibm.ejs.sm.adminserver.classpath=C:/WebSphere/AppServer/efix/pq41324.jar...
- Stop the Admin Server
- restart the admin server
- This fix also needs to be on the classpath for the administration
client.  Add the directory/jar file to the beginning of the
adminclient bat/shell script file.  Take care when editing the
script that you preserve how the classpath settings are appended.
- For remote administration clients, you will need to copy the pq41324
jar to the remote systems and then perform the same changes on
the adminclient bat/shell script file.

Note:
- You do not need to re-initialize your WebSphere Application Server
configuration to use this patch.