ASG
IBM
Zystems
Cressida
Icon
Netflexity
 
  MQSeries.net
Search  Search       Tech Exchange      Education      Certifications      Library      Info Center      SupportPacs      LinkedIn  Search  Search                                                                   FAQ  FAQ   Usergroups  Usergroups
 
Register  ::  Log in Log in to check your private messages
 
RSS Feed - WebSphere MQ Support RSS Feed - Message Broker Support

MQSeries.net Forum Index » IBM MQ Java / JMS » MQJMS 2007 when putting to a clustered queue

Post new topic  Reply to topic
 MQJMS 2007 when putting to a clustered queue « View previous topic :: View next topic » 
Author Message
TheDude
PostPosted: Fri May 19, 2006 7:05 pm    Post subject: MQJMS 2007 when putting to a clustered queue Reply with quote

Apprentice

Joined: 21 Oct 2002
Posts: 31
I am using WebSphere AS 5.1.2 and MQ 5.3 CSD 10 with a vendor written application. Our MQ department created some clustered queues on our QMGRs and when we do a put we get the following exception:

[5/18/06 17:22:02:221 MST] 46b21289 SystemOut O 18 May 2006 17:22:02,220|INFO|com.usdataworks.collections.ObjectCache||Value true for id Initial Mgt.Instream Request Step.Active cached successfuly.
[5/18/06 17:22:02:224 MST] 46b21289 SystemOut O 18 May 2006 17:22:02,223|INFO|com.usdataworks.collections.ObjectCache||Value MyRacfID for id Initial Mgt.Instream Request Step.RACFID cached successfuly.
[5/18/06 17:22:02:468 MST] 46b21289 SystemOut O 18 May 2006 17:22:02,467|INFO|com.usdataworks.collections.ObjectCache||Value jms/udwConnectionFactory for id Initial Mgt.Instream Request Step.ConnectionFactory cached successfuly.
[5/18/06 17:22:02:470 MST] 46b21289 SystemOut O 18 May 2006 17:22:02,470|INFO|com.usdataworks.collections.ObjectCache||Value jms/Amex Instream Request for id Initial Mgt.Instream Request Step.QueueName cached successfuly.
[5/18/06 17:22:02:524 MST] 46b21289 ConnectionEve A J2CA0056I: The Connection Manager received a fatal connection error from the Resource Adaptor for resource JMS$udwConnectionFactory$JMSManagedConnection@486036118. The exception which was received is javax.jms.JMSException: MQJMS2007: failed to send message to MQ queue
[5/18/06 17:22:02:540 MST] 46b21289 ConnectionEve A J2CA0056I: The Connection Manager received a fatal connection error from the Resource Adaptor for resource jms/udwConnectionFactory. The exception which was received is javax.jms.JMSException: MQJMS2007: failed to send message to MQ queue
[5/18/06 17:22:02:626 MST] 46b21289 SystemOut O 18 May 2006 17:22:02,621|ERROR|com.usdataworks.amex.instream.step.InstreamRequestStep||Could not process message.
javax.jms.JMSException: MQJMS2007: failed to send message to MQ queue
at com.ibm.mq.jms.services.ConfigEnvironment.newException(ConfigEnvironment.java:553)
at com.ibm.mq.jms.MQMessageProducer.sendInternal(MQMessageProducer.java:1602)
at com.ibm.mq.jms.MQMessageProducer.send(MQMessageProducer.java:1022)
at com.ibm.mq.jms.MQMessageProducer.send(MQMessageProducer.java:1056)
at com.ibm.ejs.jms.JMSQueueSenderHandle.send(JMSQueueSenderHandle.java:176)
at com.usdataworks.amex.instream.step.InstreamRequestStep.sendTextMessage(InstreamRequestStep.java:222)
at com.usdataworks.amex.instream.step.InstreamRequestStep.sendMessage(InstreamRequestStep.java:199)
at com.usdataworks.amex.instream.step.InstreamRequestStep.processMessage(InstreamRequestStep.java:7
at com.usdataworks.j2ee.workflow.step.transaction.WorkflowTransactionImpl.execute(WorkflowTransactionImpl.java:54)
at com.usdataworks.j2ee.workflow.step.WorkflowStepProcessorImpl.processFirstRequest(WorkflowStepProcessorImpl.java:96)
at com.usdataworks.j2ee.workflow.step.WorkflowStepProcessorImpl.processStep(WorkflowStepProcessorImpl.java:73)
at com.usdataworks.j2ee.workflow.step.MdbStep.handleMessageObject(MdbStep.java:91)
at com.usdataworks.j2ee.workflow.step.MdbStep.onMessage(MdbStep.java:55)
at com.ibm.ejs.jms.listener.MDBWrapper$PriviledgedOnMessage.run(MDBWrapper.java:208)
at com.ibm.ws.security.util.AccessController.doPrivileged(AccessController.java(Compiled Code))
at com.ibm.ejs.jms.listener.MDBWrapper.callOnMessage(MDBWrapper.java:197)
at com.ibm.ejs.jms.listener.MDBWrapper.onMessage(MDBWrapper.java:175)
at com.ibm.mq.jms.MQSession.run(MQSession.java:1744)
at com.ibm.ejs.jms.JMSSessionHandle.run(JMSSessionHandle.java:924)
at com.ibm.ejs.jms.listener.ServerSession.connectionConsumerOnMessage(ServerSession.java:752)
at com.ibm.ejs.jms.listener.ServerSession.onMessage(ServerSession.java:527)
at com.ibm.ejs.jms.listener.ServerSession.dispatch(ServerSession.java:494)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:85)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:5
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java(Compiled Code))
at java.lang.reflect.Method.invoke(Method.java(Compiled Code))
at com.ibm.ejs.jms.listener.ServerSessionDispatcher.dispatch(ServerSessionDispatcher.java:37)
at com.ibm.ejs.container.MDBWrapper.onMessage(MDBWrapper.java:91)
at com.ibm.ejs.container.MDBWrapper.onMessage(MDBWrapper.java:127)
at com.ibm.ejs.jms.listener.ServerSession.run(ServerSession.java:375)
at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:912)
[5/18/06 17:22:02:627 MST] 46b21289 SystemOut O 18 May 2006 17:22:02,626|INFO|com.usdataworks.j2ee.workflow.step.transaction.WorkflowTransactionImpl||Step Initial Mgt.Instream Request Step processed a message.
[5/18/06 17:22:02:693 MST] 46b21289 ServerSession W WMSG0036E: Maximum message delivery retry count of 0 reached for MDB InitialMgt.InstreamRequestStep, JMSDestination jms/Initial Mgt.Instream Request, MDBListener stopped
[5/18/06 17:22:03:128 MST] 6bbb128a MDBListenerIm I WMSG0043I: MDB Listener InitialMgt_InstreamRequestStepPort stopped for JMSDestination jms/Initial Mgt.Instream Request


