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

ASF GitHub Bot commented on EAGLE-870:
--------------------------------------

GitHub user jhsenjaliya opened a pull request:

    https://github.com/apache/eagle/pull/811

    [EAGLE-870] adding required packages into storm-jar

    without these required packages, it throws class not found exception, more 
detail is in the ticket.

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/jhsenjaliya/eagle EAGLE-870

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/eagle/pull/811.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #811
    
----
commit a22d33db32bb9c7aaa51429ad69db9b4cd0e35ee
Author: Jay <jhsonl...@gmail.com>
Date:   2017-02-11T01:23:57Z

    [EAGLE-870] adding required packages into storm-jar

----


> NoClassDefFoundError while running storm topology for alert and MRrunning
> -------------------------------------------------------------------------
>
>                 Key: EAGLE-870
>                 URL: https://issues.apache.org/jira/browse/EAGLE-870
>             Project: Eagle
>          Issue Type: Bug
>            Reporter: Jayesh
>            Assignee: Jayesh
>            Priority: Critical
>
> alert module is throwing this error in storm topology about not finding the 
> class
> {code}
> java.lang.NoClassDefFoundError: com/sun/jersey/api/client/GenericType at 
> org.apache.eagle.alert.engine.coordinator.impl.ZKMetadataChangeNotifyService.init(ZKMetadataChangeNotifyService.java:70)
> {code}
> GenericType class here mentioned is part of jetty-client from 
> com.sun.jersey.jetty which is not included in 
> eagle-topology-0.5.0-SNAPSHOT-assembly.jar
> due to this error, alert topology wont be able to execute.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Reply via email to