OAW
Contributor
Contributor

Vmware View 5 - all clients get disconnected sometimes

Hi all,

I got stuck with a problem causing all 2, 3 days a disconnect of all clients from a VMware view server. I collected serveral logs at the moment when the disconnect happened. I hope that someone point me to a possible cause ...

First here ist the log of the PCoIP Client (Thin Client EVGA PD-02):

08/21/2012, 08:52:14> LVL:2 RC:   0         MGMT_UI :No PCoIP data received in the past 3 seconds (connection to peer might be lost)
08/21/2012, 08:52:14> LVL:2 RC:   0 MGMT_PCOIP_DATA :****************************************************************
08/21/2012, 08:52:14> LVL:2 RC:   0 MGMT_PCOIP_DATA :Tx pkts = 144506, Tx bytes = 17006580, Rx pkts = 628977, Rx bytes = 701786842
08/21/2012, 08:52:14> LVL:2 RC:   0 MGMT_PCOIP_DATA :Tx Bandwidth (kbps): Limit = 7000, Avg = 0, Min = 0, Max = 184
08/21/2012, 08:52:14> LVL:2 RC:   0 MGMT_PCOIP_DATA :Rx Bandwidth (kbps): Avg = 40, Min = 0, Max = 7032, Loss = 0 pkts
08/21/2012, 08:52:14> LVL:2 RC:   0 MGMT_PCOIP_DATA :RTT (ms): Avg = 6, Min = 1, Max = 7
08/21/2012, 08:52:14> LVL:2 RC:   0 MGMT_PCOIP_DATA :****************************************************************
08/21/2012, 08:52:38> LVL:2 RC:   0 MGMT_PCOIP_DATA :****************************************************************
08/21/2012, 08:52:38> LVL:2 RC:   0 MGMT_PCOIP_DATA :Tx pkts = 144723, Tx bytes = 17029630, Rx pkts = 628977, Rx bytes = 701786842
08/21/2012, 08:52:38> LVL:2 RC:   0 MGMT_PCOIP_DATA :Tx Bandwidth (kbps): Limit = 7000, Avg = 0, Min = 0, Max = 184
08/21/2012, 08:52:38> LVL:2 RC:   0 MGMT_PCOIP_DATA :Rx Bandwidth (kbps): Avg = 0, Min = 0, Max = 7032, Loss = 0 pkts
08/21/2012, 08:52:38> LVL:2 RC:   0 MGMT_PCOIP_DATA :RTT (ms): Avg = 6, Min = 1, Max = 7
08/21/2012, 08:52:38> LVL:2 RC:   0 MGMT_PCOIP_DATA :****************************************************************
08/21/2012, 08:52:38> LVL:3 RC:   0       MGMT_SESS :(pcoip_data_cback): event: 0x10, PRI: 0 - queuing EVENT_PCOIP_DATA_LOST
08/21/2012, 08:52:38> LVL:3 RC:   0       MGMT_SESS :OPEN: transition 51 into TEARDOWN (PRI: 0)
08/21/2012, 08:52:38> LVL:3 RC:   0       MGMT_SSIG :tera_mgmt_ssig_reset: Queuing EVENT_RESET (PRI: 0)
08/21/2012, 08:52:38> LVL:2 RC:   0       MGMT_SSIG :Request to reset session (PRI: 0)
08/21/2012, 08:52:38> LVL:3 RC:   0       MGMT_SSIG :OPEN: transition 11 into BYE (PRI: 0)
08/21/2012, 08:52:38> LVL:2 RC:   0       MGMT_SSIG :Session closed locally (217.111.67.132, 00-0F-01-00-01-00, PRI: 0)
08/21/2012, 08:52:38> LVL:2 RC:   0       MGMT_SSIG :Sending to peer: BYE disconnect reason cause (0x403)
08/21/2012, 08:52:38> LVL:2 RC:   0       MGMT_SSIG :Session closure reason cause (device:internal: PCoIP lost)
08/21/2012, 08:52:38> LVL:3 RC:   0       MGMT_SSIG :Number of bytes in BYE APDU: 24
08/21/2012, 08:52:38> LVL:3 RC:   0       MGMT_SSIG :Sending BYE APDU to peer
08/21/2012, 08:52:38> LVL:3 RC:   0       MGMT_SESS :(hcc_cback): event: 0x8, PRI: 0 - queuing EVENT_HCC_SESS_RESET
08/21/2012, 08:52:38> LVL:3 RC:   0       MGMT_SESS :(kmp_cback): event: 0x1, PRI: 0 - queuing EVENT_KMP_RESET
08/21/2012, 08:52:38> LVL:3 RC:   0       MGMT_SESS :(vchan_cback): event: 0x1, PRI: 0 queuing EVENT_VCHAN_RESET
08/21/2012, 08:52:38> LVL:3 RC:   0       MGMT_SESS :(ddc_cback): event: 0x1, PRI: 0 - queuing EVENT_DDC_RESET
08/21/2012, 08:52:38> LVL:3 RC:   0       MGMT_SESS :TEARDOWN: transition 24 into TEARDOWN (PRI: 0)
08/21/2012, 08:52:38> LVL:3 RC:   0       MGMT_SESS :TEARDOWN: transition 30 (EVENT_KMP_RESET) into TEARDOWN (PRI: 0)
08/21/2012, 08:52:38> LVL:3 RC:   0       MGMT_SESS :TEARDOWN: transition 30 (EVENT_VCHAN_RESET) into TEARDOWN (PRI: 0)
08/21/2012, 08:52:38> LVL:3 RC:   0       MGMT_SESS :TEARDOWN: transition 30 (EVENT_DDC_RESET) into TEARDOWN (PRI: 0)
08/21/2012, 08:52:38> LVL:3 RC:   0       MGMT_SESS :(rsc_cback): event: 0x1, PRI: 0 - queuing EVENT_RSC_RESET
08/21/2012, 08:52:38> LVL:3 RC:   0       MGMT_SESS :TEARDOWN: transition 30 (EVENT_RSC_RESET) into TEARDOWN (PRI: 0)
08/21/2012, 08:52:38> LVL:3 RC:   0       MGMT_SESS :(osvchan_cback): event: 0x1, PRI: 0 - queuing TERA_MGMT_OSVCHAN_EVENT_RESET
08/21/2012, 08:52:38> LVL:3 RC:   0       MGMT_SESS :TEARDOWN: transition 30 (EVENT_OSVCHAN_RESET) into TEARDOWN (PRI: 0)

