[CAMEL-5198] Implement connection pooling in jt400 component

• Type: Improvement
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.9.2
• Fix Version/s: 2.10.0
• Labels: camel-jt400 jt400

Environment

i5/OS servers

• Patch Info: Patch Available
• Estimated Complexity: Unknown
• Assignee: Claus Ibsen
• Reporter: João Loureiro
• Created: 20/Apr/12 11:13
• Updated: 05/Jun/12 09:46
• Resolved: 05/Jun/12 09:46

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).

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 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.