Hi,
This subject may be related to this thread
http://forums.java.net/jive/message.jspa?messageID=352491
or this bug
https://glassfish.dev.java.net/issues/show_bug.cgi?id=8518
Under low to high load, the same SOAP request can lead to several exceptions.
All those exceptions deal with an XML component.
With the web container logging level defined to FINE or FINER, I can detect two distinct patterns in the logs. (see the attached file for samples)
When the treatment is successful, there is one and only one reference to realRead
ClassName=org.apache.coyote.tomcat5.InputBuffer;MethodName=realReadBytes;_RequestID=f3475597-4374-4ca2-88ab-ee3177aa396a;|realRead() R( /CampagneServiceV2/services/CampagneServiceV2)
When the treatment is erroneous, there are exactly two successive references to realRead.
This is the only difference I can notice in the way the SOAP request is dealt with before any exception.
Any idea of the meaning of this ?
Since I got a very reproduceable test case, any idea to dig into this would be greatly appreciated.
Bye
[Message sent by forum member 'vkoniecz' (vkoniecz)]
http://forums.java.net/jive/thread.jspa?messageID=352951