Thanks, Nishan Patel
SCJP 1.5, SCWCD 1.5, OCPJWSD Java Developer,My Blog
Bosun (SCJP, SCWCD).
So much trouble in the world -- Bob Marley
Haq Yunus wrote:should i provide more details?
Yes, I am, but how is trying to help you get your question answered opinionated?by the way bear, you are indeed opinionated
Bear Bibeault wrote:At this point I've moved this to the Weblogic forum.
Can this be network related thingy which I should investigate (involve network guys)? I tried 'Wireshark' but as I am very poor in networks I couldn't make it work.
In the JSP page the main form is using Post method but in the action we are also sending a query parameter (which goes as Get of course). Can this mixing cause such an intermittent problem?
Do you know any tool which captures requests coming into the WebLogic server?
I think the Post request that give the above mentioned error doesn't get logged in the first place in access.log. Right?
a: Interesting, as I don't see any 500s....
String username = request.getParameter("userName");
I am catching an exception, printing it on the server console and then throwing it again
What should I take to the network guys which shows that this might be a network issue?
Deepak Bala wrote:I asked the question out of curiosity.
When the exception is thrown if you can set a break point at the catch block, you should be able to analyze the request before the response is sent out to the client. This is what I had in mind
Haq Yunus wrote:
Deepak Bala wrote:I asked the question out of curiosity.
When the exception is thrown if you can set a break point at the catch block, you should be able to analyze the request before the response is sent out to the client. This is what I had in mind
ahh! not practical, i think, as you know it is not consistent at all. and i have to watch the system continuously for the whole day to trap that special moment. by the way do you think that the above snoop code will help?
Haq Yunus wrote:Yes. Just opened a case today. Let us see.
Meanwhile can HTTP tunneling be involved in here? Actually right now I am trying to exhaust all options. Moreover we do get 'HTTP Tunneling no enabled' exception every now and then but i never paid any attention to it as it doesn't seem to be linked with the application.
One more thing:
Yesterday we got a 'SocketTimeOutException:read timed out' (only this nothing else) in a workflow where user uploads a file. It was generated on 'InputStream.readLine()' method. again intermittent and never seen before. This made me think that the above original problem might be after all network issue....right??
Space pants. Tiny ad:
New web page for Paul's Rocket Mass Heaters movies
https://coderanch.com/t/785239/web-page-Paul-Rocket-Mass
|