newDefaultInMemoryBuilder does not work in jBPM6

[manmanlai]

Hi,

I would like to write a simple example to run jBPM6 without persistence. I have followed the user guide to write the code but meet exceptions.

The code piece:

RuntimeEnvironment env = RuntimeEnvironmentBuilder.Factory.get()

  .newDefaultInMemoryBuilder()

  .get();

  return RuntimeManagerFactory.Factory.get().

  newSingletonRuntimeManager(env);

The exception:

Exception in thread "main" javax.persistence.PersistenceException: [PersistenceUnit: org.jbpm.persistence.jpa] Unable to build EntityManagerFactory

  at org.hibernate.ejb.Ejb3Configuration.buildEntityManagerFactory(Ejb3Configuration.java:930)

  at org.hibernate.ejb.Ejb3Configuration.buildEntityManagerFactory(Ejb3Configuration.java:904)

  at org.hibernate.ejb.HibernatePersistence.createEntityManagerFactory(HibernatePersistence.java:72)

  at javax.persistence.Persistence.createEntityManagerFactory(Persistence.java:63)

  at javax.persistence.Persistence.createEntityManagerFactory(Persistence.java:47)

  at org.jbpm.runtime.manager.impl.DefaultRuntimeEnvironment.init(DefaultRuntimeEnvironment.java:72)

  at org.jbpm.runtime.manager.impl.RuntimeEnvironmentBuilder.get(RuntimeEnvironmentBuilder.java:314)

  at org.jbpm.runtime.manager.impl.RuntimeEnvironmentBuilder.get(RuntimeEnvironmentBuilder.java:56)

  at com.sample.ProcessMain.createMemoryRuntimeManager(ProcessMain.java:67)

  at com.sample.ProcessMain.main(ProcessMain.java:28)

Caused by: org.hibernate.service.jndi.JndiException: Unable to lookup JNDI name [jdbc/jbpm-ds]

  at org.hibernate.service.jndi.internal.JndiServiceImpl.locate(JndiServiceImpl.java:68)

  at org.hibernate.service.jdbc.connections.internal.DatasourceConnectionProviderImpl.configure(DatasourceConnectionProviderImpl.java:116)

  at org.hibernate.service.internal.StandardServiceRegistryImpl.configureService(StandardServiceRegistryImpl.java:75)

  at org.hibernate.service.internal.AbstractServiceRegistryImpl.initializeService(AbstractServiceRegistryImpl.java:159)

  at org.hibernate.service.internal.AbstractServiceRegistryImpl.getService(AbstractServiceRegistryImpl.java:131)

  at org.hibernate.engine.jdbc.internal.JdbcServicesImpl.buildJdbcConnectionAccess(JdbcServicesImpl.java:223)

  at org.hibernate.engine.jdbc.internal.JdbcServicesImpl.configure(JdbcServicesImpl.java:89)

  at org.hibernate.service.internal.StandardServiceRegistryImpl.configureService(StandardServiceRegistryImpl.java:75)

  at org.hibernate.service.internal.AbstractServiceRegistryImpl.initializeService(AbstractServiceRegistryImpl.java:159)

  at org.hibernate.service.internal.AbstractServiceRegistryImpl.getService(AbstractServiceRegistryImpl.java:131)

  at org.hibernate.cfg.SettingsFactory.buildSettings(SettingsFactory.java:78)

  at org.hibernate.cfg.Configuration.buildSettingsInternal(Configuration.java:2295)

  at org.hibernate.cfg.Configuration.buildSettings(Configuration.java:2291)

  at org.hibernate.cfg.Configuration.buildSessionFactory(Configuration.java:1760)

  at org.hibernate.ejb.EntityManagerFactoryImpl.<init>(EntityManagerFactoryImpl.java:94)

  at org.hibernate.ejb.Ejb3Configuration.buildEntityManagerFactory(Ejb3Configuration.java:920)

  ... 9 more

