JMS changes from 3.2.3 to 4.0DR2?

[osganian]

Hi, my message driven bean worked great under 3.2.3 but under 4.0 nothing happens. When I posts messages on my queue I receive no errors and nothing is triggered in my MDB. What configuration changes must I have to do when upgrading to 4.0?

Here is my jboss.xml portion:

<message-driven>
<ejb-name>MyMDB</ejb-name>
<jndi-name>MyMDB</jndi-name>
<destination-jndi-name>queue/myQueue</destination-jndi-name>
<configuration-name>Standard Message Driven Bean</configuration-name>
<xa-connection>false</xa-connection>
</message-driven>

And my jboss-service.xml:


<depends optional-attribute-name="DestinationManager">
jboss.mq:service=DestinationManager

<depends optional-attribute-name="SecurityManager">
jboss.mq:service=SecurityManager










Thanks for any help and suggestions!

Mike

[adrian.brock]

4.0DR2 is a lot older than 3.2.3
Try the CVS version or a nightly snapshot

Regards,
Adrian

[osganian]

So if I wanted a 'newer' 4.0 release I would have to get a nightly snapshot of HEAD? So that means I have to build JBoss from the source right?

So, using 4.0 DR2, sending messages to a message driven bean is broken? Right now I can post messages and those messages get added to the JMS_MESSAGES table but never get sent to my message driven bean.

Is there anything that I might not have correctly configured?

Thanks

[osganian]

Didn't know I was getting an error, when I start up I get an "MBeanException: Incomplete Deployment listing" error when trying to deploy my jar file.

The problem is I don't get a stack trace and I'm not sure what is the problem or what I am missing in my configuration.

[osganian]

Actually, I get the "MBeanException: Incomplete Deployment listing" without deploying any of my code.

Has anybody had any luck with getting 4.0DR2 to startup without any errors and successfully send messages from a configured Queue to a message driven bean?

Thanks!