[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [jetty-users] onFail FillInterest
|
Hi,
On Thu, Dec 12, 2019 at 5:47 PM Karel Goderis <karel.goderis@xxxxxx> wrote:
> 17:40:48.639 [p1947192530-131] DEBUG o.e.jetty.server.HttpConnection:243 - HttpConnection@2173c5af::SocketChannelEndPoint@6e62015d{/0:0:0:0:0:0:0:1:50147<->/0:0:0:0:0:0:0:1:9090,OPEN,fill=-,flush=-,to=6/30000}{io=0/0,kio=0,kro=1}->HttpConnection@2173c5af[p=HttpParser{s=START,0 of -1},g=HttpGenerator@2cc04705{s=START}]=>HttpChannelOverHttp@11bcc90a{r=0,c=false,c=false/false,a=IDLE,uri=null,age=0} onFillable enter HttpChannelState@52994fc4{s=IDLE a=NOT_ASYNC i=true r=IDLE w=false} null
This shows that Jetty has entered HttpConnection.onFillable() to read
from the network and parse the bytes.
However, there appear to be no read from the network, and therefore no parsing.
30 seconds later, idle timeout kicks in.
I have no idea what's going on, it's one of those "this can't happen".
At least I would expect to see the logs of the attempt to read from the network.
You have further logs from the OSGi framework? I'm thinking maybe some
low-level OSGi class loading failure or such?
Is this 100% reproducible?
--
Simone Bordet
----
http://cometd.org
http://webtide.com
Developer advice, training, services and support
from the Jetty & CometD experts.
