| Author |
Message
|
| paulgroo |
 Posted: Sat Jan 10, 2009 2:59 am Post subject: Workflow errors relating to the WebClient (I think) |
 |
|
Centurion
Joined: 07 Jul 2005
Posts: 138
Location: Ireland
|
Hello everyone,
I have an issue at the moment with Workflow version 3.5 running on AIX. Everything has been configured correctly in so far as I can connect to the Workflow instance and import new code. However, when I try to connect ot the Workflow from the client within a java application installed into WAS 5.1, I get the following errors below. Any help would be greatly appreciated, this is bringing me down.
On first login attempt, I get this error:
[1/10/09 10:32:24:173 GMT] 69ca8564 WebGroup I SRVE0181I: [IBM WebSphere MQ Workflow Web Client] [/workflow] [Servlet.LOG]: doGet (logon): com.ibm.workflow.servlet.client.ClientException: java.lang.Exception: FmcAssertionException, Condition=*** Post-condition failed in /projects/fmc/drv2/lbld/v350/aix/src/fmckpid.cxx(196): psz != 0
at com.ibm.workflow.catalog.Properties.setCurrentConfiguration(Native Method)
at com.ibm.workflow.catalog.Properties.<init>(Properties.java:54)
at com.ibm.workflow.api.Agent$LocLocator.locate(Agent.java:8
at com.ibm.workflow.api.Agent.setName(Agent.java:288)
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 sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:85)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:5
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:60)
at java.lang.reflect.Method.invoke(Method.java(Compiled Code))
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:1018)
at com.ibm.ws.webcontainer.webapp.WebAppRequestDispatcher.dispatch(WebAppRequestDispatcher.java:529)
at com.ibm.ws.webcontainer.webapp.WebAppRequestDispatcher.forward(WebAppRequestDispatcher.java:208)
at com.ibm.ws.webcontainer.srt.WebAppInvoker.doForward(WebAppInvoker.java:134)
at com.ibm.ws.webcontainer.srt.WebAppInvoker.handleInvocationHook(WebAppInvoker.java:321)
at com.ibm.ws.webcontainer.cache.invocation.CachedInvocation.handleInvocation(CachedInvocation.java:71)
at com.ibm.ws.webcontainer.srp.ServletRequestProcessor.dispatchByURI(ServletRequestProcessor.java:246)
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:652)
at com.ibm.ws.http.HttpConnection.run(HttpConnection.java:448)
at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:937)
And on second login attempt, I get this:
[1/10/09 10:58:10:097 GMT] 7be98564 WebGroup I SRVE0181I: [IBM WebSphere MQ Workflow Web Client] [/workflow] [Servlet.LOG]: doGet (logon): com.ibm.workflow.servlet.client.ClientException: 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 sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:85)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:5
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:60)
at java.lang.reflect.Method.invoke(Method.java(Compiled Code))
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:1018)
at com.ibm.ws.webcontainer.webapp.WebAppRequestDispatcher.dispatch(WebAppRequestDispatcher.java:529)
at com.ibm.ws.webcontainer.webapp.WebAppRequestDispatcher.forward(WebAppRequestDispatcher.java:208)
at com.ibm.ws.webcontainer.srt.WebAppInvoker.doForward(WebAppInvoker.java:134)
at com.ibm.ws.webcontainer.srt.WebAppInvoker.handleInvocationHook(WebAppInvoker.java:321)
at com.ibm.ws.webcontainer.cache.invocation.CachedInvocation.handleInvocation(CachedInvocation.java:71)
at com.ibm.ws.webcontainer.srp.ServletRequestProcessor.dispatchByURI(ServletRequestProcessor.java:246)
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:652)
at com.ibm.ws.http.HttpConnection.run(HttpConnection.java:458)
at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:937) |
|
| Back to top |
|
 |
