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 » Websphere Application Server -> JMS to MQ

Post new topic  Reply to topic
 Websphere Application Server -> JMS to MQ « View previous topic :: View next topic » 
Author Message
saneben
PostPosted: Mon Mar 17, 2008 8:15 am    Post subject: Websphere Application Server -> JMS to MQ Reply with quote

Voyager

Joined: 04 Apr 2004
Posts: 96
Hi,

We have installed WAS 6.0.2 on AIX
MQ 6.0.0 on AIX

WAS is connecting to MQ via JMS

JMS is able to take the message from MQ but it is unable to put the message to the cluster MQ.

We are getting the below message.

Please advise any solution

</serviceResponse>
[3/17/08 14:14:36:731 CST] 0000003d SystemOut O JMS Reply TO Queue
:queue://QM1/DP.REPLY
[3/17/08 14:14:36:764 CST] 0000003d ConnectionEve A J2CA0056I: The
Connection Manager received a fatal connection error from the Resource
Adaptor for resource
JMS$ETadawulConnectionFactory$JMSManagedConnection@241139513. The
exception which was received is javax.jms.JMSException: MQJMS2007: failed
to send message to MQ queue
[3/17/08 14:14:36:828 CST] 0000003d ConnectionEve A J2CA0056I: The
Connection Manager received a fatal connection error from the Resource
Adaptor for resource jms/ETadawulConnectionFactory. The exception which
was received is javax.jms.JMSException: MQJMS2007: failed to send message
to MQ queue
[3/17/08 14:14:36:830 CST] 0000003d WASLogger E CLASSNAME METHODNAME an
internal error has occurred. Please contact your system administrator.
Detail: com.ibm.mq.MQException: MQJE001: Completion Code 2, Reason 2019
[3/17/08 14:14:36:843 CST] 0000003d SystemOut O JMSException
:javax.jms.JMSException: MQJMS2007: failed to send message to MQ queue
[3/17/08 14:14:36:846 CST] 0000003d ConnectionEve A J2CA0056I: The
Connection Manager received a fatal connection error from the Resource
Adaptor for resource
JMS$ETadawulConnectionFactory$JMSManagedConnection@241139513. The
exception which was received is javax.jms.JMSException: MQJMS2000: failed
to close MQ queue
[3/17/08 14:14:36:847 CST] 0000003d ConnectionEve A J2CA0056I: The
Connection Manager received a fatal connection error from the Resource
Adaptor for resource
JMS$ETadawulConnectionFactory$JMSManagedConnection@241139513. The
exception which was received is javax.jms.JMSException: MQJMS2000: failed
to close MQ queue
[3/17/08 14:14:36:851 CST] 0000003d ConnectionEve A J2CA0056I: The
Connection Manager received a fatal connection error from the Resource
Adaptor for resource
JMS$ETadawulConnectionFactory$JMSManagedConnection@241139513. The
exception which was received is javax.jms.JMSException: MQJMS2000: failed
to close MQ queue


Error trace:
[3/17/08 14:14:36:844 CST] 0000003d SystemErr R 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:1598)
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.JMSMessageProducerHandle.send(JMSMessageProducerHandle.java:1168)

at
sa.com.shc.ttp.etadawul.ejb.TadawulMessageListener.sendReply(TadawulMessageListener.java:155)

at
sa.com.shc.ttp.etadawul.ejb.ETadawulMessageBean.onMessage(ETadawulMessageBean.java:72)

at
com.ibm.ejs.jms.listener.MDBWrapper$PriviledgedOnMessage.run(MDBWrapper.java:316)

at
com.ibm.ws.security.util.AccessController.doPrivileged(AccessController.java(Compiled
Code))
at com.ibm.ejs.jms.listener.MDBWrapper.callOnMessage(MDBWrapper.java:285)
at com.ibm.ejs.jms.listener.MDBWrapper.onMessage(MDBWrapper.java:263)
at com.ibm.mq.jms.MQSession.run(MQSession.java:1662)
at com.ibm.ejs.jms.JMSSessionHandle.run(JMSSessionHandle.java:963)
at
com.ibm.ejs.jms.listener.ServerSession.connectionConsumerOnMessage(ServerSession.java:826)

at
com.ibm.ejs.jms.listener.ServerSession.onMessage(ServerSession.java:616)
at com.ibm.ejs.jms.listener.ServerSession.dispatch(ServerSession.java:583)
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:458)
at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java(Compiled Code))
---- Begin backtrace for Nested Throwables
com.ibm.mq.MQException: MQJE001: Completion Code 2, Reason 2009
at com.ibm.mq.MQQueue.putMsg2(MQQueue.java:1501)
at
com.ibm.mq.jms.MQMessageProducer.sendInternal(MQMessageProducer.java:1578)
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.JMSMessageProducerHandle.send(JMSMessageProducerHandle.java:1168)

at
sa.com.shc.ttp.etadawul.ejb.TadawulMessageListener.sendReply(TadawulMessageListener.java:155)

at
sa.com.shc.ttp.etadawul.ejb.ETadawulMessageBean.onMessage(ETadawulMessageBean.java:72)

