VMware Cloud Community
LenK
Enthusiast
Enthusiast

vRO 7 Server Side Client Errors

We recently deployed vRA 7 using the minimal install model to begin planning for a production upgrade from vRA 6 to vRA 7.  Since we are using the minimal install model we are leveraging the vRO 7 instance that’s bundled with the vRA appliance.

As we began testing our existing WF’s in vRA 7 we noticed that the data we were writing to System.log() was not visible in our vRO client.  I reviewed /var/log/vmware/vco/app-server/server.log to confirm that the data I was logging with Server.log() was indeed being written as INFO.  While reviewing server.log I noticed the following client specific error that repeats in the log every 15-20 seconds as long as my vRO Java client is connected and I believe this is why I’m unable to view messages in the Logs tab of the vRO client:

2016-01-08 13:57:02.798-0500 [hornetq-failure-check-thread] WARN  {} [RemotingConnectionImpl] Connection failure has been detected: Did not receive data from local:ephemeral. It is likely the client has exited or crashed without closing

its connection, or the network between the server and client has failed. You also might have configured connection-ttl and client-failure-check-period incorrectly. Please check user manual for more information. The connection will now be

closed. [code=3]

2016-01-08 13:57:10.025-0500 [http-nio-127.0.0.1-8280-exec-10] ERROR {} [[messagingServlet]] Servlet.service() for servlet [messagingServlet] in context with path [/vco] threw exception

  1. java.net.SocketTimeoutException

        at org.apache.tomcat.util.net.NioBlockingSelector.read(NioBlockingSelector.java:202)

        at org.apache.tomcat.util.net.NioSelectorPool.read(NioSelectorPool.java:250)

        at org.apache.tomcat.util.net.NioSelectorPool.read(NioSelectorPool.java:231)

        at org.apache.coyote.http11.InternalNioInputBuffer.fill(InternalNioInputBuffer.java:133)

        at org.apache.coyote.http11.InternalNioInputBuffer$SocketInputBuffer.doRead(InternalNioInputBuffer.java:177)

        at org.apache.coyote.http11.filters.ChunkedInputFilter.readBytes(ChunkedInputFilter.java:320)

        at org.apache.coyote.http11.filters.ChunkedInputFilter.parseChunkHeader(ChunkedInputFilter.java:350)

        at org.apache.coyote.http11.filters.ChunkedInputFilter.doRead(ChunkedInputFilter.java:190)

        at org.apache.coyote.http11.AbstractInputBuffer.doRead(AbstractInputBuffer.java:416)

        at org.apache.coyote.Request.doRead(Request.java:469)

        at org.apache.catalina.connector.InputBuffer.realReadBytes(InputBuffer.java:342)

        at org.apache.tomcat.util.buf.ByteChunk.substract(ByteChunk.java:363)

        at org.apache.catalina.connector.InputBuffer.readByte(InputBuffer.java:356)

        at org.apache.catalina.connector.CoyoteInputStream.read(CoyoteInputStream.java:94)

        at java.io.FilterInputStream.read(FilterInputStream.java:83)

        at java.io.PushbackInputStream.read(PushbackInputStream.java:139)

        at org.jboss.netty.channel.socket.http.HttpTunnelingServlet.read(HttpTunnelingServlet.java:199)

        at org.jboss.netty.channel.socket.http.HttpTunnelingServlet.service(HttpTunnelingServlet.java:172)

        at javax.servlet.http.HttpServlet.service(HttpServlet.java:729)

        at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:291)

        at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)

        at org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:52)

        at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:239)

        at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)

        at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:219)

        at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:106)

        at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:614)

        at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:142)

        at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:79)

        at org.apache.catalina.valves.RemoteIpValve.invoke(RemoteIpValve.java:676)

        at org.apache.catalina.valves.AbstractAccessLogValve.invoke(AbstractAccessLogValve.java:616)

        at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:88)

        at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:518)

        at org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:1091)

        at org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:673)

        at org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(NioEndpoint.java:1526)

        at org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.run(NioEndpoint.java:1482)

        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)

        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)

        at org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61)

        at java.lang.Thread.run(Thread.java:745)

2016-01-08 13:57:10.553-0500 [http-nio-127.0.0.1-8280-exec-5] WARN  {} [HornetQPacketHandler] Reattach request from local:ephemeral failed as there is no confirmationWindowSize configured, which may be ok for your system

2016-01-08 13:57:11.121-0500 [http-nio-127.0.0.1-8280-exec-5] WARN  {} [HornetQPacketHandler] Reattach request from local:ephemeral failed as there is no confirmationWindowSize configured, which may be ok for your system

2016-01-08 13:57:11.681-0500 [http-nio-127.0.0.1-8280-exec-5] WARN  {} [HornetQPacketHandler] Reattach request from local:ephemeral failed as there is no confirmationWindowSize configured, which may be ok for your system

2016-01-08 13:57:12.245-0500 [http-nio-127.0.0.1-8280-exec-5] WARN  {} [HornetQPacketHandler] Reattach request from local:ephemeral failed as there is no confirmationWindowSize configured, which may be ok for your system

2016-01-08 13:57:24.800-0500 [hornetq-failure-check-thread] WARN  {} [RemotingConnectionImpl] Connection failure has been detected: Did not receive data from local:ephemeral. It is likely the client has exited or crashed without closing

its connection, or the network between the server and client has failed. You also might have configured connection-ttl and client-failure-check-period incorrectly. Please check user manual for more information. The connection will now be

closed. [code=3]

Has anyone else experienced similar errors or logging behavior in vRO 7?

Reply
0 Kudos
6 Replies
sascha_milic
Hot Shot
Hot Shot

Hi,

I've got the same issue on Win81SP1 with Java 1.8.0_66 (64bit).

Running the vRO client on W2012R2 with Java 1.7.0_67 (64bit) the System.log is visible.

What's also strange is the "Server build number mismatch" message on my Win81 desktop while starting the vRO client.

That's for now.

Reply
0 Kudos
bobvands
Contributor
Contributor

Hi Len,

I see the same issues in my log as well. Were you able to figure out the issue?

Thanks

Reply
0 Kudos
LenK
Enthusiast
Enthusiast

W‌hen launching the client using the client.jnlp file associated with the link on https://<vRA appliance> I receive the errors and can't view output in System.log in most cases. However, if you navigate to https://<vRA appliance/vco/ you will find a link where you can download an executable. Downloading and using that executable has resolved all my client issues.

Remember that vRO now uses port 443 instead of 8281 so leave the port number out when browsing /vco using https.

Len

Reply
0 Kudos
bobvands
Contributor
Contributor

Hi Len,

When I open https://<vra-app>/vco i get a "HTTP Status 404 error - /vco"

Is this the correct URL?

Thanks

Reply
0 Kudos
LenK
Enthusiast
Enthusiast

I think you just need to add a trailing '/' to your URL.

https://<vra appliance>/vco/

Len

Reply
0 Kudos
bobvands
Contributor
Contributor

Hi Len,

Thanks for the reply. I was able to download the client and got better logs.

Reply
0 Kudos