[JBoss jBPM] - jBPM timer and scheduler
by frinux
Hi,
I'm posting here because I can't find lot's of information about how to set up timers in jBPM.
I've added a timer to my task :
<timer name="waitForApproval"
| duedate="1 minute"
| transition="validee" >
| <script>
| System.out.println("Le valideur est trop lent : valid????e !!!");
| </script>
| </timer>
It seems timers need what you call a scheduler service. After some researches, I find out that I must add this to my web.xml :
| <servlet>
| <servlet-name>JbpmThreadsServlet</servlet-name>
| <servlet-class>org.jbpm.web.JbpmThreadsServlet</servlet-class>
| <load-on-startup>1</load-on-startup>
| </servlet>
| <servlet-mapping>
| <servlet-name>JbpmThreadsServlet</servlet-name>
| <url-pattern>/threads</url-pattern>
| </servlet-mapping>
|
I did that, but I find an exception :
java.lang.ClassNotFoundException: org.jbpm.web.JbpmThreadsServlet
And surprise! There is no such class in my jbpm jar file. I took the last one from jbpm-installer-3.2.6.SP1.jar : jbpm-jpdl.jar
On JarSearch, I found that the class is present only in version jbpm-3.1.4.jar and before.
So what am I doing wrong, or what did I miss?
Thanks
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4223063#4223063
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4223063
15 years, 9 months
[Advanced Documentation] - Re: Maximum Hardware Requirement for Jboss v- 4.0.3
by PeterJ
The limits are not with JBoss AS but rather with the JVM. If you run a 32-bit JVM you cannot make the heap larger than about 1.7GB (Windows) or 2.7GB (Linux). Wit ha 64-bit JVM you can get larger heaps, but larger heaps are not always practical - a major GC can take a long time.
Some multi-core chips tend to share L2 cache between the cores (on my Intel quad core, I have two L2 caches, each shared by two cores), in which case you have fewer issues cache invalidation among the threads. But multi-core chips also tend to not have a memory bus per core - often a pair of cores shares the memory bus. But this is all dependent on whether you are looking at Intel or AMD chips, each is different. The best thing to do is benchmark your app with both sets of hardware. If that is not possible, go with the hardware that gives you the most on-chip cache.
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4223047#4223047
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4223047
15 years, 9 months