I desesperatly try to deploy ODE 1.2RC1 on JBI implementations (other than
ServiceMix) like PEtALS or openESB. But in all cases I have an error of
TransactionManager.
For example with PEtALS when I use the INTERNAL DB mode, I have the error :
[petals.InstallationService]
InstallationServiceImpl.loadNewInstaller() Component succesfully installed:
OdeBpelEngine 10:30:06,406 ERROR OdeLifeCycle:178 - Database configuration
error. java.lang.RuntimeException: TransactionManager is not recoverable. at
org.apache.ode.il.dbutil.Database.initInternalDb(Database.java:179) at
org.apache.ode.il.dbutil.Database.initEmbeddedDb(Database.java:232) at
org.apache.ode.il.dbutil.Database.initDataSource(Database.java:147) at
org.apache.ode.il.dbutil.Database.start(Database.java:99) at
org.apache.ode.jbi.OdeLifeCycle.initDataSource(OdeLifeCycle.java:175) at
org.apache.ode.jbi.OdeLifeCycle.init(OdeLifeCycle.java:113) at
org.ow2.petals.container.thread.ComponentLifeCycleThread.doTask(ComponentLif
eCycleThread.java:101) at
org.ow2.petals.container.thread.AbstractThread.run(AbstractThread.java:106)
Unlike the recommendation of the mailing-list, I can't use the DB mode
EXTERNAL to force ODE use the JBI container's transaction manager as I don't
have any application server in my architecture (no way to register the
datasource in a JNDI register)
So how can I force ODE to use the JBI container's transaction manager w/o
application server (and JNDI register) ?
Must I use an external JNDI register ? Which one ? In PEtALS or openESB,
there is no one.
In your opinion, is it normal that ODE raises this error in EMBEDDED DB mode
or is there a classloader issues in ODE ?
Thanks.
Richard.
