Hi Tammo,
On the process of verifying patch of ODE-915 (
https://issues.apache.org/jira/browse/ODE-915), I found that it seems we've
already had binary incompatibility between the ODE-1.3.5 and the ODE-trunk,
so it might worth discussion on the conf call as well.
For people that are interested, here is the steps that I've used.
1. Start ODE 1.3.5 with external database, like mysql.
2. Deploy a sample process with two receives and assigns.
(like simple-correlation)
3. Start a process instance with the first receive, the first assign will
follow and the process will then wait for the next receive.
4. Stop ODE, and then switch over to ODE trunk, with the same setup and the
same process.
5. Restart ODE, and then send the second message.
with above steps, I've seen following classcast exception:
18:45:09,695 ERROR [BpelEngineImpl] Scheduled job failed;
jobDetail=JobDetails( instanceId: null mexId: hqejbhcnphr64vjbnfwfgo
processId: {http://www.jboss.org/bpel/examples}HelloGoodbye-1 type:
INVOKE_INTERNAL channel: null correlatorId: null correlationKeySet: null
retryCount: null inMem: false detailsExt: {enqueue=false})
java.lang.RuntimeException: java.lang.ClassCastException: cannot assign
instance of org.apache.ode.bpel.o.OScope to field
org.apache.ode.bpel.runtime.ScopeFrame.globals of type
org.apache.ode.bpel.runtime.InstanceGlobals in instance of
org.apache.ode.bpel.runtime.ScopeFrame
at
org.apache.ode.bpel.engine.BpelRuntimeContextImpl.<init>(BpelRuntimeContextImpl.java:177)
at
org.apache.ode.bpel.engine.BpelProcess.createRuntimeContext(BpelProcess.java:832)
at
org.apache.ode.bpel.engine.PartnerLinkMyRoleImpl.invokeInstance(PartnerLinkMyRoleImpl.java:232)
at org.apache.ode.bpel.engine.BpelProcess$1.invoke(BpelProcess.java:304)
at
org.apache.ode.bpel.engine.BpelProcess.invokeProcess(BpelProcess.java:248)
at
org.apache.ode.bpel.engine.BpelProcess.invokeProcess(BpelProcess.java:295)
at
org.apache.ode.bpel.engine.BpelProcess.handleJobDetails(BpelProcess.java:448)
at
org.apache.ode.bpel.engine.BpelEngineImpl.onScheduledJob(BpelEngineImpl.java:498)
at
org.apache.ode.bpel.engine.BpelServerImpl.onScheduledJob(BpelServerImpl.java:450)
at
org.apache.ode.scheduler.simple.SimpleScheduler$RunJob$1.call(SimpleScheduler.java:543)
at
org.apache.ode.scheduler.simple.SimpleScheduler$RunJob$1.call(SimpleScheduler.java:537)
at
org.apache.ode.scheduler.simple.SimpleScheduler.execTransaction(SimpleScheduler.java:286)
at
org.apache.ode.scheduler.simple.SimpleScheduler.execTransaction(SimpleScheduler.java:241)
at
org.apache.ode.scheduler.simple.SimpleScheduler$RunJob.call(SimpleScheduler.java:537)
at
org.apache.ode.scheduler.simple.SimpleScheduler$RunJob.call(SimpleScheduler.java:521)
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:886)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:680)
Regards
Jeff
On Wed, Feb 9, 2011 at 1:17 AM, Tammo van Lessen <tvanles...@gmail.com>wrote:
> Hi devs,
>
> a new year, a new release, time to discuss ODE's roadmap again.
>
> There are a couple of issues on my list that I'd like to discuss with you.
>
> 1) Status of JPA refactoring
> 2) Evolveable OModel and runtime model
> 3) Backports from experimental
> 4) Community & Eco system
>
> What do you think of having a skype call to discuss these issues? Please
> let me know your availability, interest, timezones and/or additional
> issues so that I can schedule a meeting.
>
> Thanks,
> Tammo
>
> --
> Tammo van Lessen - http://www.taval.de
>
--
Cheers,
Jeff Yu
----------------
blog: http://jeff.familyyu.net