| jmac |
| Posted: Sat Jan 10, 2009 1:54 pm Post subject: |
|
|
Jedi Knight
Joined: 27 Jun 2001
Posts: 3081
Location: EmeriCon, LLC
|
Can you connect from the Admin Client (fmcautil)?
Are you using the Native Java API?
_________________
John McDonald
RETIRED |
|
| Back to top |
|
|
| paulgroo |
| Posted: Sun Jan 11, 2009 11:15 am Post subject: |
|
|
Centurion
Joined: 07 Jul 2005
Posts: 138
Location: Ireland
|
Thanks for your reply!
Im after checking from commandline, and I cant connect to fmcautil. Im not getting any errors in the fmcerr or fmcout files though.
And as for the native java API, I dont thing Im using it, but how can I check? |
|
| Back to top |
|
|
| jmac |
| Posted: Sun Jan 11, 2009 11:29 am Post subject: |
|
|
Jedi Knight
Joined: 27 Jun 2001
Posts: 3081
Location: EmeriCon, LLC
|
Paul:
Check for errors in the MQ logs. Often when you can not connect via fmcautil it is an MQ issue. Also check the db2diag.log file.
I don't recall exactly when the Native Java API was rolled into the base product. It definitely was for 3.6, but I do not recall if it happened prior to that. In early versions of 3.5 the Native Java API was a support pac, as I recall it was WA0C, but a quick look at the support pac site shows that it is no longer there. The best way to tell if you are using it would be to know which jar you are using. Native Java API is fmcjapi.jar. Original Java API is fmcojagt.jar or fmcojapi.jar
_________________
John McDonald
RETIRED |
|
| Back to top |
|
|
| hos |
| Posted: Sun Jan 11, 2009 11:52 pm Post subject: |
|
|
Chevalier
Joined: 03 Feb 2002
Posts: 470
|
Hi,
from the stack trace I can tell you that you are NOT using native Java API.
It was available as SupportPac WA0C but as MQWF 3.5 is out of support now for quite a long time I think it is only available directly from IBM on request.
Did you do a configuration step on the AIX box, where the AppServer with the WebClient application is running (fmczutil)? It looks like the client code could not find a valid configurationID.
You are saying that the admin server and execution server processes are running and you still cannot logon even with fmcautil?
Try running the configuration checker fmczchk. |
|
| Back to top |
|
|
| paulgroo |
| Posted: Mon Jan 12, 2009 4:16 am Post subject: |
|
|
Centurion
Joined: 07 Jul 2005
Posts: 138
Location: Ireland
|
Ah yes. 'fmcjapi.jar not installed'... Hmm. How do I install the Java API? I previously configured this server and it ran fine, so I'm assuming I had this setup correctly before. Sorry for all the questions, Im only learning this product as the problems arise! Thanks for your help!
[APP_SERVER] /usr/lpp/fmc/bin ./fmczchk -y HDWF56D
FMC34010I: Configuration checker version 3.5.0.118 started.
FMC34012I: ===> General checks.
FMC34011I: Performing WebSphere MQ Workflow Version 3.5.0 checks.
FMC34013I: ===> Admin Server found, checks started.
FMC34013I: ===> Server message device found, checks started.
FMC34013I: ===> Execution Server found, checks started.
FMC34013I: ===> Client message layer (server API) found, checks started.
FMC34013I: ===> Client message layer (client API) found, checks started.
FMC34013I: ===> WebSphere MQ Workflow C/C++ API found, checks started.
FMC34014I: ===> Java API (fmcjapi.jar) is not installed.
FMC34100I: Messages have been written to /usr/lpp/fmc/bin/fmczchk.log.
FMC34999I: Configuration checker ended: 0 error(s), 0 warning(s), rc = 0.
[APP_SERVER] /usr/lpp/fmc/bin |
|
| Back to top |
|
|
| paulgroo |
| Posted: Mon Jan 12, 2009 4:41 am Post subject: |
|
|
Centurion
Joined: 07 Jul 2005
Posts: 138
Location: Ireland
|
Also! I have both of these jar files installed already: fmcojagt.jar and fmcojapi.jar
No sign of the fmcjapi.jar though. |
|
| Back to top |
|
|
| jmac |
| Posted: Mon Jan 12, 2009 6:41 am Post subject: |
|
|
Jedi Knight
Joined: 27 Jun 2001
Posts: 3081
Location: EmeriCon, LLC
|
I believe the post by Volker indicates that you will need to ask for this from IBM directly
| Quote: |
from the stack trace I can tell you that you are NOT using native Java API.
It was available as SupportPac WA0C but as MQWF 3.5 is out of support now for quite a long time I think it is only available directly from IBM on request. |
_________________
John McDonald
RETIRED |
|
| Back to top |
|
|
|
|
