[
https://issues.apache.org/jira/browse/ODE-758?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12829636#action_12829636
]
Renat Zubairov commented on ODE-758:
------------------------------------
Hello Antonie, Terry, all
I was digging the sources of ODE and found following method:
org.apache.ode.bpel.engine.BpelEngineImpl#route(QName, Message)
Which returns the process that could be used for P2P communication was changed
from using Entpoints to using Service QNames by Antonie committed to revision
830367 (I'm talking here about ODE_1X trunk) with following comments:
-Introduced new property "p2p.mex.timeout" used as default value for
process-to-process mex timeout
-Changed _serviceMap type to Map<QName, List<BpelProcess>> to optimize routing
common case
-MEX timeout no longer multipled by 1.5 for invokeCheck
My idea was instead of commenting the routing completely was to enable internal
P2P shortcut only when ODE is quite sure a recipient process will be able to
handle this message. In ideal case that would be checking wherever process
implement that particular operation of that particular port-type. However for
my use-cases it would be enough just to check wherever port-type or Endpoint is
implemented by the ODE.
Worth case scenario would be a configured on/off switch for P2P interaction.
What do you think?
Renat
> Disable Process2Process communication
> -------------------------------------
>
> Key: ODE-758
> URL: https://issues.apache.org/jira/browse/ODE-758
> Project: ODE
> Issue Type: Bug
> Components: BPEL Runtime
> Affects Versions: 2.0-beta3
> Reporter: Terry Mueller
>
> Hello all,
> I have a problem with the Process2Process communication inside the ODE.
> Basically I need to implement a BPEL process that uses and implements the
> same WSDL. For example I have a service A with two methods request-response
> "createEntity" and one way "confirmCreation", I expect my process to call
> "createEntity" method and then wait untill the "confirmCreation" method will
> be called on it, however since ODE route all MEXes internaly despite the fact
> that process actually only implements one single operation "confirmCreation"
> I'm getting an MEX expire and failed state.
> Would it be possible to fix the P2P communication so that it would only
> happen when ODE as a recipient side is able to handle the operation,
> otherwise just proceed with a call though Integration Layer.
> Renat
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
