Hi Dario, It's hard to know if it's expected behaviour unless you share a bit more context.
What were you doing (in JUnit tests or curl commands) to produce these? Jim On 9 Aug 2011, at 14:35, Dario Rexin wrote: > Hi, > > I just attached a hoptoad appender to my logger in the Neo4j Server and am > getting some internal neo exceptions besides the ones I’m getting from my > unmanaged extensions. I would like to know, why they happen and if it’s a > known behaviour. Here are the exceptions: > > > java.net.SocketTimeoutException > > Read timed out > > -2 SocketInputStream.java → socketRead0 > 129 SocketInputStream.java → read > 382 ByteArrayBuffer.java → readFrom > 107 StreamEndPoint.java → fill > 198 SocketConnector.java → fill > 290 HttpParser.java → parseNext > 212 HttpParser.java → parseAvailable > 404 HttpConnection.java → handle > 228 SocketConnector.java → run > 582 QueuedThreadPool.java → run > > > java.net.SocketException > > Socket closed > > 162 SocketInputStream.java →?read > 382 ByteArrayBuffer.java →?readFrom > 107 StreamEndPoint.java →?fill > 198 SocketConnector.java →?fill > 290 HttpParser.java →?parseNext > 212 HttpParser.java →?parseAvailable > 404 HttpConnection.java →?handle > 228 SocketConnector.java →?run > 582 QueuedThreadPool.java →?run > > > > Cheers, > > Dario > _______________________________________________ > Neo4j mailing list > [email protected] > https://lists.neo4j.org/mailman/listinfo/user _______________________________________________ Neo4j mailing list [email protected] https://lists.neo4j.org/mailman/listinfo/user
