Find Answers

Filter Search Results
All Operating Systems:
All Products:
All Solution Types:
Source:
 
Ask a Question
Example: "Database could not be verified"  
Tips | Start Over | Solutions | Alerts | Patches | Defects  
Pages [Next]
  Results
CMS-XML WebSocket console error, can't connect to Deployment Automation using proxy HTTP protocol
WebSocket console error, can't connect to Deployment Automation using proxy HTTP protocol
CMS-XML VM 8.6.1+: PVCS Version Manager Server Admin utility shows message: Install the WebSocket Protocol module in your IIS web server
VM 8.6.1+: PVCS Version Manager Server Admin utility shows message: Install the WebSocket Protocol module in your IIS web server
CMS-XML DA 6.1: Is there a way to timeout long running DA sessions?
As of DA 6.1.3 the UI gets the counter information via websocket thus no 20-seconds REST calls are being made now. The session successfully times out in 30 minutes of user inactivity.
CMS-XML VM 8.6.1+: How to integrate the PVCS Version Manager Web Application Server with IIS
Yes to both questions. The Agent-based VM I-Net Web Client introduced with VM 8.6.1 uses the WebSocket protocol, which the legacy Jakarta ISAPI filter does not support.
CMS-XML How to setup an Apache Reverse Proxy to access a VM I-Net Web Client server running VM 8.6.1 or newer
Starting with VM 8.6.1, the Agent process running on the end-user's PC uses the WebSocket protocol to connect to the server. A WebSocket connection is established via an HTTP protocol upgrade, and additional configuration is require to pass this through a reverse proxy.
CMS-XML VM I-Net Web Client users getting "HTTP Status 500 - Servlet execution threw an exception" after installing the 8.5.2 or 8.5.3 patch on top of VM 8.5.0
org.apache.tomcat. websocket .server.WsFilter.doFilter(WsFilter.java:52) root cause java.lang.NoClassDefFoundError: org/apache/commons/lang/builder/HashCodeBuilder
CMS-XML VM: "HTTP Status 500 - Servlet execution threw an exception - java.lang.UnsatisfiedLinkError: C:\Program Files (x86)\Serena\vm\common\bin\win32\pvcsjvms.dll:" Error when attempting to access VM - Inet homepage
org.apache.tomcat. websocket .server.WsFilter.doFilter(WsFilter.java:52) root cause
CMS-XML VM 8.6.1+: VM I-Net Web Client fails to connect to VM server via a load balancer, firewall or network security software after upgrading to VM 8.6.1 or newer
06-45-57.877:th=2: wca.webclient :E: ERROR: error occured on connection 'ws://ServerName :8080/vminet/PvcsWebClientAgentWebSocket/b48ec622-d9b2-4240-9229-46dcdf907c8d' : WebSocket Exception: Cannot upgrade to WebSocket connection In VM 8.6.1, this may show up as follows in the Java Console for the agent:
CMS-XML PDF Widget: Chrome cannot download PDF, get error "HTTP Get is not supported" in Tomcat log
at org.apache.tomcat. websocket .server.WsFilter.doFilter(WsFilter.java:52) ~[tomcat-websocket.jar:8.5.46]
CMS-XML DA: Error: An existing connection was forcibly closed by the remote host
at org.apache.tomcat.util.net.NioEndpoint$NioSocketWrapper.read(NioEndpoint.java:1190) at org.apache.tomcat. websocket .server.WsFrameServer.onDataAvailable(WsFrameServer.java:72) at org.apache.tomcat.websocket.server.WsFrameServer.doOnDataAvailable(WsFrameServer.java:171)
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs