MINA 2 Component
Available as of Camel 2.10
The mina2: component is a transport for working with Apache MINA 2.x
Favor using Netty as Netty is a much more active maintained and popular project than Apache Mina currently is
Be careful with sync=false on consumer endpoints. Since camel-mina2 all consumer exchanges are InOut. This is different to camel-mina.
Maven users will need to add the following dependency to their
pom.xml for this component:
You can specify a codec in the Registry using the codec option. If you are using TCP and no codec is specified then the
textline flag is used to determine if text line based codec or object serialization should be used instead. By default the object serialization is used.
For UDP if no codec is specified the default uses a basic
ByteBuffer based codec.
The VM protocol is used as a direct forwarding mechanism in the same JVM.
A Mina producer has a default timeout value of 30 seconds, while it waits for a response from the remote server.
In normal use,
camel-mina only supports marshalling the body content—message headers and exchange properties are not sent.
However, the option, transferExchange, does allow you to transfer the exchange itself over the wire. See options below.
You can append query options to the URI in the following format,
You can refer to a named
Whether or not to disconnect(close) from Mina session right after use. Can be used for both consumer and producer.
Only used for TCP. If no codec is specified, you can use this flag to indicate a text line based codec; if not specified or the value is
Only used for TCP and if textline=true. Sets the text line delimiter to use. Possible values are:
Setting to set endpoint as one-way or request-response.
Sessions can be lazily created to avoid exceptions, if the remote server is not up and running when the Camel producer is started.
You can configure the timeout that specifies how long to wait for a response from a remote server. The timeout unit is in milliseconds, so 60000 is 60 seconds. The timeout is only used for Mina producer.
Only used for TCP. You can transfer the exchange over the wire instead of just the body. The following fields are transferred: In body, Out body, fault body, In headers, Out headers, fault headers, exchange properties, exchange exception. This requires that the objects are serializable. Camel will exclude any non-serializable objects and log it at
You can enable the Apache MINA logging filter. Apache MINA uses
You can set a list of Mina IoFilters to register. The
Set the textline protocol encoder max line length. By default the default value of Mina itself is used which are
Set the textline protocol decoder max line length. By default the default value of Mina itself is used which are 1024.
Number of worker threads in the worker pool for TCP and UDP (UDP requires Camel 2.11.3/2.12.2 onwards).
The mina component installs a default codec if both,
If sync is enabled then this option dictates MinaConsumer if it should disconnect where there is no reply to send back.
If sync is enabled this option dictates MinaConsumer which logging level to use when logging a there is no reply to send back. Values are:
Whether to use ordered thread pool, to ensure events are processed orderly on the same channel.
SSL configuration using an
Whether to auto start SSL handshake.
|Camel 2.14: Whether to create the InetAddress once and reuse. Setting this to |
|Camel 2.15: Consumer only. If the |
Using a custom codec
See the Mina how to write your own codec. To use your custom codec with
camel-mina, you should register your codec in the Registry; for example, by creating a bean in the Spring XML file. Then use the
codec option to specify the bean ID of your codec. See HL7 that has a custom codec.
Sample with sync=false
In this sample, Camel exposes a service that listens for TCP connections on port 6200. We use the textline codec. In our route, we create a Mina consumer endpoint that listens on port 6200:
As the sample is part of a unit test, we test it by sending some data to it on port 6200.
Sample with sync=true
In the next sample, we have a more common use case where we expose a TCP service on port 6201 also use the textline codec. However, this time we want to return a response, so we set the
sync option to
true on the consumer.
Then we test the sample by sending some data and retrieving the response using the
template.requestBody() method. As we know the response is a
String, we cast it to
String and can assert that the response is, in fact, something we have dynamically set in our processor code logic.
Sample with Spring DSL
Spring DSL can, of course, also be used for MINA. In the sample below we expose a TCP server on port 5555:
In the route above, we expose a TCP server on port 5555 using the textline codec. We let the Spring bean with ID,
myTCPOrderHandler, handle the request and return a reply. For instance, the handler bean could be implemented as follows:
Closing Session When Complete
When acting as a server you sometimes want to close the session when, for example, a client conversion is finished. To instruct Camel to close the session, you should add a header with the key
CamelMinaCloseSessionWhenComplete set to a boolean
For instance, the example below will close the session after it has written the
bye message back to the client:
Get the IoSession for message
You can get the IoSession from the message header with this key
Mina2Constants.MINA_IOSESSION, and also get the local host address with the key
Mina2Constants.MINA_LOCAL_ADDRESS and remote host address with the key
Configuring Mina filters
Filters permit you to use some Mina Filters, such as
SslFilter. You can also implement some customized filters. Please note that
logger are also implemented as Mina filters of type,
IoFilter. Any filters you may define are appended to the end of the filter chain; that is, after