G'day.
I've found the followind issue with the open esb components under GFv2 (openesb's forum is in read-only mode for now..).
If the persistence is enabled, the bpel-se engine tries to start transactions recovery before the proccess are initialized, what causes a lot of warnings/errors:
Started BPEL service engine in-out thread
Recovery Called : On account of new service unit deployment to recover dangling instances (if any) for the new deployed process ..this engine id : {0} 192.168.125.28:11420e11:11656ddcf02:-7fea
Started BPEL service engine in-out thread
Recovery Called : On account of new service unit deployment to recover dangling instances (if any) for the new deployed process ..this engine id : {0} 192.168.125.28:11420e11:11656ddcf02:-7fea
Recovery failed. BPEL model not registered for {
http://enterprise.netbeans.org/bpel/HelloWorldProcess}HelloWorldProcess
Recovery failed. BPEL model not registered for {
http://enterprise.netbeans.org/bpel/HelloWorldProcess}HelloWorldProcess
BPEL service engine started with following configurations
Persistence Enabled : true
Monitor Enabled : false
Persistence Database NonXA JNDI Resource Name : jdbc/bpelseDBnonXA
Persistence Database XA JNDI Resource Name : jdbc/bpelseDBXA
Engine Expiry Interval (failover setting) : 60 seconds
Debug Enabled : true
Debug Port : 3 343
Thread Count 10
Engine Installed on Application Server Cluster : false
Recovery failed. BPEL model not registered for {
http://enterprise.netbeans.org/bpel/HelloWorldProcess}HelloWorldProcess
Started BPEL service engine in-out thread
Started BPEL service engine in-out thread
Started BPEL service engine in-out thread
Started BPEL service engine in-out thread
Started BPEL service engine in-out thread
Started BPEL service engine in-out thread
Started BPEL service engine in-out thread
JBIFW1146: Engine sun-bpel-engine has been started.
Starting BPELSE deploy process
Using DefaultParseContext for wsdl
Retrieving schema at 'AsynchronousSample.xsd', relative to 'file:/C:/Java/glassfish/domains/domain1/jbi/service-assemblies/AsynchronousSampleApplication/AsynchronousSampleApplication-AsynchronousSample/sun-bpel-engine/AsynchronousSample.wsdl'.
Using DefaultParseContext for wsdl
.... etc
I think it might be a bug. Thanks
[Message sent by forum member 'dimm' (dimm)]
http://forums.java.net/jive/thread.jspa?messageID=246025