[
https://issues.apache.org/jira/browse/FLUME-2559?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14262331#comment-14262331
]
Hans Jespersen commented on FLUME-2559:
---------------------------------------
There are several ways to specify the message-vpn. The easiest is to add
"@vpn_name" to the username.
For example, to login to the message vpn "demo_vpn" with login "hans" and
password "secret" then use "hans@demo_vpn" as the username and "secret" as the
password.
If a message vpn is not specified it will try and use the default message vpn
which is a vpn named "default". In other words, logging in as username "hans"
is the same as logging in as "hans@default".
Since a message vpn is a virtual message broker, with separate users,
passwords, and configuration parameters, you should check that your users
credentials are valid, the client username is enabled, JNDI is enabled, and a
JMS connection factory have been created on your target message vpn.
> JMS Source with Solace and the VPN initial context property?
> -------------------------------------------------------------
>
> Key: FLUME-2559
> URL: https://issues.apache.org/jira/browse/FLUME-2559
> Project: Flume
> Issue Type: Question
> Reporter: Lauren Ryan
>
> Has anyone been able to connect to a Solace queue/topic with the JMS source?
> I can't seem to get it to work. I believe this is because there is currently
> no way (that I can see, at least!) to add the VPN Solace requires. I get
> "JNDI lookup failed" with the exception:
> {{com.solacesystems.jcsmp.JCSMPErrorResponseException: 401: Incomplete
> Authentication Configuration [Subcode:1] cause: null.}}
> When I play around with the flume code locally and add the support for a
> solaceVPN property in the config and add the line:
> {code}
> contextProperties.setProperty("Solace_JMS_VPN", solaceVPNName);
> {code}
> to the JMSSource everything works fine.
> Can the JMS source work out of the box with Solace?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
