flume-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Peter Turcsanyi (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (FLUME-2976) Exception when JMS source tries to connect to a Weblogic server without authentication
Date Tue, 29 May 2018 12:27:00 GMT

    [ https://issues.apache.org/jira/browse/FLUME-2976?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16493475#comment-16493475
] 

Peter Turcsanyi commented on FLUME-2976:
----------------------------------------

[^FLUME-2976-2.patch] looks fine, +1

> Exception when JMS source tries to connect to a Weblogic server without authentication
> --------------------------------------------------------------------------------------
>
>                 Key: FLUME-2976
>                 URL: https://issues.apache.org/jira/browse/FLUME-2976
>             Project: Flume
>          Issue Type: Bug
>          Components: Sinks+Sources
>    Affects Versions: 1.6.0
>            Reporter: Denes Arvay
>            Assignee: Denes Arvay
>            Priority: Major
>              Labels: jms
>             Fix For: 1.9.0
>
>         Attachments: FLUME-2976-2.patch, FLUME-2976.patch
>
>
> If no {{userName}} and {{passwordFile}} is set for the JMS source it sets the password
to {{Optional("")}} (see: https://github.com/apache/flume/blob/trunk/flume-ng-sources/flume-jms-source/src/main/java/org/apache/flume/source/jms/JMSSource.java#L127)
> This leads to an exception in the weblogic jndi context implementation when trying to
connect to a weblogic jms server.
> {noformat}
> java.lang.IllegalArgumentException: The 'java.naming.security.principal' property has
not been specified
> 	at weblogic.jndi.Environment.getSecurityUser(Environment.java:562)
> 	at weblogic.jndi.WLInitialContextFactoryDelegate.pushSubject(WLInitialContextFactoryDelegate.java:665)
> 	at weblogic.jndi.WLInitialContextFactoryDelegate.newContext(WLInitialContextFactoryDelegate.java:485)
> 	at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java:373)
> 	at weblogic.jndi.Environment.getContext(Environment.java:319)
> 	at weblogic.jndi.Environment.getContext(Environment.java:288)
> 	at weblogic.jndi.WLInitialContextFactory.getInitialContext(WLInitialContextFactory.java:117)
> 	at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:684)
> 	at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:307)
> 	at javax.naming.InitialContext.init(InitialContext.java:242)
> 	at javax.naming.InitialContext.<init>(InitialContext.java:216)
> 	at org.apache.flume.source.jms.InitialContextFactory.create(InitialContextFactory.java:28)
> 	at org.apache.flume.source.jms.JMSSource.doConfigure(JMSSource.java:223)
> {noformat}
> Changing the above mentioned line to {{Optional.absent()}} fixes the issue.
> [~brocknoland]: Is there any specific reason for setting the password to {{Optional("")}}
when there is no {{passwordFile}} set?



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@flume.apache.org
For additional commands, e-mail: issues-help@flume.apache.org


Mime
View raw message