Clean Install VMware View 3.1

[arjanhs]

I have installed VMware View 3.1 in my test lab and have done a clean install, the setup is build up with a connection broker and an vCenter/Composer machine. After rolling out the first linked clone with the installed composer i found the following messages in the event viewer of View:

(Request883)

Request failed: com.vmware.vdi.ob.tunnelservice.cx: Failed whilst returning

body: java.io.IOException: Broken pipe

(Request872)

Request failed: com.vmware.vdi.ob.tunnelservice.cx: Failed whilst returning

body: java.io.IOException: Broken pipe

(Request750)

Request failed: com.vmware.vdi.ob.tunnelservice.cx: Failed whilst returning

body: java.io.IOException: Broken pipe

(Request437)

Request failed: com.vmware.vdi.ob.tunnelservice.cx: Failed whilst returning

body: java.net.SocketException: Connection reset by peer: socket write error

(Request416)

Request failed: com.vmware.vdi.ob.tunnelservice.cx: Failed whilst returning

body: java.io.IOException: Broken pipe

(Request400)

Request failed: com.vmware.vdi.ob.tunnelservice.cx: Failed whilst returning

body: java.io.IOException: Broken pipe

(Request241)

Request failed: com.vmware.vdi.ob.tunnelservice.cx: Failed whilst returning

body: java.io.IOException: Broken pipe

The deployment of the VM went well but i would like to resolve these messages.

Arjan

[bobo23]

I've been gettting the same errors with 3.1 and now with 3.1.1. I haven't seen it in my development environment but my production environment is posting the errors. Production is two brokers and the errors post on both brokers at the same time. I'm wondering if it has to do with replication between the brokers although data seems to be replicating between them fine.

Have you discovered and resolved the cause of this error?

[arjanhs]

What kind of load balancing are you using between the two connection brokers?

There will be a release of 3.1.2 within this month which probably will solve this problem.

[arjanhs]

View 3.1.2 have been released and when checking the release notes you can find that your messages have been solved.

[bobo23]

Just updated the brokers to 3.1.2 and almost updated all the agents on the vm's. Unfortunately, I'm still seeing the error. To answer your question about load balancing, the brokers are behind F5's.

Request failed: com.vmware.vdi.ob.tunnelservice.cx: Failed whilst returning body: java.io.IOException: Broken pipe

[arjanhs]

Did you tried a SR from VMware Support?