| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| FMC00118E |
« View previous topic :: View next topic » |
| Author |
Message
|
| paoloz |
 Posted: Thu Apr 05, 2007 10:44 pm Post subject: FMC00118E |
 |
|
Novice
Joined: 31 Dec 2004
Posts: 12
|
It is driving me crazy. 
The environment: MQ Workflow 3.4 running on z/OS system and using DB2 version 7.
The problem: User Administrator who makes a refresh of his worklist. Selecting an item in "ready" state, he gets "Object does not exist".
The question: Considering that:
- no other users had worked out that item;
- no automatic processing (Expiration time) had occurred, but mainly,
- making several refresh, he see it always in "ready" state
... HOW CAN BE POSSIBLE ? ...
Is it something related to the process, or something related to the system ?
Please help me.
Paolo Zappaterreno |
|
| Back to top |
|
 |
| jmac |
| Posted: Fri Apr 06, 2007 5:43 am Post subject: |
|
|
Jedi Knight
Joined: 27 Jun 2001
Posts: 3081
Location: EmeriCon, LLC
|
|
| Back to top |
|
|
| hos |
| Posted: Wed Apr 11, 2007 6:46 am Post subject: |
|
|
Chevalier
Joined: 03 Feb 2002
Posts: 470
|
I am almost sure that this is an URL-encoding problem.
If you use your own client implementation the Technote referred by John is the solution.
However it can also be a bug in your WebSphere version. They used to have URL-encode -decode problems in specific versions of WebSphere.
Apart from applying maintenance on the used product stack (you are far out of support with your MQWF version!!) you could try to overcome the problem by recycling the OID of the workitem which contains 'illegal' characters:
Login as an administrator who does not own the workitem.
Obtain the monitor and force restart the related activity.
This will create a new workitem (= new OID) for the administrator in state READY.
Either check it out and work on it as administrator or transfer it to an appropriate person. Do NOT transfer it to a person who already has this workitem.
For your comfort: it is a rare situation where OIDs get generated that contain characters that are 'illegal' in an URL. |
|
| Back to top |
|
|
| paoloz |
| Posted: Wed Apr 11, 2007 11:16 pm Post subject: |
|
|
Novice
Joined: 31 Dec 2004
Posts: 12
|
Even if we using our own clients, we are quite confident that URL is not wrong. In any case, how can verify if ?
Anyway, our feeling is that something occurs during the data container preparation, done by API calls.
In other words, is possible to get the problem due to a wrong container ? |
|
| Back to top |
|
|
| jmac |
| Posted: Thu Apr 12, 2007 5:23 am Post subject: |
|
|
Jedi Knight
Joined: 27 Jun 2001
Posts: 3081
Location: EmeriCon, LLC
|
| paoloz wrote: |
Anyway, our feeling is that something occurs during the data container preparation, done by API calls.
In other words, is possible to get the problem due to a wrong container ? |
Unless you are accessing the container, I don't see how this happens. The IBM supplied clients do not access the container when building the list, and if you are you should not.
_________________
John McDonald
RETIRED |
|
| 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
|
|
|
|