Second we have the debug-log of the sercuriry view:

2012-09-03 19:00:00,823 WARN  <AJP-3> [j] (Request21895) AJP connection test failed: com.vmware.vdi.ob.tunnelservice.dy: Failed to write data to server: java.net.SocketException: Software caused connection abort: socket write error
2012-09-03 19:00:09,528 DEBUG <MsgWorker#6> [a] (-) RequestGetStatus: serverType = ice, server = null, localHostname = VIEW-02
2012-09-03 19:00:09,528 DEBUG <MsgWorker#6> [av] (-) Queuing request PSGC27-28000
2012-09-03 19:00:09,528 DEBUG <PSGC27> [av] Handling request PSGC27-28000, on queue for 23uS
2012-09-03 19:00:09,528 DEBUG <PSGC27> [av] Sending GETCOUNTERS request PSGC27-28000
2012-09-03 19:00:09,528 DEBUG <PSGC27:L> [dz] Good response received for GETCOUNTERS request PSGC27-28000 in 527uS (parsed in 226uS)
2012-09-03 19:00:09,528 DEBUG <PSGC27:L> [av] Queuing receipt 170126
2012-09-03 19:00:09,528 DEBUG <PSGC27:C> [af] Handling message 170126, on queue for 49uS
2012-09-03 19:00:09,528 DEBUG <Outbound JMS Worker Thread> [au] Sending JMS message: CurrentStatus
2012-09-03 19:00:28,248 DEBUG <HandshakeCompletedNotify-Thread> [PooledProcessor] Using secure protocol TLSv1 and cipher suite SSL_RSA_WITH_RC4_128_SHA
2012-09-03 19:00:28,248 DEBUG <Thread-28> [SimpleAJPService] (Request21896) SimpleAJPService request: /broker/xml
2012-09-03 19:00:28,248 WARN  <AJP-11> [j] (Request21896) AJP connection test failed: com.vmware.vdi.ob.tunnelservice.dy: Failed to write data to server: java.net.SocketException: Software caused connection abort: socket write error
2012-09-03 19:00:28,919 DEBUG <HandshakeCompletedNotify-Thread> [PooledProcessor] Using secure protocol TLSv1 and cipher suite SSL_RSA_WITH_RC4_128_SHA
2012-09-03 19:00:28,919 DEBUG <Thread-25> [SimpleAJPService] (Request21897) SimpleAJPService request: /broker/xml
2012-09-03 19:00:28,919 WARN  <AJP-13> [j] (Request21897) AJP connection test failed: com.vmware.vdi.ob.tunnelservice.dy: Failed to write data to server: java.net.SocketException: Software caused connection abort: socket write error
2012-09-03 19:00:29,340 DEBUG <MsgWorker#7> [a] (701EA6E6DAF6D7A27E80844442E0089A) doCapStatus: capID = 701EA6E6DAF6D7A27E80844442E0089A, locationID = 00-1F-BC-0C-8D-7E, userDN = cn=s-1-5-21-2409728431-2754453975-3715340775-1165,cn=foreignsecurityprincipals,dc=vdi,dc=vmware,dc=int, clientVersion = 4.0, lite = true, newAllowed = true
2012-09-03 19:00:29,340 DEBUG <MsgWorker#7> [a] (701EA6E6DAF6D7A27E80844442E0089A) Found 2 existing connected sessions for: cn=s-1-5-21-2409728431-2754453975-3715340775-1165,cn=foreignsecurityprincipals,dc=vdi,dc=vmware,dc=int
2012-09-03 19:00:29,340 DEBUG <MsgWorker#7> [a] (701EA6E6DAF6D7A27E80844442E0089A) This session is unknown
2012-09-03 19:00:29,340 DEBUG <MsgWorker#7> [aj] (701EA6E6DAF6D7A27E80844442E0089A) makeLiteSession: capID = 701EA6E6DAF6D7A27E80844442E0089A, userID = kueche, userDN = cn=s-1-5-21-2409728431-2754453975-3715340775-1165,cn=foreignsecurityprincipals,dc=vdi,dc=vmware,dc=int, locationID = 00-1F-BC-0C-8D-7E, sh = com.vmware.vdi.ice.server.ac@6ec5122f
2012-09-03 19:00:29,340 DEBUG <MsgWorker#7> [aj] (701EA6E6DAF6D7A27E80844442E0089A) getLiteInstance: creating a new session for: capID = 701EA6E6DAF6D7A27E80844442E0089A
2012-09-03 19:00:29,340 DEBUG <MsgWorker#7> [aj] (701EA6E6DAF6D7A27E80844442E0089A) Created new LITE session for: capID = 701EA6E6DAF6D7A27E80844442E0089A, userDN = cn=s-1-5-21-2409728431-2754453975-3715340775-1165,cn=foreignsecurityprincipals,dc=vdi,dc=vmware,dc=int, locationID = 00-1F-BC-0C-8D-7E
2012-09-03 19:00:29,340 DEBUG <MsgWorker#7> [aj] (701EA6E6DAF6D7A27E80844442E0089A EC1B4232885B5E62E51360F6B98ECE2C) Extending timeout for session
2012-09-03 19:00:29,340 DEBUG <MsgWorker#7> [aj] (701EA6E6DAF6D7A27E80844442E0089A EC1B4232885B5E62E51360F6B98ECE2C) Session will time out after: 172799s, at Wed Sep 05 19:00:28 CEST 2012
2012-09-03 19:00:29,340 DEBUG <Outbound JMS Worker Thread> [au] Sending JMS message: CapPresent
2012-09-03 19:00:29,340 DEBUG <Outbound JMS Worker Thread> [au] Sending JMS message: CapPresent
2012-09-03 19:00:29,340 DEBUG <Outbound JMS Worker Thread> [au] Sending JMS message: CapAbsent
2012-09-03 19:00:29,433 DEBUG <HandshakeCompletedNotify-Thread> [PooledProcessor] Using secure protocol TLSv1 and cipher suite SSL_RSA_WITH_RC4_128_SHA
2012-09-03 19:00:29,433 DEBUG <Thread-24> [SimpleAJPService] (Request21898) SimpleAJPService request: /broker/xml
2012-09-03 19:00:29,433 WARN  <AJP-98> [j] (Request21898) AJP connection test failed: com.vmware.vdi.ob.tunnelservice.dy: Failed to write data to server: java.net.SocketException: Software caused connection abort: socket write error
2012-09-03 19:00:33,099 DEBUG <HandshakeCompletedNotify-Thread> [PooledProcessor] Using secure protocol TLSv1 and cipher suite SSL_RSA_WITH_RC4_128_SHA
2012-09-03 19:00:33,131 DEBUG <Thread-22> [SimpleAJPService] (Request21899) SimpleAJPService request: /broker/xml
2012-09-03 19:00:33,131 WARN  <AJP-97> [j] (Request21899) AJP connection test failed: com.vmware.vdi.ob.tunnelservice.dy: Failed to write data to server: java.net.SocketException: Software caused connection abort: socket write error
2012-09-03 19:00:34,847 DEBUG <MsgWorker#8> [a] (EC1B4232885B5E62E51360F6B98ECE2C) Raising channel directly
2012-09-03 19:00:34,847 DEBUG <MsgWorker#8> [aj] (EC1B4232885B5E62E51360F6B98ECE2C) Raising port *:-1 for 172.16.17.105:4172(1) keepalives called Port150
2012-09-03 19:00:34,847 DEBUG <MsgWorker#8> [av] (EC1B4232885B5E62E51360F6B98ECE2C) Queuing request EC1B4232885B5E62E51360F6B98ECE2C-97
2012-09-03 19:00:34,847 DEBUG <PSGC27> [av] Handling request EC1B4232885B5E62E51360F6B98ECE2C-97, on queue for 25uS
2012-09-03 19:00:34,847 DEBUG <PSGC27> [av] Sending ADDCONNECTION request EC1B4232885B5E62E51360F6B98ECE2C-97
2012-09-03 19:00:34,847 DEBUG <PSGC27:L> [dz] Good response received for ADDCONNECTION request EC1B4232885B5E62E51360F6B98ECE2C-97 in 822uS (parsed in 222uS)
2012-09-03 19:00:34,862 DEBUG <PSGC27:L> [av] Queuing receipt 170127
2012-09-03 19:00:34,862 DEBUG <PSGC27:C> [af] Handling message 170127, on queue for 29uS
2012-09-03 19:00:34,862 DEBUG <PSGC27:C> [aj] Lite session already connected! session = (ServerSession capID = EC1B4232885B5E62E51360F6B98ECE2C, type = LITE, userID = Kueche, userDN = cn=s-1-5-21-2409728431-2754453975-3715340775-1165,cn=foreignsecurityprincipals,dc=vdi,dc=vmware,dc=int, locationID = 00-1F-BC-0C-8D-7E)
2012-09-03 19:00:34,862 DEBUG <PSGC27:C> [aj] Lite session = (ServerSession capID = EC1B4232885B5E62E51360F6B98ECE2C, type = LITE, userID = Kueche, userDN = cn=s-1-5-21-2409728431-2754453975-3715340775-1165,cn=foreignsecurityprincipals,dc=vdi,dc=vmware,dc=int, locationID = 00-1F-BC-0C-8D-7E), connected = Mon Sep 03 19:00:34 CEST 2012
2012-09-03 19:00:34,862 DEBUG <Outbound JMS Worker Thread> [au] Sending JMS message: RaisePort
2012-09-03 19:00:35,112 DEBUG <HandshakeCompletedNotify-Thread> [PooledProcessor] Using secure protocol TLSv1 and cipher suite SSL_RSA_WITH_RC4_128_SHA
2012-09-03 19:00:35,127 DEBUG <Thread-23> [SimpleAJPService] (Request21900) SimpleAJPService request: /broker/xml
2012-09-03 19:00:35,127 WARN  <AJP-1> [j] (Request21900) AJP connection test failed: com.vmware.vdi.ob.tunnelservice.dy: Failed to write data to server: java.net.SocketException: Software caused connection abort: socket write error
2012-09-03 19:00:35,127 DEBUG <Thread-21> [SimpleAJPService] (Request21901) SimpleAJPService request: /broker/xml
2012-09-03 19:00:35,127 DEBUG <Thread-20> [SimpleAJPService] (Request21902) SimpleAJPService request: /broker/xml
2012-09-03 19:00:35,127 DEBUG <HandshakeCompletedNotify-Thread> [PooledProcessor] Using secure protocol TLSv1 and cipher suite TLS_RSA_WITH_AES_128_CBC_SHA
2012-09-03 19:00:35,127 DEBUG <HandshakeCompletedNotify-Thread> [PooledProcessor] Using secure protocol TLSv1 and cipher suite TLS_RSA_WITH_AES_128_CBC_SHA
2012-09-03 19:00:35,127 DEBUG <HandshakeCompletedNotify-Thread> [PooledProcessor] Using secure protocol TLSv1 and cipher suite TLS_RSA_WITH_AES_128_CBC_SHA
2012-09-03 19:00:35,127 DEBUG <Thread-19> [SimpleAJPService] (Request21903) SimpleAJPService request: /broker/xml
2012-09-03 19:00:38,560 DEBUG <HandshakeCompletedNotify-Thread> [PooledProcessor] Using secure protocol TLSv1 and cipher suite TLS_RSA_WITH_AES_128_CBC_SHA
2012-09-03 19:00:38,560 DEBUG <Thread-17> [SimpleAJPService] (Request21904) SimpleAJPService request: /broker/xml
2012-09-03 19:00:38,670 DEBUG <HandshakeCompletedNotify-Thread> [PooledProcessor] Using secure protocol TLSv1 and cipher suite TLS_RSA_WITH_AES_128_CBC_SHA
2012-09-03 19:00:38,719 DEBUG <Thread-18> [SimpleAJPService] (Request21905) SimpleAJPService request: /broker/xml
2012-09-03 19:00:43,590 DEBUG <HandshakeCompletedNotify-Thread> [PooledProcessor] Using secure protocol TLSv1 and cipher suite TLS_RSA_WITH_AES_128_CBC_SHA
2012-09-03 19:00:43,622 DEBUG <Thread-35> [SimpleAJPService] (Request21906) SimpleAJPService request: /broker/xml
2012-09-03 19:00:44,263 DEBUG <HandshakeCompletedNotify-Thread> [PooledProcessor] Using secure protocol TLSv1 and cipher suite TLS_RSA_WITH_AES_128_CBC_SHA
2012-09-03 19:00:44,263 DEBUG <Thread-36> [SimpleAJPService] (Request21907) SimpleAJPService request: /broker/xml
2012-09-03 19:00:44,310 DEBUG <HandshakeCompletedNotify-Thread> [PooledProcessor] Using secure protocol TLSv1 and cipher suite TLS_RSA_WITH_AES_128_CBC_SHA
2012-09-03 19:00:44,326 DEBUG <Thread-34> [SimpleAJPService] (Request21908) SimpleAJPService request: /broker/xml
2012-09-03 19:00:44,920 DEBUG <MsgWorker#0> [a] (204DBAD914581D72E33F3386FC97CE7C) doCapStatus: capID = 204DBAD914581D72E33F3386FC97CE7C, locationID = 00-1F-BC-0C-8D-0F, userDN = cn=s-1-5-21-2409728431-2754453975-3715340775-1131,cn=foreignsecurityprincipals,dc=vdi,dc=vmware,dc=int, clientVersion = 4.0, lite = true, newAllowed = true
2012-09-03 19:00:44,920 DEBUG <MsgWorker#0> [a] (204DBAD914581D72E33F3386FC97CE7C) Found 4 existing connected sessions for: cn=s-1-5-21-2409728431-2754453975-3715340775-1131,cn=foreignsecurityprincipals,dc=vdi,dc=vmware,dc=int
2012-09-03 19:00:44,920 DEBUG <MsgWorker#0> [a] (204DBAD914581D72E33F3386FC97CE7C) This session is unknown
2012-09-03 19:00:44,920 DEBUG <MsgWorker#0> [aj] (204DBAD914581D72E33F3386FC97CE7C) makeLiteSession: capID = 204DBAD914581D72E33F3386FC97CE7C, userID = desk.1, userDN = cn=s-1-5-21-2409728431-2754453975-3715340775-1131,cn=foreignsecurityprincipals,dc=vdi,dc=vmware,dc=int, locationID = 00-1F-BC-0C-8D-0F, sh = com.vmware.vdi.ice.server.ac@6ec5122f
2012-09-03 19:00:44,920 DEBUG <MsgWorker#0> [aj] (204DBAD914581D72E33F3386FC97CE7C) getLiteInstance: creating a new session for: capID = 204DBAD914581D72E33F3386FC97CE7C
2012-09-03 19:00:44,920 DEBUG <MsgWorker#0> [aj] (204DBAD914581D72E33F3386FC97CE7C) Created new LITE session for: capID = 204DBAD914581D72E33F3386FC97CE7C, userDN = cn=s-1-5-21-2409728431-2754453975-3715340775-1131,cn=foreignsecurityprincipals,dc=vdi,dc=vmware,dc=int, locationID = 00-1F-BC-0C-8D-0F
2012-09-03 19:00:44,920 DEBUG <MsgWorker#0> [aj] (204DBAD914581D72E33F3386FC97CE7C 57CACB027181C41E7A5D2FD88F59C804) Extending timeout for session
2012-09-03 19:00:44,920 DEBUG <MsgWorker#0> [aj] (204DBAD914581D72E33F3386FC97CE7C 57CACB027181C41E7A5D2FD88F59C804) Cancelling old kill timer
2012-09-03 19:00:44,920 DEBUG <MsgWorker#0> [aj] (204DBAD914581D72E33F3386FC97CE7C 57CACB027181C41E7A5D2FD88F59C804) Session will time out after: 172800s, at Wed Sep 05 19:00:44 CEST 2012
2012-09-03 19:00:44,920 DEBUG <Outbound JMS Worker Thread> [au] Sending JMS message: CapPresent
2012-09-03 19:00:44,920 DEBUG <Outbound JMS Worker Thread> [au] Sending JMS message: CapPresent
2012-09-03 19:00:44,920 DEBUG <Outbound JMS Worker Thread> [au] Sending JMS message: CapPresent
2012-09-03 19:00:44,920 DEBUG <Outbound JMS Worker Thread> [au] Sending JMS message: CapPresent
2012-09-03 19:00:44,920 DEBUG <Outbound JMS Worker Thread> [au] Sending JMS message: CapAbsent
2012-09-03 19:00:44,920 DEBUG <HandshakeCompletedNotify-Thread> [PooledProcessor] Using secure protocol TLSv1 and cipher suite TLS_RSA_WITH_AES_128_CBC_SHA
2012-09-03 19:00:44,920 DEBUG <Thread-33> [SimpleAJPService] (Request21909) SimpleAJPService request: /broker/xml
2012-09-03 19:00:44,953 DEBUG <HandshakeCompletedNotify-Thread> [PooledProcessor] Using secure protocol TLSv1 and cipher suite TLS_RSA_WITH_AES_128_CBC_SHA
2012-09-03 19:00:44,953 DEBUG <Thread-32> [SimpleAJPService] (Request21910) SimpleAJPService request: /broker/xml
2012-09-03 19:00:45,530 DEBUG <MsgWorker#9> [a] (3538BC91807774E74549DA6D7C698007) doCapStatus: capID = 3538BC91807774E74549DA6D7C698007, locationID = 00-1F-BC-0C-8D-33, userDN = cn=s-1-5-21-2409728431-2754453975-3715340775-1132,cn=foreignsecurityprincipals,dc=vdi,dc=vmware,dc=int, clientVersion = 4.0, lite = true, newAllowed = true
2012-09-03 19:00:45,530 DEBUG <MsgWorker#9> [a] (3538BC91807774E74549DA6D7C698007) Found 3 existing connected sessions for: cn=s-1-5-21-2409728431-2754453975-3715340775-1132,cn=foreignsecurityprincipals,dc=vdi,dc=vmware,dc=int
2012-09-03 19:00:45,530 DEBUG <MsgWorker#9> [a] (3538BC91807774E74549DA6D7C698007) This session is unknown
2012-09-03 19:00:45,530 DEBUG <MsgWorker#9> [aj] (3538BC91807774E74549DA6D7C698007) makeLiteSession: capID = 3538BC91807774E74549DA6D7C698007, userID = desk.2, userDN = cn=s-1-5-21-2409728431-2754453975-3715340775-1132,cn=foreignsecurityprincipals,dc=vdi,dc=vmware,dc=int, locationID = 00-1F-BC-0C-8D-33, sh = com.vmware.vdi.ice.server.ac@6ec5122f
2012-09-03 19:00:45,530 DEBUG <MsgWorker#9> [aj] (3538BC91807774E74549DA6D7C698007) getLiteInstance: creating a new session for: capID = 3538BC91807774E74549DA6D7C698007
2012-09-03 19:00:45,530 DEBUG <MsgWorker#9> [aj] (3538BC91807774E74549DA6D7C698007) Created new LITE session for: capID = 3538BC91807774E74549DA6D7C698007, userDN = cn=s-1-5-21-2409728431-2754453975-3715340775-1132,cn=foreignsecurityprincipals,dc=vdi,dc=vmware,dc=int, locationID = 00-1F-BC-0C-8D-33
2012-09-03 19:00:45,530 DEBUG <MsgWorker#9> [aj] (3538BC91807774E74549DA6D7C698007 1081B8EC28E1AEA1A6FDF0D003BEB769) Extending timeout for session
2012-09-03 19:00:45,530 DEBUG <MsgWorker#9> [aj] (3538BC91807774E74549DA6D7C698007 1081B8EC28E1AEA1A6FDF0D003BEB769) Cancelling old kill timer
2012-09-03 19:00:45,530 DEBUG <MsgWorker#9> [aj] (3538BC91807774E74549DA6D7C698007 1081B8EC28E1AEA1A6FDF0D003BEB769) Session will time out after: 172799s, at Wed Sep 05 19:00:44 CEST 2012
2012-09-03 19:00:45,530 DEBUG <Outbound JMS Worker Thread> [au] Sending JMS message: CapPresent
2012-09-03 19:00:45,530 DEBUG <Outbound JMS Worker Thread> [au] Sending JMS message: CapPresent
2012-09-03 19:00:45,530 DEBUG <Outbound JMS Worker Thread> [au] Sending JMS message: CapPresent
2012-09-03 19:00:45,530 DEBUG <Outbound JMS Worker Thread> [au] Sending JMS message: CapAbsent
2012-09-03 19:00:45,561 DEBUG <HandshakeCompletedNotify-Thread> [PooledProcessor] Using secure protocol TLSv1 and cipher suite TLS_RSA_WITH_AES_128_CBC_SHA
2012-09-03 19:00:45,561 DEBUG <Thread-31> [SimpleAJPService] (Request21911) SimpleAJPService request: /broker/xml
2012-09-03 19:00:47,844 DEBUG <HandshakeCompletedNotify-Thread> [PooledProcessor] Using secure protocol TLSv1 and cipher suite TLS_RSA_WITH_AES_128_CBC_SHA
2012-09-03 19:00:47,844 DEBUG <Thread-30> [SimpleAJPService] (Request21912) SimpleAJPService request: /broker/xml
2012-09-03 19:00:48,983 DEBUG <HandshakeCompletedNotify-Thread> [PooledProcessor] Using secure protocol TLSv1 and cipher suite TLS_RSA_WITH_AES_128_CBC_SHA
2012-09-03 19:00:49,019 DEBUG <Thread-29> [SimpleAJPService] (Request21913) SimpleAJPService request: /broker/xml
2012-09-03 19:00:49,693 DEBUG <MsgWorker#2> [a] (57CACB027181C41E7A5D2FD88F59C804) Raising channel directly
2012-09-03 19:00:49,693 DEBUG <MsgWorker#2> [aj] (57CACB027181C41E7A5D2FD88F59C804) Raising port *:-1 for 172.16.17.110:4172(1) keepalives called Port234
2012-09-03 19:00:49,693 DEBUG <MsgWorker#2> [av] (57CACB027181C41E7A5D2FD88F59C804) Queuing request 57CACB027181C41E7A5D2FD88F59C804-f0
2012-09-03 19:00:49,693 DEBUG <PSGC27> [av] Handling request 57CACB027181C41E7A5D2FD88F59C804-f0, on queue for 27uS
2012-09-03 19:00:49,693 DEBUG <PSGC27> [av] Sending ADDCONNECTION request 57CACB027181C41E7A5D2FD88F59C804-f0
2012-09-03 19:00:49,693 DEBUG <PSGC27:L> [dz] Good response received for ADDCONNECTION request 57CACB027181C41E7A5D2FD88F59C804-f0 in 753uS (parsed in 241uS)
2012-09-03 19:00:49,693 DEBUG <PSGC27:L> [av] Queuing receipt 170128

