VMware Horizon Community
fabio1975
Commander
Commander

Horizon view 7.5 - Blast Extreme Protocol - Thin Client

Hi guy,

I will want to dismiss my infrastructure Horizon View with PCOIP and thin client teradici.

I am starting with a new infrastructure with thin client  WYSE 3040, Horizon View 7.5 and i will use the Blast extreme protocol and an one Virtual Machine (Windows 7)  The VM used have the same confgiuration of old infrastructure (PCOIP) the big different is i have updated horizon agent on VM.

I am starting with a pilot  but i have little problem, when i start session from the thin client to the VM  the  same sassion hang after 30 minutes of use and the thin client display black screen.

Only solution is poweroff and powern on the thin client. But after  again 30 minutes the same situation reappears.

I have checked the blast log on the VM:

On the blast-service.log i found

2018-06-26 15:31:15.502+0200 [WARN ] 0x0628 WebSocket::WebSocket::OnRead: Websocket 0000000003BFC5C0: SSL short read seen, bytesRead=0

2018-06-26 15:31:15.502+0200 [WARN ] 0x063c WebSocket::WebSocket::OnRead: Websocket 0000000003BFC5C0: SSL short read seen, bytesRead=0

2018-06-26 15:31:15.502+0200 [WARN ] 0x0628 WebSocket::WebSocket::OnRead: Websocket 0000000003BFC5C0: SSL short read seen, bytesRead=0

2018-06-26 15:31:15.502+0200 [WARN ] 0x063c WebSocket::WebSocket::OnRead: Websocket 0000000003BFC5C0: SSL short read seen, bytesRead=0

2018-06-26 15:31:15.502+0200 [WARN ] 0x0628 WebSocket::WebSocket::OnRead: Websocket 0000000003BFC5C0: SSL short read seen, bytesRead=0

2018-06-26 15:31:15.502+0200 [INFO ] 0x0628 WebSocket::WebSocket::OnRead: Websocket 000000000101ED10: No more data left to read, closing

2018-06-26 15:31:15.502+0200 [DEBUG] 0x0628 WebSocket::WebSocket::FinishClose: WebSocket 0000000003BFC5C0: callReadCb:True.

2018-06-26 15:31:15.502+0200 [WARN ] 0x0628 WebSocket::WebSocket::NotifyReadDataReady: WebSocket 0000000003BFC5C0: Error reading, code: 335544539 [asio.ssl: short read].

2018-06-26 15:31:15.502+0200 [DEBUG] 0x0628 connectionctrl::OnConnectionError: Wait to acquire lock for ConnCtrl 0000000000FEAC90

2018-06-26 15:31:15.502+0200 [INFO ] 0x0628 WorkerSessionMgr::PurgeSession: Purging worker process with vAuth:y8E08W*****.

2018-06-26 15:31:15.502+0200 [INFO ] 0x0628 WorkerSessionMgr::PurgeSession: Keeping worker process in the map for vAuth:y8E08W*****.

2018-06-26 15:31:15.502+0200 [INFO ] 0x0628 connectionctrl::OnConnectionError: Closing ConnCtrl 0000000000FEAC90, Loopback and ClientFacing websockets

2018-06-26 15:31:15.502+0200 [INFO ] 0x0628 connectionctrl::CloseClientFacingWebSocket: Close and reset Client facing websocket 0000000003BFC5C0

2018-06-26 15:31:15.503+0200 [DEBUG] 0x0628 WebSocket::WebSocket::Close: WebSocket 0000000003BFC5C0

2018-06-26 15:31:15.503+0200 [INFO ] 0x0628 WebSocket::WebSocket::Close: WebSocket 0000000003BFC5C0 is already closing, nothing to do.

2018-06-26 15:31:15.503+0200 [INFO ] 0x0628 connectionctrl::CloseClientFacingWebSocket: Client facing websocket closed and reset

2018-06-26 15:31:15.503+0200 [INFO ] 0x0628 connectionctrl::CloseLoopbackWebSocket: Close and reset loopback websocket 0000000000FCC660

2018-06-26 15:31:15.503+0200 [INFO ] 0x0628 AsyncWebsocket::AsyncWebSocket::Close: AsyncWebSocket 0000000000FCC660 is closing.

2018-06-26 15:31:15.503+0200 [INFO ] 0x0628 AsyncWebsocket::AsyncWebSocket::Close: About to call asyncsocket close asock: 00000000010120A0

2018-06-26 15:31:15.503+0200 [INFO ] 0x0628 bora::Log: SOCKET 21 (712) Sending websocket close frame, status code = 1000

2018-06-26 15:31:15.503+0200 [INFO ] 0x0628 AsyncWebsocket::AsyncWebSocket::Close: Asyncsocket_Close done asock: 00000000010120A0

2018-06-26 15:31:15.503+0200 [INFO ] 0x0628 connectionctrl::CloseLoopbackWebSocket: Loopback websocket closed and reset

2018-06-26 15:31:15.503+0200 [DEBUG] 0x05ec AsyncWebsocket::AsyncWebSocket::FinishClose: Resetting/releasing connection ctrl 0000000000FEAC90

2018-06-26 15:31:15.503+0200 [INFO ] 0x0628 connectionctrl::OnConnectionError: Closed ConnCtrl 0000000000FEAC90 Loopback and ClientFacing websockets

