You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ode.apache.org by "Matthias von Arx (JIRA)" <ji...@apache.org> on 2006/11/15 19:33:42 UTC
[jira] Created: (ODE-81) invoking more than one service causes in
90% a NPE
invoking more than one service causes in 90% a NPE
--------------------------------------------------
Key: ODE-81
URL: http://issues.apache.org/jira/browse/ODE-81
Project: Apache Ode
Issue Type: Bug
Components: JBI Integration
Environment: Windows XP, j2sdk1.5.0_06, SM 3.0 Release, ode-jbi-2.0-SNAPSHOT-installer.zip (build of revision 475066)
Reporter: Matthias von Arx
Invoking more than one service in a BPEL process or using a <flow> causes the following NPE:
19:21:40,490 | ERROR | pool-2-thread-2 | OdeConsumer | org.apache.ode.jbi.OdeConsumer 214 | error delivering RESPONSE:
java.lang.NullPointerException
at org.apache.ode.jbi.OdeConsumer$2.call(OdeConsumer.java:187)
at org.apache.ode.jbi.OdeConsumer$2.call(OdeConsumer.java:183)
at org.apache.ode.bpel.scheduler.quartz.QuartzSchedulerImpl.execTransaction(QuartzSchedulerImpl.java:211)
at org.apache.ode.jbi.OdeConsumer.outResponse(OdeConsumer.java:182)
at org.apache.ode.jbi.OdeConsumer.onJbiMessageExchange(OdeConsumer.java:134)
at org.apache.ode.jbi.JbiMessageExchangeEventRouter.onJbiMessageExchange(JbiMessageExchangeEventRouter.java:40)
at org.apache.ode.jbi.Receiver$1.run(Receiver.java:190)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:417)
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)
After stopping SM, cleaning the data directory, removing the ode-bpel SA, restarting SM and deploy the ode-bpel SA again in some cases the NPE was not thrown and the process work's fine.
This behaviour and ODE-80 looks like serious synchronisation problems.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Resolved: (ODE-81) invoking more than one service causes in
90% a NPE
Posted by "Maciej Szefler (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ODE-81?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Maciej Szefler resolved ODE-81.
-------------------------------
Resolution: Fixed
Assignee: Maciej Szefler
Added check to prevent NPE.
> invoking more than one service causes in 90% a NPE
> --------------------------------------------------
>
> Key: ODE-81
> URL: https://issues.apache.org/jira/browse/ODE-81
> Project: Apache Ode
> Issue Type: Bug
> Components: JBI Integration
> Environment: Windows XP, j2sdk1.5.0_06, SM 3.0 Release, ode-jbi-2.0-SNAPSHOT-installer.zip (build of revision 475066)
> Reporter: Matthias von Arx
> Assigned To: Maciej Szefler
>
> Invoking more than one service in a BPEL process or using a <flow> causes the following NPE:
> 19:21:40,490 | ERROR | pool-2-thread-2 | OdeConsumer | org.apache.ode.jbi.OdeConsumer 214 | error delivering RESPONSE:
> java.lang.NullPointerException
> at org.apache.ode.jbi.OdeConsumer$2.call(OdeConsumer.java:187)
> at org.apache.ode.jbi.OdeConsumer$2.call(OdeConsumer.java:183)
> at org.apache.ode.bpel.scheduler.quartz.QuartzSchedulerImpl.execTransaction(QuartzSchedulerImpl.java:211)
> at org.apache.ode.jbi.OdeConsumer.outResponse(OdeConsumer.java:182)
> at org.apache.ode.jbi.OdeConsumer.onJbiMessageExchange(OdeConsumer.java:134)
> at org.apache.ode.jbi.JbiMessageExchangeEventRouter.onJbiMessageExchange(JbiMessageExchangeEventRouter.java:40)
> at org.apache.ode.jbi.Receiver$1.run(Receiver.java:190)
> at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:417)
> 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)
> After stopping SM, cleaning the data directory, removing the ode-bpel SA, restarting SM and deploy the ode-bpel SA again in some cases the NPE was not thrown and the process work's fine.
> This behaviour and ODE-80 looks like serious synchronisation problems.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (ODE-81) invoking more than one service causes in
90% a NPE
Posted by "Matthieu Riou (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ODE-81?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Matthieu Riou closed ODE-81.
----------------------------
> invoking more than one service causes in 90% a NPE
> --------------------------------------------------
>
> Key: ODE-81
> URL: https://issues.apache.org/jira/browse/ODE-81
> Project: Ode
> Issue Type: Bug
> Components: JBI Integration
> Environment: Windows XP, j2sdk1.5.0_06, SM 3.0 Release, ode-jbi-2.0-SNAPSHOT-installer.zip (build of revision 475066)
> Reporter: Matthias von Arx
> Assignee: Maciej Szefler
>
> Invoking more than one service in a BPEL process or using a <flow> causes the following NPE:
> 19:21:40,490 | ERROR | pool-2-thread-2 | OdeConsumer | org.apache.ode.jbi.OdeConsumer 214 | error delivering RESPONSE:
> java.lang.NullPointerException
> at org.apache.ode.jbi.OdeConsumer$2.call(OdeConsumer.java:187)
> at org.apache.ode.jbi.OdeConsumer$2.call(OdeConsumer.java:183)
> at org.apache.ode.bpel.scheduler.quartz.QuartzSchedulerImpl.execTransaction(QuartzSchedulerImpl.java:211)
> at org.apache.ode.jbi.OdeConsumer.outResponse(OdeConsumer.java:182)
> at org.apache.ode.jbi.OdeConsumer.onJbiMessageExchange(OdeConsumer.java:134)
> at org.apache.ode.jbi.JbiMessageExchangeEventRouter.onJbiMessageExchange(JbiMessageExchangeEventRouter.java:40)
> at org.apache.ode.jbi.Receiver$1.run(Receiver.java:190)
> at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:417)
> 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)
> After stopping SM, cleaning the data directory, removing the ode-bpel SA, restarting SM and deploy the ode-bpel SA again in some cases the NPE was not thrown and the process work's fine.
> This behaviour and ODE-80 looks like serious synchronisation problems.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.