| Author |
Message
|
| jairo_vazquez |
 Posted: Wed Oct 20, 2004 6:56 am Post subject: Problems with embedded MQ |
 |
|
Newbie
Joined: 20 Oct 2004
Posts: 5
|
Hi,
I am dealing with a problem related to the embedded MQ server within Websphere (Websphere JMS Provider). The environment is Websphere 5.1.0.3 on AIX 5.2. Every time that my application tries to create a connection to one of the Topic or Queue factories I get the following error:
[10/19/04 17:46:30:460 EDT] 5b254a0b FreePool E J2CA0046E: Method createManagedConnctionWithMCWrapper caught an
exception during creation of the ManagedConnection for resource performancebudgeting.Auth.Cache.Mgr.JMS.Topic.Connection.Factory,
throwing ResourceAllocationException. Original exception: javax.resource.spi.ResourceAdapterInternalException: createTopicConnection failed
The linked exceptions are:
javax.jms.JMSException: MQJMS2005: failed to create MQQueueManager for 'verne.ams.com:WAS_verne_server1'
com.ibm.mq.MQException: MQJE001: An MQException occurred: Completion Code 2, Reason 2009
MQJE003: IO error transmitting message buffer
Looking at Websphere inforcenter I found that the MQJE003 error could be related to permissions to the tmp directory, I checked those and everyone has permissions. I checked the MQ logs and I found the following errors:
AMQ9604: Channel 'WAS.JMS.SVRCONN' terminated unexpectedly
AMQ6184: An internal WebSphere MQ error has occurred on queue manager
I have tried clearing the queues and reinstalling the software but I still see the problem.
Any help will be appreciated.
Thanks in advance
Jairo |
|
| Back to top |
|
 |
| bower5932 |
| Posted: Wed Oct 20, 2004 10:23 am Post subject: |
|
|
Jedi Knight
Joined: 27 Aug 2001
Posts: 3023
Location: Dallas, TX, USA
|
Don't make multiple posts.
As far as your actual problem, a 2009 is a connection broken. The AMQ6184 internal error should have created an *.FDC file in the errors subdirectory. Post the top of it here. |
|
| Back to top |
|
|
| jairo_vazquez |
| Posted: Wed Oct 20, 2004 10:42 am Post subject: |
|
|
Newbie
Joined: 20 Oct 2004
Posts: 5
|
FDC file
+-----------------------------------------------------------------------------+
| |
| WebSphere MQ First Failure Symptom Report |
| ========================================= |
| |
| Date/Time :- Tuesday October 19 18:35:16 EDT 2004 |
| Host Name :- verne (AIX 5.2) |
| PIDS :- 5724B4101 |
| LVLS :- 530.4 CSD04 |
| Product Long Name :- WebSphere MQ for AIX |
| Vendor :- IBM |
| Probe Id :- RM487001 |
| Application Name :- MQM |
| Component :- rriChannelTerminate |
| Build Date :- Jun 18 2003 |
| CMVC level :- p530-04-030617 |
| Build Type :- IKAP - (Production) |
| UserID :- 00000208 (root) |
| Program Name :- endmqm |
| Process :- 00025056 |
| Thread :- 00000001 |
| QueueManager :- WAS_verne_server1 |
| Major Errorcode :- rrcE_CHANNEL_TERMINATED |
| Minor Errorcode :- OK |
| Probe Type :- MSGAMQ9604 |
| Probe Severity :- 2 |
| Probe Description :- AMQ9604: Channel 'WAS.JMS.SVRCONN' terminated |
| unexpectedly |
| FDCSequenceNumber :- 0 |
| Arith1 :- 545284357 20806105 |
| Arith2 :- 20536 5038 |
| Comment1 :- WAS.JMS.SVRCONN |
| |
| Comment2 :- |
| |
| Comment3 :- |
| |
| |
+-----------------------------------------------------------------------------+ |
|
| Back to top |
|
|
| bower5932 |
| Posted: Wed Oct 20, 2004 11:46 am Post subject: |
|
|
Jedi Knight
Joined: 27 Aug 2001
Posts: 3023
Location: Dallas, TX, USA
|
|
| Back to top |
|
|
| jairo_vazquez |
| Posted: Thu Oct 21, 2004 12:13 pm Post subject: |
|
|
Newbie
Joined: 20 Oct 2004
Posts: 5
|
| The fix pack is for the MQ product , I am using the embedded piece provided by Websphere Application Server. Are they the same? |
|
| Back to top |
|
|
| Nigelg |
| Posted: Fri Oct 22, 2004 1:59 am Post subject: |
|
|
Grand Master
Joined: 02 Aug 2004
Posts: 1046
|
| RM487001 is a generic FFST which just means that a channel has ended abnormally. APAR IY36646 that bower5932 has suggested deals with the rare case that this is reported in error. It is much more likely that the channel has ended abnormmally for soem other reason - killed by the user, exit crashed the MCA, etc. Do not consider the APAR until you have found why the MCA ended. |
|
| Back to top |
|
|
| bower5932 |
| Posted: Fri Oct 22, 2004 5:49 am Post subject: |
|
|
Jedi Knight
Joined: 27 Aug 2001
Posts: 3023
Location: Dallas, TX, USA
|
| I just looked at the FDC a little closer, and it is coming from endmqm. Are you attempting to shutdown your qmgr when you shouldn't be? |
|
| Back to top |
|
|
| jairo_vazquez |
| Posted: Tue Oct 26, 2004 5:49 am Post subject: |
|
|
Newbie
Joined: 20 Oct 2004
Posts: 5
|
| As I mentioned before I am only dealing with Websphere Application Server not with MQ directly. I have shut down WAS not MQ, I assume that by stopping the Websphere Server the MQ instance will also go down. |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Wed Oct 27, 2004 1:57 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
Remember the restrictions of embedded MQ:
The MQ Server only lives as long as the corresponding WAS resource is up.
No message can communicate with the outside. I would only use embedded MQ if the only task you have is decoupling processes in near Realtime. I mean realizing a usually synchronous process in an asynchronous way.
Enjoy  |
|
| Back to top |
|
|
|
|
