VMware
Orchestrator APIs:

This Question is Answered

1 "correct" answer available (10 pts) 2 "helpful" answers available (6 pts)
6 Replies Last post: Jul 16, 2009 5:03 AM by siayiu  

Recieving error with a VMO Plugin that has a JMS stack built-in posted: Jul 8, 2009 4:36 PM

Click to view pwyzorski-wyzguy's profile Enthusiast
pwyzorski-wyz…
81 posts since
Jun 5, 2008
Hey,

I have an Orchestrator 4.0 plug-in with a JMS client stack that I am attempting to initialize from within a Orchestrator workflow. The class that supports the JMS stack is getting properly created, but I am recieving an error upon initialization. Error log is below. Can anyone on the Orchestrator team take a look at it?

regards,

~Patrick

INFO | jvm 1 | 2009/07/08 15:04:38 | 2009-07-08 15:04:38.653-0700 DEBUG WrappedJavaMethod Calling method : public void ppsb.stagebank.MessageClient.initializeMessageClient()
INFO | jvm 1 | 2009/07/08 15:04:38 | 2009-07-08 15:04:38.653-0700 ERROR MessageClient destroyMessageClient: null
INFO | jvm 1 | 2009/07/08 15:04:38 | 2009-07-08 15:04:38.653-0700 DEBUG SCRIPTING_LOG org/apache/activemq/ActiveMQConnectionFactory (Workflow:Initialize SPT JMS / Initialize JMS Client (item0)#1)
INFO | jvm 1 | 2009/07/08 15:04:38 | 2009-07-08 15:04:38.669-0700 DEBUG WorkflowScriptRunner Execute exception
INFO | jvm 1 | 2009/07/08 15:04:38 | org.mozilla.javascript.EvaluatorException: org/apache/activemq/ActiveMQConnectionFactory (Workflow:Initialize SPT JMS / Initialize JMS Client (item0)#1)
INFO | jvm 1 | 2009/07/08 15:04:38 | at org.mozilla.javascript.DefaultErrorReporter.runtimeError(DefaultErrorReporter.java:95)
INFO | jvm 1 | 2009/07/08 15:04:38 | at org.mozilla.javascript.Context.reportRuntimeError(Context.java:978)
INFO | jvm 1 | 2009/07/08 15:04:38 | at org.mozilla.javascript.Context.reportRuntimeError(Context.java:1034)
INFO | jvm 1 | 2009/07/08 15:04:38 | at ch.dunes.vso.sdk.WrappedJavaMethod.call(Unknown Source)
INFO | jvm 1 | 2009/07/08 15:04:38 | at org.mozilla.javascript.Interpreter.interpretLoop(Interpreter.java:3082)
INFO | jvm 1 | 2009/07/08 15:04:38 | at script(Workflow:Initialize SPT JMS / Initialize JMS Client (item0):1)
INFO | jvm 1 | 2009/07/08 15:04:38 | at org.mozilla.javascript.Interpreter.interpret(Interpreter.java:2248)
INFO | jvm 1 | 2009/07/08 15:04:38 | at org.mozilla.javascript.InterpretedFunction.call(InterpretedFunction.java:158)
INFO | jvm 1 | 2009/07/08 15:04:38 | at org.mozilla.javascript.ContextFactory.doTopCall(ContextFactory.java:337)
INFO | jvm 1 | 2009/07/08 15:04:38 | at org.mozilla.javascript.ScriptRuntime.doTopCall(ScriptRuntime.java:2755)
INFO | jvm 1 | 2009/07/08 15:04:38 | at org.mozilla.javascript.InterpretedFunction.exec(InterpretedFunction.java:169)
INFO | jvm 1 | 2009/07/08 15:04:38 | at org.mozilla.javascript.Context.evaluateString(Context.java:1144)
INFO | jvm 1 | 2009/07/08 15:04:38 | at ch.dunes.scripting.server.script.MainScriptingObject.executeScript(Unknown Source)
INFO | jvm 1 | 2009/07/08 15:04:38 | at ch.dunes.scripting.server.script.MainScriptingObject.executeScript(Unknown Source)
INFO | jvm 1 | 2009/07/08 15:04:38 | at ch.dunes.workflow.engine.mbean.WorkflowScriptRunner.execute(Unknown Source)
INFO | jvm 1 | 2009/07/08 15:04:38 | at ch.dunes.workflow.engine.mbean.ScriptWorkflowItemRunner.runWorkflowItemTask(Unknown Source)
INFO | jvm 1 | 2009/07/08 15:04:38 | at ch.dunes.workflow.engine.mbean.runner.WorkflowItemTaskRunner.execute(Unknown Source)
INFO | jvm 1 | 2009/07/08 15:04:38 | at ch.dunes.workflow.engine.mbean.runner.WorkflowRunner.execute(Unknown Source)
INFO | jvm 1 | 2009/07/08 15:04:38 | at ch.dunes.workflow.engine.mbean.runner.WorkflowTokenRunner.execute(Unknown Source)
INFO | jvm 1 | 2009/07/08 15:04:38 | at ch.dunes.workflow.engine.mbean.helper.WorkflowHandler.execute(Unknown Source)
INFO | jvm 1 | 2009/07/08 15:04:38 | at ch.dunes.workflow.engine.mbean.helper.WorkflowHandler.run(Unknown Source)
INFO | jvm 1 | 2009/07/08 15:04:38 | at java.lang.Thread.run(Unknown Source)
INFO | jvm 1 | 2009/07/08 15:04:38 |
INFO | jvm 1 | 2009/07/08 15:04:38 | 2009-07-08 15:04:38.669-0700 WARN WorkflowItemTaskRunner Script execution error on workflow : Initialize SPT JMS / 'Initialize JMS Client'(item0) : org/apache/activemq/ActiveMQConnectionFactory (Workflow:Initialize SPT JMS / Initialize JMS Client (item0)#1)
INFO | jvm 1 | 2009/07/08 15:04:38 | 2009-07-08 15:04:38.669-0700 DEBUG WorkflowItemTaskRunner Script execution error stack
INFO | jvm 1 | 2009/07/08 15:04:38 | ch.dunes.workflow.engine.mbean.ScriptExecutionException: org/apache/activemq/ActiveMQConnectionFactory (Workflow:Initialize SPT JMS / Initialize JMS Client (item0)#1)
INFO | jvm 1 | 2009/07/08 15:04:38 | at ch.dunes.workflow.engine.mbean.WorkflowScriptRunner.execute(Unknown Source)
INFO | jvm 1 | 2009/07/08 15:04:38 | at ch.dunes.workflow.engine.mbean.ScriptWorkflowItemRunner.runWorkflowItemTask(Unknown Source)
INFO | jvm 1 | 2009/07/08 15:04:38 | at ch.dunes.workflow.engine.mbean.runner.WorkflowItemTaskRunner.execute(Unknown Source)
INFO | jvm 1 | 2009/07/08 15:04:38 | at ch.dunes.workflow.engine.mbean.runner.WorkflowRunner.execute(Unknown Source)
INFO | jvm 1 | 2009/07/08 15:04:38 | at ch.dunes.workflow.engine.mbean.runner.WorkflowTokenRunner.execute(Unknown Source)
INFO | jvm 1 | 2009/07/08 15:04:38 | at ch.dunes.workflow.engine.mbean.helper.WorkflowHandler.execute(Unknown Source)
INFO | jvm 1 | 2009/07/08 15:04:38 | at ch.dunes.workflow.engine.mbean.helper.WorkflowHandler.run(Unknown Source)
INFO | jvm 1 | 2009/07/08 15:04:38 | at java.lang.Thread.run(Unknown Source)
INFO | jvm 1 | 2009/07/08 15:04:38 | 2009-07-08 15:04:38.700-0700 DEBUG WorkflowRunner #### No catch exception (root workflow)
INFO | jvm 1 | 2009/07/08 15:04:38 | 2009-07-08 15:04:38.700-0700 TRACE VSOFactoryBean --updateWorkflowTokenWithContent() called.
INFO | jvm 1 | 2009/07/08 15:04:38 | 2009-07-08 15:04:38.716-0700 TRACE DunesObjectJMSHelper -- notify dunes model changes : 'edit' on object : 91808080808080808080808080808080808080800124603703214331e2f6fa669
INFO | jvm 1 | 2009/07/08 15:04:38 | 2009-07-08 15:04:38.716-0700 DEBUG WorkflowEngine ItemNameStack : '/item0' - Exception : 'org/apache/activemq/ActiveMQConnectionFactory (Workflow:Initialize SPT JMS / Initialize JMS Client (item0)#1)' (91808080808080808080808080808080808080800124603703214331e2f6fa669) - GlobalState : 'failed'
INFO | jvm 1 | 2009/07/08 15:04:38 | 2009-07-08 15:04:38.716-0700 TRACE LogFactoryBean --Inserting LogEvent ( '2', 'org/apache/activemq/ActiveMQConnectionFactory (Workflow:Initialize SPT JMS / Initialize JMS Client (item0)#1)' - originatorUri:'dunes://service.dunes.ch/WorkflowToken?id='91808080808080808080808080808080808080800124603703214331e2f6fa669'&dunesName='WorkflowToken'' )
INFO | jvm 1 | 2009/07/08 15:04:38 | 2009-07-08 15:04:38.716-0700 TRACE SharedVSOFactoryClient JMS Received (edit) : ch.dunes.model.workflow.WorkflowToken@4ce1cd Registered : null
INFO | jvm 1 | 2009/07/08 15:04:38 | 2009-07-08 15:04:38.716-0700 TRACE SharedVSOFactoryClient Received change on an object not registered in the factory !
INFO | jvm 1 | 2009/07/08 15:04:38 | 2009-07-08 15:04:38.731-0700 TRACE VSOFactoryClient JMS Received (edit) : ch.dunes.model.workflow.WorkflowToken@17c6631 Registered : null
INFO | jvm 1 | 2009/07/08 15:04:38 | 2009-07-08 15:04:38.731-0700 TRACE VSOFactoryClient Received change on an object not registered in the factory !
INFO | jvm 1 | 2009/07/08 15:04:38 | 2009-07-08 15:04:38.731-0700 DEBUG WorkflowHandler Workflow 'Initialize SPT JMS' failed.
INFO | jvm 1 | 2009/07/08 15:04:38 | 2009-07-08 15:04:38.731-0700 DEBUG WorkflowHandler Ending WorkflowHandler (91808080808080808080808080808080808080800124603703214331e2f6fa669)
INFO | jvm 1 | 2009/07/08 15:04:38 | 2009-07-08 15:04:38.731-0700 DEBUG VSOFactoryClient Disconnect from server
INFO | jvm 1 | 2009/07/08 15:04:38 | 2009-07-08 15:04:38.731-0700 TRACE VSOFactoryBean --disconnect() called.
INFO | jvm 1 | 2009/07/08 15:04:38 | 2009-07-08 15:04:38.731-0700 DEBUG VSOFactoryBean --VSOFactoryBean - ejbRemove called and session '1247090677466'
INFO | jvm 1 | 2009/07/08 15:04:38 | 2009-07-08 15:04:38.747-0700 DEBUG WorkflowHandler MainScriptingObject exited
INFO | jvm 1 | 2009/07/08 15:04:38 | 2009-07-08 15:04:38.747-0700 DEBUG WorkflowHandler Context exited
INFO | jvm 1 | 2009/07/08 15:04:38 | 2009-07-08 15:04:38.856-0700 TRACE VSOFactoryBean --getWorkflowForId() called.
INFO | jvm 1 | 2009/07/08 15:04:38 | 2009-07-08 15:04:38.872-0700 TRACE VSOFactoryBean --getWorkflowTokenContent() called.
INFO | jvm 1 | 2009/07/08 15:04:38 | 2009-07-08 15:04:38.872-0700 TRACE VSOFactoryBean --getWorkflowForId() called.
INFO | jvm 1 | 2009/07/08 15:04:38 | 2009-07-08 15:04:38.888-0700 TRACE VSOFactoryBean --getDebugLocation() called.
INFO | jvm 1 | 2009/07/08 15:04:38 | 2009-07-08 15:04:38.888-0700 TRACE VSOFactoryBean --getWorkflowForId() called.
INFO | jvm 1 | 2009/07/08 15:04:39 | 2009-07-08 15:04:39.091-0700 TRACE VSOFactoryBean --getChildsCountForWorkflowToken() called.
INFO | jvm 1 | 2009/07/08 15:04:39 | 2009-07-08 15:04:39.278-0700 DEBUG LocalPublisher Create Publisher on : PolicyLogTopic
INFO | jvm 1 | 2009/07/08 15:04:39 | 2009-07-08 15:04:39.278-0700 DEBUG LocalPublisher Message Dispatcher hooked on : PolicyLogTopic
INFO | jvm 1 | 2009/07/08 15:04:39 | 2009-07-08 15:04:39.403-0700 TRACE VSOFactoryBean --getWorkflowForId() called.
INFO | jvm 1 | 2009/07/08 15:04:39 | 2009-07-08 15:04:39.403-0700 TRACE VSOFactoryBean --getWorkflowForId() called.
INFO | jvm 1 | 2009/07/08 15:04:39 | 2009-07-08 15:04:39.419-0700 TRACE VSOFactoryBean --getWorkflowForId() called.


Don't forget if the answers help, award points

Re: Recieving error with a VMO Plugin that has a JMS stack built-in

1. Jul 9, 2009 12:40 AM in response to: pwyzorski-wyz…
Click to view Cédric's profile Hot Shot VMware Employees
Cédric
80 posts since
Jun 27, 2008
Hi,

How do you have defined your scripting objects in VSO.xml? Do you use the "Singleton" pattern?

Re: Recieving error with a VMO Plugin that has a JMS stack built-in

2. Jul 9, 2009 12:57 AM in response to: Cédric
Click to view pwyzorski-wyzguy's profile Enthusiast
pwyzorski-wyz…
81 posts since
Jun 5, 2008

I have no "singleton" scripting objects defined in my "vso.xml" file. Should I have? What the purpose of the "singleton" attribute anyways? The Developers Guide isn't exactly clear.

regards,

~Patrick

Don't forget if the answers help, award points

Re: Recieving error with a VMO Plugin that has a JMS stack built-in

3. Jul 9, 2009 1:57 AM in response to: pwyzorski-wyz…
Click to view Cédric's profile Hot Shot VMware Employees
Cédric
80 posts since
Jun 27, 2008
The purpose is to define some sort of Singleton object: you can compare the usage to a Java class with only Static members.

But your object is instanciated by vCO when you need it.

When exactly do you have the message error? Do you have some scripting execution? Or does it happen before any workflow start?

Re: Recieving error with a VMO Plugin that has a JMS stack built-in

4. Jul 9, 2009 2:20 AM in response to: Cédric
Click to view pwyzorski-wyzguy's profile Enthusiast
pwyzorski-wyz…
81 posts since
Jun 5, 2008
Workflow has started, in fact I manually launch a vCO workflow that calls the plug-in Java class which initializes the JMS Client. Here is the reference the debug log:
"public void ppsb.stagebank.MessageClient.initializeMessageClient()"


It seems to get called as the JMS client code appears to be getting invoked. Here is the reference that has me believe that:
"org/apache/activemq/ActiveMQConnectionFactory (Workflow:Initialize SPT JMS / Initialize JMS Client (item0)#1)"

But later it errors and this message has me concerned:
"Received change on an object not registered in the factory !"
What does the above error message mean?

Don't forget if the answers help, award points

Re: Recieving error with a VMO Plugin that has a JMS stack built-in

5. Jul 9, 2009 2:00 PM in response to: pwyzorski-wyz…
Click to view pwyzorski-wyzguy's profile Enthusiast
pwyzorski-wyz…
81 posts since
Jun 5, 2008

I didn't copy my dependent jar files to the proper location "app-server/lib" directory in the Orchestrator environment. I had actually copied them to the "app-server/server/vmo/lib" directory. Copied all dependent jars to both directories and rebooted Orchestrator fixed things. My JMS Client is now happily processing messages.

regards,

~Patrick

Re: Recieving error with a VMO Plugin that has a JMS stack built-in

6. Jul 16, 2009 5:03 AM in response to: pwyzorski-wyz…
Click to view siayiu's profile Hot Shot VMware Employees
siayiu
74 posts since
Feb 4, 2008

Moving thread to the forum that is more appropriate. Please post plugin API & web service API related topics in the Orchetrator API forum.

Thanks,

Sia

Actions

Developer SDKs & APIs

Developer Resources

Developer Social Media

Communities