[ODE-269] Common service and Process environment deployment

• Type: Bug
• Status: Resolved
• Priority: Minor
• Resolution: Incomplete
• Affects Version/s: 1.1.1
• Fix Version/s: 1.2
• Component/s: BPEL Runtime
• Environment: Windows/Linux/Apache Tomcat 6
• Assignee: Matthieu Riou
• Reporter: Miguel Correia Ricardo
• Created: 16/Apr/08 12:23
• Updated: 21/May/08 22:53
• Resolved: 21/May/08 22:53

Description

I have Apache Tomcat 6, where I deploy my bpel process and an partner web service. For example, Foo.bpel and Bar.wsdl

Foo.bpel invokes Bar.wsdl (Foo->Bar) in a synchronous manner. I have both components, deployed on the same Tomcat instance. For whatever reason, the order that they are deployed affects the behaviour of Apache ODE.
If the BPEL process (Foo.bpel) gets deployed before the web service (Bar.wsdl), tomcat hangs on startup when Apache ODE tries to initialize the partner role. Clearly there is a dependency from the bpel process to the web service, so I need to startup first the web service...
Probably this is more visible, when BPEL processes and partner external web services startup on the same tomcat instance...