Re: jetty/karaf bind issue

[Achim Nierbeck]

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 :

> 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  Committer & PMC
OPS4J Pax Web  Committer &
Project Lead
blog 
Co-Author of Apache Karaf Cookbook 

Software Architect / Project Manager / Scrum Master

Re: jetty/karaf bind issue

[smunro]

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

Re: jetty/karaf bind issue

[Achim Nierbeck]

Hi Stephen,

might it be that you have two instances of Karaf running?
One as service and the other one trying to start as standalone?

Regards, Achim

2017-11-26 17:12 GMT+01:00 smunro :

> Hello Achim,
>
> I know it's obvious it's being blocked, the problem is that there is
> nothing
> else on the machine. I've checked the running processes and blocked ports.
> This only occurs when using the wrapper-server to start/stop karaf and
> never
> seems to occur when starting/stopping karaf manually.
>
> It may just boil down to a timing/resource issue with the net-service, but
> I
> thought I'd run it past the forum in case anyone has encountered this
> issue.
>
> Stephen
>
>
>
> --
> Sent from: http://karaf.922171.n3.nabble.com/Karaf-User-f930749.html
>



-- 

Apache Member
Apache Karaf  Committer & PMC
OPS4J Pax Web  Committer &
Project Lead
blog 
Co-Author of Apache Karaf Cookbook 

Software Architect / Project Manager / Scrum Master

Re: jetty/karaf bind issue

[smunro]

Hello Achim,

I know it's obvious it's being blocked, the problem is that there is nothing
else on the machine. I've checked the running processes and blocked ports.
This only occurs when using the wrapper-server to start/stop karaf and never
seems to occur when starting/stopping karaf manually. 

It may just boil down to a timing/resource issue with the net-service, but I
thought I'd run it past the forum in case anyone has encountered this issue.

Stephen



--
Sent from: http://karaf.922171.n3.nabble.com/Karaf-User-f930749.html

Re: jetty/karaf bind issue

[Achim Nierbeck]

Hi,

obviously something else is already running on the configured port for the
webcontainer.
That is by default 8181. So you need to make sure you stop the other
process blocking that port.

regards, Achim

2017-11-26 15:01 GMT+01:00 smunro :

> Hello,
>
> I'm currently having an issue with running karaf as a windows service.
> Intermittently, I'm getting an exception during startup of the service (see
> below). If I restart sometimes, it'll be fine, but other times, I get this
> issue. This doesn't occur if I start karaf manually and stop it manually.
> Is
> there a known issue or recommended strategy for dealing with this?
>
> !org.ops4j.pax.web.pax-web-runtime - 6.0.7 | Could not start the servlet
> context for context path []
> java.net.BindException: Address already in use: bind
> at sun.nio.ch.Net.bind0(Native Method) ~[?:?]
> at sun.nio.ch.Net.bind(Net.java:433) [?:?]
> at sun.nio.ch.Net.bind(Net.java:425) [?:?]
> at
> sun.nio.ch.ServerSocketChannelImpl.bind(ServerSocketChannelImpl.java:223)
> [?:?]
> at sun.nio.ch.ServerSocketAdaptor.bind(ServerSocketAdaptor.java:74)
> [?:?]
> at org.eclipse.jetty.server.ServerConnector.open(
> ServerConnector.java:317)
> [178:org.eclipse.jetty.server:9.3.14.v20161028]
> at
> org.eclipse.jetty.server.AbstractNetworkConnector.doStart(
> AbstractNetworkConnector.java:80)
> [178:org.eclipse.jetty.server:9.3.14.v20161028]
> at
> org.eclipse.jetty.server.ServerConnector.doStart(ServerConnector.java:235)
> [178:org.eclipse.jetty.server:9.3.14.v20161028]
> at
> org.eclipse.jetty.util.component.AbstractLifeCycle.
> start(AbstractLifeCycle.java:68)
> [181:org.eclipse.jetty.util:9.3.14.v20161028]
> at org.eclipse.jetty.server.Server.doStart(Server.java:401)
> [178:org.eclipse.jetty.server:9.3.14.v20161028]
> at
> org.eclipse.jetty.util.component.AbstractLifeCycle.
> start(AbstractLifeCycle.java:68)
> [181:org.eclipse.jetty.util:9.3.14.v20161028]
> at
> org.ops4j.pax.web.service.jetty.internal.JettyServerImpl$1.start(
> JettyServerImpl.java:329)
> [203:org.ops4j.pax.web.pax-web-jetty:6.0.7]
> at
> org.ops4j.pax.web.service.internal.HttpServiceStarted.registerServlet(
> HttpServiceStarted.java:250)
> [205:org.ops4j.pax.web.pax-web-runtime:6.0.7]
> at
> org.ops4j.pax.web.service.internal.HttpServiceStarted.registerServlet(
> HttpServiceStarted.java:221)
> [205:org.ops4j.pax.web.pax-web-runtime:6.0.7]
> at
> org.ops4j.pax.web.service.internal.HttpServiceStarted.registerServlet(
> HttpServiceStarted.java:205)
> [205:org.ops4j.pax.web.pax-web-runtime:6.0.7]
> at
> org.ops4j.pax.web.service.internal.HttpServiceProxy.registerServlet(
> HttpServiceProxy.java:65)
> [205:org.ops4j.pax.web.pax-web-runtime:6.0.7]
> at
> org.apache.cxf.transport.http.osgi.ServletExporter.updated(
> ServletExporter.java:108)
> [125:org.apache.cxf.cxf-rt-transports-http:3.1.11]
> at
> org.apache.felix.cm.impl.helper.ManagedServiceTracker.
> updated(ManagedServiceTracker.java:189)
> [7:org.apache.felix.configadmin:1.8.16]
> at
> org.apache.felix.cm.impl.helper.ManagedServiceTracker.updateService(
> ManagedServiceTracker.java:152)
> [7:org.apache.felix.configadmin:1.8.16]
> at
> org.apache.felix.cm.impl.helper.ManagedServiceTracker.
> provideConfiguration(ManagedServiceTracker.java:85)
> [7:org.apache.felix.configadmin:1.8.16]
> at
> org.apache.felix.cm.impl.ConfigurationManager$
> ManagedServiceUpdate.provide(ConfigurationManager.java:1479)
> [7:org.apache.felix.configadmin:1.8.16]
> at
> org.apache.felix.cm.impl.ConfigurationManager$ManagedServiceUpdate.run(
> ConfigurationManager.java:1435)
> [7:org.apache.felix.configadmin:1.8.16]
> at org.apache.felix.cm.impl.UpdateThread.run0(
> UpdateThread.java:141)
> [7:org.apache.felix.configadmin:1.8.16]
> at org.apache.felix.cm.impl.UpdateThread.run(UpdateThread.
> java:109)
> [7:org.apache.felix.configadmin:1.8.16]
> at java.lang.Thread.run(Thread.java:748) [?:?]
>
> Stephen
>
>
>
>
> --
> Sent from: http://karaf.922171.n3.nabble.com/Karaf-User-f930749.html
>



-- 

Apache Member
Apache Karaf  Committer & PMC
OPS4J Pax Web  Committer &
Project Lead
blog 
Co-Author of Apache Karaf Cookbook 

Software Architect / Project Manager / Scrum Master