Network Deployment (Distributed operating systems), v8.0 > Troubleshoot and support > Troubleshoot Messaging resources > Troubleshoot messaging
Specify write access to the temporary directory to support message-driven bean deployment on listener ports
We can receive an exception error deploy a message-driven bean (MDB) against a listener port, because the application servers's user ID does not have write access to the operating system's temporary directory. For WAS v7 and later, listener ports are stabilized. For more information, read the article on stabilized features. You should plan to migrate your WebSphere MQ message-driven bean deployment configurations from using listener ports to using activation specifications. However, you should not begin this migration until you are sure the application does not have to work on application servers earlier than WAS v7. For example, if we have an application server cluster with some members at v6.1 and some at v7, you should not migrate applications on that cluster to use activation specifications until after you migrate all the application servers in the cluster to v7.
In order to deploy an MDB against a listener port make sure that your application server has write access to the temporary directory on the system. The following exception can occur if the application server does not have this permission:
[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 createManagedConnectionWithMCWrapper 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)If you see this exception error, you can give the application sever write access to the temporary directory by completing the following steps.
Procedure
- Ensure that all application servers have write access to the temp directory. Use the chmod 1777 command on the directory if necessary.
- Create another subdirectory under the temp directory. For example, on UNIX systems create /tmp/mydir, and on Windows systems create\Temp\mydir. Use this directory as a "working directory" for the Jacl script.
- Stop and restart the server.
Troubleshoot message-driven beans
Troubleshoot messaging
Related
Messaging troubleshooting tips
Application deployment troubleshooting tips