Binding a queue to an EJB 3.0 MDB in WebSphere 7

Question

I'm writing, or trying to write, Baby's First MDB on WebSphere 7. I have nearly no hair left, having pulled it all out trying to get the thing to work. It appears that I've got everything set up right, but I get no response when I put a message to the associated queue.

Here's the EAR file setup:

simplemdb.ear
    META-INF
        Manifest.mf
        application.xml
    simplemdb.jar
        META-INF
            Manifest.mf
            ejb-jar.xml
        com
            [ classes go here ]

I can't find any syntax for defining the queue's JNDI name in ejb-jar.xml, so instead I:

Define a WebSphere activation spec. Name SimpleMDBActivationSpec, JNDI name jms/SimpleActivationSpec, Destination jms/SimpleMDBQueue.
Define a WebSphere queue. Name SimpleMDBQueue, JNDI name jms/SimpleMDBQueue, Queue name SIMPLE.MDB.QUEUE.
Define an MQ queue, name SIMPLE.MDB.QUEUE.
Deploy the EAR file. During the deployment, I'm asked to enter binding information. I select Activation Specification, then point the Target Resource JNDI Name and Destination JNDI name at the activation spec and queue, respectively.

(The MDB code has no annotations.) At this point, the app points to the spec and queue, and the spec points to the queue - belt and suspenders. Naturally, I imagine that the app therefore knows about the queue. Full of hope, I put a message on the queue, and ... nothing. The onMessage event is supposed to use System.out to log a message. I see no message.

Clear documentation on this is conspicuous by its absence. Google gives LOTS of results, but none of them details how the configuration all fits together. There's lots of hand-waving about ibm-ejb-jar-bnd.xmi, but examples of the file are arcane, full of opaque numbers with no explanation about how they were generated, or how they relate to other parts of the configuration.

For goodness' sake. All I want to do is deploy an MDB, and have it write "Hello, world" when I put a message to a queue. I'm using vi and ant as my development and build tools. Can anybody out there give me an idea about what I'm missing?

Edit: "zos" tag added.

I'm not an MDB expert, but your config steps for actspec, queue, and binding look proper, so I'm not sure what's wrong. I'll note that when checking Google, ibm-ejb-jar-bnd.xmi is for pre-EJB3, and .xml is used for EJB3. Regardless, those files are created/populated for you during the deployment step, so you shouldn't need them. Hope that helps... — Brett Kail
Thanks. So far as I can tell, the ibm-ejb-jar-bnd.xmi/xml file gives the default values to use. I should be able to change bindings on the fly with the Admin Console. Doing so doesn't make the app work. =( Also, I just tried using a listener port instead of an activation spec. No go. WebSphere reports that everything is deployed just fine, but the MDB still doesn't respond in any way to puts to the queue. A bit of research uncovered the idea that if the MDB is properly listening, the MQ queue will show a connection (or two). That's not happening, either. Aargh! — Singlestone

Singlestone Singlestone · Accepted Answer · 2011-06-03T22:16:43

I found the problem. It's specific to WebSphere running on z/OS. For an activation spec to be fully available in that environment, the Control Region Adjunct (CRA) process must be started. I told WAS to start it up, recycled the app server, and lo! My MDB started responding.

To make the CRA start via the WebSphere Admin Console, go to ...

Application servers > [server name] > Communications > Messaging > WebSphere MQ CRA Settings

... and check the box that says "Start CRA". Hit OK, save it to the master configuration, and to make the CRA actually start, bring the app server down and back up. (This is for WAS 7.0.)

Thanks to everyone for their time and thoughtspace.

Binding a queue to an EJB 3.0 MDB in WebSphere 7

2 Answers