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

Andrew Purtell commented on PHOENIX-1233:
-----------------------------------------

Huh. And after that comment JIRA refreshes and I see Jesse's stuff. Carry on. 

> Detected both log4j-over-slf4j.jar AND slf4j-log4j12.jar on the class path, 
> preempting StackOverflowError
> ---------------------------------------------------------------------------------------------------------
>
>                 Key: PHOENIX-1233
>                 URL: https://issues.apache.org/jira/browse/PHOENIX-1233
>             Project: Phoenix
>          Issue Type: Bug
>    Affects Versions: 4.1
>            Reporter: Brian Johnson
>            Assignee: Ted Yu
>         Attachments: 1233-v1.txt, phoenix-1233-master-v1.patch, 
> phoenix-1233-v1.patch
>
>
> When adding the phoenix jar to the Storm (https://storm.incubator.apache.org) 
> classpath I get the following message and then Storm fails to start:
> SLF4J: Class path contains multiple SLF4J bindings.
> SLF4J: Found binding in 
> [jar:file:/Users/bjohnson/Documents/workspace/korrelate/O2O/jruby/target/dependency/storm/default/logback-classic-1.0.6.jar!/org/slf4j/impl/StaticLoggerBinder.class]
> SLF4J: Found binding in 
> [jar:file:/Users/bjohnson/Documents/workspace/korrelate/O2O/jruby/target/dependency/topology/default/phoenix-4.1.0-client-hadoop2.jar!/org/slf4j/impl/StaticLoggerBinder.class]
> SLF4J: See http://www.slf4j.org/codes.html#multiple_bindings for an 
> explanation.
> SLF4J: Actual binding is of type 
> [ch.qos.logback.classic.selector.DefaultContextSelector]
> SLF4J: Detected both log4j-over-slf4j.jar AND slf4j-log4j12.jar on the class 
> path, preempting StackOverflowError. 
> SLF4J: See also http://www.slf4j.org/codes.html#log4jDelegationLoop for more 
> details.
> NameError: cannot initialize Java class backtype.storm.LocalCluster



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to