camel-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Igor Stepanov (JIRA)" <>
Subject [jira] [Updated] (CAMEL-6104) Authentication does not work for Weblogic JMS
Date Tue, 26 Feb 2013 20:28:12 GMT


Igor Stepanov updated CAMEL-6104:

    Attachment: instruction.txt

Adding the attachments
> Authentication does not work for Weblogic JMS
> ---------------------------------------------
>                 Key: CAMEL-6104
>                 URL:
>             Project: Camel
>          Issue Type: Bug
>          Components: camel-jms
>    Affects Versions: 2.9.2, 2.10.3
>         Environment: Red Hat Enterprise Linux Server release 5.8, Weblogic,
Tibco EMS
>            Reporter: Igor Stepanov
>              Labels: authentication, camel, camel-jms, tibco, weblogic
>         Attachments: exception.xml, instruction.txt
> Dear collegues,
> I'm trying to configure JMS integration between my application (in Weblogic) and Tibco
EMS. As an example I used next tutorial:
> Application context is configured as suggested:
>     <bean id="weblogic" class="org.apache.camel.component.jms.JmsComponent">
>         <property name="connectionFactory" ref="beaConnectionFactory"/>
>     </bean>
>     <jee:jndi-lookup id="beaConnectionFactory" jndi-name="jms/EAIConnectionFactory"/>
> But connection cannot be established due to authentication issues. Weblogic logs show
> Caused By: javax.jms.JMSSecurityException: invalid name or password
> Tibco console shows:
> 2013-02-26 22:08:25 [anonymous@devapp097]: connect failed: not authorized to connect
> I'm sure that login&password are specified correctly. When I turn off authentication
(on the Tibco side), or try to connect directly (without Weblogic), everything works fine.
So I assumed that issue is between Camel and Weblogic and even found some examples examples
of similar cases:
> Tibco EMS connectivity parameters are configured in WL console according to the attached
> Appreciate your help

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:

View raw message