2017-09-15 227 views
0

基于Web的应用程序间歇性地抛出'500 Internal Server Error'。此应用程序部署在WAS 8.0服务器上,IHS和WAS服务器托管在不同的机器上。请在IHS末尾查找TRACE级插件日志。从部署在IHS和WAS服务器上的应用程序中获取500内部服务器错误

DEBUG: ws_common: websphereExecute: Wrote the request; reading the response (timeout 900) 
DETAIL: lib_htresponse: htresponseRead: Reading the response: 64040a70 TRACE: lib_rio: Blocking for read, waiting 900 
DEBUG: lib_rio.c line 896 : Read failed, rc=104 
DEBUG: lib_htresponse: htresponseSetError: Setting the error to: |READ_FAILED|(1, Line: 713) 
DEBUG: ws_common: websphereExecute: Failed to read from an old stream; probably Keep-Alive timeout fired 
DEBUG: ws_transport: transportStreamDequeue: Checking for existing stream from the queue 
DEBUG: lib_stream: destroyStream: Destroying the stream 
DEBUG: lib_rio: rclose: socket 13 closed 
STATS: ws_server: serverSetFailoverStatus: Server xxxxx : pendingRequests 0 failedRequests 7 affinityRequests 57 totalRequests 51. 
ERROR: ws_common: websphereHandleRequest: Failed to execute the transaction to 'xxxxx' on host 'yyyyy'; will try another one 
ERROR: ws_common: websphereWriteRequestReadResponse: Failed to find an app server to handle this request 
ERROR: ESI: getResponse: failed to get response: rc = 10 DEBUG: ESI: esiHandleRequest: failed to get response 
DEBUG: ESI: esiRequestUrlStackDestroy 
DEBUG: ESI: cacheURL: '/site/index' 
DETAIL: ESI: esiRequestPopUrl: '/site/index' 
DEBUG: ESI: esiUrlDestroy: '/site/index' 
ERROR: [://site/index] ws_common: websphereHandleRequest: Failed to handle request rc=10 
DEBUG: ws_common: websphereCloseConnection 
DETAIL: ws_common: websphereEndRequest: Ending the request 

请帮我解决问题。在此先感谢

+0

您需要查看WebSphere上的SystemOut.log是什么导致问题。 – Gas

回答

0

rc = 104是指示套接字由伙伴地址重置的Linux返回代码,因此您需要查看应用程序服务器以查找错误。

+0

我选中了,但在请求时间戳期间没有在WAS结束时生成日志。你能否让我知道下面错误的原因?它是与网络/防火墙相关的还是与WAS/IHS相关的错误? “无法从旧流读取;可能保持激活超时已触发” – pankaj

+0

“无法从旧流读取;可能保持激活超时激发”表示插件收到套接字通知但没有数据可用。 “读取失败,rc = 104”是一个OS返回码,ECONNRESET,连接由对等重置。我会建议检查连接的网络跟踪,以查看谁重置了连接。如果它不是应用程序服务器,则它可能是防火墙或端点之间的其他设备。 –