| Author |
Message
|
| Ratan |
 Posted: Fri Jan 17, 2003 12:55 pm Post subject: WebClient login Timeout error |
 |
|
Grand Master
Joined: 18 Jul 2002
Posts: 1245
|
I am unable to login to my Webclient. It used to work previously and all of a sudden it is throwing me the following exception.
| Quote: |
FMC00014E Timeout occurred
com.ibm.workflow.api.FmcException:
FMC38009E MQSeries Workflow API Error :
API Return Code : 14
Error Origin : e:\v332\src\fmcjcesv.cxx, line 2420
Error Message : FMC00014E Timeout occurred
Nested Exception : None
at com.ibm.workflow.api.loc.ExecutionServiceImpl.queryProcessTemplateLists(ExecutionServiceImpl.java:563)
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(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 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.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:523)
at com.ibm.servlet.engine.webapp.WebAppRequestDispatcher.dispatch(WebAppRequestDispatcher.java:282)
at com.ibm.servlet.engine.webapp.WebAppRequestDispatcher.forward(WebAppRequestDispatcher.java:112)
at com.ibm.servlet.engine.srt.WebAppInvoker.doForward(WebAppInvoker.java:91)
at com.ibm.servlet.engine.srt.WebAppInvoker.handleInvocationHook(WebAppInvoker.java:184)
at com.ibm.servlet.engine.invocation.CachedInvocation.handleInvocation(CachedInvocation.java:67)
at com.ibm.servlet.engine.srp.ServletRequestProcessor.dispatchByURI(ServletRequestProcessor.java:122)
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:323)
at com.ibm.ws.http.HttpConnection.run(HttpConnection.java:252)
at com.ibm.ws.util.CachedThread.run(ThreadPool.java:122)
|
I am able to succesfully use fmcautil from WebServer, so I can safely assume there is no problem with the MQ Communication.
Any Idea ?????
-Laze |
|
| Back to top |
|
 |
