[esb-issues] [JBoss JIRA] Created: (JBESB-2489) JMS bus with topic cannot be used in jms-jca-provider
Martin Vecera (JIRA)
jira-events at lists.jboss.org
Wed Mar 25 04:55:22 EDT 2009
JMS bus with topic cannot be used in jms-jca-provider
-----------------------------------------------------
Key: JBESB-2489
URL: https://jira.jboss.org/jira/browse/JBESB-2489
Project: JBoss ESB
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Rosetta
Affects Versions: 4.4 CP2
Reporter: Martin Vecera
JMS bus based on a topic cannot be used within jms-jca-provider. On deployment the following exception occurs:
009-03-25 09:46:45,904 WARN [org.jboss.resource.adapter.jms.inflow.JmsActivation] Failure in jms activation org.jboss.resource.adapter.jms.inflow.JmsActivationSpec at 3efbb1d8(ra=org.jboss.resource.adapter.jms.JmsResourceAdapter at 6333934d destination=queue/pt_qs_nojbm_notifier_topictest_gw isTopic=true tx=true durable=false reconnect=10 provider=java:/DefaultJMSProvider user=null maxMessages=1 minSession=1 maxSession=1 keepAlive=60000 useDLQ=true DLQHandler=org.jboss.resource.adapter.jms.inflow.dlq.GenericDLQHandler DLQJndiName=queue/DLQ DLQUser=null DLQMaxResent=5)
java.lang.ClassCastException: Object at 'queue/pt_qs_nojbm_notifier_topictest_gw' in context {java.naming.factory.initial=org.jnp.interfaces.NamingContextFactory, hostKey=localhost:1100, jnp.partitionName=DefaultPartition, jnp.discoveryTimeout=5000, jnp.discoveryGroup=230.0.0.4, jnp.disableDiscovery=false, java.naming.provider.url=localhost:1100, java.naming.factory.url.pkgs=org.jboss.naming:org.jnp.interfaces:org.jboss.naming:org.jnp.interfaces, jnp.maxRetries=1, jnp.discoveryPort=1102, jnp.discoveryTTL=16} is not an instance of [class=javax.jms.Topic classloader=org.jboss.mx.loading.UnifiedClassLoader3 at 6f9bb25a{ url=null ,addedOrder=2} interfaces={interface=javax.jms.Destination classloader=org.jboss.mx.loading.UnifiedClassLoader3 at 6f9bb25a{ url=null ,addedOrder=2}}] object class is [class=org.jboss.jms.destination.JBossQueue classloader=org.jboss.mx.loading.UnifiedClassLoader3 at 6f9bb25a{ url=null ,addedOrder=2} interfaces={interface=javax.jms.Queue classloader=org.jboss.mx.loading.UnifiedClassLoader3 at 6f9bb25a{ url=null ,addedOrder=2}}]
at org.jboss.util.naming.Util.checkObject(Util.java:329)
at org.jboss.util.naming.Util.lookup(Util.java:216)
at org.jboss.resource.adapter.jms.inflow.JmsActivation.setupDestination(JmsActivation.java:409)
at org.jboss.resource.adapter.jms.inflow.JmsActivation.setup(JmsActivation.java:316)
at org.jboss.resource.adapter.jms.inflow.JmsActivation$SetupActivation.run(JmsActivation.java:635)
at org.jboss.resource.work.WorkWrapper.execute(WorkWrapper.java:204)
at org.jboss.util.threadpool.BasicTaskWrapper.run(BasicTaskWrapper.java:275)
at EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(PooledExecutor.java:756)
at java.lang.Thread.run(Thread.java:595)
Then on usage:
2009-03-25 09:46:55,926 INFO [org.jboss.resource.adapter.jms.inflow.JmsActivation] Attempting to reconnect org.jboss.resource.adapter.jms.inflow.JmsActivationSpec at 3efbb1d8(ra=org.jboss.resource.adapter.jms.JmsResourceAdapter at 6333934d destination=queue/pt_qs_nojbm_notifier_topictest_gw isTopic=true tx=true durable=false reconnect=10 provider=java:/DefaultJMSProvider user=null maxMessages=1 minSession=1 maxSession=1 keepAlive=60000 useDLQ=true DLQHandler=org.jboss.resource.adapter.jms.inflow.dlq.GenericDLQHandler DLQJndiName=queue/DLQ DLQUser=null DLQMaxResent=5)
2009-03-25 09:46:55,931 ERROR [org.jboss.resource.adapter.jms.inflow.JmsActivation] Unable to reconnect org.jboss.resource.adapter.jms.inflow.JmsActivationSpec at 3efbb1d8(ra=org.jboss.resource.adapter.jms.JmsResourceAdapter at 6333934d destination=queue/pt_qs_nojbm_notifier_topictest_gw isTopic=true tx=true durable=false reconnect=10 provider=java:/DefaultJMSProvider user=null maxMessages=1 minSession=1 maxSession=1 keepAlive=60000 useDLQ=true DLQHandler=org.jboss.resource.adapter.jms.inflow.dlq.GenericDLQHandler DLQJndiName=queue/DLQ DLQUser=null DLQMaxResent=5)
java.lang.ClassCastException: Object at 'queue/pt_qs_nojbm_notifier_topictest_gw' in context {java.naming.factory.initial=org.jnp.interfaces.NamingContextFactory, hostKey=localhost:1100, jnp.partitionName=DefaultPartition, jnp.discoveryTimeout=5000, jnp.discoveryGroup=230.0.0.4, jnp.disableDiscovery=false, java.naming.provider.url=localhost:1100, java.naming.factory.url.pkgs=org.jboss.naming:org.jnp.interfaces:org.jboss.naming:org.jnp.interfaces, jnp.maxRetries=1, jnp.discoveryPort=1102, jnp.discoveryTTL=16} is not an instance of [class=javax.jms.Topic classloader=org.jboss.mx.loading.UnifiedClassLoader3 at 6f9bb25a{ url=null ,addedOrder=2} interfaces={interface=javax.jms.Destination classloader=org.jboss.mx.loading.UnifiedClassLoader3 at 6f9bb25a{ url=null ,addedOrder=2}}] object class is [class=org.jboss.jms.destination.JBossQueue classloader=org.jboss.mx.loading.UnifiedClassLoader3 at 6f9bb25a{ url=null ,addedOrder=2} interfaces={interface=javax.jms.Queue classloader=org.jboss.mx.loading.UnifiedClassLoader3 at 6f9bb25a{ url=null ,addedOrder=2}}]
at org.jboss.util.naming.Util.checkObject(Util.java:329)
at org.jboss.util.naming.Util.lookup(Util.java:216)
at org.jboss.resource.adapter.jms.inflow.JmsActivation.setupDestination(JmsActivation.java:409)
at org.jboss.resource.adapter.jms.inflow.JmsActivation.setup(JmsActivation.java:316)
at org.jboss.resource.adapter.jms.inflow.JmsActivation.handleFailure(JmsActivation.java:259)
at org.jboss.resource.adapter.jms.inflow.JmsActivation$SetupActivation.run(JmsActivation.java:639)
at org.jboss.resource.work.WorkWrapper.execute(WorkWrapper.java:204)
at org.jboss.util.threadpool.BasicTaskWrapper.run(BasicTaskWrapper.java:275)
at EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(PooledExecutor.java:756)
at java.lang.Thread.run(Thread.java:595)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the esb-issues
mailing list