We are facing an issue in our production environment. We have our application (J2EE) deployed on Websphere Application Server(WAS 7). We have a report screen which takes one or more search criteria and based on that it generates a report. The issue we face here is that, for some search criteria, when the transaction time exactly reaches 1 minute, the java thread is lost and we get an exception which is not logged in any of the server logs.  We tried simulating this for other reports screens as well and we inferred that whenever the java process thread reaches exactly 1 minute, we get an exception in the screen which is not logged in any of the logs.

 

The exception which we receive is a generic “Internal Server Error” exception(500 Error) and it has no other information in it. We used firebug and also printed the error in our jquery error handlers and at both the places we could see that the error we receive is a Generic Internal Server error.

 

So from our analysis we infer that the error is because of the java thread related issue and we could not figure out what exact setting or configuration(in the WAS admin console) should be modified to solve this issue.

Hi Sri,

  As you say you can reproduce the problem.  Why you don't enable traces?

  Tell us if you need more support.

regards,

Hey Sri,

It may not necessarily be a java thread issue (although it is known WAS doesn't support multi threaded requests).  It sounds like you need to tune your JVM timeout settings.  The application server's SystemOut logs and Nativestdout/Nativestderr logs are a good place to start looking for what is timing out so you can adjust your JVM settings accordingly.  It also wouldn't help to cross reference the nodeagent's SystemOut logs as well to rule out any anamolies.

Cheers!

Danielle

Thanks a lot Gabriel and Danielle for your quick response. But the problem i face is that, there are no traces of the exception in the SystemOut.log and also in the SystemErr.log. We observe that from the time the user clicks on the button, exactly after 60 seconds, we get an exception that is not logged anywhere.

We do not whether is there any setting in the admin console or something which causes this... We have other devlopment environments where the same scenario works fine without this time out scenario. So thats the state we are in...

Appreciate further help on this..

Thanks in advance...

Hi Sri,
The Best options would be that of the others, as mentioned by Gabriel, Danielle & Ralph.
Additionally,
What is your application trying to do in that 1 minute?
Have you tried to take any thread dump for analysis?
Have you set any timeout values  in Production?
Why dont you compare the configuration between Production and development issues.. ex: transatcion services timeout, webcontainer  timeout values etc...

Regards
Ashraf

My guess will be websphere plugin timeout value.   Check the plugin-cfg.xml to see if the ServerIOTimeout is set to be 60 seconds.

Sam