Hi, at the time of failure with the debugger stopped I have only 10 connections in CLOSE_WAIT or FIN_WAIT mode from the previous tests. The weird thing is it happens only after a certain number of tests have been run for example tests A-D pass by them selves. If I run them sequentially test C fails everytime on the same request (which otherwise works).
I tried to make a gist to test this but it runs find in a for loop. It shouldn't be dependent on any pooled or graph connections I have elsewhere in my code I guess? Maybe I have a leak there but the Java API with the HTTP API are unrelated as I understand. thanks On Thursday, May 14, 2015 at 3:05:43 AM UTC+2, l.garulli wrote: > > Hi Aris, > I'm not an expert of Jersey. Could you check that there are so many > ESTABLISHED connections against OrientDB server? > > netstat -a > > Best Regards, > > Luca Garulli > CEO at Orient Technologies LTD > the Company behind OrientDB > http://about.me/luca.garulli > > > On 13 May 2015 at 15:59, Aris Alexis <[email protected] <javascript:>> > wrote: > >> Hi, >> >> because each thread runs this code only once and the client object is not >> passed around, but I was mainly trying to debug the rejected connections. >> Any ideas? >> >> On Wednesday, May 13, 2015 at 3:51:51 PM UTC+2, l.garulli wrote: >>> >>> Hi Aris, >>> Why closing the connection if Jersey could be able to reuse the same >>> with a Keep-Alive setting? >>> >>> >>> >>> >>> >>> Best Regards, >>> >>> Luca Garulli >>> CEO at Orient Technologies LTD >>> the Company behind OrientDB >>> http://about.me/luca.garulli >>> >>> >>> On 13 May 2015 at 14:57, Aris Alexis <[email protected]> wrote: >>> >>>> Hi, >>>> >>>> I am running 2.0.1 and I am using the http index interface as a >>>> key/value store. I access it with jersey client and have also in the >>>> headers added "Connection","close". >>>> The configuration is set at max pool connections at 1500. When running >>>> my tests without even reaching 20-30 requests I get >>>> >>>> 2015-05-13 14:52:03:127 WARNING Reached maximum number of concurrent >>>> connections >>>> (1013), reject incoming connection from /127.0.0.1:65231 >>>> [OServerNetworkListener] >>>> >>>> I am using a pool (but is it even related to the graph pool?). >>>> >>>> here is a sample request >>>> >>>> Client client=buildClient(); >>>> try { >>>> Response response = client.target(OrientDatabase.getHTTP_URL() + >>>> "/index/exchange/exchangeKV/" + codingUtilities.toUtf(key)) >>>> .request() >>>> .header("Connection", "close") >>>> .put(Entity.entity(value.toString(), >>>> MediaType.APPLICATION_JSON_TYPE)); >>>> >>>> if (response.getStatus() == Response.Status.ACCEPTED.getStatusCode()) >>>> return true; >>>> else return false; >>>> }finally { >>>> client.close(); >>>> } >>>> >>>> >>>> maybe the header is not sent with PUT requests? but again, I am nowhere >>>> near close 1500 connections. >>>> >>>> -- >>>> >>>> --- >>>> You received this message because you are subscribed to the Google >>>> Groups "OrientDB" group. >>>> To unsubscribe from this group and stop receiving emails from it, send >>>> an email to [email protected]. >>>> For more options, visit https://groups.google.com/d/optout. >>>> >>> >>> -- >> >> --- >> You received this message because you are subscribed to the Google Groups >> "OrientDB" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to [email protected] <javascript:>. >> For more options, visit https://groups.google.com/d/optout. >> > > -- --- You received this message because you are subscribed to the Google Groups "OrientDB" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
