Specifying write access to the temporary directory to support message-driven bean deployment on listener ports
When deploying a message-driven bean (MDB) against a listener port, you might receive an exception error if the application server's user ID does not have write access to the operating system's temporary directory.
About this task
![[AIX Solaris HP-UX Linux Windows]](../images/dist.gif)
For more information about how to configure activation specifications for non-ASF mode, see Configuring activation specifications for non-ASF mode. However, you should not begin this migration until you are sure the application does not have to work on application servers earlier than WebSphere Application Server Version 7. For example, if you have an application server cluster with some members at Version 6.1 and some at a later version, you should not migrate applications on that cluster to use activation specifications until after you migrate all the application servers in the cluster to the later version. In
order to deploy an MDB against a listener port you must make sure
that your application server has write access to the temporary directory
on your system. The following exception can occur if your 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 your 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.
作業主題