camel-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From João Loureiro (Updated) (JIRA) <j...@apache.org>
Subject [jira] [Updated] (CAMEL-5198) Implement connection pooling in jt400 component
Date Fri, 20 Apr 2012 11:18:40 GMT

     [ https://issues.apache.org/jira/browse/CAMEL-5198?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

João Loureiro updated CAMEL-5198:
---------------------------------

    Description: 
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). There is one exception: failure to connect to the
system might arise sooner, at Endpoint creation time, rather than at Producer/Consumer start
time (although this depends on the pool implementation, it is the default behaviour).

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 {{com.ibm.as400.access.AS400ConnectionPool}} instance in the
Registry. This is used for obtaining connections to the AS/400 system. The look up notation
('#' character) should be used.

  was:
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). There is one exception: failure to connect to the
system might arise sooner, at Endpoint creation time, rather than at Producer/Consumer start
time (although this depends on the pool implementation, it is the default behaviour).

    
> Implement connection pooling in jt400 component
> -----------------------------------------------
>
>                 Key: CAMEL-5198
>                 URL: https://issues.apache.org/jira/browse/CAMEL-5198
>             Project: Camel
>          Issue Type: Improvement
>    Affects Versions: 2.9.2
>         Environment: i5/OS servers
>            Reporter: João Loureiro
>              Labels: camel-jt400, jt400
>             Fix For: 2.10.0
>
>         Attachments: patch.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). There is one exception: failure to connect to
the system might arise sooner, at Endpoint creation time, rather than at Producer/Consumer
start time (although this depends on the pool implementation, it is the default behaviour).
> 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 {{com.ibm.as400.access.AS400ConnectionPool}} 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: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

       

Mime
View raw message