Thanks for the information and the workaround.
I think it's unintuitive behavior at best.
Ian
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3925906#3925906
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3925906
---
I'm using 3.1.
It strikes me that if an action is used for task assignment, it should call the
action every time. What if a process instance runs for a long time (mine will
run for at least 3 or 4 months) and the task actors should be set based on
information that could be modified by the appl
I have a process with a task in a loop, and although the assignment handler
gets called the first time, it doesn't get called any subsequent times. Here's
an example process that shows the behavior:
|
|
|
|
|
|
|
|
|
Shriram,
I am successfully using both multiple subprocesses AND
.getSubProcessInstance(), so I doubt that's the issue.
Are the SubProcessInstanceIDs getting set in the database? Look at the values
manually to tell. If they are null, make sure that you are saving the process
instances you cre
Haha. My oh my. It has been one long week.
One of my co-developer's was running an instance of our app against the same
database. /His/ instance of my scheduler was executing the timers.
Wow.
I'm so optimistic that my first hope was magic. :)
Ian
View the original post :
http://www.jboss
And one more follow up question: Does that make external schedulers
unnecessary? Mine just seems to annoy me with log statements every 5 seconds.
:)
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3924449#3924449
Reply to the post :
http://www.jboss.com/in
I just migrated my code from 3.0.2 to 3.1, and umm, I've noticed something
strange with the scheduler that I was using previously to execute timers. It
finds the timers, but then doesn't execute them. Instead, they just disappear.
Now, I've checked the database; they're working properly.
Do
I'm more than willing to give back by contributing this solution; just gotta
test it a bit more and see if I can't make it a little more robust. :)
Ian
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3924442#3924442
Reply to the post :
http://www.jboss.com/i
Can anyone give any recommendations on the best sort of scheduler to use in a
distributed JBoss environment?
Right now I have a custom-made SLSB that mimics the behavior of
org.jbpm.scheduler.impl.SchedulerServlet using javax.ejb.Timer's. Can anyone
offer any insight on this approach (any pitf
Koen,
3.1 seems to solve this problem. Thanks!
Ian
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3923948#3923948
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3923948
---
Koen,
Thanks for your response. Also, I apologize, I'm usually much better at
posting symptoms of problems. I migrated to 3.1 to try to correct issues I was
having with 3.0.2, and it was on the whole a long and frustrating day. :)
In the course of getting the information together for this re
I'll be the first to admit, I've had more than a tiny bit of difficulty using
jBPM as our workflow solution. I had several issues with timer and
subProcessInstance persistence with 3.0.2, so I switched today to 3.1.
However, now I'm having some problems I didn't have before, even before I've
In the process of migrating my code and processes from 3.0.2 to 3.1, I've
encountered the following issue:
When deploying the following process
|
|
|
|
|
|
|
from a stateless session bean (with pd = parseXMLString(...);
jbpmContext.deployProcessDefin
http://jira.jboss.com/jira/browse/JBPM-559
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3923736#3923736
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3923736
---
Th
Haha. Further experimentation shows me what I can only assume must be a bug in
the interpretation of whitespace.
The following revision to the test process works as expected:
|
|
|
|
|
|
|
|
|
Is there any example code for a decision node in version 3.1? I'm migrating my
code from 3.0.2 and it sounds like that has to change to a JSP-like syntax.
Unfortunately, I don't see any relevant code snippets in the user guide, the
migration guide, or in src/process.examples.
Here's my test p
mennen: I do believe you should post further questions about this in a new
thread; your problem appears unrelated to mine.
But. I'm not a jBPM expert by any means, but my guess is that since the action
DoNothing is associated with the timer in state1, and not directly with the
task you define
3.0.2 right now.
I may try to migrate my existing code to 3.1 though, to see if I still have
trouble there.
Ian
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3923583#3923583
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=repl
ejimenez:
anonymous wrote : Is there something you want to do that you cant accomplish
using the subprocess end event?
Actually, I think yes. I have a process that uses subprocesses for repetitive
tasks like calling someone (with carefully designed business rules for a busy
signal, leaving a
Any chance anyone thought about this over the weekend and came up with some
great insight? :)
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3923335#3923335
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3923335
-
Thanks for the information, guys.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3923332#3923332
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3923332
---
This SF.net
Ok, here's the situation.
I have a process that relies heavily on timers. In fact, the business process
looks something like: do something, do something else after 10 days, do
something else after 10 more days, etc. Some of the somethings are automated
(node), and some are not (tasknode).
My
Maybe I can try to be at least a little useful then, after that bad advice.
;-)
Using JBoss 4.0.3 I have:
|
hibernate.transaction.factory_class=org.hibernate.transaction.JTATransactionFactory
|
hibernate.transaction.manager_lookup_class=org.hibernate.transaction.JBossTransactionManager
Alternatively, you could probably use xdoclet as:
[MDB xdoclet settings: transaction-type="Bean" ]
Don't quote that as gospel; just guessing. :)
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3922563#3922563
Reply to the post :
http://www.jboss.com/index.h
Tom,
I see you try accessing it in a new transaction; is that also starting a new
jbpmSession? I get the error when everything is persisted and I try accessing
it in a later session; it works fine when still in the original one.
I'm using 3.0.2; I tried going to 3.1 beta 3 to test it, but I h
I've had similar errors using EJB Timers. I believe what is going on is that
your application server is managing your transactions but that is not getting
communicated to jBPM's Hibernate.
Since my timer's logic was simple and purely jBPM related, I solved the problem
by letting the bean manag
I have a similar problem, and have posted about it here:
http://www.jboss.com/index.html?module=bb&op=viewtopic&t=76936
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3922290#3922290
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mo
I'm having a little bit of trouble accessing a subprocess instance via a
Token's getSubProcessInstance method.
I'm using the processes:
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Nevermind, fixed it! The answer is very simple. Turns out that after doing a
task you have to explicitly save the process instance, like so:
|
jbpmSession.getGraphSession().saveProcessInstance(task.getTaskMgmtInstance().getProcessInstance());
|
View the original post :
http://www.jbos
I'm using jBPM in an EJB3 application, and I didn't feel that the web tier was
the proper place for the scheduler. I wrote a stateless session bean that uses
EJB3 timers for scheduling instead. It's basically the same algorithm (oh, and
same code :) that's in the servlet, just now instead of u
Anyone able to offer any insight on this problem? :)
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3914787#3914787
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3914787
--
More info (whoops!):
If I advance from "call" directly with a processInstance.signal("go"), the
timer is created and found and works properly.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3913657#3913657
Reply to the post :
http://www.jboss.com/index.html?
I'm experimenting with jBPM before integrating it into my application, and I've
run into a small snag.
My original process went like this:
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
I'm currently having trouble reobtaining a reference to a sfsb, myself.
Unfortunately, I've tried every method listed in this thread. :)
My initial (perhaps naive) approach was to stick a reference to the bean in the
HttpSession, but after approximately 2-5 minutes method invocations via that
34 matches
Mail list logo
