| Author |
Message
|
| ajomillar |
 Posted: Mon Apr 26, 2004 1:18 pm Post subject: FMC00014E Timeout occurred |
 |
|
Centurion
Joined: 22 Aug 2003
Posts: 121
Location: Milwaukee, WI
|
Running Workflow v3.4 on AIX (WF server) but connecting via MQSeries from Sun (WAS server). After attempting to logon using the default web client, I get the following error.
| Code: |
FMC00014E Timeout occurred
com.ibm.workflow.api.FmcException:
FMC38009E MQSeries Workflow API Error :
API Return Code : 14
Error Origin : /projects/fmc/drvl/lbld/v340/solaris/src/fmcjcesv.cxx, line 2465
Error Message : FMC00014E Timeout occurred
Nested Exception : None
at com.ibm.workflow.api.loc.ExecutionServiceImpl.queryProcessTemplateLists(ExecutionServiceImpl.java:593)
at com.ibm.workflow.servlet.client.BuiltinHandler.queryProcessTemplateLists(Unknown Source)
at com.ibm.workflow.servlet.client.BuiltinHandler.queryLists(Unknown Source)
at com.ibm.workflow.servlet.client.RequestContext.mostRecentList(Unknown Source)
at com.ibm.workflow.servlet.client.DefaultViewer.mostRecentList(Unknown Source)
at com.ibm.workflow.servlet.client.JSPViewer.logonResponse(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.render(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.servlet.engine.webapp.StrictServletInstance.doService(ServletManager.java:827)
at com.ibm.servlet.engine.webapp.StrictLifecycleServlet._service(StrictLifecycleServlet.java:167)
at com.ibm.servlet.engine.webapp.IdleServletState.service(StrictLifecycleServlet.java:297)
at com.ibm.servlet.engine.webapp.StrictLifecycleServlet.service(StrictLifecycleServlet.java:110)
at com.ibm.servlet.engine.webapp.ServletInstance.service(ServletManager.java:472)
at com.ibm.servlet.engine.webapp.ValidServletReferenceState.dispatch(ServletManager.java:1012)
at com.ibm.servlet.engine.webapp.ServletInstanceReference.dispatch(ServletManager.java:913)
at com.ibm.servlet.engine.webapp.WebAppRequestDispatcher.handleWebAppDispatch(WebAppRequestDispatcher.java:721)
at com.ibm.servlet.engine.webapp.WebAppRequestDispatcher.dispatch(WebAppRequestDispatcher.java:374)
at com.ibm.servlet.engine.webapp.WebAppRequestDispatcher.forward(WebAppRequestDispatcher.java:118)
at com.ibm.servlet.engine.srt.WebAppInvoker.doForward(WebAppInvoker.java:134)
at com.ibm.servlet.engine.srt.WebAppInvoker.handleInvocationHook(WebAppInvoker.java:239)
at com.ibm.servlet.engine.invocation.CachedInvocation.handleInvocation(CachedInvocation.java:67)
at com.ibm.servlet.engine.srp.ServletRequestProcessor.dispatchByURI(ServletRequestProcessor.java:151)
at com.ibm.servlet.engine.oselistener.OSEListenerDispatcher.service(OSEListener.java:317)
at com.ibm.servlet.engine.http11.HttpConnection.handleRequest(HttpConnection.java:60)
at com.ibm.ws.http.HttpConnection.readAndHandleRequest(HttpConnection.java:391)
at com.ibm.ws.http.HttpConnection.run(HttpConnection.java:274)
at com.ibm.ws.util.CachedThread.run(ThreadPool.java:144)
|
This was not a problem that existed before today. I suspect some hardware maintenance over the weekend on the AIX server messed things up (we had to stop/start the QMs for the Integration Broker v2.1 running on the same AIX).
I tried the following but no success:
1. Connected using admin userid from WAS server to WF server.
2. Stopped and started QMs on both WAS and WF servers.
3. Stopped and started WF using fmcautil.
Any help is appreciated |
|
| Back to top |
|
 |
| mqonnet |
| Posted: Mon Apr 26, 2004 1:20 pm Post subject: |
|
|
Grand Master
Joined: 18 Feb 2002
Posts: 1114
Location: Boston, Ma, Usa.
|
|
| Back to top |
|
|
| Ratan |
| Posted: Mon Apr 26, 2004 1:22 pm Post subject: |
|
|
Grand Master
Joined: 18 Jul 2002
Posts: 1245
|
Did you try fmcautil to connect to WF Server from your client box?
_________________
-Ratan |
|
| Back to top |
|
|
| ajomillar |
| Posted: Mon Apr 26, 2004 1:29 pm Post subject: |
|
|
Centurion
Joined: 22 Aug 2003
Posts: 121
Location: Milwaukee, WI
|
| Quote: |
Looks like the same exact problem discussed here.
|
Yes, I read the thread before my posting. Thanks!
| Quote: |
| Did you try fmcautil to connect to WF Server from your client box? |
Yes and I receive the appropriate "success" messages. This is what puzzles me...if I can connect from the WAS server using fmcautil, then why does the web client logon have a problem. The method throwing the exception is worklist query...Is it possible that a message is sent to WF but WF isn't replying in a timely manner? |
|
| Back to top |
|
|
| Ratan |
| Posted: Mon Apr 26, 2004 2:07 pm Post subject: |
|
|
Grand Master
Joined: 18 Jul 2002
Posts: 1245
|
how big is the worklist?
Did you try to login with fat client from the client machine and query worklists?
_________________
-Ratan |
|
| Back to top |
|
|
| praveenchhangani |
| Posted: Tue Apr 27, 2004 8:46 am Post subject: |
|
|
Disciple
Joined: 20 Sep 2002
Posts: 192
Location: Chicago, IL
|
Is this setup being used in conjunction with a client concentrator? What is the state of the MQSeries channels?
_________________
Praveen K. Chhangani,
IBM Certified Solutions Designer -
MQ Workflow 3.4. |
|
| Back to top |
|
|
| ajomillar |
| Posted: Tue Apr 27, 2004 12:24 pm Post subject: |
|
|
Centurion
Joined: 22 Aug 2003
Posts: 121
Location: Milwaukee, WI
|
The fat client is on Windows. I've not attempted a connection to the AIX WF Server using the fat client. The worklist has over 800 items. We expect that it may hold thousands of items...
| Quote: |
| Is this setup being used in conjunction with a client concentrator? |
No client concentrator used in this setup.
| Quote: |
| What is the state of the MQSeries channels? |
On the WAS Server, the cluster sender and system.admin.svrconn are running. All other channels are inactive.
On the WF Server, the cluster receiver and system.admin.svrconn are running. All other channels are inactive.
Looking at the stack trace, the exception was thrown by a query method. Is it possible that the number of workitems is too large to be returned by the method?? |
|
| Back to top |
|
|
| ajomillar |
| Posted: Wed Apr 28, 2004 1:36 pm Post subject: |
|
|
Centurion
Joined: 22 Aug 2003
Posts: 121
Location: Milwaukee, WI
|
I queried the WORK_ITEM table in the FMCDB database: there are 2743 records. Also, I asked the system admin about last weekend's activities. The test AIX server was shutdown then started up again. The DB2 diag log captured the events as "crash" with a later "recovery."
I think the fact that the default (out-of-box) web client times out at the queryWorklist method is an indication of a WF server to Runtime DB issue. Any thoughts??? |
|
| Back to top |
|
|
| Ratan |
| Posted: Wed Apr 28, 2004 1:56 pm Post subject: |
|
|
Grand Master
Joined: 18 Jul 2002
Posts: 1245
|
|
| Back to top |
|
|
|
|
