This is a deadlock in the Jetty NIO code, so a further question is what version of the org.apache.felix.http.jetty bundle do you use? You might get rid of this bug by upgrading to the latest released version ( 2.2.1 ) .
If you can't do that, you can tell Jetty not to use NIO ( Felix Web Console -> Comopnents -> 'Apache Felix Jetty Based Http Service' and uncheck the 'NIO for HTTP', 'NIO for HTTPS' ). Hope this helps, Robert On Sat, Nov 30, 2013 at 7:49 AM, bob1986 <[email protected]> wrote: > Hi, > > This is pastebin link: > > http://pastebin.com/nhQFxXUK <http://pastebin.com/nhQFxXUK> > > > > ----- > Babak Behzadi > -- > View this message in context: > http://apache-sling.73963.n3.nabble.com/Apache-Sling-Does-Not-Respond-Any-Request-tp4029042p4029282.html > Sent from the Sling - Users mailing list archive at Nabble.com. -- Sent from my (old) computer
