House of Fusion
Search over 2,500 ColdFusion resources here
  
Home of the ColdFusion Community

Mailing Lists
Home /  Groups /  JRun-Talk

doPost leads to "Read timed out" and JRun death

  << Previous Post |  RSS |  Subscribe to this Group Next >> 

doPost leads to "Read timed out" and JRun death

We've been experiencing an intermittent issue with the doPost method which has Kari Scott 03/12/2007 02:11 PM

03/12/2007 02:11 PM
Author: Kari Scott Short Link: http://www.houseoffusion.com/groups/jrun-talk/thread.cfm/threadid:2238#5794 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         at javax.servlet.http.HttpUtils.parsePostData(HttpUtils.java:242) 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. Thanks, Kari
<< Previous Thread Today's Threads Next Thread >>

Search jrun-talk

May 18, 2013

<<   <   Today   >   >>
Su Mo Tu We Th Fr Sa
       1 2 3 4
5 6 7 8 9 10 11
12 13 14 15 16 17 18
19 20 21 22 23 24 25
26 27 28 29 30 31   

Designer, Developer and mobile workflow conference