aravind kopparthi [http://community.jboss.org/people/aravindsk] created the discussion "switching from DbSchedulerServiceFactory to JmsSchedulerServiceFactory causes unexpected behaviour with BpmProcessor in esb service" To view the discussion, visit: http://community.jboss.org/message/533078#533078 -------------------------------------------------------------- I have deployed test.esb that calls BpmProcessor from one of the services that is defined in jboss-esb.xml. This works great and creates bpm process-instance. With default settings of jbpm-cfg.xml. but when I modify jbpm-cfg.xml to use JmsschedulerService instead of default DBScheduler it stopped working. Please provide your inputs what else do I need to change to initiate process instance from jboss-esb to work with jbpm that is using jmsscheduler instead for JobExecuter. jboss-esb.xml <action name="startProcessInstance"  >               <property name="command" value="StartProcessInstanceCommand" />               <property name="process-definition-name" value="EsbFileProcess"/>                               <property name="esbToBpmVars">                                            <mapping esb="BODY_CONTENT" bpm="message" />               </property> </action> <service factory="org.jbpm.scheduler.db.DbSchedulerServiceFactory" /> To Jms <service name="scheduler" factory="org.jboss.soa.esb.services.jbpm.integration.timer.JmsSchedulerServiceFactory"/> <null name="jbpm.job.executor"/> -------------------------------------------------------------- Reply to this message by going to Community [http://community.jboss.org/message/533078#533078] Start a new discussion in JBoss ESB Development at Community [http://community.jboss.org/choose-container!input.jspa?contentType=1&...]