When HTML5 WebSockets are used, the communication protocol between the client and server upgrades from the HTTP to WebSockets during an initial handshake. The WebSocket protocol simply establishes the WebSocket handshake and the format for the WebSocket data frames. It does nothing different if there is a proxy server .
Logging in gives error "The proxy server isn’t responding" and server.log gives " Error creating bean with name 'liquibase' defined in class path resource"
RM SyncEngine QC class name error With RM QC10 is the Action section of an event for a QC10 data source sets the QC class name to Requirements instead of Requirement the following error in generated in the log: DataSource QCSource: Test Director Sync Proxy : Unknown Exception in CDataSource::BeginEvent(LpSyncEvent) The SyncEngine should generate an error in the syntax check – startup review – and post an error to the syncing.log
It appears that we are supplying a combination of connected userid with the ALM proxy userid's password when attempting to connect to a ZMF 7.1.3 instance. The userid validation is obviously failing and the user sees a web services error in RLM.
Dimensions CM to run a high availability / load balanced environment, with Dimensions CM running on two physical hosts; the clients connect to Dimensions via load balancer / proxy . However, when running Builds, it occasionally fails, and returns a number of errors including the following: BLD4207100E build communications error on line 997: reportBuildMessagesReturn = -1
If we cluster Tomcat, we need to enforce stickiness with Tomcat. This KB handles the case where the Application Engine and Tomcat components are installed on the same server, and we are using IIS to proxy all connections.
If you have a proxy user registered and you try to update their attributes using the UUA command via DMCLI you get the following message: 1019-DBIO: Database I/O error occurred SQL-0304(3642) ORA-02291: integrity constraint QLARIUS_CM.SYSOBJ_HISTORY_K1) violated - parent key not found