| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Reason Code: 2019, Failing Object: BPI.BPIGRP.EXE |
« View previous topic :: View next topic » |
| Author |
Message
|
| chintu |
 Posted: Wed Sep 10, 2008 12:07 pm Post subject: Reason Code: 2019, Failing Object: BPI.BPIGRP.EXE |
 |
|
Acolyte
Joined: 27 Dec 2004
Posts: 64
|
FMC38009E MQSeries Workflow API Error :
API Return Code : 13
Error Origin : FmcSession.java
Error Message : FMC00013E Communication error - Failing Action: put, Reason Code: 2019, Failing Object: BPI.BPIGRP.EXE.
Nested Exception : None
at com.ws.bpi.workflow.service.Workflow.createProcessInstance(Workflow.java(Compiled Code))
We see this error intermittently in our custom webclient(using WF java api 3.6) logs when we call create and start process instance method.
AIX 5.3
MQ 6.0.2.3
WAS 6.1
WF 3.6
We moved from a single tier WF setup to distributed and clustered WF setup. Here is our topology change
FROM
WF,MQ,Websphere app server,db2 on Box A
TO
WF,MQ,Websphere on BoxA(BPI.BPIGRP.BPISYS,BPIWFQM)
WF,MQ,Websphere on BoxB(BPI.BPIGRP.BPISYS2,SRAC001A)
db2 on BoxC
http://www-01.ibm.com/support/docview.wss?uid=swg21190196
I saw some posts with the same error message...but on z/OS. Has anyone seen this error on AIX? Could a topology change cause this. When we changed our topology...we dropped and recreated WF configurations on both A and B boxes. Now we see this error on both A and B..however intermittently.
Any help or suggestion is highly appreciated. Thanks |
|
| Back to top |
|
 |
| jmac |
| Posted: Wed Sep 10, 2008 2:03 pm Post subject: |
|
|
Jedi Knight
Joined: 27 Jun 2001
Posts: 3081
Location: EmeriCon, LLC
|
Ive not run into this error before and when I look it up in the Messages and Codes it appears to indicate that this is a zOS error (as you seem to have seen also). I would say this is PMR material.
_________________
John McDonald
RETIRED |
|
| Back to top |
|
|
| Gaya3 |
| Posted: Wed Sep 10, 2008 10:00 pm Post subject: |
|
|
Jedi
Joined: 12 Sep 2006
Posts: 2493
Location: Boston, US
|
Reason Code 2019 x'7E3'
MQRC_HOBJ_ERROR
The object handle Hobj is not valid. If the handle is a shareable handle, the handle may have been made invalid by another thread issuing the MQCLOSE call using that handle. If the handle is a nonshareable handle, the call may have been issued by a thread that did not create the handle. This reason also occurs if the parameter pointer is not valid, or (for the MQOPEN call) points to read-only storage. (It is not always possible to detect parameter pointers that are not valid; if not detected, unpredictable results occur.)
Corrective action: Ensure that a successful MQOPEN call is performed for this object, and that an MQCLOSE call has not already been performed for it. For MQGET and MQPUT calls, also ensure that the handle represents a queue object. Ensure that the handle is being used within its valid scope.
_________________
Regards
Gayathri
-----------------------------------------------
Do Something Before you Die |
|
| Back to top |
|
|
| chintu |
| Posted: Mon Sep 15, 2008 6:33 am Post subject: |
|
|
Acolyte
Joined: 27 Dec 2004
Posts: 64
|
| Thanks for your reply John and Gayathri. I will post the response that we get back from IBM. |
|
| Back to top |
|
|
|
|
|
| |
|
Page 1 of 1 |
|
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
|
|
|
|
