| Author |
Message
|
| kingsean |
 Posted: Thu Sep 11, 2008 2:31 am Post subject: integration of weblogic 9.3.2 and Mq series 6.0 |
 |
|
Novice
Joined: 10 Sep 2008
Posts: 14
|
Iam trying to send mesage from weblogic message bridge to Mq series queue.
my message bridge configuration :
AdapterJNDIName=eis.jms.WLSConnectionFactoryJNDIXA
Classpath=
ConnectionURL = t3://localhost:7001
DestinationType = Queue
DestinationJNDIName = WLSOutgoingQueue
InitialContextFactory = weblogic.jndi.WLInitialContextFactory
ConnectionFactoryJNDIName = DefaultJmsConnectionFactory
>
<Sep 11, 2008 9:50:45 AM IST> <Debug> <MessagingBridgeStartup> <000000> <Bridge MQBridge's target configurations are:
AdapterJNDIName=eis.jms.WLSConnectionFactoryJNDIXA
Classpath=
ConnectionURL = t3://localhost:7001
DestinationType = Queue
DestinationJNDIName = jms/WLMyReplyQueue
InitialContextFactory = weblogic.jndi.WLInitialContextFactory
ConnectionFactoryJNDIName = jms/WLReceiverQCF
>
The target actually points to a foriegn JMS server destinations pointing to Remote Mq Series queue using
file based JNDI bindings .
The connection all works fine as in message bridge status it shows Forwarding messages
but when i try to send message by putting a message in the local queue a trace appears
in weblogic message bridge but it is related to Mq series .
<Sep 8, 2008 5:24:34 PM IST> <Error> <MessagingBridge> <BEA-200015> <An error occurred in bridge "MQBridge" during the transfer of me
ssages (java.lang.Exception: javax.resource.ResourceException: Error sending message
at weblogic.jms.adapter.JMSBaseConnection.throwResourceException(JMSBaseConnection.java:1663)
at weblogic.jms.adapter.JMSBaseConnection.send(JMSBaseConnection.java:794)
at weblogic.jms.adapter.JMSConnectionHandle.send(JMSConnectionHandle.java:144)
at weblogic.jms.bridge.internal.MessagingBridge.processMessages(MessagingBridge.java:1508)
at weblogic.jms.bridge.internal.MessagingBridge.beginForwarding(MessagingBridge.java:1002)
at weblogic.jms.bridge.internal.MessagingBridge.run(MessagingBridge.java:1079)
at weblogic.work.ServerWorkManagerImpl$WorkAdapterImpl.run(ServerWorkManagerImpl.java:518)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:181)
-------------- Linked Exception ------------
javax.resource.ResourceException: Error creating producer or sending message
at weblogic.jms.adapter.JMSBaseConnection.throwResourceException(JMSBaseConnection.java:1663)
at weblogic.jms.adapter.JMSBaseConnection.sendInternal(JMSBaseConnection.java:906)
at weblogic.jms.adapter.JMSBaseConnection.access$200(JMSBaseConnection.java:85)
at weblogic.jms.adapter.JMSBaseConnection$6.run(JMSBaseConnection.java:787)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
at weblogic.security.service.SecurityManager.contact admin(SecurityManager.java:147)
at weblogic.jms.adapter.JMSBaseConnection.send(JMSBaseConnection.java:784)
at weblogic.jms.adapter.JMSConnectionHandle.send(JMSConnectionHandle.java:144)
at weblogic.jms.bridge.internal.MessagingBridge.processMessages(MessagingBridge.java:1508)
at weblogic.jms.bridge.internal.MessagingBridge.beginForwarding(MessagingBridge.java:1002)
at weblogic.jms.bridge.internal.MessagingBridge.run(MessagingBridge.java:1079)
at weblogic.work.ServerWorkManagerImpl$WorkAdapterImpl.run(ServerWorkManagerImpl.java:518)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:181)
-------------- Linked Exception 2 ------------
javax.jms.JMSException: MQJMS2007: failed to send message to MQ queue
at com.ibm.mq.jms.services.ConfigEnvironment.newException(ConfigEnvironment.java:567)
at com.ibm.mq.jms.MQMessageProducer.sendInternal(MQMessageProducer.java:1738)
at com.ibm.mq.jms.MQMessageProducer.send(MQMessageProducer.java:1056)
at com.ibm.mq.jms.MQMessageProducer.send(MQMessageProducer.java:1108)
at weblogic.jms.adapter.JMSBaseConnection.sendInternal(JMSBaseConnection.java:878)
at weblogic.jms.adapter.JMSBaseConnection.access$200(JMSBaseConnection.java:85)
at weblogic.jms.adapter.JMSBaseConnection$6.run(JMSBaseConnection.java:787)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
at weblogic.security.service.SecurityManager.contact admin(SecurityManager.java:147)
at weblogic.jms.adapter.JMSBaseConnection.send(JMSBaseConnection.java:784)
at weblogic.jms.adapter.JMSConnectionHandle.send(JMSConnectionHandle.java:144)
at weblogic.jms.bridge.internal.MessagingBridge.processMessages(MessagingBridge.java:1508)
at weblogic.jms.bridge.internal.MessagingBridge.beginForwarding(MessagingBridge.java:1002)
at weblogic.jms.bridge.internal.MessagingBridge.run(MessagingBridge.java:1079)
at weblogic.work.ServerWorkManagerImpl$WorkAdapterImpl.run(ServerWorkManagerImpl.java:518)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:181)
-------------- Linked Exception 3 ------------
com.ibm.mq.MQException: MQJE001: Completion Code 2, Reason 2072
at com.ibm.mq.MQQueue.putMsg2(MQQueue.java:1680)
at com.ibm.mq.jms.MQMessageProducer.sendInternal(MQMessageProducer.java:1715)
at com.ibm.mq.jms.MQMessageProducer.send(MQMessageProducer.java:1056)
at com.ibm.mq.jms.MQMessageProducer.send(MQMessageProducer.java:1108)
at weblogic.jms.adapter.JMSBaseConnection.sendInternal(JMSBaseConnection.java:878)
at weblogic.jms.adapter.JMSBaseConnection.access$200(JMSBaseConnection.java:85)
at weblogic.jms.adapter.JMSBaseConnection$6.run(JMSBaseConnection.java:787)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
at weblogic.security.service.SecurityManager.contact admin(SecurityManager.java:147)
at weblogic.jms.adapter.JMSBaseConnection.send(JMSBaseConnection.java:784)
at weblogic.jms.adapter.JMSConnectionHandle.send(JMSConnectionHandle.java:144)
at weblogic.jms.bridge.internal.MessagingBridge.processMessages(MessagingBridge.java:1508)
at weblogic.jms.bridge.internal.MessagingBridge.beginForwarding(MessagingBridge.java:1002)
at weblogic.jms.bridge.internal.MessagingBridge.run(MessagingBridge.java:1079)
at weblogic.work.ServerWorkManagerImpl$WorkAdapterImpl.run(ServerWorkManagerImpl.java:518)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:181)
).>
<Sep 8, 2008 5:24:34 PM IST> <Info> <JMS> <BEA-040370> <Linked Exception -----------
javax.resource.ResourceException: Error sending message
at weblogic.jms.adapter.JMSBaseConnection.throwResourceException(JMSBaseConnection.java:1663)
at weblogic.jms.adapter.JMSBaseConnection.send(JMSBaseConnection.java:794)
at weblogic.jms.adapter.JMSConnectionHandle.send(JMSConnectionHandle.java:144)
at weblogic.jms.bridge.internal.MessagingBridge.processMessages(MessagingBridge.java:1508)
at weblogic.jms.bridge.internal.MessagingBridge.beginForwarding(MessagingBridge.java:1002)
at weblogic.jms.bridge.internal.MessagingBridge.run(MessagingBridge.java:1079)
at weblogic.work.ServerWorkManagerImpl$WorkAdapterImpl.run(ServerWorkManagerImpl.java:518)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:181)
>
please suggest any solutions .. thanks in advance |
|
| Back to top |
|
 |