Caused by: javax.naming.NameNotFoundException: unable to find a bound object at name 'jdbc/jbpm-ds'

  at bitronix.tm.jndi.BitronixContext.lookup(BitronixContext.java:83)

  at bitronix.tm.jndi.BitronixContext.lookup(BitronixContext.java:67)

  at javax.naming.InitialContext.lookup(InitialContext.java:396)

  at org.hibernate.service.jndi.internal.JndiServiceImpl.locate(JndiServiceImpl.java:65)

  ... 24 more

I have checked code, it is quite strange in org.jbpm.runtime.manager.impl.DefaultRuntimeEnvironment.init()

If I don't configure EMF, it will try to create a default one regardless of this.usePersistence. And the exception is thrown in here.

Does anyone meet same problem? or i have miss some configurations?

Best Regards

Xiang

[swiderski.maciej]

that's why it's called default builder, as it tried to request less information from the used assuming some defaults - like convention over configuration approach. So it does what it is expected, configures the builder with defaults for in memory usage.

If you would like to start from scratch use empty builder instead where you are responsible to setup everything yourself.

HTH

[manmanlai]

There is an example in 5.4.3.1, http://docs.jboss.org/jbpm/v6.0/userguide/jBPMCoreEngine.html#d0e1916

and in java doc for RuntimeEnvironmentBuilder class, it claims

• getDefaultInMemory() - returns preconfigured environment with disabled persistence for runtime engine

Both gives me wrong impression than we can use this api to create an in memory environment.

It would be nice that RuntimeEnvironmentBuilder can provide completed non-persistence environment support.

/Xiang

[swiderski.maciej]

it does provide in memory runtime engine (which is actually process engine) but it requires persistence for human task interaction and since this is default it allows you to run processes with in memory only but task service must be configured with persistence.

You can easily disable that by providing your selected RegisterableItemsFactory implementation.

HTH

[mani.adari]

I am using Drools 6.0.0 Final version.

I am a beginner in jBPM and Drools. I need to do the same stuff.

Can you guide me on How to implement RegisterableItemsFactory implementation? Also, I found TaskImpl in JBPM is tightly coupled with Hibernate annotations. This doesnt effect anything until unless we have some transaction management is in place. Otherwise TaskImpl can be used as regular java bean.

If possible can you provide a sample implementation to this interface.

Thanks

Mani Adari

[swiderski.maciej]

here is a quote from documentation about available implementations of RegisterableItemsFactory:

• org.jbpm.runtime.manager.impl.SimpleRegisterableItemsFactory - simplest possible implementations that comes empty and is based on reflection to produce instances of handlers and listeners based on given class names
• org.jbpm.runtime.manager.impl.DefaultRegisterableItemsFactory - extension of the Simple implementation that introduces defaults described above and still provides same capabilities as Simple implementation
• org.jbpm.runtime.manager.impl.KModuleRegisterableItemsFactory - exension of default implementation that provides specific capabilities for kmodule and still provides same capabilities as Simple implementation
• org.jbpm.runtime.manager.impl.cdi.InjectableRegisterableItemsFactory - extension of default implementation that is tailored for CDI environments and provides CDI style approach to finding handlers and listeners via producers

If you would like to use process engine in memory without task service at all then you could use SimpleRegisterableItemsFactory.

If that is not suitable you can extend any of the above implementations and override methods to provide alternative configuration to the runtime manager. See docs for more info on this.

HTH

[manmanlai]

I directly use SimpleRegisterableItemsFactory for in memory usage. Here is my code piece

     KieServices ks = KieServices.Factory.get();

     KieContainer kContainer = ks.getKieClasspathContainer();

     kbase = kContainer.getKieBase("kbase");

     SimpleRegisterableItemsFactory factory = new SimpleRegisterableItemsFactory();

     factory.addWorkItemHandler("Manual Task", MockManualTaskHandler.class);

     builder = RuntimeEnvironmentBuilder.Factory.get().newEmptyBuilder()

                 .persistence(false).knowledgeBase(kbase)

                 .registerableItemsFactory(factory);

     manager = RuntimeManagerFactory.Factory.get()

                 .newPerRequestRuntimeManager(builder.get(),

                 "jbpm.benchmark:1.0");

/Xiang