MQSeries.net :: View topic - [WICSv4.3] ICS downs!?

MQSeries.net

Tech Exchange

Education

Certifications

Library

Info Center

SupportPacs

FAQÂ Â

Usergroups

RSS Feed - WebSphere MQ Support

RSS Feed - Message Broker Support

MQSeries.net Forum Index » WebSphere Interchange Server + Adapters » [WICSv4.3] ICS downs!?

[WICSv4.3] ICS downs!?

« View previous topic :: View next topic »

Author

Message

JYama

Posted: Thu Mar 10, 2005 6:18 pm Post subject: [WICSv4.3] ICS downs!?

Master

Joined: 27 Mar 2002
Posts: 281

Hi all,

I'm in trouble with ICSv4.3 on Win2K and got this error below.
I have no idea what's going on.

Is there anybody who is familiar with this kind of situation?

When I posted an event to an adapter, the event was successfully processed and sent to the target adapter through the collaboration. However, an additional event, which was exactly the same as the previous one, was automatically posted again to the target adapter.
When the target adapter sent back its response, then, the ICS downed!(I'm using VTCs, BTW.)

Thanks in advance,

Quote:

[Time: 2005/03/11 10:34:15.281] [System: ConnectorController] [SS: WebServicesCo
nnector] [Thread: WebServicesConnectorThreadPool.thread1 (#1082795412)] [Type: T
race] [Mesg: After mapping <StartHeader>
<Version = 3.0>
<EndHeader>
<StartBO:BO_ORDERS>
BusinessObject = BO_ORDERS
Verb = Create
Locale = en
ORDERDATE = CxIgnore
ITEM = 222
QTY = 33
STAT = 4
ObjectEventId = WebServicesConnector_1110504825187_3
<EndBO:BO_ORDERS>]
[Time: 2005/03/11 10:34:15.291] [System: ConnectorController] [SS: WebServicesCo
nnector] [Thread: WebServicesConnectorThreadPool.thread1 (#1082795412)] [Type: T
race] [Mesg: Delivering Business Object: BO_ORDERS to CO_ORDER_CREATE_SAP]
MQJE001: 完了コード 2、理由 2033
[Time: 2005/03/11 10:34:17.724] [System: Collaboration] [SS: CO_ORDER_CREATE_SAP
] [Thread: CO_ORDER_CREATE_SAP.thread1 (#1090479508)] [Type: Error] [MsgID: 1105
6] [Mesg: The server will be shut down because the collaboration cannot delete e
vent BO_ORDERS.Create from persistent storage. Business object keys = ORDERDATE
=null.Reason:A recovered event at message ID 00000000000000000000000000000000000
0000000000000 could not be removed from the messagingqueue for connector WebServ
icesConnector after it had been processed. Reason: MQSeries:Completion code 2 Re
ason code 2033]
[Time: 2005/03/11 10:34:17.734] [System: Server] [Thread: CO_ORDER_CREATE_SAP.th
read1 (#1090479508)] [Type: Info] [MsgID: 300] [Mesg: InterChange Server "ICS43"
is shutdown immediately.]

csmith28

Posted: Thu Mar 10, 2005 6:24 pm Post subject:

Grand Master

Joined: 15 Jul 2003
Posts: 1196
Location: Arizona

2033 Xâ€™07F1â€™ MQRC_NO_MSG_AVAILABLE
An MQGET call was issued, but there is no message on the queue satisfying the selection
criteria specified in MQMD (the MsgId and CorrelId fields), and in MQGMO (the Options and
MatchOptions fields). Either the MQGMO_WAIT option was not specified, or the time interval
specified by the WaitInterval field in MQGMO has expired. This reason is also returned for
an MQGET call for browse, when the end of the queue has been reached.
This reason code can also be returned by the mqGetBag and mqExecute calls. mqGetBag is
similar to MQGET. For the mqExecute call, the completion code can be either
MQCC_WARNING or MQCC_FAILED:
v If the completion code is MQCC_WARNING, some response messages were received
during the specified wait interval, but not all. The response bag contains system-generated
nested bags for the messages that were received.
v If the completion code is MQCC_FAILED, no response messages were received during the
specified wait interval.
Corrective action: If this is an expected condition, no corrective action is required.
If this is an unexpected condition, check that:
v The message was put on the queue successfully.
v The unit of work (if any) used for the MQPUT or MQPUT1 call was committed
successfully.
v The options controlling the selection criteria are specified correctly. All of the following can
affect the eligibility of a message for return on the MQGET call:
MQGMO_LOGICAL_ORDER
MQGMO_ALL_MSGS_AVAILABLE
MQGMO_ALL_SEGMENTS_AVAILABLE
MQGMO_COMPLETE_MSG
MQMO_MATCH_MSG_ID
MQMO_MATCH_CORREL_ID
MQMO_MATCH_GROUP_ID
MQMO_MATCH_MSG_SEQ_NUMBER
MQMO_MATCH_OFFSET
Value of MsgId field in MQMD
Value of CorrelId field in MQMD
Consider waiting longer for the message.
_________________
Yes, I am an agent of Satan but my duties are largely ceremonial.

JYama

Posted: Thu Mar 10, 2005 6:43 pm Post subject:

Master

Joined: 27 Mar 2002
Posts: 281

Thank you very much for your information.

Let me clarify the issue.

First of all, please make sure that I know this MQ 2033 error is a common bug of ICS and it's just an internal process so that we can ignore it this time. (It doesn't harm the ICS processes.)

My questions are;
1. Why duplicated events were posted?
2. What is the message with message ID 0000000000000000000000000? (Who created it?)
3. Why ICS downed immedeately?

I have never seen this problem with older version...

Thanks,

csmith28

Posted: Thu Mar 10, 2005 7:16 pm Post subject:

Grand Master

Joined: 15 Jul 2003
Posts: 1196
Location: Arizona

Yes well, right then.... You are Welcome for the information. But if you are so sure you

Quote:

know this MQ 2033 error is a common bug of ICS and it's just an internal process so that we can ignore it this time.

then WMQ must be performing as expected so I'm not sure why you are your posting your ICS problem here? This isn't www.ics.net, it is www.mqseries.net.

1. Since WMQ doesn't post ICS events, I would say "dunno".
2. Since WMQ doesn't create messages I would say ICS.
3. Since (as far as I know) WMQ doesn't tend to have authority over ICS Processes I would have to assume that ICS shut itself down.
_________________
Yes, I am an agent of Satan but my duties are largely ceremonial.

vennela

Posted: Thu Mar 10, 2005 7:58 pm Post subject:

Jedi Knight

Joined: 11 Aug 2002
Posts: 4055
Location: Hyderabad, India

What does the ICS log say?

csmith28

Posted: Thu Mar 10, 2005 8:05 pm Post subject:

Grand Master

Joined: 15 Jul 2003
Posts: 1196
Location: Arizona

I think it said:

Quote:

But I could be wrong.
_________________
Yes, I am an agent of Satan but my duties are largely ceremonial.

JYama

Posted: Thu Mar 10, 2005 8:57 pm Post subject:

Master

Joined: 27 Mar 2002
Posts: 281

Thank you so much for your support.

I built another simple collaboration and got exactly the same error when I posted an event. (I can't see any errors in the Flow Manager.)

Additionally, I tried to use a real JDBC adapter instead of VTC but my situation didn't change.

I think if I find the reason for the duplicated events, this MQ problem will be solved, because the second event should not be posted and this additional event may be the reason for MQ 2033 error.

,,,,I'm still not sure why two events were created by one event posting.
Maybe an environmental problem?

Quote:

[Time: 2005/03/11 13:29:04.443] [System: ConnectorController] [SS: JDBCConnector
] [Thread: CO_JustInOut.thread1 (#1104794058)] [Type: Trace] [Mesg: Received Ack
response in lieu of BusObj. Status: 0 Cookie: Fri Mar 11 13:26:27 JST 2005]
[Time: 2005/03/11 13:29:04.443] [System: ConnectorController] [SS: JDBCConnector
] [Thread: CO_JustInOut.thread1 (#1104794058)] [Type: Trace] [Mesg: Delivering A
cknowledgement for Business Object: BO_USER_ORDER to CO_JustInOut]
[Time: 2005/03/11 13:29:04.443] [System: ConnectorController] [SS: JDBCConnector
] [Thread: CO_JustInOut.thread1 (#1104794058)] [Type: Trace] [Mesg: removePendLi
st Cookie: Fri Mar 11 13:26:27 JST 2005]
MQJE001: 完了コード 2、理由 2033
[Time: 2005/03/11 13:29:04.443] [System: Collaboration] [SS: CO_JustInOut] [Thre
ad: CO_JustInOut.thread1 (#1104794058)] [Type: Error] [MsgID: 11056] [Mesg: The
server will be shut down because the collaboration cannot delete event BO_USER_O
RDER.Update from persistent storage. Business object keys = ORDERDATE=2005-10-1
0.Reason:A recovered event at message ID 000000000000000000000000000000000000000
000000000 could not be removed from the messagingqueue for connector JDBCConnect
or after it had been processed. Reason: MQSeries:Completion code 2 Reason code 2
033]
[Time: 2005/03/11 13:29:04.443] [System: Server] [Thread: CO_JustInOut.thread1 (
#1104794058)] [Type: Info] [MsgID: 300] [Mesg: InterChange Server "ICS43" is shu
tdown immediately.]

BTW, the reason I posted a message onto this site was that ICS is a part of MQ family under WebSphere brand and I found a couple of postings about ICS on this site.

fschofer

Posted: Fri Mar 11, 2005 1:49 am Post subject:

Knight

Joined: 02 Jul 2001
Posts: 524
Location: Mainz, Germany

Hi,
please post your connector configuration.

In particular the queues you are using.

Greetings
Frank

malammik

Posted: Fri Mar 11, 2005 12:20 pm Post subject:

Partisan

Joined: 27 Jan 2005
Posts: 397
Location: Philadelphia, PA

Make sure that your AP/CONNECTORNAME/ICSNAME queue is not being emptied by some other process while MQ connector is trying to process that event.
_________________
Mikhail Malamud
http://www.netflexity.com
http://groups.google.com/group/qflex

JYama

Posted: Sun Mar 13, 2005 6:00 pm Post subject:

Master

Joined: 27 Mar 2002
Posts: 281

Hello everybody,

Thank you very much again for your help.

I observed MQ queues related to event delivery process of the adapters.

I have two queues, AP/WEBSERVICESCONNECTOR/ICS43 and AP/SAPCONNECTOR/ICS43 and both of them were empty before posting an event. (WebServices adapter is the front of the collaboration.)
In Addition, it seemd that two queues were opened by two processes each(input/output mode)

I used VTCs to simulate WebServices and mySAP.com adapters.

When I posted an event through WS adapter, the event was queued into AP/WEBSERVICESCONNECTOR/ICS43 and then it reached the target adapter(mySAP.com) and I could see the event received by the VTC(target).

I replied it from the VTC(target)., it seemed that this event was processed successfully because there're no error messages both in the console and logs, and also AP/WEBSERVICESCONNECTOR/ICS43 was cleared.

However, the target adapter received an additional event, which was the same as the previous event.
At this time, AP/WEBSERVICESCONNECTOR/ICS43 was totally empty, BTW.
When I replied it again, my ICS downed immediately. (The log message was attached to my past postings.)

I have no idea what's going on...

As additional information, there're no errors in the Flow Manager.

JYama

Posted: Sun Apr 24, 2005 8:48 pm Post subject:

Master

Joined: 27 Mar 2002
Posts: 281

I found that the duplicate events depend on MQ CSD level.

We must use MQ CSD7 with WICS v4.3.
http://www-1.ibm.com/support/docview.wss?rs=100&q1=4.3+multiple&uid=swg21203918&loc=en_US&cs=utf-8&lang=en

bschelst

Posted: Tue Oct 11, 2005 12:08 pm Post subject:

Novice

Joined: 30 May 2004
Posts: 16

JYama wrote:

Hello,

Is MQ CSD07 also needed for remote queue managers?

So: ICS on machine 1 with MQ 5.3 CSD 07
Machine 2, with remote queues to machine 1 with CSD 09

Is that valid?

djeripo

Posted: Wed Oct 12, 2005 8:44 am Post subject:

Master

Joined: 25 Jan 2004
Posts: 225

No.You should have WebSphere MQ 5.3 CSD 07 on both.

hopsala

Posted: Wed Oct 12, 2005 9:53 am Post subject:

Guardian

Joined: 24 Sep 2004
Posts: 960

CSD08 and CSD09 have been withdrawn due to the discovery of critical bugs, see CSD08 AND CSD09.

Display posts from previous:

Page 1 of 1

MQSeries.net Forum Index » WebSphere Interchange Server + Adapters » [WICSv4.3] ICS downs!?

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