[jboss-jira] [JBoss JIRA] Commented: (EJBTHREE-527) Websphere MQ cannot be integrated with EJB3 (deployment fails)

[Michael Grübsch (JIRA)]

    [ http://jira.jboss.com/jira/browse/EJBTHREE-527?page=comments#action_12347258 ] 
            
Michael Grübsch commented on EJBTHREE-527:
------------------------------------------

Elias, you might be right. I already know that I had forgotten to link the MDB back to the RAR via the JBoss specific deployment configuration in jboss.xml. However, I have observed that depending on some "arbitrary EJB3 artefacts" (here: the file persistence.xml into the META-INF) an application is succuessfully deployed or not. When neither persistence.xml exists nor any other EJB3 artefact is given, the configuration binds the administrative object QUEUE at the WebSphere queue, while in the other case (when persistence.xml exists) the QUEUE is bound to a generic JBoss queue.

> Websphere MQ cannot be integrated with EJB3 (deployment fails)
> --------------------------------------------------------------
>
>                 Key: EJBTHREE-527
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-527
>             Project: EJB 3.0
>          Issue Type: Bug
>    Affects Versions: EJB 3.0 RC6 - PFD
>         Environment: Windows XP, JBoss 4.0.4 CR2 with EJB3 RC6
>            Reporter: Michael Grübsch
>
> When trying to integrate Websphere MQ with an EJB 3 application the following exception occurs while deploying the application:
> 12:28:10,906 WARN  [ServiceController] Problem starting service jboss.j2ee:jar=wsmqmdb.jar,name=MDB,service=EJB3
> java.lang.ClassCastException: com.ibm.mq.jms.MQQueue
> 	at org.jboss.mq.SpyConnectionConsumer.<init>(SpyConnectionConsumer.java:107)
> 	at org.jboss.mq.SpyConnection.createConnectionConsumer(SpyConnection.java:209)
> 	at org.jboss.ejb3.mdb.MDB.innerCreateQueue(MDB.java:530)
> 	at org.jboss.ejb3.mdb.MDB.innerCreate(MDB.java:454)
> 	at org.jboss.ejb3.mdb.MDB.innerStart(MDB.java:267)
> 	at org.jboss.ejb3.mdb.MDB.start(MDB.java:256)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> 	at java.lang.reflect.Method.invoke(Method.java:585)
> 	at org.jboss.ejb3.ServiceDelegateWrapper.startService(ServiceDelegateWrapper.java:99)
> 	at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:289)
>                      ....
> To reproduce the bug do the following:
> 1. set up environment JBoss 4.0.4 CR2 with EJB3 RC6
> 2. Download wsmqdemo.zip from the integration tutorial http://wiki.jboss.org/wiki/Wiki.jsp?page=UsingWebSphereMQSeriesWithJBossASPartI (http://wiki.jboss.org/wiki/attach?page=UsingWebSphereMQSeriesWithJBossASPartI%2Fwsmqdemo.zip)
> 3. Configure it for using Websphere for inbound and outbound (see http://wiki.jboss.org/wiki/Wiki.jsp?page=UsingWebSphereMQSeriesWithJBossASPart2)
> 4. put a valid file "persistence.xml" into the META-INF directory of the application or tag some class using a @Stateful annotation (indicating that EJB3 is to be used(?))
> 5. deploy the application

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira