Author |
Message
|
MSAT |
Posted: Tue Dec 27, 2005 10:04 pm Post subject: WorkFlow Adapter Issue |
|
|
Acolyte
Joined: 17 Aug 2005 Posts: 62 Location: Bengalooru
|
Hi,
We are using WorkFlow 3.5 and and Workflow Adapter 2.7 with ICS 4.3, MQ Series 5.3, DB2 8.1 + FP2
We are getting the below error messages in the Worklow adapter log
--------------------------------------------------------------------------------
Failed to connect to queue "MQWFCONN.ARCHIVE". WebSphere MQ reported the following error: MQJE001: Completion Code 2, Reason 2009 [Connection broken].
Application call to method poll() returned failure. The application could not be contacted.
--------------------------------------------------------------------------------
After this the connector was able to establish connection to the Queue Manager... But it goes into inconsistent state indicating below error
--------------------------------------------------------------------------------
Exception caught in the method BusObjJavaInterface::poll. Reason: java.lang.IllegalStateException: Cannot retrieve next message without accepting last
The call to method poll() in the application connector failed.
--------------------------------------------------------------------------------
What might be the problem ?
One thing to be noted here is this problem never occured for around 1 month, but now we are facing this issue after restarting the servers.
Thanks in advance
sat |
|
Back to top |
|
 |
vennela |
Posted: Wed Dec 28, 2005 8:43 am Post subject: |
|
|
 Jedi Knight
Joined: 11 Aug 2002 Posts: 4055 Location: Hyderabad, India
|
What is the state of your QMANAGER? |
|
Back to top |
|
 |
kotha |
Posted: Wed Dec 28, 2005 5:50 pm Post subject: |
|
|
Partisan
Joined: 12 Mar 2005 Posts: 333
|
clear the messages in the UPES Queue and try again. Make sure all the queue mentioned in the connector are working properly. this might resolve your issue as there is inconsistancy after you restart the server. |
|
Back to top |
|
 |
MSAT |
Posted: Wed Dec 28, 2005 10:44 pm Post subject: |
|
|
Acolyte
Joined: 17 Aug 2005 Posts: 62 Location: Bengalooru
|
Hi,
Thanks for the reply.
The adpter will be in the running state after restart and it was able to function preperly. But in between if the connection brekas between the server qhere queue manager running and the server where the adpter is running then the adapter tries to establish the connection again, and also it succeds. after this it goes into inconsistence state throwing above mentioned errors in the log file.
We are not able to find why it is happening.
Thanks
Sat |
|
Back to top |
|
 |
vennela |
Posted: Thu Dec 29, 2005 1:00 pm Post subject: |
|
|
 Jedi Knight
Joined: 11 Aug 2002 Posts: 4055 Location: Hyderabad, India
|
Are you client connecting to the workflow queues? |
|
Back to top |
|
 |
Nupiman |
Posted: Thu Jan 19, 2006 9:24 am Post subject: |
|
|
Newbie
Joined: 27 Sep 2005 Posts: 7 Location: Germany
|
Hello,
I am facing similar errors:
Code: |
[Time: 2006/01/19 11:37:34.836] [System: ConnectorAgent] [SS: WebSphereMQWorkflo
wConnector] [Thread: appPolling (#1214050043)] [Type: Trace] [Mesg: :MQWorkflowC
onnectorAgent: Polling for messages: iteration 1/1.]
[Time: 2006/01/19 11:37:34.836] [System: ConnectorAgent] [SS: WebSphereMQWorkflo
wConnector] [Thread: appPolling (#1214050043)] [Type: Error] [MsgID: 17109] [Mes
g: Exception caught in the method BusObjJavaInterface::poll. Reason: java.lang.I
llegalStateException: Cannot retrieve next message without accepting last]
[Time: 2006/01/19 11:37:34.836] [System: ConnectorAgent] [SS: WebSphereMQWorkflo
wConnector] [Thread: appPolling (#1214050043)] [Type: Trace] [Mesg: :checkStatus
]
[Time: 2006/01/19 11:37:34.836] [System: ConnectorAgent] [SS: WebSphereMQWorkflo
wConnector] [Thread: appPolling (#1214050043)] [Type: Error] [MsgID: 17050] [Mes
g: The call to method poll() in the application connector failed.]
|
The unusual is that the scenario works correct for one time (i.e. the adapter receives and sends messages correctly). And after trying the second time it doesn`t poll its input queue where the MQ Workflow output message remains
Did anyone here solve this issue?
I am looking forward to your ideas.
Thanks,
Sebastian |
|
Back to top |
|
 |
vennela |
Posted: Thu Jan 19, 2006 10:06 am Post subject: |
|
|
 Jedi Knight
Joined: 11 Aug 2002 Posts: 4055 Location: Hyderabad, India
|
Increase the trace level and see if you can find out why the message is not being parsed correctly |
|
Back to top |
|
 |
Nupiman |
Posted: Fri Jan 20, 2006 12:21 am Post subject: |
|
|
Newbie
Joined: 27 Sep 2005 Posts: 7 Location: Germany
|
Hello Vennela,
thanks for your posting!
The issue was an uncorrect referred ARCHIVE-queue... so I renamed this queue and everything works fine now
Thanks
Sebastian |
|
Back to top |
|
 |
|