ASG
IBM
Zystems
Cressida
Icon
Netflexity
 
  MQSeries.net
Search  Search       Tech Exchange      Education      Certifications      Library      Info Center      SupportPacs      LinkedIn  Search  Search                                                                   FAQ  FAQ   Usergroups  Usergroups
 
Register  ::  Log in Log in to check your private messages
 
RSS Feed - WebSphere MQ Support RSS Feed - Message Broker Support

MQSeries.net Forum Index » Workflow Engines - IBM MQ Workflow & Business Process Choreographer » PropertyVetoException - Urgent

Post new topic  Reply to topic
 PropertyVetoException - Urgent « View previous topic :: View next topic » 
Author Message
ushadenshah
PostPosted: Wed Feb 05, 2003 12:37 am    Post subject: PropertyVetoException - Urgent Reply with quote

Newbie

Joined: 23 Dec 2002
Posts: 8

Hi all

We are getting the following exception in our application and it gets resolved only when we restart the web server

The following exception occured in init(): java.beans.PropertyVetoException: FMC38001E Configuration WRKCON cannot be set

Please can some one help urgently

Thanks,
Usha Shah
_________________
Usha Shah
Back to top
View user's profile Send private message AIM Address
yaakovd
PostPosted: Thu Feb 06, 2003 9:22 am    Post subject: Reply with quote

Partisan

Joined: 20 Jan 2003
Posts: 319
Location: Israel

I see nobody answered on "urgent" problem

Can you provide relevant code with short description about your configuratin? Is this exception was thrown from WF servlet?..
_________________
Best regards.
Yaakov
SWG, IBM Commerce, Israel
Back to top
View user's profile Send private message Send e-mail
krismurali
PostPosted: Mon Feb 10, 2003 6:40 am    Post subject: PropertyVetoException - Urgent Reply with quote

Newbie

Joined: 04 Feb 2002
Posts: 5


I work with Usha -(who posted the orig. problem.)
we were using the - agent.setConfigID() to get the service object in our code - (this is using java api to connect to workflow from websphere app server ). The application is a servlet..

For some reason we changed the code from - agent.setLocator() to setConfigID few months back.
Everything was working fine, but after 100+ users login, we used to get this propertyveto error and had to recycle the app.
The manual is not clear which method to use - all it says is - use any one.

we changed it back to setlocator and it is working fine now, without the propertyveto error - for the last 2 days.
_________________
Cheers,
Q Man
MQ, MQ workflow Certified soln,. expert
Back to top
View user's profile Send private message
vennela
PostPosted: Mon Feb 10, 2003 7:32 am    Post subject: Reply with quote

Jedi Knight

Joined: 11 Aug 2002
Posts: 4055
Location: Hyderabad, India

Kris:

The JAVA api doc says:
for "setConfigurationID"
Sets the configuration identifier to be used by the embedded agent. Note that this call implicitly sets the LOC_LOCATOR policy. Consequently, any subsequent calls to Agent.setLocator() will throw a java.beans.PropertyVetoException

And vice versa for "setLocator"

Are you sure that you get this error for 100+ users?
Is this a possibility ---- Your code has some traces of setLocator when you changed it to setConfigurationID

-------
Venny
Back to top
View user's profile Send private message Send e-mail Visit poster's website
krismurali
PostPosted: Mon Feb 10, 2003 9:17 am    Post subject: Reply with quote

Newbie

Joined: 04 Feb 2002
Posts: 5

Venny,

yes, I did see the doc - as you say, we should use either the config id or locator, not both.
we used only one.
one theory is since the agent is serialized, and not sure how the websphere appserver itself behaves (as the workflow code is being called by the application, running under websphere..), may be while using config id, the same instance is somehow called again after certain # of logins and it is set with the config id again, throwing the exception, but with Locator, it does not..
anyway, with the locator, it seems to be working without any prob.
(most sample codes uses the locator , not setconfig id..)
before - this error occurred after many users log in > 100 ..
and goes away after we recycle the application.
I am not sure exactly how many user logins..
May be IBM docs. should clarify - use setLocator for these and use setconfigId for these situations.

Thanks
_________________
Cheers,
Q Man
MQ, MQ workflow Certified soln,. expert
Back to top
View user's profile Send private message
vennela
PostPosted: Mon Feb 10, 2003 11:34 am    Post subject: Reply with quote

Jedi Knight

Joined: 11 Aug 2002
Posts: 4055
Location: Hyderabad, India

Kris:
The manual is not clear which method to use - all it says is - use any one.

Which manual (and where in that manual) are you referring to. I am not sure if we can use these two interchangeably.

Hey OTHERS ... do you think setLocator and setConfigID can be used interchangeably.

WHY do you want to use either of them anyway. Is there any specific reason that you are using these?

-------
Venny
Back to top
View user's profile Send private message Send e-mail Visit poster's website
Ratan
PostPosted: Mon Feb 10, 2003 12:35 pm    Post subject: Reply with quote

Grand Master

Joined: 18 Jul 2002
Posts: 1245

I think they are both interchangeable.
You acheive the same thing using either of them. I dont see anything unique to either of them.

-Laze
Back to top
View user's profile Send private message Send e-mail
Display posts from previous:   
Post new topic  Reply to topic Page 1 of 1

MQSeries.net Forum Index » Workflow Engines - IBM MQ Workflow & Business Process Choreographer » PropertyVetoException - Urgent
Jump to:  



You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
Protected by Anti-Spam ACP
 
 


Theme by Dustin Baccetti
Powered by phpBB © 2001, 2002 phpBB Group

Copyright © MQSeries.net. All rights reserved.