ode-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Waruna Ranasinghe <waruna...@gmail.com>
Subject Re: Simple Scheduler ERROR
Date Fri, 03 Jun 2011 08:52:19 GMT
Hi Rodolfo,

Are you using p2p invokes in this particular scenario?

Thanks,
Waruna

On 28 April 2011 23:26, Rodolfo Souza Barbeiro <
rodolfo-s-barbeiro@ptinovacao.pt> wrote:

> Hi everyone!
>
> I have trouble with ODE. I'm trying to run concurrent requests with 10
> threads, each thread makes 100 requests (10*100=1000 requests) .
>
> While executing the requests the following error occurs:
>
> WARN  [Runtime] Detected possible orphaned reference to deleted object
> "org.apache.ode.dao.jpa.MessageDAOImpl-8025" in
> "org.apache.ode.dao.jpa.MessageExchangeDAOImpl._request".
> ERROR [BpelEngineImpl] Scheduled job failed; jobDetail=JobDetails(
> instanceId: null mexId: hqejbhcnphr68hd1g2qfl2 processId: {
> http://powProcess}PowProcess-1 type: INVOKE_INTERNAL channel: null
> correlatorId: null correlationKeySet: null retryCount: null inMem: false
> detailsExt: {})
> java.lang.NullPointerException
>      at
> org.apache.ode.bpel.engine.MessageImpl.getMessage(MessageImpl.java:104)
>      at
> org.apache.ode.bpel.engine.PartnerLinkMyRoleImpl.computeCorrelationKeys(PartnerLinkMyRoleImpl.java:294)
>      at
> org.apache.ode.bpel.engine.PartnerLinkMyRoleImpl.findRoute(PartnerLinkMyRoleImpl.java:122)
>      at
> org.apache.ode.bpel.engine.BpelProcess.invokeProcess(BpelProcess.java:233)
>      at
> org.apache.ode.bpel.engine.BpelProcess.invokeProcess(BpelProcess.java:279)
>      at
> org.apache.ode.bpel.engine.BpelProcess.handleJobDetails(BpelProcess.java:426)
>      at
> org.apache.ode.bpel.engine.BpelEngineImpl.onScheduledJob(BpelEngineImpl.java:460)
>      at
> org.apache.ode.bpel.engine.BpelServerImpl.onScheduledJob(BpelServerImpl.java:450)
>      at
> org.apache.ode.scheduler.simple.SimpleScheduler$RunJob$1.call(SimpleScheduler.java:518)
>      at
> org.apache.ode.scheduler.simple.SimpleScheduler$RunJob$1.call(SimpleScheduler.java:512)
>      at
> org.apache.ode.scheduler.simple.SimpleScheduler.execTransaction(SimpleScheduler.java:284)
>      at
> org.apache.ode.scheduler.simple.SimpleScheduler.execTransaction(SimpleScheduler.java:239)
>     at
> org.apache.ode.scheduler.simple.SimpleScheduler$RunJob.call(SimpleScheduler.java:512)
>     at
> org.apache.ode.scheduler.simple.SimpleScheduler$RunJob.call(SimpleScheduler.java:496)
>      at java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source)
>      at java.util.concurrent.FutureTask.run(Unknown Source)
>      at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown
> Source)
>      at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
>      at java.lang.Thread.run(Unknown Source)
>
> Some requests are lost.
>
> I'm change derby database (default) for MySQL 5.5.
>
> Now I'm using ODE 1.3.5 in Tomcat 7.0.12 with MySQL 5.5.
> The requests are in the format SOAP.
>
> Any ODE configuration missing?
> Any idea?
>
>
> Thanks,
> Rodolfo
>



-- 
-----------------------------------------------------
Regards,
Waruna Ranasinghe

mob: 0724318285
blog: http://warunapw.blogspot.com
twitter: http://twitter.com/warunapww
http://lk.linkedin.com/in/waruna
www.facebook.com/waruna.ranasinghe

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