Found this solution Which worked for one of the users

http://dev.eclipse.org/mhonarc/lists/jetty-users/msg04338.html


On Mon, Jun 16, 2014 at 11:32 AM, Srikar Appalaraju (Reco Team - Tech) <
[email protected]> wrote:

> have they not patched this since 2013? This kind of excessive logging is a
> serious issue in prod envs.  Is turning OFF the only option? Is there no
> "varied" levels of logging?
>
> Srikar
>
>
> On Mon, Jun 16, 2014 at 11:26 AM, Hemanth Haridas (Tech - BLR) <
> [email protected]> wrote:
>
>> Hello
>>
>> We are using *jetty 8.1.14.v20131031 *on Java 6.
>>
>> We are seeing the following warning (When we have a server load) . The
>> warning gets repeated thousands of time and this is slowing down our server
>> and causing timeouts.
>>
>> 2014-06-11 07:18:03,500  [qtp1653858092-49 Selector7] WARN
>>  org.eclipse.jetty.io.nio - Dispatched Failed! SCEP@4a18198b{l(/
>> 10.65.30.11:11500
>> )<->r(/IP:PORT),s=-1,open=true,ishut=false,oshut=false,rb=false,wb=false,w=true,i=0}-{AsyncHttpConnection@74351aad,g=HttpGenerator{s=0,h=-1,b=-1,c=-1},p=HttpParser{s=-14,l=0,c=0},r=0}
>> to
>> org.eclipse.jetty.server.nio.SelectChannelConnector$ConnectorSelectorManager@733d7210
>>
>>
>> The problem is quite similar to the following stack exchange thread. -
>> http://stackoverflow.com/questions/16592537/jetty-8-1-flooding-the-log-file-with-dispatched-failed-messages
>> .
>>
>> Is turning off the warning the right solution?
>>
>> Does this issue get resolved if we move to Jetty9 from Jetty 8.
>> Right now we are not in a position to move from Jetty 8 to Jetty9 as this
>> involves moving from Java 6 to Java 7 and we do not want to do that move
>> immediately due to other pressing priorities.
>>
>> Is this a known issue and Is there a patch for the issue.  Is there a
>> solution without moving from Jetty 8 to Jetty 9 .
>>
>> Warm Regards
>> Hemanth
>> Engineer @ Flipkart
>>
>
>
_______________________________________________
jetty-users mailing list
[email protected]
https://dev.eclipse.org/mailman/listinfo/jetty-users

Reply via email to