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 » exception Locator LOC_LOCATOR is not supported thrown

Post new topic  Reply to topic
 exception Locator LOC_LOCATOR is not supported thrown « View previous topic :: View next topic » 
Author Message
it_qoo
PostPosted: Fri Mar 26, 2004 12:15 am    Post subject: exception Locator LOC_LOCATOR is not supported thrown Reply with quote

Novice

Joined: 23 Feb 2004
Posts: 24
I've installed more than one Workflow configuration, if I tried to login in the web client using not the default configuration ID, the following exception throws. Does anyone know why?

com.ibm.workflow.servlet.client.ClientException
E-Help
java.beans.PropertyVetoException: FMC38002E Locator LOC_LOCATOR is not supported

at com.ibm.workflow.api.Agent.failureLocator(Agent.java:506)

at com.ibm.workflow.api.Agent.setLocator(Agent.java:406)

at com.ibm.workflow.api.Agent.setConfigurationID(Agent.java:348)

at com.ibm.workflow.servlet.client.ApplicationContextImpl.getAgent(Unknown Source)

at com.ibm.workflow.servlet.client.ApplicationContextImpl.locateService(Unknown Source)

at com.ibm.workflow.servlet.client.BuiltinHandler.logon(Unknown Source)

at java.lang.reflect.Method.invoke(Native Method)

at com.ibm.workflow.servlet.client.Util.invoke(Unknown Source)

at com.ibm.workflow.servlet.client.BuiltinHandler.execute(Unknown Source)

at com.ibm.workflow.servlet.client.ApplicationContextImpl.dispatch(Unknown Source)

at com.ibm.workflow.servlet.client.Main.doGet(Unknown Source)

at com.ibm.workflow.servlet.client.Main.doPost(Unknown Source)

at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)

at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)

at com.ibm.ws.webcontainer.servlet.StrictServletInstance.doService(StrictServletInstance.java:110)

at com.ibm.ws.webcontainer.servlet.StrictLifecycleServlet._service(StrictLifecycleServlet.java:174)

at com.ibm.ws.webcontainer.servlet.IdleServletState.service(StrictLifecycleServlet.java:313)

at com.ibm.ws.webcontainer.servlet.StrictLifecycleServlet.service(StrictLifecycleServlet.java:116)

at com.ibm.ws.webcontainer.servlet.ServletInstance.service(ServletInstance.java:283)

at com.ibm.ws.webcontainer.servlet.ValidServletReferenceState.dispatch(ValidServletReferenceState.java:42)

at com.ibm.ws.webcontainer.servlet.ServletInstanceReference.dispatch(ServletInstanceReference.java:40)

at com.ibm.ws.webcontainer.webapp.WebAppRequestDispatcher.handleWebAppDispatch(WebAppRequestDispatcher.java:923)

at com.ibm.ws.webcontainer.webapp.WebAppRequestDispatcher.dispatch(WebAppRequestDispatcher.java:528)

at com.ibm.ws.webcontainer.webapp.WebAppRequestDispatcher.forward(WebAppRequestDispatcher.java:176)

at com.ibm.ws.webcontainer.srt.WebAppInvoker.doForward(WebAppInvoker.java:79)

at com.ibm.ws.webcontainer.srt.WebAppInvoker.handleInvocationHook(WebAppInvoker.java:201)

at com.ibm.ws.webcontainer.cache.invocation.CachedInvocation.handleInvocation(CachedInvocation.java:71)

at com.ibm.ws.webcontainer.cache.invocation.CacheableInvocationContext.invoke(CacheableInvocationContext.java:114)

at com.ibm.ws.webcontainer.srp.ServletRequestProcessor.dispatchByURI(ServletRequestProcessor.java:186)

at com.ibm.ws.webcontainer.oselistener.OSEListenerDispatcher.service(OSEListener.java:334)

at com.ibm.ws.webcontainer.http.HttpConnection.handleRequest(HttpConnection.java:56)

at com.ibm.ws.http.HttpConnection.readAndHandleRequest(HttpConnection.java:516)

at com.ibm.ws.http.HttpConnection.run(HttpConnection.java:366)

at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:593)
Back to top
View user's profile Send private message
hos
PostPosted: Fri Mar 26, 2004 7:15 am    Post subject: Reply with quote

Chevalier

Joined: 03 Feb 2002
Posts: 470
Hi,
you cannot run more than one configuration in a single process. And the process in your case is the JVM of your AppServer. So if you ever start a web client with a certain configuration, you will be unable to switch to a different configuration UNLESS YOU STOP THE APPSERVER. The error message is kind of misleading, though.
Back to top
View user's profile Send private message
it_qoo
PostPosted: Tue Mar 30, 2004 6:07 pm    Post subject: Reply with quote

Novice

Joined: 23 Feb 2004
Posts: 24
I know one configuration corresponds to one application in the websphere. Do you mean I cannot start more than one application in the websphere at the same time? Even if the database is not shared?
Back to top
View user's profile Send private message
hos
PostPosted: Wed Mar 31, 2004 7:52 am    Post subject: Reply with quote

Chevalier

Joined: 03 Feb 2002
Posts: 470
Hi,

what I'm saying is that you cannot start multiple MQWF clients using different configurations in the same AppServer. The API keeps track of the configurationID you set and won't let you change this ID twice. The scope of the API is not limited to a database but to the process that has loaded it. And the process is java.exe (i.e. the WAS JVM).
Back to top
View user's profile Send private message
kriersd
PostPosted: Thu Apr 01, 2004 10:01 am    Post subject: The Solution Reply with quote

Master

Joined: 22 Jul 2002
Posts: 209
Location: IA, USA
The solution here is that you will be required to build another appserver to house one of the web apps.

I ran into the same issue when I tried to deploy an EJB that was using some Workflow API's on the same appserver hosting my webclient.
_________________
Dave Krier

IBM WebSphere MQ Workflow V3.4 Solution Designer
Back to top
View user's profile Send private message
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 » exception Locator LOC_LOCATOR is not supported thrown
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.