| Author |
Message
|
| r2504 |
 Posted: Fri Jan 20, 2006 6:51 am Post subject: WAS embedded WMQ JMS provider |
 |
|
Novice
Joined: 05 Mar 2004
Posts: 22
|
I'm trying to get a servlet to send a message via JMS and the build in Websphere MQ JMS provider in my WAS (actually a development environment in Rational Software Architect).
The problem is when I run it, I get a Error 500: java.lang.Error: Unresolved compilation problem: The import com.ibm.mq cannot be resolved.
Looking in the WAS admin console, I see however that the MQ_INSTALL_ROOT is pointing to the correct directory which contains the COM.IBM.MQ jar file (which is part of the WAS 6 in RSA).
I fixed this by putting COM.IBM.MQ in the lib directory of my application... but I wonder if that is the way to go ? (looks funny because this way I loose the embedded aspect).
And I have a new problem now...
MQJMS2007: failed to send message to MQ queue MQJMS2007
MQJE001: Completion Code 2, Reason 2009 |
|
| Back to top |
|
 |
| vennela |
| Posted: Fri Jan 20, 2006 11:12 am Post subject: |
|
|
Jedi Knight
Joined: 11 Aug 2002
Posts: 4055
Location: Hyderabad, India
|
Where are you trying to send the message to?
A QMGR outside WAS or to the Default Messaging in WAS |
|
| Back to top |
|
|
| r2504 |
| Posted: Sat Jan 21, 2006 7:18 am Post subject: |
|
|
Novice
Joined: 05 Mar 2004
Posts: 22
|
| To a queuemanager outside of WAS... and when I debug my servlet, I see that the actual connection is established with my queuemanager, but the send itself fails. |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Sat Jan 21, 2006 7:42 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20768
Location: LI,NY
|
If you do not have the actual client jars in your classpath the connection will always fail. Embedded WAS cannot communicate outside WAS (feature).
Enjoy 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| r2504 |
| Posted: Sun Jan 22, 2006 6:29 am Post subject: |
|
|
Novice
Joined: 05 Mar 2004
Posts: 22
|
| fjb_saper wrote: |
| If you do not have the actual client jars in your classpath the connection will always fail. Embedded WAS cannot communicate outside WAS (feature). |
Apart from that I'm not happy with this (when WAS has the jars itself in the MQ_ROOT_INSTALL), the fact is that even after I loaded the jars in my lib directory, it still doesn't work.
What is causing my... ?
MQJMS2007: failed to send message to MQ queue MQJMS2007
MQJE001: Completion Code 2, Reason 2009 |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Sun Jan 22, 2006 10:25 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20768
Location: LI,NY
|
Read up on the setup of WAS MQ JMS in the management console. The help files should give you a good indication as well as the WAS manuals.
Search as well the site for 2009 you should find numerous hits to guide you.
Enjoy
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| r2504 |
| Posted: Mon Jan 23, 2006 10:04 am Post subject: |
|
|
Novice
Joined: 05 Mar 2004
Posts: 22
|
I checked the forum for 2009 messages, and found the thread about mismatches in CSD levels, hence I looked at the CSD of the iSeries which is V5R3 CSD11... and the one included in Rational Software Architect included test server was CSD08.
I now replaced the com.ibm.mq.jar and com.ibm.mqjms.jar of the WAS 6 test server in RSA... but I still have the samen problem 
Strange thing is that initially it didn't work when I didn't have the jars in my lib directory, and now when I deleted them it DOES work (so it must be using those of MQ_INSTALL_ROOT as defined in WAS) 
I'm really confused... |
|
| Back to top |
|
|
| r2504 |
| Posted: Tue Jan 24, 2006 6:40 am Post subject: |
|
|
Novice
Joined: 05 Mar 2004
Posts: 22
|
| r2504 wrote: |
| I now replaced the com.ibm.mq.jar and com.ibm.mqjms.jar of the WAS 6 test server in RSA... but I still have the samen problem |
I had the impression that I did it (using a Citrix environment, and while it asked if I wanted to overwrite the files, it apparently didn't). Anyway, I now asked the admin to overwrite both files with those of our iSeries (CSD 11) and now it works  |
|
| Back to top |
|
|
|
|
