[jira] Commented: (ODE-269) Common service and Process environment deployment

["Matthieu Riou (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/ODE-269?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12589688#action_12589688 ] 

Matthieu Riou commented on ODE-269:
-----------------------------------

Could you provide a Thread stack or something that would show the hanging? That sounds really weird to me, ODE only calls a web service on invoke, never at startup. Unless you have leftover instances.

> Common service and Process environment deployment
> -------------------------------------------------
>
>                 Key: ODE-269
>                 URL: https://issues.apache.org/jira/browse/ODE-269
>             Project: ODE
>          Issue Type: Bug
>          Components: BPEL Runtime
>    Affects Versions: 1.1.1
>         Environment: Windows/Linux/Apache Tomcat 6
>            Reporter: Miguel Correia Ricardo
>            Priority: Minor
>
> 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...

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.