ode-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Michael Kammholz" <...@arlanis.com>
Subject Re: Invalid response state for mex ASYNCH
Date Wed, 02 May 2007 12:33:41 GMT
We tried to trace this issue down a bit and found out that when deploying  
the process with the flag "in-memory" (deploy.xml) the error does NOT  
occour (Tested with a build from 04.16).
As mentioned from Jan Loewe the problem seems to be in the method  
BpelRuntimeContextImpl.reply(...) or rather in the DAO handling in that  
area.
In this method the state is set correctly to Status.RESPONSE for the  
MyRoleMessageExchangeImpl instance on line 528 and MessageExchangeDAO on  
line 535 (shouldn't this happen inherent on line 528 ?). But this only  
affects the objects in memory, not in the database.
Then on line 540 the pmex object is loaded where the status is reloaded  
 from database and reset to ASYNC for any object with this MEX-ID so the  
object m now has the wrong status in the switch statement after this. This  
does not happen when process is deployed with the in-memory flag.

Hope that helps to review the right section to solve this problem.

Beside that, with a build from today the aforementioned stack overflow  
still happens:
java.lang.StackOverflowError at  
org.apache.axis2.client.Options.getTransportOut(Options.java:331)

Any idea why that happens?

Best regards,
Michael

-- 
Michael Kammholz
Arlanis Software AG
Kurf├╝rstenstr. 15
14467 Potsdam

http://www.arlanis.com
Phone:  +49 331 27911-29
Fax:    +49 331 27911-1
eM@il:  michael.kammholz@arlanis.com

Amtsgericht Potsdam: HRB 19134 P
Steuer Nr.: 046 100 01292
Vorstand: Christian Metzger

Mime
View raw message