WebSphere MQ problems and workarounds - Middleware News
You might encounter these WebSphere MQ problems, and use these workarounds:
Problem: JMS message send errors occur with WebSphere global security enabled on AIX.
An issue has been identified with the Java Virtual Machine (JVM) bundled with WebSphere Application Server Version 5.1.1 for AIX systems that causes socket errors on the network connection used to secure access to embedded messaging queues. This can cause JMS message sends to fail with an error similar to the following error in the WebSphere logs:
MQJMS2008: failed to open MQ queue WQ_itim_wf
The following error will also be present in the WebSphere jmsserver logs:
MSGS0504E: An JMS Server security service thread experienced a socket exception:
java.net.SocketException: Socket closed
Workaround: It is recommended that all Tivoli Identity Manager applications running on AIX systems should install WebSphere APAR PK07924, which corrects the issue in the JVM. Apply this APAR after installing Fix Pack 1 for WebSphere Application Server Version 5.1, which also updates the WebSphere Application Server JVM. APAR PK07924 is available on the WebSphere Application Server support site:
http://www.ibm.com/software/webservers/appserv/was/support/
Problem: On a Windows system, during DSML feed activity with Tivoli Identity Manager account provisioning enabled, the WebSphere embedded messaging fails. Error messages describe failure to open a queue, a lack of permission to access a resource, or Java Message Service errors. You might see a WebSphere embedded messaging error similar to this message:
AMQ9181 The response set by the exit is not valid.
Workaround: On all cluster members, set the ephemeral port range to the maximum value of 65534. For more information on problems connecting to TCP/IP ports above 5000, refer to the following Web site:
http://support.microsoft.com/default.aspx?scid=kb;EN-US;196271
Problem: When you install Tivoli Identity Manager on Windows Server 2003, the WebSphere Embedded Messaging Publish and Subscribe service is not started. Attempting to start it manually causes an error and the following message:
Could not start the Websphere Embedded Messaging Publish and
Subscribe WAS__server1 service on Local Computer.
Error 1075: The dependency service does not exist or has been
marked for deletion
Workaround: Ignore the message and continue. Tivoli Identity Manager does not require the Websphere Embedded Messaging Publish and Subscribe service. Do not attempt to start the service.
Problem: An error occurs creating the queue manager. The error in the Amqerr*.log file is the following:
AMQ9213: A communications error for TCP/IP occurred.
EXPLANATION:
An unexpected error occurred in communications.
ACTION:
The return code from the TCP/IP (ioctlsocket) call was 10038 (X'2736'). Record
these values and tell the systems administrator.
Workaround:
The 10038 return code indicates that the WebSphere MQ listener pool has had trouble passing the initial socket from the listener to the pool. This is rather common in environments that have a firewall. To work around the problem, disable the pool with the following environment variable:
set MQNOREMPOOL=1
You might encounter these WebSphere MQ problems, and use these workarounds:
Problem: JMS message send errors occur with WebSphere global security enabled on AIX.
An issue has been identified with the Java Virtual Machine (JVM) bundled with WebSphere Application Server Version 5.1.1 for AIX systems that causes socket errors on the network connection used to secure access to embedded messaging queues. This can cause JMS message sends to fail with an error similar to the following error in the WebSphere logs:
MQJMS2008: failed to open MQ queue WQ_itim_wf
The following error will also be present in the WebSphere jmsserver logs:
MSGS0504E: An JMS Server security service thread experienced a socket exception:
java.net.SocketException: Socket closed
Workaround: It is recommended that all Tivoli Identity Manager applications running on AIX systems should install WebSphere APAR PK07924, which corrects the issue in the JVM. Apply this APAR after installing Fix Pack 1 for WebSphere Application Server Version 5.1, which also updates the WebSphere Application Server JVM. APAR PK07924 is available on the WebSphere Application Server support site:
http://www.ibm.com/software/webservers/appserv/was/support/
Problem: On a Windows system, during DSML feed activity with Tivoli Identity Manager account provisioning enabled, the WebSphere embedded messaging fails. Error messages describe failure to open a queue, a lack of permission to access a resource, or Java Message Service errors. You might see a WebSphere embedded messaging error similar to this message:
AMQ9181 The response set by the exit is not valid.
Workaround: On all cluster members, set the ephemeral port range to the maximum value of 65534. For more information on problems connecting to TCP/IP ports above 5000, refer to the following Web site:
http://support.microsoft.com/default.aspx?scid=kb;EN-US;196271
Problem: When you install Tivoli Identity Manager on Windows Server 2003, the WebSphere Embedded Messaging Publish and Subscribe service is not started. Attempting to start it manually causes an error and the following message:
Could not start the Websphere Embedded Messaging Publish and
Subscribe WAS__server1 service on Local Computer.
Error 1075: The dependency service does not exist or has been
marked for deletion
Workaround: Ignore the message and continue. Tivoli Identity Manager does not require the Websphere Embedded Messaging Publish and Subscribe service. Do not attempt to start the service.
Problem: An error occurs creating the queue manager. The error in the Amqerr*.log file is the following:
AMQ9213: A communications error for TCP/IP occurred.
EXPLANATION:
An unexpected error occurred in communications.
ACTION:
The return code from the TCP/IP (ioctlsocket) call was 10038 (X'2736'). Record
these values and tell the systems administrator.
Workaround:
The 10038 return code indicates that the WebSphere MQ listener pool has had trouble passing the initial socket from the listener to the pool. This is rather common in environments that have a firewall. To work around the problem, disable the pool with the following environment variable:
set MQNOREMPOOL=1
Comments
Post a Comment