And last the log of the PCoIT Secure Gateway:

[2012-Sep-03 17:09:38.050023]: xml received 93 93
[2012-Sep-03 17:09:38.050023]: Received command: get-counters
[2012-Sep-03 17:10:43.055337]: header received
[2012-Sep-03 17:10:43.055337]: PCOIP-SG/1.0
[2012-Sep-03 17:10:43.055337]: XML
[2012-Sep-03 17:10:43.055337]: PSGC27-27f9b
[2012-Sep-03 17:10:43.055337]: 93
[2012-Sep-03 17:10:43.055337]: xml received 93 93
[2012-Sep-03 17:10:43.055337]: Received command: get-counters
[2012-Sep-03 17:11:42.023441]: SSIG client connection error while reading SSIG APDU header: Das Zeitlimit für die Semaphore wurde erreicht
[2012-Sep-03 17:11:45.143446]: SSIG client connection error while reading SSIG APDU header: Das Zeitlimit für die Semaphore wurde erreicht
[2012-Sep-03 17:11:48.060651]: header received
[2012-Sep-03 17:11:48.060651]: PCOIP-SG/1.0
[2012-Sep-03 17:11:48.060651]: XML
[2012-Sep-03 17:11:48.060651]: PSGC27-27f9c
[2012-Sep-03 17:11:48.060651]: 93
[2012-Sep-03 17:11:48.060651]: xml received 93 93
[2012-Sep-03 17:11:48.060651]: Received command: get-counters
[2012-Sep-03 17:11:50.681456]: SSIG client connection error while reading SSIG APDU header: Das Zeitlimit für die Semaphore wurde erreicht
[2012-Sep-03 17:11:52.225859]: SSIG client connection error while reading SSIG APDU header: Das Zeitlimit für die Semaphore wurde erreicht
[2012-Sep-03 17:11:52.569059]: SSIG client connection error while reading SSIG APDU header: Das Zeitlimit für die Semaphore wurde erreicht
[2012-Sep-03 17:11:53.910662]: SSIG client connection error while reading SSIG APDU header: Das Zeitlimit für die Semaphore wurde erreicht
[2012-Sep-03 17:11:57.015468]: SSIG client SSL write error Eine vorhandene Verbindung wurde vom Remotehost geschlossen
[2012-Sep-03 17:11:57.237269]: SSIG client connection error while reading SSIG APDU header: Das Zeitlimit für die Semaphore wurde erreicht
[2012-Sep-03 17:11:57.268470]: SSIG client SSL write error Eine vorhandene Verbindung wurde vom Remotehost geschlossen
[2012-Sep-03 17:11:58.124872]: SSIG client SSL write error Eine vorhandene Verbindung wurde vom Remotehost geschlossen
[2012-Sep-03 17:11:59.144275]: SSIG client SSL write error Eine vorhandene Verbindung wurde vom Remotehost geschlossen
[2012-Sep-03 17:11:59.300275]: SSIG client SSL write error Eine vorhandene Verbindung wurde vom Remotehost geschlossen
[2012-Sep-03 17:11:59.399876]: SSIG client SSL write error Eine vorhandene Verbindung wurde vom Remotehost geschlossen
[2012-Sep-03 17:12:11.024500]: header received
[2012-Sep-03 17:12:11.024500]: PCOIP-SG/1.0
[2012-Sep-03 17:12:11.024500]: XML
[2012-Sep-03 17:12:11.024500]: CCC750558B0B306E381E313A9FD1C4AA-7f
[2012-Sep-03 17:12:11.024500]: 360
[2012-Sep-03 17:12:11.024500]: xml received 360 360
[2012-Sep-03 17:12:11.024500]: Received command: add-connection
[2012-Sep-03 17:12:11.024500]: Parameter: connection-id Value: CCC750558B0B306E381E313A9FD1C4AA/port128
[2012-Sep-03 17:12:11.024500]: Parameter: ctag Value: SCS1t/poUSrv1RBZUxr1Rrtw9Zeo7qrqBMW6mL2G1I9Tl5V2PXWZUs5jUUj5S0592ZezMTkDhzkEdAVyr2SJOOUULTCronmBLwgn6GoH
[2012-Sep-03 17:12:11.024500]: Parameter: ip-address Value: 172.16.17.102
[2012-Sep-03 17:12:11.024500]: Parameter: tcp-port Value: 4172
[2012-Sep-03 17:12:11.024500]: Connected to PCoIP server
[2012-Sep-03 17:12:13.333304]: header received
[2012-Sep-03 17:12:13.333304]: PCOIP-SG/1.0
[2012-Sep-03 17:12:13.333304]: XML

