| Author |
Message
|
| Ratan |
 Posted: Tue Feb 17, 2004 9:43 am Post subject: propertyvetoexception |
 |
|
Grand Master
Joined: 18 Jul 2002
Posts: 1245
|
I am getting this exception while trying to login from webclient deployed in weblogic 7.0. I deployed it in weblogic (this is where the error could be, as I did it for the first time with weblogic).
If anybody deployed Webclient in Weblogic server, please give me some info on how to do it.
Exception:
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 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 weblogic.servlet.internal.ServletStubImpl$ServletInvocationAction.run(ServletStubImpl.java:1075)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:418)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:306)
at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:5517)
at weblogic.security.service.SecurityServiceManager.contact admin(SecurityServiceManager.java:685)
at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:3156)
at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2506)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:234)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:210)
_________________
-Ratan |
|
| Back to top |
|
 |
| vennela |
| Posted: Tue Feb 17, 2004 9:49 am Post subject: |
|
|
Jedi Knight
Joined: 11 Aug 2002
Posts: 4055
Location: Hyderabad, India
|
Ratan:
This is from the IBM database. Did you select java agent while creating the configuration
| Quote: |
This message is an indication JW was not selected in the
fmczutil configuration selection. It is not sufficient enough to
select the Webclient (w) only.
If using a standalone set-up, it is mandatory, to select (jw).
It then automatically selects the client with queue manager.
After deleting and re-creating the Webclient configuration
using FMCQM, FMCSYS, FMCGRP from previous configuration and
the suggestions above a successful logon with the webclient was achieved. |
|
|
| Back to top |
|
|
| Ratan |
| Posted: Tue Feb 17, 2004 9:53 am Post subject: |
|
|
Grand Master
Joined: 18 Jul 2002
Posts: 1245
|
when we select Webclient, Java Agent is automatically selected.
_________________
-Ratan |
|
| Back to top |
|
|
| vennela |
| Posted: Tue Feb 17, 2004 9:57 am Post subject: |
|
|
Jedi Knight
Joined: 11 Aug 2002
Posts: 4055
Location: Hyderabad, India
|
| Quote: |
| when we select Webclient, Java Agent is automatically selected. |
I don't think so. |
|
| Back to top |
|
|
| Ratan |
| Posted: Tue Feb 17, 2004 9:59 am Post subject: |
|
|
Grand Master
Joined: 18 Jul 2002
Posts: 1245
|
I used Windows config utility and I sure it was automatically selected. can you run a test and see, may be I am wrong.
_________________
-Ratan |
|
| Back to top |
|
|
| vennela |
| Posted: Tue Feb 17, 2004 10:05 am Post subject: |
|
|
Jedi Knight
Joined: 11 Aug 2002
Posts: 4055
Location: Hyderabad, India
|
I just ran fmczutil on Windows and UNIX and when I select w for web client j is not selected.
With the GUI it is automatically selected.
Then you should try configuring the web client using fmczutil (that is how it's done in earlier versions anyway) |
|
| Back to top |
|
|
| Ratan |
| Posted: Tue Feb 17, 2004 10:26 am Post subject: |
|
|
Grand Master
Joined: 18 Jul 2002
Posts: 1245
|
I ran fmczutil selected my configID and am able to see the Java Agent configured.
Are you sure this is the only scenario which causes this exception? If you are, I will delete my configuration and recreate it using fmczutil.
_________________
-Ratan |
|
| Back to top |
|
|
| Ratan |
| Posted: Tue Feb 17, 2004 10:54 am Post subject: |
|
|
Grand Master
Joined: 18 Jul 2002
Posts: 1245
|
Venny, I took your suggestion and recreated configuration using fmczutil. Still no luck.
_________________
-Ratan |
|
| Back to top |
|
|
| vennela |
| Posted: Tue Feb 17, 2004 10:57 am Post subject: |
|
|
Jedi Knight
Joined: 11 Aug 2002
Posts: 4055
Location: Hyderabad, India
|
|
| Back to top |
|
|
| Ratan |
| Posted: Tue Feb 17, 2004 11:31 am Post subject: |
|
|
Grand Master
Joined: 18 Jul 2002
Posts: 1245
|
I did all those tests (successfully) before posting the question here.
I will just leave this issue to our Weblogic experts to figure out.
-Thanks
_________________
-Ratan |
|
| Back to top |
|
|
| vennela |
| Posted: Tue Feb 17, 2004 12:25 pm Post subject: |
|
|
Jedi Knight
Joined: 11 Aug 2002
Posts: 4055
Location: Hyderabad, India
|
| Post the solution for other members of the forum. |
|
| Back to top |
|
|
| vennela |
| Posted: Sun Feb 22, 2004 2:43 pm Post subject: |
|
|
Jedi Knight
Joined: 11 Aug 2002
Posts: 4055
Location: Hyderabad, India
|
| Installed a new configuration with just web client on WAS 5.0 ( MQWF 3.4 with no Service Packs). Had the same problem (FMC38002E). Stop and Start of the web client Enterprise Application inside WAS didn't solve the problem. Bounced entire WAS app server and the problem was gone. |
|
| Back to top |
|
|
| kriersd |
| Posted: Tue Feb 24, 2004 7:16 pm Post subject: |
|
|
Master
Joined: 22 Jul 2002
Posts: 209
Location: IA, USA
|
I have came accross this issue a time or two, but I was using WAS. Here is what I found.
The problem came when I attempted to deploy a Webclient webapp in the same Appserver container that already had a Workflow webclient installed. I found that due to some native c dll's, which are bound to another Workflow web app I was not able to have multiple applications that require a connection to Workflow. I built a new appserver and loaded the new Webclient within the newly created appserver and it worked.
Also, look in your documentation directory for a file called "unspd.html". This html file is not referenced in the general documentation. This is a guide on how to install the web client on some unsupported java servers such as Weblogic.
Hope this helps.
Dave
_________________
Dave Krier
IBM WebSphere MQ Workflow V3.4 Solution Designer |
|
| Back to top |
|
|
|
|