| newbiedude |
| Posted: Fri Jan 17, 2003 2:35 pm Post subject: |
|
|
Voyager
Joined: 22 Dec 2002
Posts: 87
|
lazenight
| Quote: |
I am unable to login to my Webclient. It used to work previously and all of a sudden it is throwing me the following exception
|
can you elaborate on your current setup. Are you using client concentrators?
-you might wanna check your MQ channels (disconnect interval)
anything strange in the log files?
_________________
Newbiedude |
|
| Back to top |
|
|
| Ratan |
| Posted: Fri Jan 17, 2003 2:37 pm Post subject: |
|
|
Grand Master
Joined: 18 Jul 2002
Posts: 1245
|
yeah, I am using a client concentrator setup and there is nothing wrong with my channels, which is evident when I said 'fmcautil' works fine from webserver.
-Thnx Laze |
|
| Back to top |
|
|
| vennela |
| Posted: Fri Jan 17, 2003 2:53 pm Post subject: |
|
|
Jedi Knight
Joined: 11 Aug 2002
Posts: 4055
Location: Hyderabad, India
|
Have you tried to logon to the web-client after fmcautil test.
1. Logon to the web-client (Times out)
2. fmcautil and query the status of the server
3. Logon to the web-client now
If you can't then you may have to look at the log files in
<MQWF Install DIR>\cfgs\<WEB CLI CONFIG ID>\log
like
C:\Program Files\MQSeries Workflow\cfgs\fmc1\log
---
Venny |
|
| Back to top |
|
|
| Ratan |
| Posted: Fri Jan 17, 2003 2:59 pm Post subject: |
|
|
Grand Master
Joined: 18 Jul 2002
Posts: 1245
|
Venny,
I tried everything that occured to my head. Even bounced the Web box a couple of times, hoping the problem would be resolved. But no luck.
When I give a non-existant UserId in the UserID field I get back an immediate reply saying 'unknown userID'. I guess that means the client is able to communicate to the workflow server. There is catch though, when I give the User name as 'adminXX' ( this is also a non existant userID) , I get the 'timeout error'. Isn't that weird. Any Idea?
-Thnx Laze |
|
| Back to top |
|
|
| vennela |
| Posted: Fri Jan 17, 2003 3:09 pm Post subject: |
|
|
Jedi Knight
Joined: 11 Aug 2002
Posts: 4055
Location: Hyderabad, India
|
If that is the case do this:
Stop the CLUSSDR channels on both sides.
Issue the logon command:
Browse the transmit queue (the best way is use amqsbcg and redirect the output to a text file).
Start the CLUSSDR channel on the web-client
Browse the transmit queue on the WF server.
Look at the userID's of both the messages
My guess is MQ QMGR was not started by a WORKFLOW principal (on the server).
Does the UserId that started the WAS have the right authorizations?
---
Venny |
|
| Back to top |
|
|
| Ratan |
| Posted: Fri Jan 17, 2003 3:33 pm Post subject: |
|
|
Grand Master
Joined: 18 Jul 2002
Posts: 1245
|
Well you dont have to worry about all the user authority in Windows2000. WAS was started with local admin rights.
-Laze |
|
| Back to top |
|
|
| vennela |
| Posted: Fri Jan 17, 2003 3:38 pm Post subject: |
|
|
Jedi Knight
Joined: 11 Aug 2002
Posts: 4055
Location: Hyderabad, India
|
The messages are definitely struck somewhere
either on the web QMGR or on the WFserver QMGR
What does your servlet error logs say? |
|
| Back to top |
|
|
| jmac |
| Posted: Sat Jan 18, 2003 6:23 am Post subject: |
|
|
Jedi Knight
Joined: 27 Jun 2001
Posts: 3081
Location: EmeriCon, LLC
|
Laze:
1. Any messages in fmcsys.log or fmcerror.log?
2. Is this a new user? I.E can you logon with another user?
3. Can you logon with this user using fat client?
_________________
John McDonald
RETIRED |
|
| Back to top |
|
|
| Ratan |
| Posted: Mon Jan 20, 2003 9:51 am Post subject: |
|
|
Grand Master
Joined: 18 Jul 2002
Posts: 1245
|
Hi John,
| Quote: |
1. Any messages in fmcsys.log or fmcerror.log?
|
No, fmcsys and fmcerr.log files are only available on Workflow server node and there are no error messages in them.
| Quote: |
2. Is this a new user? I.E can you logon with another user?
|
No, it is an old user.
| Quote: |
3. Can you logon with this user using fat client?
|
Yes, I can succesfully logon with fat client.
I still get the same old error message. Timeout Error.
-Laze[/quote] |
|
| Back to top |
|
|
| Ratan |
| Posted: Mon Jan 20, 2003 11:12 am Post subject: |
|
|
Grand Master
Joined: 18 Jul 2002
Posts: 1245
|
Hi guy,
Finally it is working now. I restarted the Workflow Server machine and it started working.
For the last 2 days I was only restarting the web Server machine and was checking the channels. There were no error messages indicating a channel is dead.
Important Observation:
If you are running on Win2K the first thing to do in case of an error is restarting all your machines. 
-Laze |
|
| Back to top |
|
|
| kriersd |
| Posted: Tue Jan 21, 2003 6:31 am Post subject: |
|
|
Master
Joined: 22 Jul 2002
Posts: 209
Location: IA, USA
|
Venny
| Quote: |
Have you tried to logon to the web-client after fmcautil test.
1. Logon to the web-client (Times out)
2. fmcautil and query the status of the server
3. Logon to the web-client now
|
This issue you describe above happens to us all the time. Can you explain why a logon issued from the web client does not start the cluster sender channel on the Websphere server, but a logon using the FMCAUTIL utility from the Websphere server does?
_________________
Dave Krier
IBM WebSphere MQ Workflow V3.4 Solution Designer |
|
| Back to top |
|
|
| mkhadse |
| Posted: Fri May 16, 2003 5:46 am Post subject: |
|
|
Acolyte
Joined: 31 Dec 1969
Posts: 73
|
I had a similar problem with a webclient connecting to the server as a client. Restarting the server and the trigger monitor helped. There was no indication of any error in the db2/workflow/mqseries log files.
Does anybody have any idea what might be happening? |
|
| Back to top |
|
|
| sshaker |
| Posted: Fri May 16, 2003 7:07 am Post subject: |
|
|
Disciple
Joined: 20 Sep 2002
Posts: 185
|
hi
nice to know that ur all set ..
looks interesting.. did u see ur servlet log..
did u look stdout.log .. and servlet log.. can u pl send ur servlet log file.. if possible..
regards
shaker
_________________
shaker |
|
| Back to top |
|
|
|
|
