[jboss-user] [JBoss jBPM] - Re: async pain
kukeltje wrote : so the 1 second is not to bad imo (jms could do this automatically for you with the retry-timeout) | ... I hope you jocking! ;) I am not agree to loose 99% of performance by getting only 1 command-exec instead of my current 100. 1 sec -solution is only solution for SimpleTest View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=4059807#4059807 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4059807 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss jBPM] - Re: async pain
thanks ed for working on this problem. I'd like to see some of the developers to work on this too to have it fixed in a public version. we did some bad hacks similar to ed's to get this to work, but still, I believe its not production ready. right now I don't have any more time to work on this, I just hope our stuff will do... al View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=4058602#4058602 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4058602 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss jBPM] - Re: async pain
Alex, There are 3 ways to get this fixed quickly: - Develop a good patch and contribute it - Get many people to vote for the issue - Buy commercial support and report it as a major issue. There are currently to few people having a problem with this to get it 'fixed' by the core developers working on it and dropping other things. View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=4058606#4058606 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4058606 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss jBPM] - Re: async pain
Ronald, you're absolutely right, but there's nothing I can do now. Our hacks are not of a quality for a patch. I can quickly describe what we did: - new job executor who is starting 1 job reader thread - job reader thread uses java executor service for thread pool - reads jobs from db and starts new single job execution thread for each job - synchronize on exclusive and on process id/node - wait 1 second in each single job execution thread to not interfere with other jobs still running, this is the worst part, but it works - changes are extensions, no patches. new job executor configured in jbpm config too bad above doesn't work with 3.2.1 how many is many people ? alex View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=4058616#4058616 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4058616 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss jBPM] - Re: async pain
ax666 wrote : Ronald, you're absolutely right, but there's nothing I can do now. | Our hacks are not of a quality for a patch. I can quickly describe what we did: | - new job executor who is starting 1 job reader thread | - job reader thread uses java executor service for thread pool | - reads jobs from db and starts new single job execution thread for each job | - synchronize on exclusive and on process id/node | - wait 1 second in each single job execution thread to not interfere with other jobs still running, this is the worst part, but it works | - changes are extensions, no patches. new job executor configured in jbpm config | | I asked one of the core developers to comment on this, so let's wait on that. Mind that real-time processing was never one of the main requirements of jBPM, so the 1 second is not to bad imo (jms could do this automatically for you with the retry-timeout) ax666 wrote : | too bad above doesn't work with 3.2.1 Hmm... so you mean there is a difference in this area between 3.2 and 3.2.1? ax666 wrote : | how many is many people ? | A few hundred no just kidding... getting it in the top 10 of most voted issues should be enough.. 3-5 votes i think View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=4058624#4058624 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4058624 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss jBPM] - Re: async pain
with 3.2.1 : anonymous wrote : 11:19:01,985 [pool-1-thread-1] DEBUG GraphElement - event 'node-leave' on 'Node(fileCheck)' for 'Token(/)' | 11:19:02,003 [pool-1-thread-1] DEBUG GraphElement - event 'transition' on 'Transition(check-to-fork)' for 'Token(/)' | 11:19:02,006 [pool-1-thread-1] DEBUG GraphElement - event 'node-enter' on 'Fork(fork1)' for 'Token(/)' | 11:19:02,010 [pool-1-thread-1] DEBUG DbMessageService - saved job[2, org.jbpm.job.ExecuteNodeJob] | 11:19:02,012 [pool-1-thread-1] DEBUG Token - token[1] is unlocked by token[1] | 11:19:02,024 [pool-1-thread-1] ERROR GraphElement - action threw exception: token '1' can't be locked by 'job[2]' cause it's already locked by 'token[1]' | org.jbpm.JbpmException: token '1' can't be locked by 'job[2]' cause it's already locked by 'token[1]' | at org.jbpm.graph.exe.Token.lock(Token.java:646) | View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=4058631#4058631 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4058631 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss jBPM] - Re: async pain
this occurs with me when I have async on the fork... View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=4058679#4058679 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4058679 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss jBPM] - Re: async pain
See (lengthy) update on http://jira.jboss.com/jira/browse/JBPM-983 -Ed Staub View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=4058347#4058347 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4058347 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss jBPM] - Re: async pain
I attached a new version of the test case to the jira issue. It's not working despite the changes. View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=4056869#4056869 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4056869 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss jBPM] - Re: async pain
If you expect the fork to behave as a multi-threaded parallel execution, then sorry.. that is not what jBPM is/does. If you want that, make the nodes in each leg of a fork async, but not the fork itself. According to the code, async on a node locks the currenttoken. Not strange then that in the join it cannot be reactivated. So try removing the async on both join and fork. View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=4056348#4056348 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4056348 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss jBPM] - Re: async pain
Alex, Building these kinds of 'does-this-file-exist' checks is not something we promote in doing with jBPM timers. The better solution is to have an ESB like solution, which often has really good file polling. This can then signal the tokens. You are correct in the assumption that JMS would not help in this case. I mixed two things up. The thing is that the subject does not cover the issue anymore. The issue is purely related to concurrent access to a token (in this case when 2 tokens go in the join) Sorry I did not try to run the testcase (yet) Do you get an exeption? btw, why is there an async=true on the fork? What behaviour do you expect? View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=4056345#4056345 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4056345 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss jBPM] - Re: async pain
A quick test with both the join and fork set to async=false gave me ERRORS too. View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=4056386#4056386 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4056386 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss jBPM] - Re: async pain
same ones? if so, can you post a stacktrace? In the meantime I'll try to get the case running View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=4056396#4056396 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4056396 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss jBPM] - Re: async pain
Alex,
I did some tests and I have varying results. Varying in the sense that the same
test run multiple times sometimes pass and sometimes don't.
This is what I used for the jobexecuterconfig
bean name=jbpm.job.executor class=org.jbpm.job.executor.JobExecutor
| field name=jbpmConfigurationref bean=jbpmConfiguration //field
| field name=namestring value=JbpmJobExector //field
| field name=nbrOfThreadsint value=2 //field
| field name=idleIntervalint value=5000 //field
| field name=maxIdleIntervalint value=360 //field !-- 1
hour --
| field name=historyMaxSizeint value=20 //field
| field name=maxLockTimeint value=60 //field !-- 10
minutes --
| field name=lockMonitorIntervalint value=6 //field !-- 1
minute --
| field name=lockBufferTimeint value=5000 //field !-- 5
seconds --
| /bean
My process:
| process-definition xmlns=urn:jbpm.org:jpdl-3.2 name=simpletest
| start-state name=start-state1
| descriptionstart of the process/description
| event type=node-enter
| script name=script_start
| System.out.println(START);
| executionContext.leaveNode();
| /script
| /event
| transition name=start-to-check to=fileCheck /
| /start-state
|
| node name=fileCheck
| script name=script_filecheck
| System.out.println(FILE-CHECK);
| executionContext.leaveNode();
| /script
| transition name=check-to-fork to=fork1/transition
| /node
|
| fork name=fork1
| transition name=toNode1 to=node1/transition
| transition name=toNode2 to=node2/transition
| /fork
|
| node name=node1 async=true
| script name=script_node1
| System.out.println(NODE1);
| executionContext.leaveNode();
| /script
| transition name=node1toJoin1 to=join1/transition
| /node
|
| node name=node2 async=true
| script name=script_node2
| System.out.println(NODE2);
| executionContext.leaveNode();
| /script
| transition name=node2toJoin1 to=join1/transition
| /node
|
| join name=join1
| transition name=join1ToNode3 to=node3/transition
| /join
|
| node name=node3
| script name=script_node3
| System.out.println(NODE3);
| /script
| transition name=node3ToEnd
to=end-state-success/transition
| /node
|
| end-state name=end-state-success
| descriptionprocess finished normally/description
| event type=node-enter
| script name=script_endSuccess
| System.out.println(END-SUCCESS);
| /script
| /event
| /end-state
| /process-definition
unittest
|
| public class AlexTest extends AbstractDbTestCase {
|
| public void testAlex(){
|
| try {
| ProcessDefinition processDefinition =
ProcessDefinition.parseXmlResource(alex.xml);
|
| processDefinition = saveAndReload(processDefinition);
| ProcessInstance processInstance = new
ProcessInstance(processDefinition);
| processInstance.signal();
| jbpmContext.save(processInstance);
| processJobs(2);
| processDefinition =
graphSession.loadProcessDefinition(processDefinition.getId());
| processInstance =
graphSession.loadProcessInstance(processInstance.getId());
| assertEquals(processDefinition.getNode(node3),
processInstance.getRootToken().getNode());
| } catch (Exception e) {
| e.printStackTrace();
| assertFalse(true);
| }
| }
|
| }
Try copying this test method multiple times in the testcase with different
names. Often the first one failes, but the others always succeed then.
changing async=true in async=exclusive makes the test always work.
For me this is the end of the research...
- async is exclusive makes the problem go away (tom suggested this in the other
thread, did you try it?)
- since the problem is kind of strange, I'm still of the opinion that jms
improves things.
- polling like you want to do it is not a 'good practice', using an ESB is.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4056487#4056487
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4056487
___
jboss-user mailing list
jboss-user@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss jBPM] - Re: async pain
ronald, the polling is only in the testcase. I added it because sometimes workflow simply did not finish. I will try the other stuff later and give a report. What I see now you're not using subprocesses. View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=4056504#4056504 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4056504 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss jBPM] - Re: async pain
no, correct, no subprocesses. I used the xml example in this topic View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=4056516#4056516 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4056516 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss jBPM] - Re: async pain
I fulfilled Ronalds request and added a version of the test case that uses an action handler. Our project state is, that jBPM allows only single thread execution which isn't something we can live with, but I don't have the time to investigate further. And yes, this should be fixed, right now I'm waiting for any reaction on this. Thanks for your efforts Ed! Alex View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=4055979#4055979 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4055979 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss jBPM] - Re: async pain
The reason I asked for a scriptless version is that I'm not the scripted version can run async very wel.. I assume the non-scripted version shows the same (for you unwanted) behaviour? View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=4056034#4056034 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4056034 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss jBPM] - Re: async pain
Now I come to think of it I/we overlooked something. AFAIR, the async mechanism in the WAR version of jBPM was for simple environments. For enterprise grade solutions, a switch should be made to JMS. More than one MDB can be deployed there which can process the async actions. (not scripted ones) Alex, do you use JMS or not? Is it an option? View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=4056035#4056035 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4056035 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss jBPM] - Re: async pain
Ronald, we're running the war in Tomcat without Jms. Behavior is the same with or without scripting. View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=4056096#4056096 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4056096 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss jBPM] - Re: async pain
ok.. I think Tom will be reluctant to 'fix' this since (and I have to check this) he did not want to build a new highly scalable async system where there is JMS. View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=4056128#4056128 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4056128 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss jBPM] - Re: async pain
If JMS like functionality is required consider using Mule. I hope this solves your problem View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=4056133#4056133 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4056133 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss jBPM] - Re: async pain
Ronald, Re JMS... can you explain how you think it will solve these problems? If you mean that there would be only one bean in the pool, that's not solving it at all - that's single-threading all requests. As I see it, the problem looks like one of token synchronization, and I don't see anything remotely relevant in the JMS support. -Ed Staub View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=4056154#4056154 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4056154 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss jBPM] - Re: async pain
ok, I partly mixed 2 things up but... nevertheless, the one/multiple threads thing of the jobexecutor was never explicitly meant to work (nor was it not meant to work) and no, I was not saying there should be one mdb but maybe the behaviour when jms is involved is different and why is it not enough to have multiple timers on one processinstance but have them processed one after the other... prevents locking to. Multiple threads could probably work then. StillI think that concurrent access to tokens is another issue... what should the behaviour be in those cases rather hard to decideSo is it a theoretical(?) case for workflow? I agree that the second timer should not fail, but rather report something like 'nothing to process anymore' correct?... Someone should try to describe some real scenario's so we can decide what the behaviour should be. View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=4056218#4056218 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4056218 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss jBPM] - Re: async pain
fady.matar wrote : If JMS like functionality is required consider using Mule. | I hope this solves your problem Or use JBoss AS (has JMS) or JBoss ESB ;-) View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=4056240#4056240 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4056240 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss jBPM] - Re: async pain
Alex, Apart from Ronald's request for scriptlessness, it doesn't look like anyone's dug into your http://jira.jboss.com/jira/browse/JBPM-983. Do you still need a fix? If so, I'll try to go after it in the next few days. -Ed Staub View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=4055596#4055596 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4055596 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss jBPM] - Re: async pain
http://jira.jboss.com/jira/browse/JBPM-983 View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=4053103#4053103 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4053103 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss jBPM] - Re: async pain
Alex, I took a quick look at the unit test. It uses a JbpmContextCallback class that I don't recognize, or see an import for. Do you need to attach it? I didn't look rigorously for other missing bits; you might want to. -Ed Staub View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=4053111#4053111 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4053111 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss jBPM] - Re: async pain
ed, thanks for pointing htat out, I added the missing interface, the unit test should not depend on anything now... alex View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=4053162#4053162 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4053162 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss jBPM] - Re: async pain
I can't provide anything useful to go on with, in every run something different doesn't work. Sometimes a subprocess is not executed any more, sometimes variables are lost or an action handler's executionContext doesn't have a contextInstance (executionContext.getContextInstance() returns null). It's just something goes terribly wrong, and its hard to tell what. I don't have the time to dig further in this. I guess we will leave it to single threaded execution for now and look for some other product to use. Our project has to be finished soon... I might do some test case and open a jira issue... alex View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=4052130#4052130 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4052130 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss jBPM] - Re: async pain
Could someone please confirm that this simple process doesn't work with more than 1 JobExecutor thread configured? | ?xml version=1.0 encoding=UTF-8? | process-definition xmlns=urn:jbpm.org:jpdl-3.2 name=simpletest | start-state name=start-state1 | descriptionstart of the process/description | event type=node-enter | script name=script_start | System.out.println(START); | executionContext.leaveNode(); | /script | /event | transition name=start-to-check to=fileCheck / | /start-state | | node name=fileCheck async=true | script name=script_filecheck | System.out.println(FILE-CHECK); | executionContext.leaveNode(); | /script | transition name=check-to-fork to=fork1/transition | /node | | fork name=fork1 async=true | transition name=toNode1 to=node1/transition | transition name=toNode2 to=node2/transition | /fork | | node name=node1 async=true | script name=script_node1 | System.out.println(NODE1); | executionContext.leaveNode(); | /script | transition name=node1toJoin1 to=join1/transition | /node | | node name=node2 async=true | script name=script_node2 | System.out.println(NODE2); | executionContext.leaveNode(); | /script | transition name=node2toJoin1 to=join1/transition | /node | | join name=join1 async=true | transition name=joinToEnd to=end-state-success/transition | /join | | end-state name=end-state-success | descriptionprocess finished normally/description | event type=node-enter | script name=script_endSuccess | System.out.println(END-SUCCESS); | /script | /event | /end-state | /process-definition | thanks, alex View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=4052207#4052207 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4052207 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss jBPM] - Re: async pain
executionContext.leaveNode(); in a startnode on an event? Does that work correctly? and the same in async nodes? hm... looks a bit strange to me What if you use java classes for leaving these nodes. Same errors then? View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=4052225#4052225 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4052225 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss jBPM] - Re: async pain
Alex, Maybe in Timer.Timer(token) and Timer.Timer() you could try calling setExclusive(). Once again, both thanks and condolences for being a pioneer in this area! -Ed Staub View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=4051715#4051715 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4051715 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss jBPM] - Re: async pain
I reworked my processes and avoid timers now at all. The waiting and timing out is done in the ActionHandlers now. Let's see what the next problem is. The jBPM guys should write a simple process definition to test with, just async join/fork with nodes using timers, all with multiple JobExecutor threads. Lots of problems, guaranteed! View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=4051738#4051738 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4051738 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss jBPM] - Re: async pain
Alex, That's not much to go on... -Ed Staub View the original post : http://www.jboss.com/index.html?module=bbop=viewtopicp=4051800#4051800 Reply to the post : http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4051800 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
