| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| [SOLVED]Mysterious FMC0100805E Error In Dead Queue |
« View previous topic :: View next topic » |
| Author |
Message
|
| jmeier |
 Posted: Wed Feb 12, 2003 11:03 am Post subject: [SOLVED]Mysterious FMC0100805E Error In Dead Queue |
 |
|
Apprentice
Joined: 30 Aug 2002
Posts: 46
Location: Minneapolis
|
I have a mysterious message showing up on the dead letter queue. It shows up 1 time per process instance. There are several processes that execute during the workflow process instance, and we think that the last process prior to ending, causes workflow to return the message.
The return code on the message is: 805.
The Reason Code on the message is: 2085 (Unknown object name)
The text of the message is: “FMC00805E OID for Persistent Object() not valid”.
The queues that I send and read messages from are all Persistent. The program that ends the process instance just returns a return code and another id that are used by workflow to go on. All the other programs in the process return the same values. We are at a loss as to why this is occurring on this 1 program.
For a little background the program that seems to be causing the bad message is running on Windows 2000, which is where the queues reside. Workflow is running on Unix. I reply back to the exexmlinput queue (Unix) on all the programs when sending a return code.
Several of us are scratching our heads on this one, so any help is appreciated.
Thanks.
_________________
Joe Meier |
|
| Back to top |
|
 |
| vennela |
| Posted: Wed Feb 12, 2003 12:38 pm Post subject: |
|
|
Jedi Knight
Joined: 11 Aug 2002
Posts: 4055
Location: Hyderabad, India
|
I think this message is because of this:
When you PUT an XML message and in that you specify
ResponseRequired to YES
ReplyToQ
and ReplyToQMGR etc
I think the ReplyToQ or ReplyToQMGR or both of them are not defined or not known to the MQWF QMGR.
I may be completely wrong here but that's what I think is happening.
Soemthing to est tonight
-------
Venny |
|
| Back to top |
|
|
| Ratan |
| Posted: Wed Feb 12, 2003 12:59 pm Post subject: |
|
|
Grand Master
Joined: 18 Jul 2002
Posts: 1245
|
Venny, I dont think so. Reply2Q and Reply2QM are for ProcessResponse messages. This message doesnot appear to be caused by a bad XML format.
My Guess, I believe you are making a OID access call for an object that no longer exists. As you said it is caused by the last process activity in your process model, I would double check that I am not making any unwanted OID calls.
-Laze. |
|
| Back to top |
|
|
| jmac |
| Posted: Wed Feb 12, 2003 1:21 pm Post subject: |
|
|
Jedi Knight
Joined: 27 Jun 2001
Posts: 3081
Location: EmeriCon, LLC
|
Joe:
Is it possible that this instance runs so quickly, that by the time the Response message is being generated the Instance has already terminated. This sounds pretty unlikely to me, but I think it could generate the situation you are observing
GOOD LUCK
_________________
John McDonald
RETIRED |
|
| Back to top |
|
|
| jmeier |
| Posted: Thu Feb 13, 2003 10:37 am Post subject: |
|
|
Apprentice
Joined: 30 Aug 2002
Posts: 46
Location: Minneapolis
|
Well I tried the tip about ResponseRequired, and as some of you thought, that didn't fix the problem - however, having the ResponseRequired set to IfError is probably a good idea in my code - the problem was being caused by the process prior to the end process. I slowed down my application so that I could tell when this message was being sent back. What was happening is the process that puts a message to the queue, isn't a workflow process, it is a homegrown notification application. I read the message and respond back to workflow which then freaks out and sends a message back to the dead queue. Thanks folks for all your help.
_________________
Joe Meier |
|
| 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
|
|
|
|