2018-06-26 15:31:15.503+0200 [DEBUG] 0x05ec AsyncWebsocket::AsyncWebSocket::FinishClose: AsyncWebSocket 0000000000FCC660: Resetting/releasing redirect 0000000003BFC5C0

2018-06-26 15:31:15.503+0200 [INFO ] 0x0628 WebSocket::WebSocket::HandleConnectionError: WebSocket 0000000003BFC5C0: OnConnectionError() succeeded.

2018-06-26 15:31:15.503+0200 [INFO ] 0x05ec AsyncWebsocket::AsyncWebSocket::FinishClose: AsyncWebSocket 0000000000FCC660: Closed.

2018-06-26 15:31:15.503+0200 [DEBUG] 0x0628 WebSocket::WebSocket::FinishClose: Resetting/releasing connection ctrl 0000000000FEAC90

2018-06-26 15:31:15.504+0200 [DEBUG] 0x0628 connectionctrl::~ConnectionCtrl: ConnCtrl 0000000000FEAC90 destructor called.

2018-06-26 15:31:15.504+0200 [DEBUG] 0x0628 WebSocket::WebSocket::FinishClose: WebSocket 0000000003BFC5C0: Resetting/releasing redirect 0000000000FCC660

2018-06-26 15:31:15.504+0200 [DEBUG] 0x0628 AsyncWebsocket::AsyncWebSocket::~AsyncWebSocket: AsyncWebSocket 0000000000FCC660.

2018-06-26 15:31:15.504+0200 [INFO ] 0x0628 AsyncWebsocket::AsyncWebSocket::~AsyncWebSocket: AsyncWebSocket 0000000000FCC660: Destroyed.

2018-06-26 15:31:15.504+0200 [INFO ] 0x0628 WebSocket::WebSocket::FinishClose: WebSocket 0000000003BFC5C0: Closed.

2018-06-26 15:31:15.504+0200 [DEBUG] 0x0628 WebSocket::WebSocket::~WebSocket: WebSocket 0000000003BFC5C0.

2018-06-26 15:31:15.504+0200 [INFO ] 0x0628 WebSocket::WebSocket::~WebSocket: WebSocket 0000000003BFC5C0: Socket shutdown completed. Starting connection close.

2018-06-26 15:31:15.504+0200 [INFO ] 0x0628 http2::Connection::Close: Connection 0000000001003F10 (#2)

2018-06-26 15:31:15.504+0200 [INFO ] 0x0628 WebSocket::WebSocket::~WebSocket: WebSocket 0000000003BFC5C0: Destroyed.

2018-06-26 15:31:15.504+0200 [DEBUG] 0x0628 http2::Connection::~Connection: Connection 0000000001003F10 (#2): Destroying...

2018-06-26 15:31:15.504+0200 [INFO ] 0x0628 http2::Connection::~Connection: Connection 0000000001003F10 (#1) destroyed.

I have tried to use the same horizon view 7.5 with the same VM but with pcoip protocol but i not found the same issue.

Any idea?

Thank You

Fabio

Fabio

Visit vmvirtual.blog
If you're satisfied give me a kudos

Reply
0 Kudos
3 Replies
markadams123
Contributor
Contributor

Hi!

PCoIP is the ideal protocol for display back of virtual desktops because it enables complete compression of these desktops. I don’t think there are any other protocols that can offer you this level of experience. If we talk about Blast Extreme, it is built on a single H.264 codec for compressing an entire display. On the other hand, PCoIP supports multiple codecs which you can apply to the display when the situation calls for it. So, it is ideal for multi-monitor lossless support and it even comes with configurable bandwidth options. 

 

That said, I would advise you to continue with your current setup of Horizon View with PCoIP and Teradici Thin Client if it supports your new infrastructure plan. Who knows, it might be able to resolve your current issue with the Blast-Service.log file.

If the problem persists, I would suggest contacting your vendor so that they can come up with the best solution for this. I also recommend doing some research on other thin client options in the market, such as ClearCube and HP. 

Feel free to share your thoughts with me!

Reply
0 Kudos
techguy129
Expert
Expert

Blast Extreme experience hasn't been the best with ThinOS. I still recommend using PCoIP.

Confirm you have the latest firmware installed on your thin client. For Blast, make sure you install RTME and horizon package installed and at the correct version for the firmware.

Latest ThinOS - 8.5 017

Horizon - 4.6.49204

RTME 2.4.48792

Known Issues with Blast:

Issue number

Description

Workaround

TIR96652

VMware Blast protocol—Trap 14 event log error occurs when you launch or reconnect the VMware session. This event results in a blank display.

There is no workaround available in this release.

TIR95973

Wyse 3040 thin client with ThinOS and PCoIP—Monitors may not wake up when you exit the power-saving mode.

There is no workaround available in this release.

Reply
0 Kudos
nburton935
Hot Shot
Hot Shot

We have customers experiencing similar issues when using BLAST from the Horizon Linux Client. Did you end up opening a case with VMware on this?

Experienced it across 7.3.2, 7.5, and 7.8. Upgrading to 7.10 soon and we will see if the issue persists. Also across multiple client versions.

Reply
0 Kudos