| Gaya3 |
| Posted: Thu Sep 11, 2008 2:35 am Post subject: |
|
|
Jedi
Joined: 12 Sep 2006
Posts: 2493
Location: Boston, US
|
Reason Code 2072 x'818'
MQRC_SYNCPOINT_NOT_AVAILABLE
Either MQGMO_SYNCPOINT was specified on an MQGET call or MQPMO_SYNCPOINT was specified on an MQPUT or MQPUT1 call, but the local queue manager was unable to honor the request. If the queue manager does not support units of work, the SyncPoint queue-manager attribute will have the value MQSP_NOT_AVAILABLE. This reason code can also occur on the MQGET, MQPUT, and MQPUT1 calls when an external unit-of-work coordinator is being used. If that coordinator requires an explicit call to start the unit of work, but the application has not issued that call prior to the MQGET, MQPUT, or MQPUT1 call, reason code MQRC_SYNCPOINT_NOT_AVAILABLE is returned.
Corrective action: Remove the specification of MQGMO_SYNCPOINT or MQPMO_SYNCPOINT, as appropriate. On OS/400, ensure that Commitment Control has been started. If this reason code occurs after Commitment Control has been started, contact your systems programmer.
_________________
Regards
Gayathri
-----------------------------------------------
Do Something Before you Die |
|
| Back to top |
|
|
| kingsean |
| Posted: Thu Sep 11, 2008 2:43 am Post subject: how do remove it ? |
|
|
Novice
Joined: 10 Sep 2008
Posts: 14
|
Remove the specification of MQGMO_SYNCPOINT or MQPMO_SYNCPOINT
is it something I change in the weblogic message bridge or
on MQ Series .
the OS enviroment is windows .
please give me the steps to follow .. iam only starting up on this...
thanks ... |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Thu Sep 11, 2008 3:11 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20697
Location: LI,NY
|
Completion Code 2, Reason 2072 syncpoint not available...
Are you trying to do a multiphase commit without the etc client using a client connection??? 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| kingsean |
| Posted: Thu Sep 11, 2008 3:14 am Post subject: no multi-phase comit . |
|
|
Novice
Joined: 10 Sep 2008
Posts: 14
|
| transaction is container managed (weblogic ) |
|
| Back to top |
|
|
| kingsean |
| Posted: Thu Sep 11, 2008 3:20 am Post subject: current weblogic message bridge configuration |
|
|
Novice
Joined: 10 Sep 2008
Posts: 14
|
New Bridge Name : MQBridge
Quality of Service : Exactly-once
intialize : started
sourceDestinations : Source
Messaging Provider:WLS 7.0 or higher
Target Destinations: Target
Messaging Provider : Other JMS
target : AdminServer |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Thu Sep 11, 2008 3:20 am Post subject: Re: no multi-phase comit . |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20697
Location: LI,NY
|
| kingsean wrote: |
| transaction is container managed (weblogic ) |
| Quote: |
| AdapterJNDIName=eis.jms.WLSConnectionFactoryJNDIXA |
So you are working with an XA QCF ? in Client mode? without the etcclient jar file on the path?
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| kingsean |
| Posted: Thu Sep 11, 2008 3:23 am Post subject: where can i get etcclient.jar ? |
|
|
Novice
Joined: 10 Sep 2008
Posts: 14
|
i didnt know any thing abt etcclient.jar
please advice on which class path i shud put it and were can i get it from .. |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Thu Sep 11, 2008 3:30 am Post subject: Re: where can i get etcclient.jar ? |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20697
Location: LI,NY
|
| kingsean wrote: |
i didnt know any thing abt etcclient.jar
please advice on which class path i shud put it and were can i get it from .. |
Should be in your mq distribution. If not talk to your IBM rep.
Same classpath as were you put the rest of the mq jar files.
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| kingsean |
| Posted: Thu Sep 11, 2008 3:37 am Post subject: no change .. |
|
|
Novice
Joined: 10 Sep 2008
Posts: 14
|
i tried without xa transaction ..
i selected eis.jms.WLSConnectionFactoryJNDINoTX
but still same issue .. |
|
| Back to top |
|
|
| kingsean |
| Posted: Thu Sep 11, 2008 3:39 am Post subject: also.. |
|
|
Novice
Joined: 10 Sep 2008
Posts: 14
|
| moreover the jar : com.ibm.mqetclient.jar is already in the class path |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Thu Sep 11, 2008 3:42 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20697
Location: LI,NY
|
Transactionality setting on the ejb/MDB method ??
Beyond that open a PMR....
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| kingsean |
| Posted: Thu Sep 11, 2008 3:55 am Post subject: not involved |
|
|
Novice
Joined: 10 Sep 2008
Posts: 14
|
there is no EJB/MDB involved ..
Iam using a standalone client to put message into a local JMS queue
in weblogic . that acts as the source for the bridge . |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Thu Sep 11, 2008 9:37 am Post subject: Re: not involved |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20697
Location: LI,NY
|
| kingsean wrote: |
there is no EJB/MDB involved ..
Iam using a standalone client to put message into a local JMS queue
in weblogic . that acts as the source for the bridge . |
If that is truely the case you are violating best practice J2EE.
Get back to the design drawing board!.
If you are using standalone JMS to put a message to the queue verify the transactionality attribute of the qmgr. (runmqsc dis qmgr syncpt). I believe this is a read only attribute. It may well be that your qmgr does not support syncpointing UOWs.
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| kingsean |
| Posted: Sun Sep 14, 2008 9:20 pm Post subject: it is available |
|
|
Novice
Joined: 10 Sep 2008
Posts: 14
|
I ran the command :
display QMGR SYNCPT
but no output is coming only this:
D:\>RUNMQSC ICARGO_QMGR
5724-H72 (C) Copyright IBM Corp. 1994, 2004. ALL RIGHTS RESERVED.
Starting MQSC for queue manager ICARGO_QMGR.
DISPLAY QMGR SYNCPT
1 : DISPLAY QMGR SYNCPT
AMQ8408: Display Queue Manager details.
QMNAME(ICARGO_QMGR) SYNCPT
It should be available ..my OS is Windows NT ... this is what i saw in
MQSC documentation:
SYNCPT
Whether syncpoint support is available with the queue manager. On OS/2
Warp, OS/390, OS/400, UNIX systems, and Windows NT it is always
available.
so what should i do to get a MQ series to support Sync Point and so that messges will be forwarded from the Weblogic Bridge .
thanks for all.. |
|
| Back to top |
|
|
|
|
