When Broker Restarts None of the Temporary Queues Are Created

Question

Somehow when the broker restarts none of the temporary queues are getting recreated. The queues were created successfully the 1st time and the applications were happily exchanging messages. Things just fall apart when the broker restarts.
I'm able to reproduce this problem consistently by doing the following:
1. Start imqbrokerd (mq start)
2. Start client application
3. Shutdown imbrokerd (mq stop)
4. Start imqbrokerd (mq start)
After the producers in the client application have reconnected the following messages are displayed in the console. I'm only able to get the client app to work again is if I restart the client apps.
[02/Mar/2009:23:01:01 CST] attempting to set Message Bytes Limit to 10485760K for destination temporary_destination://queue/192.168.20.14/49823/1 [Queue]
[02/Mar/2009:23:01:01 CST] attempting to set Message Size Limit to 10240K for destination temporary_destination://queue/192.168.20.14/49823/1 [Queue]
[02/Mar/2009:23:01:01 CST] [B1065]: Accepting: [email protected]:57123->jms:37646. Count: service=9 broker=9
[02/Mar/2009:23:01:01 CST] [B2083]: Unable to create destination temporary_destination://queue/192.168.20.14/49823/1 [Queue], autocreation is forbidden
Do you guys have any idea on what's going on? Does anybody know of an existing workaround?
Environment:
- OpenMQ 4.3
- CentOS 5.2
- Sun JDK 1.6_05
- Spring 2.5.5
- Camel 1.3.0
I also looked at the code and found only one location where the error message is used. I still need to figure our how I can get the conditional expression to evaluate to false.
share/java/com/sun/messaging/jmq/jmsserver/core/Destination.java
1395 if (!DestType.isAdmin(type) && !canAutoCreate(DestType.isQueue(type),type) && !BrokerMonitor.isInternal(destination)) {
1396 throw new BrokerException(
1397 Globals.getBrokerResources().getKString(
1398 BrokerResources.W_DST_NO_AUTOCREATE,
1399 getName()),
1400 BrokerResources.W_DST_NO_AUTOCREATE,
1401 (Throwable) null,
1402 Status.FORBIDDEN);
-bash-3.2$ /tmp/openmq-4.3/mq/bin/imqcmd query bkr -t q -n MYQUEUE -u admin
Password: admin
Querying the broker specified by:
Host Primary Port
localhost 7676
Version 4.3
Instance Name imqbroker
Broker ID
Primary Port 7676
Broker is Embedded false
Instance Configuration/Data Root Directory /tmp/openmq-4.3-data/var/mq
Current Number of Messages in System 202
Current Total Message Bytes in System 317483
Current Number of Messages in Dead Message Queue 201
Current Total Message Bytes in Dead Message Queue 316444
Log Dead Messages true
Truncate Message Body in Dead Message Queue false
Max Number of Messages in System unlimited (-1)
Max Total Message Bytes in System unlimited (-1)
Max Message Size 70m
Auto Create Queues true
Auto Create Topics true
Auto Created Queue Max Number of Active Consumers unlimited (-1)
Auto Created Queue Max Number of Backup Consumers 0
Cluster ID
Cluster is Highly Available false
Cluster Broker List (active) mq://192.168.1.123:7676/
Cluster Broker List (configured)
Cluster Master Broker
Cluster URL
Log Level DEBUG
Log Rollover Interval (seconds) 604800
Log Rollover Size (bytes) 268435456
Successfully queried the broker.
I also tried versions 4.4 and 4.2 and received the same behavior :(

Answer 1

The application is inside an app server but we're not using a resource adapter as we're using Spring and Camel to hide the JMS details. Spring (JMSComponent) manages the connection directly. (We current don't have any JMS connection pooling as well.)
<bean id="jmsTransactionManager" class="org.springframework.jms.connection.JmsTransactionManager">
<property name="connectionFactory" ref="jmsConnectionFactory" />
</bean>
<bean id="jmsConnectionFactory" class="com.norvax.framework.jms.OpenMQConnectionFactory">
<property name="openmqBrokerConfiguration">
<props>
<prop key="imqBrokerHostName">$remoting{openmq.hostName}</prop>
<prop key="imqBrokerHostPort">$remoting{openmq.hostPort}</prop>
<prop key="imqReconnect">true</prop>
</props>
</property>
</bean>
<bean id="jms" class="org.apache.camel.component.jms.JmsComponent">
<property name="connectionFactory" ref="jmsConnectionFactory" />
</bean>
I'm going to write a very basic producer using Spring without using Camel and see if I'll get the same behavior. I'd like to see if the way Camel uses JMS is what's making OpenMQ broker to deny creation of temporary queues.
Thanks,
Jeff