Hi

> Can you provide more information on this?   It looks like a 
> configuration
> issue wrt TransactionManager.

Configuration issue sounds good to me! ;-) 

I'm using ODE within ServiceMix (3.2) within Geronimo (2.0.1). The 
ode-jbi.properties pointing to an external DataSource.  This DataSource is 
configured as a ConnectionPool within Geronimo. (I'm using MySQL.)

--- 8< ---

ode-jbi.db.mode=EXTERNAL
ode-jbi.db.ext.dataSource=java:db/OdeDatasource

--- 8< ---

The Geronimo transaction libs (coming from Geronimo 2.0.1) are used in my 
configuration. Using the 'Ode transaction libs' (Geronimo 1.2) resulted in 
ClassCastExceptions because the configured ConnectionPool uses the libs coming 
from the AppServer.

Is there a way to configure the Transaction Manager lookup from Ode. I like to 
use the TM used from the DataSource...

Hope this helps... ;-)

Kristian

---
http://gaswerk.sourceforge.net

> 
> alex
> 
> 
> On 11/2/07, Kristian Köhler <[EMAIL PROTECTED]> wrote:
> >
> >
> > You're right this was with ode_trunk. My first test was 
> with version 1.1which resulted in the following error. I will 
> now test with the sendSynch
> > property.
> >
> > Thanks!
> >
> > Kristian
> >
> > --- 8< ---
> >
> > 14:51:19,018 ERROR [JacobVPU] Method "run" in class "
> > org.apache.ode.bpel.runtime.INVOKE" threw an unexpected exception.
> > org.apache.ode.bpel.iapi.ContextException: Unable to register
> > synchronizer.
> >         at
> > 
> org.apache.ode.scheduler.simple.SimpleScheduler.registerSynchronizer(
> > SimpleScheduler.java:200)
> >         at 
> org.apache.ode.jbi.OdeConsumer.invokePartner(OdeConsumer.java
> > :119)
> >         at 
> org.apache.ode.jbi.MessageExchangeContextImpl.invokePartner(
> > MessageExchangeContextImpl.java:60)
> >         at org.apache.ode.bpel.engine.BpelRuntimeContextImpl.invoke(
> > BpelRuntimeContextImpl.java:794)
> >         at org.apache.ode.bpel.runtime.INVOKE.run(INVOKE.java:96)
> >         at 
> sun.reflect.GeneratedMethodAccessor147.invoke(Unknown Source)
> >         at sun.reflect.DelegatingMethodAccessorImpl.invoke(
> > DelegatingMethodAccessorImpl.java:25)
> >         at java.lang.reflect.Method.invoke(Method.java:585)
> >         at org.apache.ode.jacob.vpu.JacobVPU$JacobThreadImpl.run(
> > JacobVPU.java:451)
> >         at 
> org.apache.ode.jacob.vpu.JacobVPU.execute(JacobVPU.java:139)
> >         at 
> org.apache.ode.bpel.engine.BpelRuntimeContextImpl.execute(
> > BpelRuntimeContextImpl.java:836)
> >         at 
> org.apache.ode.bpel.engine.PartnerLinkMyRoleImpl.invokeMyRole(
> > PartnerLinkMyRoleImpl.java:193)
> >         at org.apache.ode.bpel.engine.BpelProcess.invokeProcess(
> > BpelProcess.java:169)
> >         at org.apache.ode.bpel.engine.BpelProcess.handleWorkEvent(
> > BpelProcess.java:306)
> >         at org.apache.ode.bpel.engine.BpelEngineImpl.onScheduledJob(
> > BpelEngineImpl.java:318)
> >         at org.apache.ode.bpel.engine.BpelServerImpl.onScheduledJob(
> > BpelServerImpl.java:364)
> >         at org.apache.ode.scheduler.simple.SimpleScheduler$4$1.call(
> > SimpleScheduler.java:335)
> >         at org.apache.ode.scheduler.simple.SimpleScheduler$4$1.call(
> > SimpleScheduler.java:334)
> >         at 
> org.apache.ode.scheduler.simple.SimpleScheduler.execTransaction
> > (SimpleScheduler.java:173)
> >         at org.apache.ode.scheduler.simple.SimpleScheduler$4.call(
> > SimpleScheduler.java:333)
> >         at org.apache.ode.scheduler.simple.SimpleScheduler$4.call(
> > SimpleScheduler.java:330)
> >         at 
> java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java
> > :269)
> >         at java.util.concurrent.FutureTask.run(FutureTask.java:123)
> >         at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(
> > ThreadPoolExecutor.java:650)
> >         at java.util.concurrent.ThreadPoolExecutor$Worker.run(
> > ThreadPoolExecutor.java:675)
> >         at java.lang.Thread.run(Thread.java:595)
> > Caused by: java.lang.NullPointerException
> >         at
> > 
> org.apache.ode.scheduler.simple.SimpleScheduler.registerSynchronizer(
> > SimpleScheduler.java:188)
> >         ... 25 more
> >
> >
> 

Reply via email to