Lakshmi, Tim, Ovidiu,
I have isolated the variable that caused the problem. When I configured my
consumer with Spring the problem was duplicated. I noticed that there was a
difference between my test and the Spring configuration and that was the user
of our own configured QueueConnectionFactory. I then switched from using
Click's configured WMXQueueConnectionFactory:
<connection-factories>
<tx-connection-factory>
<jndi-name>WMXQueueConnectionFactory</jndi-name>
<use-java-context>false</use-java-context>
<xa-transaction/>
<rar-name>jms-ra.rar</rar-name>
<connection-definition>org.jboss.resource.adapter.jms.JmsConnectionFactory</connection-definition>
<config-property name="SessionDefaultType"
type="java.lang.String">javax.jms.Queue</config-property>
<blocking-timeout-millis>60000</blocking-timeout-millis>
<min-pool-size>5</min-pool-size>
<max-pool-size>45</max-pool-size>
<idle-timeout-minutes>5</idle-timeout-minutes>
</tx-connection-factory>
</connection-factories>
To using the generic Jboss "/XAConnectionFactory" and the problem went away.
This is very good news... however, I imagine that it would be important to
Jboss to understand why the problem occurs with the WMXConnectionFactory
configuration as to avoid others encountering the same problem.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3961711#3961711
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3961711
_______________________________________________
jboss-user mailing list
[email protected]
https://lists.jboss.org/mailman/listinfo/jboss-user
