Hard to tell from here, though since it's JettyServerImpl which fails to bind to the configured Port, something else blocks it. So this isn't a common problem seen unless there is already another process blocking it.
regards, Achim 2017-11-26 17:24 GMT+01:00 smunro <[email protected]>: > No, I've checked that in the process list. > > The only thing that's suspect is that we have a massive client bundle (that > could arguably broken). We've used declarative services to try and impose a > start up order. The client bundle in question holds all the jetty features > and the angular WAR, but sits in a grace period for a number of minutes > before coming up, but I expect that to be normal given that's the last > bundle I expect to start. > > This problem can only be replicated when I use the service-wrapper. I'll > put > sysutils to work on it to see If can diagnose it further, but if this isn't > a common issue people are finding, then it must be something up with the > environment. If it was happening both in manual mode and service mode, it > would be a lot easier to pinpoint the problem. > > Stephen > > > > -- > Sent from: http://karaf.922171.n3.nabble.com/Karaf-User-f930749.html > -- Apache Member Apache Karaf <http://karaf.apache.org/> Committer & PMC OPS4J Pax Web <http://wiki.ops4j.org/display/paxweb/Pax+Web/> Committer & Project Lead blog <http://notizblog.nierbeck.de/> Co-Author of Apache Karaf Cookbook <http://bit.ly/1ps9rkS> Software Architect / Project Manager / Scrum Master
