JBESB 4.7 and IBM MQ 6.0 - topics accessed via a jms-jca-provider fail to deploy - java.lang.ClassCastException raised ---------------------------------------------------------------------------------------------------------------------- Key: JBESB-3204 URL: https://jira.jboss.org/jira/browse/JBESB-3204 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Rosetta Affects Versions: 4.7 Environment: 4.7 GA, IBM MQ 6.0.2, RHEL5, Java 1.6 Reporter: Len DiMaggio See the attached quickstart - helloworld modified to use IBM MQ. With this jms-jca-provider definition: <jms-jca-provider name="JBossMQ" jndi-URL="dev75.mw.lab.eng.bos.redhat.com:1414/SYSTEM.DEF.SVRCONN" jndi-context-factory="com.ibm.mq.jms.context.WMQInitialContextFactory" connection-factory="ConnectionFactory" providerAdapterJNDI="java:/WSMQProvider" > <jms-bus busid="ibmGwChannel"> <jms-message-filter dest-type="TOPIC" dest-name="ACTION_TOPIC" /> </jms-bus> This exception is raised when the quickstart is deployed: 10:58:01,512 WARN [JmsActivation] Failure in jms activation org.jboss.resource.adapter.jms.inflow.JmsActivationSpec@89c1ee(ra=org.jboss.resource.adapter.jms.JmsResourceAdapter(a)884c0e destination=ACTION_TOPIC isTopic=true tx=true durable=false reconnect=10 provider=java:/WSMQProvider 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 'ACTION_TOPIC' in context {java.naming.factory.initial=com.ibm.mq.jms.context.WMQInitialContextFactory, java.naming.provider.url=dev75.qa.atl.jboss.com:1414/SYSTEM.DEF.SVRCONN, java.naming.factory.url.pkgs=org.jboss.naming:org.jnp.interfaces:org.jboss.naming:org.jnp.interfaces} is not an instance of [class=javax.jms.Topic classloader=org.jboss.mx.loading.UnifiedClassLoader3@17f409c{ url=null ,addedOrder=2} interfaces={interface=javax.jms.Destination classloader=org.jboss.mx.loading.UnifiedClassLoader3@17f409c{ url=null ,addedOrder=2}}] object class is [class=com.ibm.mq.jms.MQQueue classloader=org.jboss.mx.loading.UnifiedClassLoader3@17f409c{ url=null ,addedOrder=2} interfaces={interface=javax.jms.Queue classloader=org.jboss.mx.loading.UnifiedClassLoader3@17f409c{ url=null ,addedOrder=2}, interface=javax.naming.Referenceable classloader=null, interface=java.io.Serializable classloader=null}] 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:619) The exception is not seen if a jms-provider is used. -- 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