I don't have the linked exception, but the strange thing is that when they change the Base Queue Name in the Queue Destination portion of the WAS JMS config, it works. They just change the name to a regular old local queue and there is no problem.

Here is the cluster q definition:

DESCR(WebSphere MQ Default Local Queue)
PROCESS( ) BOQNAME( )
INITQ( ) TRIGDATA( )
CLUSTER(ESBUSCLT01) CLUSNL( )
QUEUE(DETAILLEVELCONTROL.UDW.REQMGR) CRDATE(2006-05-02)
CRTIME(21.01.05) ALTDATE(2006-05-19)
ALTTIME(13.43.23) GET(ENABLED)
PUT(ENABLED) DEFPRTY(0)
DEFPSIST(YES) MAXDEPTH(0)
MAXMSGL(4194304) BOTHRESH(0)
SHARE DEFSOPT(SHARED)
HARDENBO MSGDLVSQ(PRIORITY)
RETINTVL(999999999) USAGE(NORMAL)
NOTRIGGER TRIGTYPE(FIRST)
TRIGDPTH(1) TRIGMPRI(0)
QDEPTHHI(80) QDEPTHLO(20)
QDPMAXEV(DISABLED) QDPHIEV(DISABLED)
QDPLOEV(ENABLED) QSVCINT(999999999)
QSVCIEV(NONE) DISTL(NO)
NPMCLASS(NORMAL) DEFTYPE(PREDEFINED)
TYPE(QLOCAL) SCOPE(QMGR)
DEFBIND(NOTFIXED) IPPROCS(0)
OPPROCS(0) CURDEPTH(0)

The regular queue (the one that works) has all of the default values used when creating a queue and just giving the name


Any help is greatly appreciated.
Brian
Back to top
View user's profile Send private message
EddieA
PostPosted: Fri May 19, 2006 10:27 pm    Post subject: Reply with quote

Jedi

Joined: 28 Jun 2001
Posts: 2453
Location: Los Angeles
Quote:
I don't have the linked exception

And without that it's guesswork.

And my guess is that the PUTting application is supplying a QMGR name, because:
Quote:
They just change the name to a regular old local queue and there is no problem

For a Cluster PUT to work, you cannot supply a QMGR name.

Cheers,
_________________
Eddie Atherton
IBM Certified Solution Developer - WebSphere Message Broker V6.1
IBM Certified Solution Developer - WebSphere Message Broker V7.0
Back to top
View user's profile Send private message
fjb_saper
PostPosted: Sat May 20, 2006 4:54 am    Post subject: Reply with quote

Grand High Poobah

Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
One way to alleviate all that trouble is to specify a cluster alias on the put. Make the put with a fictitious qmgr that resolves in the cluster to a 'blank' qmgr.

Enjoy
_________________
MQ & Broker admin
Back to top
View user's profile Send private message Send e-mail
TheDude
PostPosted: Sat May 20, 2006 6:27 pm    Post subject: Reply with quote

Apprentice

Joined: 21 Oct 2002
Posts: 31
Problem solved. The Base QMGR Name was listed as local instead of Hub (which is blank).

Thanks for your help.
Back to top
View user's profile Send private message
Display posts from previous:   
Post new topic  Reply to topic Page 1 of 1

MQSeries.net Forum Index » IBM MQ Java / JMS » MQJMS 2007 when putting to a clustered queue
Jump to:  



You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
Protected by Anti-Spam ACP
  
 


Theme by Dustin Baccetti
Powered by phpBB © 2001, 2002 phpBB Group

Copyright © MQSeries.net. All rights reserved.