APAR status
Closed as program error.
Error description
ON WSAS 5.0.2.7 (with
PQ83628 &
PQ88152 applied) and on WSAS
5.1.1.1 we see that ports 1507,5557,5558,5559 bind to zeroed out
IP address , leaving the port open for anyone to use.
Require Fix for WSAS 5.0.2.7 and WSAS 5.1.1.1
APAR
PQ96338 will address this issue for WSAS 5.1.1.1.
Local fix
NA
Problem summary
****************************************************************
* USERS AFFECTED: This problem affects customers who use the *
* Embedded Messaging Server provided with *
* WebSphere Application Server Version *
* 5.0.2.x. *
****************************************************************
* PROBLEM DESCRIPTION: The Embedded JMS Server that ships *
* with WebSphere Application Server *
* Version 5.0.2.x uses a number of *
* ports for all it's communication with *
* the outside world: *
* *
* 5557 - The JMS Server Security port *
* 5558 - The port used by the queue *
* manager to listen for incoming *
* requests *
* *
* These ports are all bound to the *
* TCP/IP address 0.0.0.0. This means *
* that customers with single or multiple *
* instances of WebSphere Application *
* Server in multiple Network card *
* scenarios would experience port *
* binding failures. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
The problem here was caused by the fact that the ports used
by the Embedded JMS Server were never being bound to specific
TCP/IP addresses.
Problem conclusion
The fix for this APAR is currently targeted for inclusion in
fixpack 5.0.2.10. Please refer to the Recommended Updates
page for delivery dates:
http://www-1.ibm.com/support/
docview.wss?rs=180&context=SSEQTP&uid=swg27004980
After this fixpack has been installed, you will need to
carry out the following steps in order to bind the ports used
by the JMS Server to specific TCP/IP addresses:
- When the application server has restarted, bring up the
WebSphere Administrative Console and login.
- Expand the Servers entry in the left hand tree view, and
click on the Application Servers link.
- The Application Servers panel will now appear, containing
a list of application servers. Click on the entry for the
appropriate application server.
- In the next panel, click on the Process Definition link
within the Additional Properties table.
- The Process Definition panel should now appear. Click on
the Java Virtual Machine link.
- In the Generic JVM arguments field, enter:
-Dcom.ibm.websphere.messaging.LocalHost=x.x.x.x
-Dcom.ibm.websphere.messaging.useMultiHome=false
-Dcom.ibm.websphere.messaging.ServerSocketQueueDepth=250
where x.x.x.x is the TCP/IP address that ports 5557 and
5558 will be bound to.
- Click OK, and save the configuration changes.
- Logoff the Administrative Console.
- Define the following system wide environment variable:
AMQ_WAS_HOSTNAME=<the hostname of machine with
TCP/IP address x.x.x.x>
- Restart the Application Server.
Temporary fix Comments
APAR information |
APAR number |
PQ96144 |
Reported component name |
WAS NETWRK DEPL |
Reported component ID |
5630A3601 |
Reported release |
00I |
Status |
CLOSED PER |
PE |
NoPE |
HIPER |
NoHIPER |
Special Attention |
NoSpecatt |
Submitted date |
2004-10-22 |
Closed date |
2005-02-01 |
Last modified date |
2005-02-01 |
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Modules/Macros
Publications Referenced
Applicable component levels |
R003 PSY |
UP |
R00A PSY |
UP |
R00H PSY |
UP |
R00I PSY |
UP |
R00P PSY |
UP |
R00S PSY |
UP |
R00W PSY |
UP |
R103 PSN |
UP |
R10A PSN |
UP |
R10H PSN |
UP |
R10I PSN |
UP |
R10P PSN |
UP |
R10S PSN |
UP |
R10W PSN |
UP |
|