ode-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alex Boisvert" <boisv...@intalio.com>
Subject Re: Async Error
Date Mon, 03 Mar 2008 20:26:07 GMT
Hi Simone,

On 3/3/08, Simone Maletta <simonemaletta@alice.it> wrote:
>
> Hi guys,
>     I'm writing a sample to try to understand the way I have to deploy my
> master thesis, and I wrote this two partnerLinkTypes int my examplle wsdl:
>
> <partnerLinkType name="in">
>     <role name="receive" portType="inPT"/>
> </partnerLinkType>
>
> <partnerLinkType name="out">
>     <role name="read" portType="outPT"/>
> </partnerLinkType>
>
> and in the bpel:
> <partnerLink name="inPL" partnerLinkType="in" myRole="receive"/>
>
> <partnerLink name="outPL" partnerLinkType="out" partnerRole="read"/>
>
> and I invoke async operation on them, respectivly a receive and an invoke.
> Trying to invoke my process I get the following error:
>
> ERROR - BpelEngineImpl                 - Scheduled job failed;
> jobDetail={ckey=-1~hqejbhcnphr334wev5cdp2, correlatorId=16.echoResp,
> inmem=false, iid=3287, type=MATCHER}
> java.lang.NullPointerException
>         at
> org.apache.ode.dao.jpa.MessageExchangeDAOImpl.getCorrelationKeys(
> MessageExchangeDAOImpl.java:320)
>         at org.apache.ode.dao.jpa.CorrelatorDAOImpl.dequeueMessage(
> CorrelatorDAOImpl.java:74)
>         at org.apache.ode.bpel.engine.BpelRuntimeContextImpl.matcherEvent(
> BpelRuntimeContextImpl.java:1316)
>         at org.apache.ode.bpel.engine.BpelProcess.handleWorkEvent(
> BpelProcess.java:342)
>         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
> :303)
>         at java.util.concurrent.FutureTask.run(FutureTask.java:138)
>         at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(
> ThreadPoolExecutor.java:885)
>         at java.util.concurrent.ThreadPoolExecutor$Worker.run(
> ThreadPoolExecutor.java:907)
>         at java.lang.Thread.run(Thread.java:619)


I've created a Jira tracker for this issue,
https://issues.apache.org/jira/browse/ODE-244


Where this error come from?


Seems to come from the combination of using the OpenJPA persistence with
incoming messages without explicit correlation.

Is there a way, using Dynamic Partner Link in my background, to solve this
> problem?


I'm going to commit a fix for the issue right now.

Or I have to use message correlation?


That's also an alternative.

How I may extract sender address from a message incoming into inPT portType
> using inPL partnerLink?


You may use partnerLink assignments, e.g.,

<copy>
  <from partnerLink="fromPartnerLink" endpointReference="someRole"/>
  <to partnerLink="toPartnerLink"/>
</copy>

alex

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message