PI09925: PORT CONFLICT MESSAGE IS NOT GENERATED ON LIBERTY PROFILE COLLECTIVE CONTROLLER

Fixes are available

APAR status

Closed as program error.

Error description

The default replicaPort for initial controller is 10010. If
the port was listened on by another process (outside
WebSphere Application Server), a port conflict message was not
generated into messages.log.

Local fix

Changing the default replicaPort by adding the entry into
server.xml.

Example:
server.xml
---------------
    <collectiveController replicaPort="20010"
                          isInitialReplicaSet="true" />
---------------

By adding the entry above, initial controller listens port
20010.

Problem summary

****************************************************************
* USERS AFFECTED:  All users of IBM WebSphere Application      *
*                  Server Liberty Profile V8.5.5 collective    *
*                  controller.                                 *
****************************************************************
* PROBLEM DESCRIPTION: A port conflict is not detected on      *
*                      the listening port or logged which      *
*                      may prevent the controller from         *
*                      working properly.                       *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
A port conflict is not detected on the listening port
"replicaPort" of a controller and the condition is not logged.
The failure to detect the conflict may prevent the controller
from working properly as other controllers are not able to
contact it on that port.
With event level tracing enabled on the other controllers in
the same replica set with the problem controller, it will be
logged that the problem controller cannot be reached (for
example, 10010 in the below trace messages):
[13/11/09 19:42:23:255 CST] 0000002c Communication >
tcpFailed Entry
TCP to host=127.0.0.1
port=10010
java.nio.channels.SocketChannel[connected
local=/127.0.0.1:55983
remote=/127.0.0.1:10010]
false
notified by DSF
[13/11/09 19:42:23:255 JST] 0000002c Communication 3
nodeFailed : The
127.0.0.1:10010 node has not been in the live nodes list

Problem conclusion

The controller was modified to detect the duplicated listener
port condition and to write this message when it occurs:

CWWKX6027E: The collective controller initialization did not
succeed. The socket bind did not succeed for host * and port
<the port value here>. The port might already be in use or the
host does not match the system configuration.


The fix for this APAR is currently targeted for inclusion in
fix pack 8.5.5.2. Please refer to the Recommended Updates page
for delivery information:
http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980

Temporary fix

Change the replicaPort value to a port that is not in use on
the problem system.  If the replicaPort is not explicitly set
in the server.xml, then this line must be added:

<collectiveController replicaPort="<the new port number>" />

Comments

APAR Information

APAR number
PI09925
Reported component name
LIBERTY PROFILE
Reported component ID
5724J0814
Reported release
850
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2014-01-20
Closed date
2014-01-22
Last modified date
2014-01-22

APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:

Fix information

Fixed component name
LIBERTY PROFILE
Fixed component ID
5724J0814

Applicable component levels

R850 PSY
UP

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"850","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
28 April 2022

Tips

PI09925: PORT CONFLICT MESSAGE IS NOT GENERATED ON LIBERTY PROFILE COLLECTIVE CONTROLLER

Fixes are available

Subscribe

APAR status

Closed as program error.

Error description

Local fix

Problem summary

Problem conclusion

Temporary fix

Comments

APAR Information

APAR number

Reported component name

Reported component ID

Reported release

Status

PE

HIPER

Special Attention

Submitted date

Closed date

Last modified date

APAR is sysrouted FROM one or more of the following:

APAR is sysrouted TO one or more of the following:

Fix information

Fixed component name

Fixed component ID

Applicable component levels

R850 PSY

Document Information

Share your feedback

Need support?