gearpump-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Weihua Jiang (JIRA)" <j...@apache.org>
Subject [jira] [Issue Comment Deleted] (GEARPUMP-19) JarStoreService is not on the client classpath
Date Thu, 07 Apr 2016 03:27:25 GMT

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

Weihua Jiang updated GEARPUMP-19:
---------------------------------
    Comment: was deleted

(was: Actually, I have a 70% ready patch I made in last Oct. At that time, it was blocked
by an issue at rest service. And I guess [~stanleyxu2005] has removed this blocker already.)

> JarStoreService is not on the client classpath
> ----------------------------------------------
>
>                 Key: GEARPUMP-19
>                 URL: https://issues.apache.org/jira/browse/GEARPUMP-19
>             Project: Apache Gearpump
>          Issue Type: Bug
>          Components: core, daemon
>    Affects Versions: 0.8.0
>            Reporter: Manu Zhang
>            Priority: Blocker
>
> To submit an application jar, client creates JarStore and requires JarStoreService (daemon
module) to be on the classpath but daemon is not published. This breaks any application that
is not submit by Gearpump. E.g. 
> {code}
> Exception in thread "main" java.util.NoSuchElementException: None.get
> 	at scala.None$.get(Option.scala:347)
> 	at scala.None$.get(Option.scala:345)
> 	at io.gearpump.jarstore.JarStoreService$.get(JarStoreService.scala:81)
> 	at io.gearpump.jarstore.JarStoreService$.get(JarStoreService.scala:72)
> 	at io.gearpump.cluster.client.ClientContext.<init>(ClientContext.scala:61)
> 	at io.gearpump.cluster.client.ClientContext$.apply(ClientContext.scala:164)
> 	at io.gearpump.cluster.client.ClientContext.apply(ClientContext.scala)
> {code}



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

Mime
View raw message