Problem Configuring JMS Client for Websphere MQ

[nordmeyer]

Hi,

I want to connect to a Websphere MQ JMS interface. I am trying to configure the connection and client-side libraries for a few days now. My main resource of information about the matter is this here from JBoss
http://www.jboss.org/community/docs/DOC-12535

According to this documentation, I placed the rar in the deploy dir and created the *-service.xml and *-ds.xml file at the same place. As I don't want to receive messages, I skipped all other configuration.

When starting JBoss AS (4.2.2.GA) the log ends with the following message:

11:23:36,725 ERROR [URLDeploymentScanner] Incomplete Deployment listing:

--- Packages waiting for a deployer ---
org.jboss.deployment.DeploymentInfo@c418ff1c { url=file:/C:/Programme/jboss-4.2.2.GA/server/default/deploy/rwbJboss-mq-server.xml }
 deployer: null
 status: null
 state: INIT_WAITING_DEPLOYER
 watch: file:/C:/Programme/jboss-4.2.2.GA/server/default/deploy/rwbJboss-mq-server.xml
 altDD: null
 lastDeployed: 1225103016709
 lastModified: 1225103016709
 mbeans:

--- Incompletely deployed packages ---
org.jboss.deployment.DeploymentInfo@c418ff1c { url=file:/C:/Programme/jboss-4.2.2.GA/server/default/deploy/rwbJboss-mq-server.xml }
 deployer: null
 status: null
 state: INIT_WAITING_DEPLOYER
 watch: file:/C:/Programme/jboss-4.2.2.GA/server/default/deploy/rwbJboss-mq-server.xml
 altDD: null
 lastDeployed: 1225103016709
 lastModified: 1225103016709
 mbeans:

A few lines above, I read

11:23:30,551 ERROR [STDERR] WMQ Resource Adapter warning: MQJCA4005:Distributed transactions are not available in client mode.

but the IBM documenation
http://publib.boulder.ibm.com/infocenter/wmqv6/v6r0/index.jsp?topic=/com.ibm.mq.csqzaw.doc/uj40040_.htm
says I can ignore it when I don't need distributed transactions.

Is there someone out in the world who connected the WS MQ the way I have to?

Thanks,
Thomas

[jay.howell]

Check out. https://www.jboss.org/community/docs/DOC-12678. I believe this answers all of your questions.

Jay:)

[nordmeyer]

me again ...

Meanwhile I found second doc source
http://www.ibm.com/developerworks/websphere/library/techarticles/0710_ritchie/0710_ritchie.html
Configuring my JMS client the way described there avoids the startup messages. Now I get an Exception saying

javax.jms.InvalidDestinationException: Destination is not an instance of SpyDestination queue://XNMERC1T/XNMERC1T.IQ.RWBTEST

what looks to me like the message type sent doesn't fit the receiver's capabilities - and therefore leads me back to my configuration.

The change I suspect to make the difference between my first post and now is that I substituted the mbean configuration from

<mbean code="org.jboss.resource.deployment.AdminObject"
 name="jboss.jca:service=WASDestination,name=QueueName">

to

<mbean code="org.jboss.resource.deployment.AdminObject"
 name="jca.wmq:name=rwb-wsmq">

I don't understand at all what I've done, it's just pasted from my documentation. Can anyone explain or give me a hint?

CU,
Thomas

[nordmeyer]

Finally the mbean declaration with

<mbean code="org.jboss.resource.deployment.AdminObject"
 name="jca.wmq:name=rwb-wsmq">

works.

The IBM link seems to describe the procedure that works.

CU,
Thomas