| Author |
Message
|
| karthik |
 Posted: Fri Oct 15, 2004 9:42 am Post subject: Timeout error |
 |
|
Centurion
Joined: 17 Oct 2003
Posts: 114
|
Hi all,
I have a problem while viewing my process instances in my webclient.
The webclient application and the workflow server is using the same queue manager. Both WAS and MQ workflow are on the same box.
I have a specific process instance list which has a threshold of 20. But still if i want to view the process instances , i get a timeout error.
The queue manager has a max message length of 15000000.
I also get a timeout error while creating a new process instances.
What do i have to do get this problem solved.
Please help me out of this situation.
Thanks
karthik |
|
| Back to top |
|
 |
| kriersd |
| Posted: Fri Oct 15, 2004 12:03 pm Post subject: |
|
|
Master
Joined: 22 Jul 2002
Posts: 209
Location: IA, USA
|
Do the Workflow logs show any errors? Also, check the Websphere servlet error and servlet out logs. If you find any error messages please post them.
You may want to just try the thick client and see if you get the same problem. If that works then you can narrow it down to a problem on the WebSphere server.
_________________
Dave Krier
IBM WebSphere MQ Workflow V3.4 Solution Designer |
|
| Back to top |
|
|
| karthik |
| Posted: Fri Oct 15, 2004 1:23 pm Post subject: |
|
|
Centurion
Joined: 17 Oct 2003
Posts: 114
|
Hi Dave,
Thanks for the Reply. I do not see any errors in the servlet.err or mq logs or the workflow logs either related to this. I checked the dates and times also to make sure. But nothing seemed relevant.
The fat client also time out.
The errors in servlet-out are these:
[10/15/04 10:22:20:939 GMT-06:00] 552900ca WebGroup I SRVE0092I: [Servlet LOG]: doGet (queryProcessInstances): com.ibm.workflow.servlet.client.ClientException: FMC00014E Timeout occurred: com.ibm.workflow.api.FmcException:
FMC38009E MQSeries Workflow API Error :
API Return Code : 14
Error Origin : /projects/fmc/drvp/lbld/v332/src/fmcjclis.cxx, line 2732
Error Message : FMC00014E Timeout occurred
Nested Exception : None
at com.ibm.workflow.api.loc.ProcessInstanceListImpl.queryProcessInstances(ProcessInstanceListImpl.java:47)
at com.ibm.workflow.servlet.client.SessionContextImpl.setInstances(Unknown Source)
at com.ibm.workflow.servlet.client.SessionContextProxy.setInstances(Unknown Source)
at com.ibm.workflow.servlet.client.BuiltinHandler.queryProcessInstances(Unknown Source)
at com.ibm.workflow.servlet.client.BuiltinHandler.queryProcessInstances(Unknown Source)
at java.lang.reflect.Method.invoke(Native Method)
at com.ibm.workflow.servlet.client.Util.invoke(Util.java:124)
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 javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
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.ServicingServletState.service(StrictLifecycleServlet.java:317)
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:678)
at com.ibm.servlet.engine.webapp.WebAppRequestDispatcher.dispatch(WebAppRequestDispatcher.java:331)
at com.ibm.servlet.engine.webapp.WebAppRequestDispatcher.forward(WebAppRequestDispatcher.java:117)
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.invocation.CacheableInvocationContext.invoke(CacheableInvocationContext.java:106)
at com.ibm.servlet.engine.srp.ServletRequestProcessor.dispatchByURI(ServletRequestProcessor.java:154)
at com.ibm.servlet.engine.oselistener.OSEListenerDispatcher.service(OSEListener.java:315)
at com.ibm.servlet.engine.http11.HttpConnection.handleRequest(HttpConnection.java:60)
at com.ibm.ws.http.HttpConnection.readAndHandleRequest(HttpConnection.java(Compiled Code))
at com.ibm.ws.http.HttpConnection.run(HttpConnection.java(Compiled Code))
at com.ibm.ws.util.CachedThread.run(ThreadPool.java:137)
[10/15/04 11:46:59:287 GMT-06:00] 553000ca ServletHost W SRVE0023E: Web Group not found
[10/15/04 11:46:59:317 GMT-06:00] 553000ca ServletReques X SRVE0023E: Web Group not found
[10/15/04 11:46:59:342 GMT-06:00] 553000ca OSEListenerDi X PLGN0021E: Servlet Request Processor Exception: Virtual Host/WebGroup Not Found : The web group /favicon.ico has not been defined
[10/15/04 11:53:25:334 GMT-06:00] 552900ca WebGroup I SRVE0092I: [Servlet LOG]: doGet (createPersistentList): com.ibm.workflow.servlet.client.ClientException: FMC00014E Timeout occurred: com.ibm.workflow.api.FmcException:
FMC38009E MQSeries Workflow API Error :
API Return Code : 14
Error Origin : /projects/fmc/drvp/lbld/v332/src/fmcjclis.cxx, line 2732
Error Message : FMC00014E Timeout occurred
Nested Exception : None
at com.ibm.workflow.api.loc.ProcessInstanceListImpl.queryProcessInstances(ProcessInstanceListImpl.java:47)
at com.ibm.workflow.servlet.client.SessionContextImpl.setInstances(Unknown Source)
at com.ibm.workflow.servlet.client.SessionContextProxy.setInstances(Unknown Source)
at com.ibm.workflow.servlet.client.BuiltinHandler.queryProcessInstances(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.DefaultViewer.createPersistentListResponse(Unknown Source)
at java.lang.reflect.Method.invoke(Native Method)
at com.ibm.workflow.servlet.client.Util.invoke(Util.java:124)
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 javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
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:678)
at com.ibm.servlet.engine.webapp.WebAppRequestDispatcher.dispatch(WebAppRequestDispatcher.java:331)
at com.ibm.servlet.engine.webapp.WebAppRequestDispatcher.forward(WebAppRequestDispatcher.java:117)
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.invocation.CacheableInvocationContext.invoke(CacheableInvocationContext.java:106)
at com.ibm.servlet.engine.srp.ServletRequestProcessor.dispatchByURI(ServletRequestProcessor.java:154)
at com.ibm.servlet.engine.oselistener.OSEListenerDispatcher.service(OSEListener.java:315)
at com.ibm.servlet.engine.http11.HttpConnection.handleRequest(HttpConnection.java:60)
at com.ibm.ws.http.HttpConnection.readAndHandleRequest(HttpConnection.java(Compiled Code))
at com.ibm.ws.http.HttpConnection.run(HttpConnection.java(Compiled Code))
at com.ibm.ws.util.CachedThread.run(ThreadPool.java:137)
That seemed strange , but can we say that this might be a problem with the database?
but for further info our db is Oracle 8.17
Thanks in advance
karthik |
|
| Back to top |
|
|
| vennela |
| Posted: Sat Oct 16, 2004 7:50 pm Post subject: |
|
|
Jedi Knight
Joined: 11 Aug 2002
Posts: 4055
Location: Hyderabad, India
|
| Are there any messages piling up on any of the queues??? |
|
| Back to top |
|
|
| mike_mq |
| Posted: Sun Oct 17, 2004 12:48 pm Post subject: |
|
|
Centurion
Joined: 17 Oct 2003
Posts: 123
|
| Are you using any Authentications ? if so, please see how much time it is taking to authenticate user login. |
|
| Back to top |
|
|
| karthik |
| Posted: Sun Oct 17, 2004 10:36 pm Post subject: |
|
|
Centurion
Joined: 17 Oct 2003
Posts: 114
|
Hi venny,
Nothing specific where a queue had messages piled up.
There are a few queues which had more messages than other.
These mostly are system queues.
SYSTEM.AUTH.DATA.QUEUE
SYSTEM.CLUSTER.REPOSITORY.QUEUE
Also we are not using any authentication. The user login is fairly quick enough. I also get to see the process template list easily. Its only when i try to get the process instances , i get a timeout. The number of process instances is very large (more than 30,000).
Please advise me on any tests , to exclude each factor(Like WAS,MQ,database etc;) so that the final hurdle is find out and the required action can be taken.
Thanks all for your help
karthik |
|
| Back to top |
|
|
| CHF |
| Posted: Mon Oct 18, 2004 4:39 am Post subject: |
|
|
Master
Joined: 16 Dec 2003
Posts: 297
|
| Quote: |
| process instances is very large (more than 30,000) |
This is the reason why you are getting Timeout Error.
_________________
CHF  |
|
| Back to top |
|
|
| karthik |
| Posted: Mon Oct 18, 2004 9:19 am Post subject: |
|
|
Centurion
Joined: 17 Oct 2003
Posts: 114
|
Hi CHF,
you were right.That is the problem.But that doesnot suggest a solution to my problem.
But the requirement is that i should be able to view atleast few process instances. So, i tried to create a process instance list with a threshold of 5 and applied a filter for that list(Based on name). Amazingly that seemed to work and i can see a few process instances. I am happy to see this.
But is there a way that i can see only latest created process instances.
Only a few like 10 or 15 is also ok.
Please advise.
Thanks all
karthik
Last edited by karthik on Mon Oct 18, 2004 3:01 pm; edited 1 time in total |
|
| Back to top |
|
|
| vennela |
| Posted: Mon Oct 18, 2004 10:28 am Post subject: |
|
|
Jedi Knight
Joined: 11 Aug 2002
Posts: 4055
Location: Hyderabad, India
|
| Put a filter with sort on time and threshold |
|
| Back to top |
|
|
| karthik |
| Posted: Mon Oct 18, 2004 1:52 pm Post subject: |
|
|
Centurion
Joined: 17 Oct 2003
Posts: 114
|
Hi Venny,
That works great. The solution you provide mostly works.
Thanks all for your help
karthik |
|
| Back to top |
|
|
|
|
