• Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

Error 500 and also getting an ISAPI error.

 
Thaya Thava
Ranch Hand
Posts: 38
  • 0
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Description of the Problem/Question:

Here is the error message we are seeing in the extended logging on the webserver. We can replicate in our test
environment and this log is from the test region. It throws an error 500, ISAPI error to the user.
Here are the log entries from wlacess.log on cssna105. I tried to search for the root cause without any success.
At some point, some one was saying to set the KeepAlive value to off. It is recommended to set to ON in performance guide.
Ct claims, small size of the messaging is getting through and some with larger size is getting this errors.


wlacess.log:

<79241247502601228> SSL is not being used
Mon Jul 13 12:30:01 2009 <79241247502601228> resolveRequest: wlforward: /
Mon Jul 13 12:30:01 2009 <79241247502601228> URI is /, len=1
Mon Jul 13 12:30:01 2009 <79241247502601228> Request URI = [/]
Mon Jul 13 12:30:01 2009 <79241247502601228> attempt #0 out of a max of 5
Mon Jul 13 12:30:01 2009 <79241247502601228> Trying a pooled connection for 'XXXXXX/9100/9100'
Mon Jul 13 12:30:01 2009 <79241247502601228> got pooled connection to server 'XXXXXXX/9100/9100' from general list for '/', Local port: 1318
Mon Jul 13 12:30:01 2009 <79241247502601228> WLS info in sendRequest: XXXXXXX:9100 recycled? 1
Mon Jul 13 12:30:01 2009 <79241247502601228> URL::parseHeaders: CompleteStatusLine set to http://HTTP/1.1 200 OK
Mon Jul 13 12:30:01 2009 <79241247502601228> URL::parseHeaders: StatusLine set to 200 OK
Mon Jul 13 12:30:01 2009 <79241247502601228> parsed all headers OK
Mon Jul 13 12:30:01 2009 <79241247502601228> sendResponse() : uref->getStatus() = '200'
Mon Jul 13 12:30:01 2009 <79241247502601228> Going to send headers to the client. Status :200 OK
Mon Jul 13 12:30:01 2009 <79241247502601228> Content Length = 1573
Mon Jul 13 12:30:01 2009 <79241247502601228> canRecycle: conn=1 status=200 isKA=1 clen=1573 isCTE=0
Mon Jul 13 12:30:01 2009 <79241247502601228> closeConn: pooling for 'XXXXXX/9100'
Mon Jul 13 12:30:01 2009 <79241247502601228> request [/] processed successfully ..................
Mon Jul 13 12:30:02 2009 <79241247502598226> URL::parseHeaders: CompleteStatusLine set to http://HTTP/1.1 200 OK
Mon Jul 13 12:30:02 2009 <79241247502598226> URL::parseHeaders: StatusLine set to 200 OK
Mon Jul 13 12:30:02 2009 <79241247502598226> parsed all headers OK
Mon Jul 13 12:30:02 2009 <79241247502598226> sendResponse() : uref->getStatus() = '200'
Mon Jul 13 12:30:02 2009 <79241247502598226> Going to send headers to the client. Status :200 OK
Mon Jul 13 12:30:02 2009 <79241247502598226> Content Length Unknown
Mon Jul 13 12:30:02 2009 <79241247502598226> *******Exception type READ_ERROR_FROM_SERVER (socket read failure) raised at line 207 of ..\nsapi\.\Reader.cpp
Mon Jul 13 12:30:02 2009 <79241247502598226> got exception in sendResponse phase: READ_ERROR_FROM_SERVER http://os error=0, line 207 of ..\nsapi\.\Reader.cpp: socket read failure at line 1043
Mon Jul 13 12:30:02 2009 <79241247502598226> NOT failing over after sendResponse() exception: READ_ERROR_FROM_SERVER
Mon Jul 13 12:30:02 2009 <79241247502598226> request [/PSIGW/HttpListeningConnector] did NOT process successfully ..................
Mon Jul 13 12:30:03 2009 <79241247502603229>
and

from JAVA STACK TRACE, see attached, any thoughts for the cause...
Filename: untitled.bmp
Description:
File size: 658 Kbytes
[Download untitled.bmp] Download Attachment
 
I agree. Here's the link: http://aspose.com/file-tools
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic