Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [jetty-dev] 8.1.2.v20120308 - rare mixup of requests

Thomas Becker skrev:
Hi Per,

surely we do care about bugs in jetty. :) My schedule today is pretty tight, I will send you a longer answer. But if you could try switching the connector to SelectChannelConnector in the meanwhile would be good. I wonder why solr is using the blocking one by default.

There should be a config file for jetty where the connectors are being setup (usually jetty.xml in our standard distribution).

In there there's a section setting up the connectors, simply switch the class in yours to: "org.eclipse.jetty.server.nio.SelectChannelConnector". Then it should look similar to this one.

 36     <Call name="addConnector">
 37       <Arg>
38 <New class="org.eclipse.jetty.server.nio.SelectChannelConnector">
 39             <Set name="host"><Property name="jetty.host" /></Set>
40 <Set name="port"><Property name="jetty.port" default="8080"/></Set>
 41             <Set name="maxIdleTime">300000</Set>
 42             <Set name="Acceptors">2</Set>
 43             <Set name="statsOn">false</Set>
 44             <Set name="confidentialPort">8443</Set>
 45       <Set name="lowResourcesConnections">20000</Set>
 46       <Set name="lowResourcesMaxIdleTime">5000</Set>
 47           </New>
 48       </Arg>
 49     </Call>
I have made a new run of my performance/endurance test with org.eclipse.jetty.server.nio.SelectChannelConnector instead of the SocketConnector and the problem still occures, so I guess it is not due to the SocketConnector. Just a question, how did you know that I was running with SocketConnector instead of SelectChannelConnector?

Cheers,
Thomas




Back to the top