Can someone lighten my darkness? Thanks in advance,

Tom

0 Kudos
7 Replies
mittim12
Immortal
Immortal

Welcome to the forums.   Do all the clients disconnect at the same time?   Are all of these clients using a PCOIP Gateway or do the clients connect directly to the desktop? 

0 Kudos
OAW
Contributor
Contributor

Hi mittim12,

yes, all clients disconnect at the same time. Clients are using a PCoIP Gateway.

Tom

0 Kudos
mittim12
Immortal
Immortal

Are they all external users?  

What are the resources assigned to the connection brokers?

When the disconnects happen does the connection broker appear to still be online, actively pinging?

0 Kudos
OAW
Contributor
Contributor

Hm, what do yopu mean with internal or external users? All users connect to a external IP with a dns name view.domain.de.

All clients uses a PCoIP thin client and Windows7 VMware guest OS.

Yes, the network connection between the PCoIP, the guest OS ans the view-02 server is still alive, ping shows no interupt. The session is closed and about 5 or 10 seconds later all users can reconnect and are able to work again from the point when they got disconnected. No data loss.

0 Kudos
mittim12
Immortal
Immortal

Typically users who are internal and on the LAN will not use a security server or a tunneled connection.   You typically only see that when people are outside the network and need to connect in. 

0 Kudos
jtfernan
Contributor
Contributor

AOW,

Did you figure out why the connections are getting disconnected?

0 Kudos
brickleberry
Enthusiast
Enthusiast

i have 30 ZC users that have this issue.

starting at 4:15 to 4:30 they get booted.

both internal and external networks.

i would be happy to supply more data if there is a response to this.

0 Kudos