gearpump-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Qian Xu (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (GEARPUMP-19) JarStoreService is not on the client classpath
Date Thu, 07 Apr 2016 06:57:25 GMT

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

Qian Xu commented on GEARPUMP-19:
---------------------------------

After the refactor of FileUploadService, this is not a blocker (if I remember it correctly).

> 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