With the EJB-based scheduler service, timer persistence is the responsibility
of the EJB container. jBPM will save Timer objects to the database, but it is
up to the EJB timer service to execute them.
Check your EJB timer configuration. In JBoss AS the persistence policy
implementation in use
Have you solucionated this???
I've looked into the jboss jbpm log and I found this:
| 2009-01-14 11:37:08,812 INFO [org.quartz.core.QuartzScheduler] Scheduler
DefaultQuartzScheduler_$_NON_CLUSTERED started.
|
I suposse that the scheduler is running but the timer doesn't work!!
Any
i think that in the jbpm.cfg.xml must be appear the next line
| service name=scheduler
factory=org.jbpm.scheduler.db.DbSchedulerServiceFactory /
|
but i don't know how to test that the scheduler is really running.
is this ok?
View the original post :
i have defined:
in the class i have a system.out.println but i don't see the message after
waiting the 20 seconds that i have defined.
I am using my personal webapp deployed in tomcat.
any idea?
thanks
View
sorry, i have problems with the code:
| state name=state1
| timer duedate=20 seconds name=imprimirMensaje
| action
class=cinfo.proyecto.wf.modelo.handlers.ImprimirMensajeHandler/action
| /timer
| transition to=task-node1/transition
| /state
|
View the original post :
is the scheduler running?
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4201012#4201012
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4201012
___
jboss-user mailing list
How I could ckeck if the scheduler is running?? I'm using jboss jbpm 3.2.3 and
in the deploy folder are two files called schedule-manager-service.xml
scheduler-service.xml but all its content are commented. How explain me a bit
or redirect any site where I could find information about timers
There is nothing wrong with the documentation except for maybe it being a
little bit (too?) concise:
1. If you specify a timer on a node it gets translated to a create-timer and a
cancel-timer action. The create-timer action is associated with the node-enter
event and the cancel-timer action
The relevant portion of the docs can be found here:
http://docs.jboss.com/jbpm/v3.2/userguide/html_single/#tasktimers
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4187902#4187902
Reply to the post :
Sorry, the code was cut during submitting it should look this:
state name=warte 1
| timer name='reminder'
| duedate='2 minutes'
| transition='ex1'
|cancel-timer name='reminder'/
| /timer
| transition
Is the job scheduler correctly configured in the jbpm.cfg ? Please post the
config here.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4179768#4179768
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4179768
jbpm-configuration
|
| !--
| This configuration is used when there is no jbpm.cfg.xml file found in
the
| root of the classpath. It is a very basic configuration without
persistence
| and message services. Only the authorization service installed.
| You can
Looks fine at first sight.
Is the executor started? Eg in a non-enterprise environment, have you called
jbpmConfiguration.startJobExecutor() ?
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4179773#4179773
Reply to the post :
I think so. It should be started via the web.xml entry:
!-- Job executor launcher (begin) --
| listener
| description
| Starts the job executor on servlet context initialization and
stops it on
| servlet context destruction.
|
any errors in the logging? turn on debug level to see what happens.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4179827#4179827
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4179827
btw, your first example is wrong. You cannot (and should not) cancel the timer
within itself. The cancel timer should be on the transition, and it might even
be left out completely, since (afaik, but you should check) a timer on a node
is cancelled when this node is left.
View the original
small correction: timers are only cancelled when they are on a task that is
ended. So either use a cancel-timer in a transition or define the cancel-event
attribute on the timer and set it e.g. to node-leave
View the original post :
This was THE hint - now it works as expected:
state name=warte 1
| timer name='reminder'
| duedate='2 minutes'
| transition='ex1'
| cancel-event='node-left'
| script
|
ok... great that it works... can you file a jira issue for the 'misleading'
docs? so it won't get lost
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4179889#4179889
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4179889
You probably did not start a TimerRunner in some other console... This
TimerRunner will poll the database for expired timers and consume them. Check
the docs.
Regards,
Koen
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4066386#4066386
Reply to the post :
You mean to clean the orphans ? OK. But how to correctly create a new entries ?
I found, that the transaction must be commited after the ProcessInstance has
been signaled, e.g. in the example above:
// ...init code
| ProcessInstance pInst = ctx.newProcessInstance(test1);
| pInst.signal();
Ok. This code works for me:public class Test2
| {
| public static void main(String[] args)
| {
| try
| {
| JbpmConfiguration conf =
JbpmConfiguration.getInstance(src/main/config/jbpm.cfg.xml);
| JbpmContext ctx = conf.createJbpmContext();
|
or try using ejb3 timers...
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4057291#4057291
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4057291
___
jboss-user mailing list
ignore previous comment (wrong thread...)
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4057298#4057298
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4057298
___
jboss-user
jbpm.cfg.xml
jbpm-context
| service name=persistence
factory=org.jbpm.persistence.jta.JtaDbPersistenceServiceFactory
| field name=sessionFactoryJndiName
| string value=java:/WorkflowSessionFactory /
| /field
| field name=isCurrentSessionEnabledtrue //field
Ok, found the problem.
TimerService.add() does not have interval, so only one execution suppose to
run. Made a small patch, works fine now.
Still, the concurrent execption is really ugly. Will try tree cache to see if
any difference.
View the original post :
Brad,
As is the other post, please post the pd.xml and the code. It is easier then to
comment.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=3962720#3962720
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=3962720
Here is the code of my business process:
| ?xml version=1.0 encoding=UTF-8?
|
| process-definition
| xmlns= name=Solicit
|start-state name=start
| transition name= to=validateSecurityToken/transition
|/start-state
|end-state name=end1/end-state
|node
The transitions have no names.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=3962875#3962875
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=3962875
___
jboss-user mailing list
Ah yes, my dunce alarm wasn't faulty. Thanks for the tip. Somehow from looking
at examples I was under the impression that transitions could reference names
of the nodes transitioned to, not the name of the transition itself. Thanks for
the help -- I added a transition name and it worked.
ROTFLOL, Sorry all you had to do was do a reply where you have 'edit'
buttons (try hitting the preview or the 'postreply' button. There is a code tag
which puts a [ c o d e ] [ / c o d e ] (remove the spaces) around your
xml. That would have worked and given you
myxml./myxml
tasks are not cancelled by default when a token leaves a tasknode. Put a
end-tasks=true on the tasknode to achieve this (by default this is false)
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=3957544#3957544
Reply to the post :
32 matches
Mail list logo
