camel-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Claus Ibsen (JIRA)" <>
Subject [jira] [Resolved] (CAMEL-5198) Implement connection pooling in jt400 component
Date Tue, 05 Jun 2012 09:46:22 GMT


Claus Ibsen resolved CAMEL-5198.

    Resolution: Fixed

Thanks for the patch. I have updated the docs as well.
> Implement connection pooling in jt400 component
> -----------------------------------------------
>                 Key: CAMEL-5198
>                 URL:
>             Project: Camel
>          Issue Type: Improvement
>    Affects Versions: 2.9.2
>         Environment: i5/OS servers
>            Reporter: João Loureiro
>            Assignee: Claus Ibsen
>              Labels: camel-jt400, jt400
>             Fix For: 2.10.0
>         Attachments: patch_v2.txt
> Instead of eagerly obtaining a new connection to the AS/400 system, Endpoint instances
request one from a connection pool. Users can specify that their own connection pool be used,
or let Camel provide one (default behaviour).
> Functionally speaking, this feature does not introduce any change (it can be viewed as
an optimization in advanced usage scenarios).
> Thread safety: the producers/consumers, which were inherently thread-safe, became not
thread-safe in regard to their start/stop lifecycle.
> The following text can be used as the documentation for the new URI option:
> *Name*
> {{connectionPool}}
> *Default value*
> {{AS400ConnectionPool}} instance
> *Description*
> *Camel 2.10:* Reference to an {{}} instance in
the Registry. This is used for obtaining connections to the AS/400 system. The look up notation
('#' character) should be used.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


View raw message