PQ79459: EVENT BROKER DOES NOT COME UP UNDER WMQXWEMP | |||||||||||||||||||||||||||||||||
![]() |
|||||||||||||||||||||||||||||||||
APAR status Closed as unreproducible in next release. Error description The Event Broker should start up under WMQXWEMP name. Instead, it takes the name of the app server in Base App environment (BBOS001) or JMS server in ND environment (BBOJ001). . When configuring IJP through customization dialog, one of the steps is to reserve port 5559, as shown in BBOTCPII member: . 5559 TCP WMQXWEMP ; JMS Server Direct Address port . If this is done, similar error could come up: +CSQX218E +WMQX CSQXLSTT Listener unable to bind to port 5559 address 0.0.0.0, TRPTYPE=TCP INDISP=QMGR, RC=0000006F . The following is another set of symptoms that may occur: When starting BBOJ001 and ABEND SA03 happens you can enable tracing with startupTraceSpecification="JMSServer=all=enabled" and then if you rerun BBOJOO1 you will see this: ExtendedMessage: MSGS0001E: Starting the JMS Server failed with exception: com.ibm.broker.ws.brokermanager.BrokerManagerException$Failed: Broker instance failure: Unprocessed request in control queue. Failed: Broker instance failure: Unprocessed request in control ALSO, in the SYSLOG you will see: +BIP7020S WMQX WebSpherePubSub 14 START UP FAILURE Failed during creati 5125|Tcp|5559|java.net.BindException of ClientConnectionBundle: -1039695125|Tcp|5559|java.net.BindExcept ion: EDC5111I Permission denied.| . INITIALIZATION OF THE PUBLICATION NODE FAILED. CHECK THE SYSTEM LOG FOR POSSIBLE ERRORS AND RESTART THE BROKER. When IJP is running and port 5559 is NOT reserved, netstat command shows BBOS001 listening on port 5559, not WMQXWEMP.Local fix Port 5559 should not be reserved until the name issue for Event Broker (WMQXWEMP) is resolved.Problem summary **************************************************************** * USERS AFFECTED: The Embedded Event Broker process name * * is not right. It should be composed of * * the short queue manager name and the * * "WEMP" termination. For ex. WMQXWEMP. * **************************************************************** * PROBLEM DESCRIPTION: The Embedded Event Broker process name * * is not right. It should be composed of * * the short queue manager name and the * * "WEMP" termination. For ex. WMQXWEMP. * **************************************************************** * RECOMMENDATION: * **************************************************************** The incorrect name is given to the JMS Embedded Event Broker process. The process takes the name of the Base Application Server, BBOS0011 or the name of the JMSServer, BBOJ0011 in an ND configuration. When configuring IJP through the customization dialog, one of the steps is to reserve port 5559, in the BBOTCPII member: 5559 TCP WMQXWEMP ; JMS Server Direct Address port Since the port is reserved for WMQXWEMP and not for BBOS0011 or BBOJ0011, starting the broker produces the following error: +CSQX218E +WMQX CSQXLSTT Listener unable to bind to port 5559 address 0.0.0.0, TRPTYPE=TCP INDISP=QMGR, RC=0000006FProblem conclusion Temporary fix Comments The problem is unrecreatable in next release. Customer agreed to UR1 closing.
APAR is sysrouted FROM one or more of the following: APAR is sysrouted TO one or more of the following: Modules/Macros Publications Referenced
|
Document Information |
Current web document: swg1PQ79459.html
Product categories: Software > Application Servers >
Distributed Application & Web Servers > WebSphere Application
Server for z/OS
Operating system(s):
Software version: 500
Software edition:
Reference #: PQ79459
IBM Group: Software Group
Modified date: Mar 3, 2004
(C) Copyright IBM Corporation 2000, 2009. All Rights Reserved.