You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@flume.apache.org by "Ferenc Szabo (JIRA)" <ji...@apache.org> on 2017/09/12 13:36:04 UTC

[jira] [Updated] (FLUME-2976) Exception when JMS source tries to connect to a Weblogic server without authentication

     [ https://issues.apache.org/jira/browse/FLUME-2976?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ferenc Szabo updated FLUME-2976:
--------------------------------
    Fix Version/s:     (was: 1.8.0)
                   1.9.0

> 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
>              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
(v6.4.14#64029)