at
com.ibm.ejs.jms.listener.MDBWrapper$PriviledgedOnMessage.run(MDBWrapper.java:316)

at
com.ibm.ws.security.util.AccessController.doPrivileged(AccessController.java(Compiled
Code))
at com.ibm.ejs.jms.listener.MDBWrapper.callOnMessage(MDBWrapper.java:285)
at com.ibm.ejs.jms.listener.MDBWrapper.onMessage(MDBWrapper.java:263)
at com.ibm.mq.jms.MQSession.run(MQSession.java:1662)
at com.ibm.ejs.jms.JMSSessionHandle.run(JMSSessionHandle.java:963)
at
com.ibm.ejs.jms.listener.ServerSession.connectionConsumerOnMessage(ServerSession.java:826)

at
com.ibm.ejs.jms.listener.ServerSession.onMessage(ServerSession.java:616)
at com.ibm.ejs.jms.listener.ServerSession.dispatch(ServerSession.java:583)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:85)

at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:5
Back to top
View user's profile Send private message
Vitor
PostPosted: Mon Mar 17, 2008 8:19 am    Post subject: Re: Websphere Application Server -> JMS to MQ Reply with quote

Grand High Poobah

Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
saneben wrote:
Please advise any solution


- apply some maintenance to the WMQ & don't try the plain v6.0.0

- search the forum for tips on resolving 2009 errors.
_________________
Honesty is the best policy.
Insanity is the best defence.
Back to top
View user's profile Send private message
saneben
PostPosted: Mon Mar 17, 2008 11:08 am    Post subject: Reply with quote

Voyager

Joined: 04 Apr 2004
Posts: 96
Hi Victor,

Thanks for the update. I am downloading the refesh pack for WMQ
This wanted to let you know that the Queue Manager I am putting the message is on a different machine but on a MQ cluster

I searched the forum for the above scenario I found the below

Quute
<bean id="jmsMQConnectionFactory" class="com.ibm.mq.jms.MQQueueConnectionFactory">
<!--property name="queueManager" value="QM.CBX2GSS2"/-->
<property name="hostName" value="192.168.219.80"/>
<property name="port" value="1442"/>
<property name="channel" value="CH.CBX2GSS.SRVC"/>
</bean>

any idea what is still wrong?
What about the transport attribute ? TCP_Client ?

<property name="transportType" value="1"/>
Unquote


I need to know where to add the below to help the team
<property name="transportType" value="1"/>

Regards
Back to top
View user's profile Send private message
Vitor
PostPosted: Mon Mar 17, 2008 12:17 pm    Post subject: Reply with quote

Grand High Poobah

Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
saneben wrote:
I need to know where to add the below to help the team
<property name="transportType" value="1"/>


Why would this help? You're clearly clienting onto a remote queue manager, hence the 2009 (client connection broken) so why change the transport type?

(Java is not enirely my thing, so I struggle to see what you're trying to achieve)
_________________
Honesty is the best policy.
Insanity is the best defence.
Back to top
View user's profile Send private message
saneben
PostPosted: Wed Mar 19, 2008 11:23 am    Post subject: Reply with quote

Voyager

Joined: 04 Apr 2004
Posts: 96
Dear Vitor,

We upgraded the WAS from version 6.0.2 to 6.0.2.13 the JMS issue is resolved. I am able to put the message.

One small issue is that when the Reply to Queue - QueueManager is blank and only Reply Queue is specified it works fine.

The application putting the message is sending the QueueManager name and reply Queue name as we are using a cluster.

Any idea how to fix this.

Regards
Back to top
View user's profile Send private message
fjb_saper
PostPosted: Wed Mar 19, 2008 2:12 pm    Post subject: Reply with quote

Grand High Poobah

Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
saneben wrote:
Dear Vitor,

We upgraded the WAS from version 6.0.2 to 6.0.2.13 the JMS issue is resolved. I am able to put the message.

Great!

saneben wrote:
One small issue is that when the Reply to Queue - QueueManager is blank and only Reply Queue is specified it works fine.

This is the standard way to specify a cluster queue.

saneben wrote:
The application putting the message is sending the QueueManager name and reply Queue name as we are using a cluster.

Any idea how to fix this.

Regards

There is nothing to be fixed.
You need to find out why the qmgrs are not communicating. (lack of a default path?)
The message may be stuck in the xmitq because the channel is out of sync?

Try manually starting the channels and check the logs (sender and receiver side) to see what you discover...
Enjoy
_________________
MQ & Broker admin
Back to top
View user's profile Send private message Send e-mail
saneben
PostPosted: Thu Mar 20, 2008 12:25 pm    Post subject: Reply with quote

Voyager

Joined: 04 Apr 2004
Posts: 96
Hi,

Thanks for the Reply,

I have checked the settings under Resources -JMS -> Message MQ -Connection factory ->

QueueManager name is blank

but we are using DataPower(DP) which puts the message to the WAS ,MQ
maty be I have to check the settings on DP.

Regards[/i]
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 » Websphere Application Server -> JMS to MQ
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.