PQ68217: WHEN SPECIFYING PORT PROPERTIES IN THE SYSTEM PROPERTIES TABLE, THE PROPERTIES DO NOT GET PROPAGATED TO THE CLONES

 A fix is available

4.0.5: WebSphere Application Server Version 4.0 Fix Pack 5 (Version 4.0.5)



APAR status
Closed as program error.

Error description
When specifying com.ibm.CORBA.ListenerPort and
com.ibm.CORBA.SSLPort properties in the System Properties
table (under JVM Settings) for a ServerGroup, the properties
do not get propagated to the clones (and subsequently are not
run).
If I specify these same properties in the same place on the
clone itself, likewise it does not take.
If I specify them in the Advanced JVM Settings command line
listens on the specified ports.
In all three cases above, the property shows as being set on
the "Generated Command Line Arguments" box.  Thus, the defect:
Either I should not be able to specify these parameters in the
"System Properties" table (and thus it should not show up on
the generated command line arguments) or (and preferred) it
should propogate and "take" when I specify it in the System
Properties table.
This was hit using WAS v4.03 with WebSphere security enabled
on HP-UX.
Local fix Problem summary
****************************************************************
* USERS AFFECTED: WebSphere Application Server users.          *
****************************************************************
* PROBLEM DESCRIPTION: Some properties, when set for the       *
*                      ServerGroup, do not proagate to         *
*                      the clones.                             *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
Certain properties, e.g., com.ibm.CORBA.ListenerPort and
com.ibm.CORBA.SSLPort, when set in the System Properties table
(under JVM Settings) for a ServerGroup, do not get propagated
to the clones (and subsequently are not run).
.
If these same properties in the same place on the clone
itself, likewise it does not take.
.
If they are specified in the Advanced JVM Settings command line
(under the ServerGroup), then they do propagate correctly to
the clones.
.
In all three cases above, the property shows as being set on
the "Generated Command Line Arguments" box.  Thus, the defect:
Either these parameters should not be allowed to be specified
in the "System Properties" table (and thus it should not show
up on the generated command line arguments) or (and preferred)
it should propogate and "take" when it is specified in the
System Properties table.
Problem conclusion
The reason for this is that the setORBProperties() method in
the ActiveEJBServerProcess class overwrites the user-
specified arguments with ORB default properties.  The ORB
default ListenerPort (according to the  trace) is 3000, so
when trying to start two clones on the same node, one works
but the other fails because the port number is already taken,
and the ports must be explicitly set in order for security
to work.
.
Fix for this was to check to ensure that if a user-specified
ORB property (such as com.ibm.CORBA.ListenerPort) exists, it
will not be overwritten.
Temporary fix
Andy McCright verified the code change on system where
problem is occurring.  This was sufficient since no other
customers are reporting that this is a problem.
Comments
APAR information
APAR number PQ68217
Reported component name WEBSPHERE AE AI
Reported component ID 5630A2200
Reported release 400
Status CLOSED PER
PE NoPE
HIPER NoHIPER
Submitted date 2002-11-13
Closed date 2003-01-05
Last modified date 2003-01-05

APAR is sysrouted FROM one or more of the following:

APAR is sysrouted TO one or more of the following:

Modules/Macros

SRLS

Fix information
Fixed component name WEBSPHERE AE AI
Fixed component ID 5630A2200

Applicable component levels
R400 PSY    UP


Document Information


Product categories: Software > Application Servers > Distributed Application & Web Servers > WebSphere Application Server > General
Operating system(s):
Software version: 400
Software edition:
Reference #: PQ68217
IBM Group: Software Group
Modified date: Jan 5, 2003