[
https://issues.apache.org/jira/browse/ODE-533?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12678443#action_12678443
]
Ciaran Jessup commented on ODE-533:
-----------------------------------
Sorry about ODE-537 Matthieu asked for a new bug to be raised (we figured out
that the regression came in with your changes ;) ). While you're back in
there, those properties don't work either, reading the code it looked as
though they should be:
ode-axis2.http.connection-manager.foo.bar
Is this deliberate ? (The property bag appears to stick an unexpected prefix in
there)
> Share a connection manager across SoapExternalServices
> ------------------------------------------------------
>
> Key: ODE-533
> URL: https://issues.apache.org/jira/browse/ODE-533
> Project: ODE
> Issue Type: Improvement
> Components: Axis2 Integration
> Affects Versions: 1.1, 1.1.1, 1.2
> Reporter: Alexis Midon
> Assignee: Alexis Midon
> Fix For: 1.3.1, 2.0
>
>
> All external service should share the same http connection manager. The
> connection manager will be initialized by ODEServer. ExternalServices would
> receive a ConfigurationContext instance containing this connection manager.
> Configuration of the connection manager will be done through
> ode-axis2.properties :
> "http.connection-manager.max-per-host"
> "http.connection-manager.max-total"
> In addition, we should make sure axis2 release the connections to the pool.
> By invoking OperationClient#complete.
> see http://markmail.org/thread/voabzcl6u2pck74n
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
