[
https://issues.apache.org/jira/browse/ODE-302?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12614271#action_12614271
]
aillet commented on ODE-302:
----------------------------
I have patched ODE-1.2 with the previous patch and try to deploy the new ODE
zip on PETALS JBI implementation .
Unfortunatly the patch seems not good.
I have a runtime exception at deployment time when ODE starts the BPEL Engine
(see below) :
10:26:03,046 ERROR SimpleScheduler:289 - Error retrieving node list.
org.apache.ode.bpel.iapi.ContextException: Internal Error, could not begin
transaction.
at
org.apache.ode.scheduler.simple.SimpleScheduler.execTransaction(SimpleScheduler.java:170)
at
org.apache.ode.scheduler.simple.SimpleScheduler.start(SimpleScheduler.java:280)
at
org.apache.ode.bpel.engine.BpelServerImpl.start(BpelServerImpl.java:137)
at org.apache.ode.jbi.OdeLifeCycle.start(OdeLifeCycle.java:370)
at
org.ow2.petals.container.thread.ComponentLifeCycleThread.doTask(ComponentLifeCycleThread.java:104)
at
org.ow2.petals.container.thread.AbstractThread.run(AbstractThread.java:106)
Caused by: java.lang.NullPointerException
at
org.apache.ode.scheduler.simple.SimpleScheduler.execTransaction(SimpleScheduler.java:167)
... 5 more
10:26:03,046 ERROR OdeLifeCycle:373 - ODE BPEL Server failed to
start.org.apache.ode.bpel.iapi.ContextException: Error retrieving node list.
at
org.apache.ode.scheduler.simple.SimpleScheduler.start(SimpleScheduler.java:290)
at
org.apache.ode.bpel.engine.BpelServerImpl.start(BpelServerImpl.java:137)
at org.apache.ode.jbi.OdeLifeCycle.start(OdeLifeCycle.java:370)
at
org.ow2.petals.container.thread.ComponentLifeCycleThread.doTask(ComponentLifeCycleThread.java:104)
at
org.ow2.petals.container.thread.AbstractThread.run(AbstractThread.java:106)
Caused by: org.apache.ode.bpel.iapi.ContextException: Internal Error, could
notbegin transaction.
at
org.apache.ode.scheduler.simple.SimpleScheduler.execTransaction(SimpleScheduler.java:170)
at
org.apache.ode.scheduler.simple.SimpleScheduler.start(SimpleScheduler.java:280)
... 4 more
Caused by: java.lang.NullPointerException
at
org.apache.ode.scheduler.simple.SimpleScheduler.execTransaction(SimpleScheduler.java:167)
... 5 more
[petals.Container] [Installer_OdeBpelEngine] -CALL -
LifeCycleAbstract.stateChanged()
[petals.Container] [Installer_OdeBpelEngine] -CALL -
LifeCycleAbstract.stateChangeFailed()
[petals.Autoloader] Error occured during auto installation.
javax.management.MBeanException
at
mx4j.server.ReflectionMBeanInvoker.doInvoke(ReflectionMBeanInvoker.java:135)
at
mx4j.server.ReflectionMBeanInvoker.invoke(ReflectionMBeanInvoker.java:52)
at
mx4j.server.interceptor.InvokerMBeanServerInterceptor.invoke(InvokerMBeanServerInterceptor.java:238)
at
mx4j.server.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:120)
at
mx4j.server.interceptor.SecurityMBeanServerInterceptor.invoke(SecurityMBeanServerInterceptor.java:84)
at
mx4j.server.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:120)
at
mx4j.server.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:120)
at
mx4j.server.interceptor.ContextClassLoaderMBeanServerInterceptor.invoke(ContextClassLoaderMBeanServerInterceptor.java:203)
at mx4j.server.MX4JMBeanServer.invoke(MX4JMBeanServer.java:1043)
at
org.ow2.petals.jbi.management.autoload.AutoLoaderServiceImpl.performInstall(AutoLoaderServiceImpl.java:455)
at
org.ow2.petals.jbi.management.autoload.AutoLoaderServiceImpl.install(AutoLoaderServiceImpl.java:232)
at
org.ow2.petals.jbi.management.autoload.InstallDirectoryScanner.run(InstallDirectoryScanner.java:56)
at java.util.TimerThread.mainLoop(Timer.java:512)
at java.util.TimerThread.run(Timer.java:462)
Caused by: javax.jbi.JBIException: An exception occured during the start.
at
org.ow2.petals.container.lifecycle.LifeCycleAbstract.start(LifeCycleAbstract.java:289)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at
mx4j.server.ReflectionMBeanInvoker.invokeImpl(ReflectionMBeanInvoker.java:156)
at
mx4j.server.ReflectionMBeanInvoker.doInvoke(ReflectionMBeanInvoker.java:117)
... 13 more
Caused by: javax.jbi.JBIException: Life cycle exception on START
at
org.ow2.petals.container.thread.ComponentLifeCycleThread.doTask(ComponentLifeCycleThread.java:120)
at
org.ow2.petals.container.thread.AbstractThread.run(AbstractThread.java:106)
Caused by: javax.jbi.JBIException: ODE BPEL Server failed to start.
at org.apache.ode.jbi.OdeLifeCycle.start(OdeLifeCycle.java:374)
at
org.ow2.petals.container.thread.ComponentLifeCycleThread.doTask(ComponentLifeCycleThread.java:104)
... 1 more
Caused by: org.apache.ode.bpel.iapi.ContextException: Error retrieving node
list.
at
org.apache.ode.scheduler.simple.SimpleScheduler.start(SimpleScheduler.java:290)
at
org.apache.ode.bpel.engine.BpelServerImpl.start(BpelServerImpl.java:137)
at org.apache.ode.jbi.OdeLifeCycle.start(OdeLifeCycle.java:370)
... 2 more
Caused by: org.apache.ode.bpel.iapi.ContextException: Internal Error, could
notbegin transaction.
at
org.apache.ode.scheduler.simple.SimpleScheduler.execTransaction(SimpleScheduler.java:170)
at
org.apache.ode.scheduler.simple.SimpleScheduler.start(SimpleScheduler.java:280)
... 4 more
Caused by: java.lang.NullPointerException
at
org.apache.ode.scheduler.simple.SimpleScheduler.execTransaction(SimpleScheduler.java:167)
Richard.
> Use embedded TransactionManager if database mode is EMBEDDED or INTERNAL
> ------------------------------------------------------------------------
>
> Key: ODE-302
> URL: https://issues.apache.org/jira/browse/ODE-302
> Project: ODE
> Issue Type: Bug
> Components: JBI Integration
> Reporter: Alex Boisvert
> Attachments: ODE302.patch.txt
>
>
> Ode should not use the TransactionManager provided by the JBI container in
> EMBEDDED and INTERNAL database modes since it creates its own DataSource
> which are not under the responsibility of the container's TransactionManager.
> This happened to work with ServiceMix since it uses the same
> TransactionManager (Geronimo's), but it's not something we can assume in
> other JBI environments.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
