| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| [SOLVED]FMC00106E Not logged on |
« View previous topic :: View next topic » |
| Author |
Message
|
| FloridaSilverback |
 Posted: Thu May 13, 2004 7:40 am Post subject: [SOLVED]FMC00106E Not logged on |
 |
|
Novice
Joined: 13 May 2004
Posts: 16
|
I am getting the FMC00106E error when I attempt to checkout a work item using a 'saved' session.
A ‘test’ class calls both methods in the ‘workflow API class’.
Workflow API class
First method call
Get the agent
Logon to the service
Get a work item and save it in a generic work item object along with the service user id and service session id
Return the generic work item to the test class
Logoff
Second method call – receives the generic work item object from above
Get the agent
Get the service, but don’t log on
Set the service session using the setSessionContext() method using the service userid and the service sessionId that was saved from above.
Cast the generic work item as a MQ Workflow work item
Perform a ‘checkout’ on the work item.
The following error is thrown…
FMC38009E MQSeries Workflow API Error :
API Return Code : 106
Error Origin : e:\v340\src\fmcjcesv.cxx, line 2610
Error Message : FMC00106E Not logged on
Nested Exception : None
If I actually log on in the second method before setting the session context I receive a ‘already logged on’ exception when I attempt to set the session context.
FMC38009E MQSeries Workflow API Error :
API Return Code : 11
Error Origin : e:\v340\src\fmcjcesv.cxx, line 396
Error Message : FMC00011E Already logged on to the system
Nested Exception : None
I have verified that the user id and the session id matched what was saved before.
Thanks
 |
|
| Back to top |
|
 |
| jmac |
| Posted: Thu May 13, 2004 8:02 am Post subject: |
|
|
Jedi Knight
Joined: 27 Jun 2001
Posts: 3081
Location: EmeriCon, LLC
|
Can you post the actual code... some of the terms (generic workitem) you are using don't mean anything to me. I have done what it seems to me you are attempting to do many times, so you probably just have a small issue with the code.
_________________
John McDonald
RETIRED |
|
| Back to top |
|
|
| FloridaSilverback |
| Posted: Thu May 13, 2004 10:03 am Post subject: |
|
|
Novice
Joined: 13 May 2004
Posts: 16
|
It seems I found my own answer. I looked at the IBM Workflow Programming guide and there is a section called 'Stateless Server Support'. (Chapter 13) In there is an explination of how to implement a stateless solution. There were two lines that clued me in:
'Note that the session exists until Logoff() is called or until the
session expires. The session is not removed from the MQ Workflow server
when the application program ends.'
When I changed my first method to 'NOT' logoff then everything worked as expected. However, it raises some questions about this stateless approach. I guess that the state is being preserved on the server until logoff or timeout which may mean that it is statefull? Without thinking to hard, I think it will be fine. I will discuss it later with some colleagues but for now I will move ahead. |
|
| 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
|
|
|
|
