Here the process:
| ...
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
anonymous wrote : Is it not possible the fork/join with the intermediate nodes
in async way?
You mean async nodes between the fork and the join? If you think this is a
problem, please make a unittest for it that demonstrates the problem
View the original post :
http://www.jboss.com/index.html
Has somebody resolve this issue?
Is it not possible the fork/join with the intermediate nodes in async way?
Thanks
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4134605#4134605
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=re
Not 100% sure on this but I've had similar problems - I think that on async a
job is put in the database for execution to start at the given node. The job
executor servlet then picks it up and wants to run it. But since there is
already a token lock from the instance running from the console thr
Honestly, does no one have any suggestions? Is this such a strange question
after all?
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4088308#4088308
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4088308
___
Fair enough. However, is there a reason I am getting the same exceptions no
matter if I use the JobExecutor or Jms Queues? Is there a way to overcome the
fact that whenever I have a fork with asynchronous nodes I get the stack trace
shown above?
View the original post :
http://www.jboss.com/
afaik, the suite does not use the enterprise version, but the plain version.
The plain version uses the jobexcutor, the enterprise version jms queues
(again, afaik)
So it should not be necessary to use the jobexecutor and post the exceptions
you get when running the enterprise version on your J
