| Author | Message | 
		
		  | ushadenshah | 
			  
				|  Posted: Wed Feb 05, 2003 12:37 am    Post subject: PropertyVetoException - Urgent |   |  | 
		
		  | Newbie
 
 
 Joined: 23 Dec 2002Posts: 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 |  | 
		
		  |  | 
		
		  | yaakovd | 
			  
				|  Posted: Thu Feb 06, 2003 9:22 am    Post subject: |   |  | 
		
		  | Partisan
 
 
 Joined: 20 Jan 2003Posts: 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 |  | 
		
		  |  | 
		
		  | krismurali | 
			  
				|  Posted: Mon Feb 10, 2003 6:40 am    Post subject: PropertyVetoException - Urgent |   |  | 
		
		  |  Newbie
 
 
 Joined: 04 Feb 2002Posts: 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 |  | 
		
		  |  | 
		
		  | vennela | 
			  
				|  Posted: Mon Feb 10, 2003 7:32 am    Post subject: |   |  | 
		
		  |  Jedi Knight
 
 
 Joined: 11 Aug 2002Posts: 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 |  | 
		
		  |  | 
		
		  | krismurali | 
			  
				|  Posted: Mon Feb 10, 2003 9:17 am    Post subject: |   |  | 
		
		  |  Newbie
 
 
 Joined: 04 Feb 2002Posts: 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 |  | 
		
		  |  | 
		
		  | vennela | 
			  
				|  Posted: Mon Feb 10, 2003 11:34 am    Post subject: |   |  | 
		
		  |  Jedi Knight
 
 
 Joined: 11 Aug 2002Posts: 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 |  | 
		
		  |  | 
		
		  | Ratan | 
			  
				|  Posted: Mon Feb 10, 2003 12:35 pm    Post subject: |   |  | 
		
		  |  Grand Master
 
 
 Joined: 18 Jul 2002Posts: 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 |  | 
		
		  |  | 
		
		  |  |