Camel Mail Component doesn't use host/port information from session URI parameter

Solution Verified - Updated -

Issue

The Camel documentation states abut the session option to the mail component:

"Specifies the mail session that camel should use for all mail interactions. Useful in scenarios where mail sessions are created and managed by some other resource, such as a JavaEE container. When using a custom mail session, then the hostname and port from the mail session will be used (if configured on the session). The option is a javax.mail.Session type."

However, when configuring a mail session in JBoss with different host/port information that is provided in the base URI of the route the mail component continues to use the host:port information specified in the core URI of the route instead of looking up the values from the session parameter.

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content