[CAMEL-2049] Improper configuration of MINA connector and acceptor instances; Better producer

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 1.6.0
• Fix Version/s: 1.6.2, 2.0.0, 2.1.0
• Component/s: camel-mina

Environment

Windows XP

• Patch Info: Patch Available
• Assignee: Claus Ibsen
• Reporter: Dmytro Rud
• Created: 01/Oct/09 09:00
• Updated: 07/Feb/10 09:56
• Resolved: 08/Oct/09 06:23

Description

A sample scenario where both MINA producer(s) and consumer(s) are used in the same route (e.g. some kind of dispatching or proxying):

from("mina:tcp://localhost:8888?lazySessionCreation=true&sync=true")
.to("mina:tcp://localhost:7777?lazySessionCreation=true&sync=true");

from("mina:tcp://localhost:7777?lazySessionCreation=true&sync=true")
.process(/prepare answer/);

Due to improper configuration of MINA acceptor and connector instances in MinaComponent#createSocketEndpoint(), no more than 15 incoming threads can be served at port 8888 – the producer becomes unable to open an outgoing session. This is actually an issue of MINA, not of Camel – a test application written using "raw" MINA shows the same behaviour.

A solution is to apply configuration rules described, e.g., at http://mina.apache.org/configuring-thread-model.html, as done in the attached patch.

Moreover, the standard Camel-MINA producer is not thread-safe – actually a well-known point. A second attached file contains a thread pool-based reentrant version, which can be efficiently used for TCP endpoints with both parameters 'lazySessionCreation' and 'sync' set to true.