[
https://issues.apache.org/jira/browse/SLIDER-809?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15075372#comment-15075372
]
Jonathan Maron commented on SLIDER-809:
---------------------------------------
OK - so I'm not certain how you ended up allocating the same port, unless it's
a unique timing issue. The code in agent
(CustomServiceOrchestrator.allocatePort()) will attempt open a socket from
either a provided list or randomly (passing in 0 to socket.bind). If
successful, it will close the socket and relate the port back to the AM during
its handshake. I suppose it's possible that if two containers are starting up
on the same host and and the code is somehow executed sequentially on both
agents they may relate back the same port number?
> Apache Tomcat App-Package
> -------------------------
>
> Key: SLIDER-809
> URL: https://issues.apache.org/jira/browse/SLIDER-809
> Project: Slider
> Issue Type: New Feature
> Components: app-package
> Reporter: Josh Elser
> Assignee: Josh Elser
> Fix For: Slider 2.0.0
>
>
> I started working on an app-package for Tomcat.
> https://github.com/apache/incubator-slider/tree/feature/SLIDER-809-tomcat-app-package/app-packages/tomcat
> Some things that need to happen for a generally usable app-package:
> * -Maven module in slider for the code-
> * -Template for server.xml -- notably the port to listen on and other options-
> * Reference external WAR file
> * Fix exports so allocated port for tomcat is advertised (e.g. can view on
> appmaster status page)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
