Author: Kari Scott
We've been experiencing an intermittent issue with the doPost method which has
the look and feel of using a sendRedirect without a return: the number of JRun
threads jumps significantly, the Apache log shows a 503 error for the POST
request, and, in some cases, JRun never recovers and has to be restarted.
The JRun out log shows this error:
03/11 17:34:19 warning Error while parsing POST data
java.lang.IllegalArgumentException: Read timed out
The JRun err log shows:
03/11 19:16:32 error Requested resource 'null' (null) not found
And is usually followed by a number of various socket time out exceptions.
The doPost is done in a servlet that does remote credit card verification and is
sending information to various bank servers which sometimes don't respond or
don't respond quicky and I'm guessing that is the root cause.
The question then is what can I do to prevent JRun from tanking in this
situation? I'm also wondering why JRun is using the deprecated HttpUtils class
when JRun 4 is supposed to be up to Servlet 2.3.
We're using JRun 4, Updater 6 on Solaris 9 with the 1.4.2 JVM.