고객지원

질문과 답변 (Q&A)

자주 묻는 질문(FAQ) 에서 원하는 답변을 찾지 못하셨을 경우 문의해 주세요.
최대한 빠르게 답변해 드리겠습니다.

XCom

제품문의 Socket is in bad state! 문의 2017-10-10
강준호 kkangjuno@kctech.co.kr 60
안녕하세요
XCom 제품 사용중에 아래와 같은 Message 발생 후 통신 끊김현상이 발생하여 문의드립니다.

17:10:33 [Proc:Alarm] Socket error=10054: Connection closed by foreign host on socket write
17:10:33 [Proc:Alarm] Socket send data error: 10054
17:10:33 [Socket:Dump] dump of message stream failed sending for the socket error (10054), elapsed time=0
00 00 00 32 00 00 06 01 00 00 03 97 AD B8 01 04 41 04 32 30 31 32 41 01 37 41 10 32 30 31
37 31 30 30 37 31 37 30 39 34 39 30 30 01 02 41 02 35 30 41 03 31 32 39
17:10:33 [I/F:Alarm] Cannot send S6F1 [system bytes=0397adb8] - Line is not ready; -10023
17:10:33 [SECS-II:Send] XCom.Send() failed

17:10:33 [Proc:Alarm] Socket is in bad state!
17:10:33 [I/F:Alarm] Cannot send S6F11 [system bytes=0397adba] - Line is not ready; -10023
17:10:33 [SECS-II:Send] XCom.Send() failed
17:10:33 [Proc:Alarm] socket error=10053 : connection closed in socket event
17:10:33 [HSMS:Event] Socket closed
17:10:33 [Proc:Event] handling network close
17:10:33 [HSMS:State] State Changed : Selected -> Not Connected
17:10:33 [Proc:Alarm] Passive HSMS will restart after T5.
17:10:33 [Proc:Alarm] HSMS will restart after T5.
17:10:33 [Proc:Alarm] HSMS will restart after T5.
17:10:43 [Proc:Event] XCom restarting
17:10:43 [Proc:Event] XCom Stopped
17:10:43 [Proc:Event] Protection Type : HASP, Serial NO : SC-0002-00002A6F
17:10:43 [Proc:Event] XCom Started
17:10:43 [Proc:Event] XCom restarted
17:48:43 [Proc:Event] XCom Version: v2.3.1.4, 2013/04/16
17:48:43 [Proc:Event] Protection Type : HASP, Serial NO : SC-0002-00002A6F
18:23:34 [Proc:Event] XCom Initialized
18:23:34 [Proc:Event] XCom File: C:Program FilesIT InnovationXCom v2.xSEBineXCom.ocx
18:23:34 [Proc:Event] XCom Version: XCom WSE SECS Driver v2.3.1 - 2013-04-16
18:23:34 [Proc:Event] Protection Type : HASP, Serial NO : SC-0002-00002A6F
18:23:34 [Proc:Event] XCom Started
18:36:13 [Proc:Event] XCom Initialized
18:36:13 [Proc:Event] XCom File: C:Program FilesIT InnovationXCom v2.xSEBineXCom.ocx
18:36:13 [Proc:Event] XCom Version: XCom WSE SECS Driver v2.3.1 - 2013-04-16
18:36:14 [Proc:Event] Protection Type : HASP, Serial NO : SC-0002-00002A6F
18:36:14 [Proc:Event] XCom Started
18:36:17 [HSMS:State] State Changed : Not Connected -> Not Selected
18:36:17 [HSMS:Rcv] Select.req, 8000000D
18:36:17 [HSMS:Send] Select.rsp, 8000000D
18:36:17 [HSMS:State] State Changed : Not Selected -> Selected
18:36:20 [HSMS:Send] Linktest.req, 0000155D
18:36:20 [HSMS:Rcv] Linktest.rsp, 0000155D

해당 현상이 나타나는 문제가 단순 물리적인 연결상태 문제로 볼수있는지 아니면 운영체제의 리소스 문제 등 과부하 문제도 있을 수 있는지 확인 부탁드립니다.
==================================================
안녕하세요

링크제니시스입니다.

문의주신 내용 답변드립니다.


소켓에러는 XCom 에러 메시지가 아니고 Windows Socket 에러 입니다.
10054 에러는 외부 요인에 의해서 연결이 끊어 졌음을 의미합니다.
소켓 에러가 발생하면 XCom 은 문제가 발생한 Connection을 종료하고Restarting 하게 됩니다.


설명
참조
http://msdn.microsoft.com/en-us/library/ms740668(VS.85).aspx
10054
Connection reset by peer.
An existing connection was forcibly closed by the remote host. This normally results if the peer application on the remote host is suddenly stopped, the host is rebooted, the host or remote network interface is disabled, or the remote host uses a hard close (see setsockopt for more information on the SO_LINGER option on the remote socket). This error may also result if a connection was broken due to keep-alive activity detecting a failure while one or more operations are in progress. Operations that were in progress fail with WSAENETRESET. Subsequent operations fail with WSAECONNRESET.


운영체제의 리소스 부족 등이 원인이라면 10055 에러가 발생하기도 합니다.
우선 네트워크 연결 상태를 확인해주세요

이상입니다.
감사합니다.


답변 목록

  답변XCom제품문의Socket is in bad state! 문의2017-10-13


  이전글XCom사용방법문의Spool 함수 사용 문의
  다음글XCom운영중문의LinkTest를 시도 하지 않는 현상