| Author |
Message
|
| princy |
 Posted: Fri Feb 04, 2005 3:14 pm Post subject: WBI ICS MQConnector mqjms2007 error |
 |
|
Newbie
Joined: 13 Jan 2005
Posts: 3
|
Dear All,
When using the WBI ICS MQ adapter to put messages from a Window 2000 Server to a OS/390 queue manager the first PUT to the queue
fails with a mqjms2007 error.linked exception mqjms2007.
This happens only when the WBI MQ connector is started and there is no activity in the connector for long time and then when tried to put the messages.
WBI connector uses jms session caching and here is the part of error log.
Has anyone seen this with WBI MQ connector?
[Time: 2004/12/13 09:33:45.532] [System: ConnectorAgent] [SS: PJT_Connector] [Thread: WT=752 (#356286507)] [Type: Error] [MsgID: 27004] [Mesg: Failed to put message (no ID assigned) in destination queue://PJQM/PJT.MEM.PRODUCER.COMP?CCSID=500&targetClient=1. JMS Provider (IBM) reported the following error: MQJMS2007: failed to send message to MQ queue. LinkedException: MQJMS2007: failed to send message to MQ queue.]
[Time: 2004/12/13 09:33:45.532] [System: ConnectorAgent] [SS: PJT_Connector] [Thread: WT=752 (#356286507)] [Type: Trace] [Mesg: :JMSSessionCache: Entering method getInstance.]
[Time: 2004/12/13 09:33:45.532] [System: ConnectorAgent] [SS: PJT_Connector] [Thread: WT=752 (#356286507)] [Type: Trace] [Mesg: :JMSSessionCache: Exiting method getInstance.]
[Time: 2004/12/13 09:33:45.532] [System: ConnectorAgent] [SS: PJT_Connector] [Thread: WT=752 (#356286507)] [Type: Trace] [Mesg: :JMSSessionCache: Entering method returnMessageProducer .]
[Time: 2004/12/13 09:33:45.532] [System: ConnectorAgent] [SS: PJT_Connector] [Thread: WT=752 (#356286507)] [Type: Trace] [Mesg: :JMSSessionCache: Exiting method returnMessageProducer .]
[Time: 2004/12/13 09:33:45.532] [System: ConnectorAgent] [SS: PJT_Connector] [Thread: WT=752 (#356286507)] [Type: Error] [MsgID: 21010] [Mesg: Failed to complete processing due to an unrecoverable error. See previous error message(s) for details and correct the situation before continuing.]
[Time: 2004/12/13 09:33:45.532] [System: ConnectorAgent] [SS: PJT_Connector] [Thread: WT=752 (#356286507)] [Type: Trace] [Mesg: :JMSSessionCache: Entering method getInstance.]
[Time: 2004/12/13 09:33:45.532] [System: ConnectorAgent] [SS: PJT_Connector] [Thread: WT=752 (#356286507)] [Type: Trace] [Mesg: :JMSSessionCache: Exiting method getInstance.]
[Time: 2004/12/13 09:33:45.532] [System: ConnectorAgent] [SS: PJT_Connector] [Thread: WT=752 (#356286507)] [Type: Trace] [Mesg: :JMSSessionCache: Entering method returnSession .]
[Time: 2004/12/13 09:33:45.532] [System: ConnectorAgent] [SS: PJT_Connector] [Thread: WT=752 (#356286507)] [Type: Trace] [Mesg: :JMSSessionCache: Exiting method returnSession .]
[Time: 2004/12/13 09:33:45.532] [System: ConnectorAgent] [SS: PJT_Connector] [Thread: WT=752 (#356286507)] [Type: Error] [MsgID: 21003] [Mesg: Failed in doVerbFor for business object CALLIDUS_MEMBERSHIP with verb Create. Explanation provided to InterChange server: [Type: Error] [MsgID: 27004] [Mesg: Failed to put message (no ID assigned) in destination queue://PJQM/PJT.MEM.PRODUCER.COMP?CCSID=500&targetClient=1. JMS Provider (IBM) reported the following error: MQJMS2007: failed to send message to MQ queue. LinkedException: MQJMS2007: failed to send message to MQ queue.] .]
[Time: 2004/12/13 09:33:45.532] [System: ConnectorAgent] [SS: PJT_Connector] [Thread: WT=752 (#356286507)] [Type: Trace] [Mesg: :BaseBOHandler: Exiting method doVerbFor for business object CALLIDUS_MEMBERSHIP.Create, return value = Integer -2.]
[Time: 2004/12/13 09:33:45.532] [System: ConnectorAgent] [SS: PJT_Connector] [Thread: WT=752 (#356286507)] [Type: Trace] [Mesg: :Error in AgentBOM.DoVerbFor - rtnObj.status = -2 rtnObj.message = [Type: Error] [MsgID: 27004] [Mesg: Failed to put message (no ID assigned) in destination queue://PTQM/PJT.MEM.PRODUCER.COMP?CCSID=500&targetClient=1. JMS Provider (IBM) reported the following error: MQJMS2007: failed to send message to MQ queue. LinkedException: MQJMS2007: failed to send message to MQ queue.] ] |
|
| Back to top |
|
 |
| csmith28 |
| Posted: Fri Feb 04, 2005 4:13 pm Post subject: |
|
|
Grand Master
Joined: 15 Jul 2003
Posts: 1196
Location: Arizona
|
OK,
| Quote: |
2007 X’07D7’ MQRC_CHAR_ATTRS_ERROR
CharAttrs is not valid. The parameter pointer is not valid, or points to read-only storage for
MQINQ calls or to storage that is not as long as implied by CharAttrLength. (It is not always
possible to detect parameter pointers that are not valid; if not detected, unpredictable results
occur.)
Corrective action: Correct the parameter. |
That is what the WMQ Message Guide say about WMQ return Code 2007 but I don't think that is the same as MQJMS2007: failed to send message to MQ queue and I didn't really see anything that was identifiable as a WMQ return code.
Have you tried searching the IBM site or Google for MQJMS2007?
This appears to be more of a JMS issue than MQ. Please post more details.
_________________
Yes, I am an agent of Satan but my duties are largely ceremonial. |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Fri Feb 04, 2005 5:47 pm Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
Actually, I'm sure there's a real Reason Code and Completion Code hidden inside that JMS exception.
It just seems that whoever wrote the connector/adapter code decided not to make that information available.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| csmith28 |
| Posted: Fri Feb 04, 2005 5:56 pm Post subject: |
|
|
Grand Master
Joined: 15 Jul 2003
Posts: 1196
Location: Arizona
|
Is it just me or are programmers their own worst enemy?
_________________
Yes, I am an agent of Satan but my duties are largely ceremonial. |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Sat Feb 05, 2005 4:15 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
| csmith28 wrote: |
| Is it just me or are programmers their own worst enemy? |
Since I sit on both sides of the fence on this issue... I can't agree. But I can't disagree either.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| vennela |
| Posted: Sat Feb 05, 2005 4:34 pm Post subject: |
|
|
Jedi Knight
Joined: 11 Aug 2002
Posts: 4055
Location: Hyderabad, India
|
| From the windows QMGR, can you put the message to that particular queue. |
|
| Back to top |
|
|
| princy |
| Posted: Mon Feb 07, 2005 12:04 pm Post subject: WBI ICS MQConnector mqjms2007 error |
|
|
Newbie
Joined: 13 Jan 2005
Posts: 3
|
Thanks everyone for the inputs.
let me provide some more information.
Say the WBI conector is started and the data is passed immediately, everything works as expected.
Now say after a day, when tried to send say 25 messages, (using the cached sessions)the first couple of messages fails( is put to the failed flow) and the rest goes through fine.
Also, when the conector gets the mqjms2007, it tries to close the connection(disconect) and then it gets the linked exception 2009(connection broken).
At mainframe side we see a lot of CSQX208E error receiving data , with tcp return code 461 (connection reset by peer) |
|
| Back to top |
|
|
| csmith28 |
| Posted: Mon Feb 07, 2005 12:31 pm Post subject: |
|
|
Grand Master
Joined: 15 Jul 2003
Posts: 1196
Location: Arizona
|
Sounds like your having intermittent network connectivity issues either between your app and the JMS Provider or your MQManager.
_________________
Yes, I am an agent of Satan but my duties are largely ceremonial. |
|
| Back to top |
|
|
| princy |
| Posted: Mon Feb 07, 2005 2:09 pm Post subject: WBI ICS MQConnector mqjms2007 error |
|
|
Newbie
Joined: 13 Jan 2005
Posts: 3
|
yes, looks like the intermittant network problems are causing the connection to end.
But WBI connector should be able to reconnect/recover after a network problem right? Currently, it looks like after it gets a mqjms2007, the 'inflight messages' during failure is been put to the failed flow.
Any thoghts? |
|
| Back to top |
|
|
| csmith28 |
| Posted: Mon Feb 07, 2005 2:49 pm Post subject: Re: WBI ICS MQConnector mqjms2007 error |
|
|
Grand Master
Joined: 15 Jul 2003
Posts: 1196
Location: Arizona
|
| princy wrote: |
yes, looks like the intermittant network problems are causing the connection to end.
But WBI connector should be able to reconnect/recover after a network problem right? Currently, it looks like after it gets a mqjms2007, the 'inflight messages' during failure is been put to the failed flow.
Any thoghts? |
That will be determined by the application code not to mention the network.
_________________
Yes, I am an agent of Satan but my duties are largely ceremonial. |
|
| Back to top |
|
|
|
|
