[JBoss Cache Users] - Re: JBC spends 90% of its time in TPE$Worker.run
by chtimi2
Hi Manik
yes it might be serialization. But still with the async tag, this serialization is supposed to happen asynchronously after the commit right? So by definition it shouldn't increase latency.
I have reduced the latency a lot (more than half) by:
-using invalidation instead of replication
-setting a Heap size that is a bit more than what is really used, instead of the big heap i used before
But it is still a bit slow, and CPU usage (another of our requirements) is at 50% instead of 10%. Isn't a 50% CPU load too much for this use case? (A and B are quad-core 2.33GHz 4G RAM, linked by a 100Mega switch (yes that is slow but this too is a requirement))
At any rate from what i saw in VisualVM i suspect that the threads that i mentioned are what makes CPU usage so high.
Anyway any clue? What can i do to investigate further?
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4270138#4270138
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4270138
15 years
[jBPM Users] - Re: task & timers
by MohReece
>From the code you supplied I cannot see why the timer is not created (I'm assuming that you're not using abstract classes as handlers and that the class name for the task timer action handler does match in your actual code, because otherwise you'd have other problems running your example). At a first glance it seems to be OK...
What should happen is that an automatic task instance is created upon the node-enter event, when the StartCheck handler is executed and the TaskMgmtInstance.createTaskInstance(...) method is called; this should trigger the task-create event by which the CreateTimerAction should be executed (which was inserted when the process definition containing the task node was parsed from its XML form).
This CreateTimerAction is supposed to be creating the timer instance in the Scheduler service (i.e. saving the timer job on the JobSession).
My advice would be to crank up the logging levels to reveal the jBPM debug entries and see whether the expected events occur and if the timer is saved to the JobSession. Then you may be able to backtrace what went wrong...
I'm aware this is not too helpful yet, but from the given code it's all the help I can offer you so far...
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4270136#4270136
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4270136
15 years