Errors connecting to WebSphere MQ and creating WebSphere MQ queue connection factory

If this problem does not resembles yours, or if the information provided does not solve your problem, see Troubleshooting WebSphere Messaging. If you are still unable to resolve the problem, contact IBM support for further assistance.

The following exception may occur when trying to create the MDBListener instance:

6/23/03 22:45:58:232 CDT] 673106a8 MsgListenerPo W WMSG0049E: 
Failed to start MDB PSSampleMDB against listener port SamplePubSubListenerPort  
[6/23/03 22:47:58:289 CDT] 673106a8 FreePool E J2CA0046E: 
Method createManagedConnctionWithMCWrapper caught an exception 
during creation of the ManagedConnection for resource 
JMS$SampleJMSQueueConnectionFactory, throwing ResourceAllocationException.  
Original exception:  javax.resource.spi.ResourceAdapterInternalException:
 createQueueConnection failed com.ibm.mq.MQException: MQJE001: An MQException occurred: 
Completion Code 2, Reason 2009  
MQJE003: IO error transmitting message buffer at 
com.ibm.mq.MQManagedConnectionJ11.(MQManagedConnectionJ11.java:239)

This problem occurs because the MQ manager userid does not have write access to the /tmp directory. To correct this problem, before you use a
Jacl procedure to configure WebSphere Application Server resources and install an application:

Ensure that all applications have write access to /tmp directory. Use the chmod 1777 command on the directory if necessary.
Create another subdirectory under /tmp (for example, /tmp/mydir). Use this directory as a "working directory" for the Jacl.
Restart the server.

Applications that use messaging on startup should start successfully.

Related reference

Troubleshooting testing and first time run problems

Searchable topic ID: rtrb_mqconnprobs