[jira] [Resolved] (SAMZA-102) SamzaAppMasterService.scala - exception handling onInit() always assume port conflict, very misleading

["Chris Riccomini (JIRA)" <ji...@apache.org>]

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

Chris Riccomini resolved SAMZA-102.
-----------------------------------

       Resolution: Invalid
    Fix Version/s: 0.7.0

As [~zjshen] suggests, done as part of SAMZA-175.

> SamzaAppMasterService.scala - exception handling onInit() always assume port conflict, very misleading
> ------------------------------------------------------------------------------------------------------
>
>                 Key: SAMZA-102
>                 URL: https://issues.apache.org/jira/browse/SAMZA-102
>             Project: Samza
>          Issue Type: Bug
>          Components: container
>    Affects Versions: 0.6.0
>            Reporter: Jim Huang
>             Fix For: 0.7.0
>
>
> Inside the onInit() method tries to start up WebAppServer, the catch exception only assumes the port number maybe the issue.  
> {code:title=SamzaAppMasterService.scala}      try {
>         rpcApp = new WebAppServer("/", rpcPort)
>         rpcApp.addServlet("/*", new ApplicationMasterRestServlet(config, state, registry))
>         rpcApp.start
>         webApp = new WebAppServer("/", trackingPort)
>         webApp.addServlet("/*", new ApplicationMasterWebServlet(config, state))
>         webApp.start
>         state.rpcPort = rpcPort
>         state.trackingPort = trackingPort
>         return
>       } catch {
>         case e: Exception => {
>           warn("Unable to start webapp on rpc port %d, tracking port %d .. retrying" format (rpcPort, trackingPort))
>         }
>       }{code}
> In my environment, I was using IBM JDK and after some debugging the issue has nothing to do with port number not been available, but in the Java reflection layer.  



--
This message was sent by Atlassian JIRA
(v6.2#6252)