ASG
IBM
Zystems
Cressida
Icon
Netflexity
 
  MQSeries.net
Search  Search       Tech Exchange      Education      Certifications      Library      Info Center      SupportPacs      LinkedIn  Search  Search                                                                   FAQ  FAQ   Usergroups  Usergroups
 
Register  ::  Log in Log in to check your private messages
 
RSS Feed - WebSphere MQ Support RSS Feed - Message Broker Support

MQSeries.net Forum Index » Workflow Engines - IBM MQ Workflow & Business Process Choreographer » FMC00106E error but isLoggedOn = true

Post new topic  Reply to topic
 FMC00106E error but isLoggedOn = true « View previous topic :: View next topic » 
Author Message
chintu
PostPosted: Wed May 16, 2007 11:04 am    Post subject: FMC00106E error but isLoggedOn = true Reply with quote

Acolyte

Joined: 27 Dec 2004
Posts: 64
WF 3.6 on AIX. Java App on WAS 6.0 on the same box.

Hello all,
I get FMC00106E not-logged-on error sporadically when calling
processTemplate.initialInContainer() or
workItem.outContainer() or
workItem.transfer().

I am using PRESENT_HERE and execService.isLoggedOn() returns true right before these errors.

My application caches all the existing Process template OID's during its initializing phase. All createProcessInstance requests use these OID's to get the initialInContainer. Is it possible that these OIDs become stale after a period of time? If a newly created executionService object( new user logs-in) performs the same exact createProcessInstance, there is no error. Why did the first request fail even though execService.isLoggedOn() returns true? Is it possible that the actual error is different but the api throws an FMC00106E error? If have tried using a decompiler to see what piece of code throws this error, but the line numbers in the stack trace and the line numbers in the decompiled class file are not in sync. If anyone has the souce code for fmcjapi.jar..can you please pm me?

Thanks
Back to top
View user's profile Send private message
vijaycr
PostPosted: Thu May 17, 2007 2:43 am    Post subject: Reply with quote

Acolyte

Joined: 11 Oct 2006
Posts: 62
Location: Singapore
executionService.isLoggedOn returns the state as known by the client. If you need to check the current session status u need to include a refresh call before isLoggedOn is called. The executionService.refresh will also throw a not logged on exception if your session is invalid.

It is most likely that you are forced out by another logon with PRESENT_HERE session mode or your session might have expired.
Back to top
View user's profile Send private message
vijaycr
PostPosted: Thu May 17, 2007 6:16 pm    Post subject: Reply with quote

Acolyte

Joined: 11 Oct 2006
Posts: 62
Location: Singapore
Caching the proceess instance oid is not a good idea as it changes with every new version of the template. If some one imports a modified template then you would need to 'refresh' your cache.
Back to top
View user's profile Send private message
tsrisudh
PostPosted: Thu May 24, 2007 2:09 am    Post subject: Reply with quote

Centurion

Joined: 11 Aug 2005
Posts: 113
you have to do a refresh before trying to check isLoggedOn, first do a service.refresh() and then check.

I too had faced the same problem and after using the refresh, it solved the problem
_________________
Srisudhir Tadepalli
Back to top
View user's profile Send private message Yahoo Messenger
Display posts from previous:   
Post new topic  Reply to topic Page 1 of 1

MQSeries.net Forum Index » Workflow Engines - IBM MQ Workflow & Business Process Choreographer » FMC00106E error but isLoggedOn = true
Jump to:  



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
Protected by Anti-Spam ACP
  
 


Theme by Dustin Baccetti
Powered by phpBB © 2001, 2002 phpBB Group

Copyright © MQSeries.net. All rights reserved.