[Design of JBoss jBPM] - Re: Asynchronous Continuation with JBPM 3.2.2
by mandrita.ca
Hi tom,
I checked out the web.xml file of the deployed web-app and found the following entry:
<servlet-name>JobExecutorServlet</servlet-name>
<servlet-class>org.jbpm.job.executor.JobExecutorServlet</servlet-class>
<load-on-startup>1</load-on-startup>
<servlet-mapping>
<servlet-name>JobExecutorServlet</servlet-name>
<url-pattern>/jobs</url-pattern>
</servlet-mapping>
So the job executor loads up on startup.But is there some other way I can verify the same?
One more thing I am trying the fork-join concept.As the fork node states that it splits an execution path into branches.However when i associate two tasks with the fork handler and attach two action handler for the same to print the Thread IDs i find that the Thread IDs are same and also i verified that these classes are executed on the same thread as when one branch throws an error the entire execution stops.Also as you mentioned that pending messages get inserted into the JBPM_JOB table i didn't find any entry for the two asynch nodes.
Where am i going wrong?Totally clueless...
Please help.
Thanks,
Mandrita
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4111102#4111102
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4111102
18 years, 4 months
[Design of JBoss Profiler] - Re: Profiler Setup
by william-zhu
Hello, thanks for your help!
now, I got the issue about directory. but encoutered a new problem when attemptting to add a parameter to JVM by executing the following:
java -XrunjbossInspector:/tmp,include=org.jboss,ignore=*,start=org.jboss.mq.MQServer
the messages are like:
this is the new DLL
Running process on Windows 4040
Usage: java [-options] class [args...]
<to execute a class>
or java [-options] -jar jarfile [args....]
<to execute a jar file>
.......................
I have read the guides and a jboss profiler quick start released in the forum.
Installation quick start:
1) copy jboss-profiler-noAOP.sar to the JBoss AS deploy directory
2) put jbossInspector.dll in your PATH (Windows)
or libjbossInspector.so in your LD_LIBRARY_PATH (Linux/Unix)
3) copy jboss-profiler.war to the JBoss AS deploy directory
Configuration:
1) Add something like this to the JBoss JVM options: -XrunjbossInspector:/tmp/profiler,include=com.unisys,ignore=*,memory=false
Make sure the output directory (/tmp/profiler in this example) exists.
thanks for your any ideas
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4111097#4111097
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4111097
18 years, 4 months