My Oracle Support Banner

Complete Message Timeout 만료후에도 SSL Socket 종료되지 않음 (Doc ID 2293836.1)

Last updated on JANUARY 10, 2018

적용 대상:

Oracle WebLogic Server - 버전 12.1.3.0.0 과(와) 그 후속
이 문서의 내용은 모든 플랫폼에 적용됩니다.

증상

아래와 같이 쓰레드 덤프상에서 많은 쓰레드들이 SocketOutputStream.socketWrite0 에서 STUCK 상태인것을 확인할 수 있습니다. 

"[STUCK] ExecuteThread: '299' for queue: 'weblogic.kernel.Default (self-tuning)'" #349 daemon prio=1 os_prio=0 tid=0x00007fe3d4341800 nid=0x1e2e2 runnable [0x00007fe1ec2ba000]
java.lang.Thread.State: RUNNABLE
at java.net.SocketOutputStream.socketWrite0(Native Method)
at java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:109)
at java.net.SocketOutputStream.write(SocketOutputStream.java:153)
at weblogic.socket.JSSEFilterImpl.writeToNetwork(JSSEFilterImpl.java:773)
at weblogic.socket.JSSEFilterImpl.wrapAndWrite(JSSEFilterImpl.java:734)
at weblogic.socket.JSSEFilterImpl.write(JSSEFilterImpl.java:457)
at weblogic.socket.JSSESocket$JSSEOutputStream.write(JSSESocket.java:127)
at weblogic.servlet.internal.ChunkOutput.writeChunkTransfer(ChunkOutput.java:622)
……

 <BEA-101366>  메세지가   <BEA-000337> 메세지 전후로 서버로그에 출력됩니다.

####<Jun 10, 2017 1:45:12 PM CST> <Info> <HTTP> <xyz> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <> <> <> <1497073512041> <BEA-101366> <The server could not send the HTTP message during the configured timeout value. The socket has been closed.>

“The socket has been closed”라고 표시되었지만 쓰레드가 여전히 socketWrite0 에서 STUCK 상태입니다.

한편, 앞쪽의 OHS 서버 로그는 아래와 같은 로그 메세지들이 확인됩니다. 

[2017-02-08T22:35:37.2141+09:00] [OHS] [ERROR:32] [OHS-9999] [mod_weblogic.c] [client_id: xxx.xxx.xxx.9] [host_id: xxxxxxw1] [host_addr: xxx.xxx.xxx.41] [tid: 140470948534016] [user: xxxxxx] [ecid: 005I0JkRZCT2rI6NzMgOu0000J5E004YfW] [rid: 0] [VirtualHost: m.xyz.com:0] <005I0JkRZCT2rI6NzMgOu0000J5E004YfW> weblogic: Write to the client failed: calling URL::close at line 559 of BaseProxy.cpp, referer: http://m.xyz.com/path/ex?e=xyz

[2017-02-08T22:35:37.2142+09:00] [OHS] [ERROR:32] [OHS-9999] [mod_weblogic.c] [client_id: xxx.xxx.xxx.9] [host_id: xxxxxxw1] [host_addr: xxx.xxx.xxx.41] [tid: 140470948534016] [user: xxxxxx] [ecid: 005I0JkRZCT2rI6NzMgOu0000J5E004YfW] [rid: 0] [VirtualHost: m.xyz.com:0] <005I0JkRZCT2rI6NzMgOu0000J5E004YfW> weblogic: *******Exception type [WRITE_ERROR_TO_CLIENT] raised at line 560 of BaseProxy.cpp, referer: http://m.xyz.com/path/ex?e=xyz

[2017-02-08T22:35:37.2144+09:00] [OHS] [ERROR:32] [OHS-9999] [mod_weblogic.c] [client_id: xxx.xxx.xxx.9] [host_id: xxxxxxw1] [host_addr: xxx.xxx.xxx.41] [tid: 140470948534016] [user: xxxxxx] [ecid: 005I0JkRZCT2rI6NzMgOu0000J5E004YfW] [rid: 0] [VirtualHost: m.xyz.com:0] <005I0JkRZCT2rI6NzMgOu0000J5E004YfW> weblogic: request [http://m.xyz.com/path] did NOT process successfully.................., referer: http://m.xyz.com/path/ex?e=xyz

 

원인

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


이 문서에서
증상
원인
해결책
참고

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.