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

ASF GitHub Bot commented on GEARPUMP-368:
-----------------------------------------

Github user karol-brejna-i commented on the issue:

    https://github.com/apache/incubator-gearpump/pull/241
  
    I did search for AkkaApp usages and there are few groups of them:
    1. examples (proper AkkaApp usage)
    2. gearpupm-core (comands like submit, kill, etc. plus master and worker)
    3. gearpump-services 
    3. experiments (storm, yarn, akka-streams)
    
    Some details on experiments (AkkaApp usages):
    ```
    gearpump-experiments-storm  (2 usages found)
        org.apache.gearpump.experiments.storm.main  (2 usages found)
            GearpumpNimbus.scala  (1 usage found)
                47 object GearpumpNimbus extends AkkaApp with ArgumentsParser {
            GearpumpStormClient.scala  (1 usage found)
                27 object GearpumpStormClient extends AkkaApp with 
ArgumentsParser {
    gearpump-experiments-yarn  (3 usages found)
        org.apache.gearpump.experiments.yarn.appmaster  (1 usage found)
            YarnAppMaster.scala  (1 usage found)
                281 object YarnAppMaster extends AkkaApp with ArgumentsParser {
        org.apache.gearpump.experiments.yarn.client  (2 usages found)
            LaunchCluster.scala  (1 usage found)
                160 object LaunchCluster extends AkkaApp with ArgumentsParser {
            ManageCluster.scala  (1 usage found)
                87 object ManageCluster extends AkkaApp with ArgumentsParser {
    gearpump-servicesJVM  (1 usage found)
        org.apache.gearpump.services.main  (1 usage found)
            Services.scala  (1 usage found)
                41 object Services extends AkkaApp with ArgumentsParser {
    ```
    
    This is something I'd like to discuss. Do we change the ancestor here, too?
    I need to refresh this yarn code in my head...
    



> Application details page does not load
> --------------------------------------
>
>                 Key: GEARPUMP-368
>                 URL: https://issues.apache.org/jira/browse/GEARPUMP-368
>             Project: Apache Gearpump
>          Issue Type: Bug
>          Components: services
>    Affects Versions: 0.8.5
>            Reporter: Hashan Gayasri Udugahapattuwa
>            Assignee: Karol Brejna
>            Priority: Major
>         Attachments: gearpump-master-47505.log, gearpump-ui-47572.log, 
> gearpump-worker-47538.log, logs.zip
>
>
> Application details page does not load in the 
> 0.8.5-SNAPSHOT(8aac07b86d4b90e4f5118f3204610d3510f93b02). This is recreatable 
> with the default examples. 
> This issue not present in the 0.8.4 release.
>  
> Request : [http://172.25.34.11:8090/api/v1.0/appmaster/1?detail=true]
> Status Code : 500 Internal Server Error
>  
> Response : 
> akka.pattern.AskTimeoutException: Ask timed out on 
> [Actor[akka.tcp://app1-executor-1@10.10.1.20:33881/user/daemon/appdaemon1/$c#1247996686]]
>  after [15000 ms]. Sender[null] sent message of type 
> "org.apache.gearpump.cluster.MasterToAppMaster$AppMasterDataDetailRequest".
>  at akka.pattern.PromiseActorRef$$anonfun$1.apply$mcV$sp(AskSupport.scala:604)
>  at akka.actor.Scheduler$$anon$4.run(Scheduler.scala:126)
>  at 
> scala.concurrent.Future$InternalCallbackExecutor$.unbatchedExecute(Future.scala:601)
>  at 
> scala.concurrent.BatchingExecutor$class.execute(BatchingExecutor.scala:109)
>  at 
> scala.concurrent.Future$InternalCallbackExecutor$.execute(Future.scala:599)
>  at 
> akka.actor.LightArrayRevolverScheduler$TaskHolder.executeTask(LightArrayRevolverScheduler.scala:329)
>  at 
> akka.actor.LightArrayRevolverScheduler$$anon$4.executeBucket$1(LightArrayRevolverScheduler.scala:280)
>  at 
> akka.actor.LightArrayRevolverScheduler$$anon$4.nextTick(LightArrayRevolverScheduler.scala:284)
>  at 
> akka.actor.LightArrayRevolverScheduler$$anon$4.run(LightArrayRevolverScheduler.scala:236)
>  at java.lang.Thread.run(Unknown Source)
>  
>  
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to