Explanation | Annotated Server Endpoint class must be public, concrete, and have a public no-args constructor. |
Action | Fix Annotated Server Endpoint class to be public, concrete, and have a public no-args constructor. After you resolve the problem, deploy the application again. |
Explanation | Annotated ServerEndpoint class is invalid if both @OnOpen and @onMessage are missing. |
Action | Fix Annotated ServerEndpoint class by adding @OnOpen and/or @OnMessage. After you resolve the problem, deploy the application again. |
Explanation | Annotated ServerEndpoint is invalid because more than one @OnMessage method with Pong message type is defined in Annotated Endpoint class. WebSocket application is not deployed successfully. |
Action | Fix Annotated ServerEndpoint class by defining only one pong msg type @OnMessage method. After you resolve the problem, deploy the application again. |
Explanation | Annotated ServerEndpoint is invalid because more than one @OnMessage method with binary message type is defined in Annotated Endpoint class. WebSocket application is not deployed successfully. |
Action | Fix Annotated ServerEndpoint class by defining only one binary message type @OnMessage method. After you resolve the problem, deploy the application again. |
Explanation | Annotated ServerEndpoint is invalid because @OnMessage method does not have pong, binary or text type message parameter. WebSocket application is not deployed successfully. |
Action | Fix Annotated ServerEndpoint class by declaring @OnMessage method with either text or binary or pong type message parameter. After you resolve the problem, deploy the application again. |
Explanation | Annotated ServerEndpoint is invalid because more than one @OnMessage method with text message type is defined in Annotated Endpoint class. WebSocket application is not deployed successfully. |
Action | Fix Annotated ServerEndpoint class by defining only one text msg type @OnMessage method. After you resolve the problem, deploy the application again. |
Explanation | Invalid parameter type found in @OnOpen method. @OnOpen method can have only optional Session, optional EndpointConfig and optional @PathParam parameters |
Action | Fix Annotated ServerEndpoint class by removing invalid parameter type in @OnOpen method. After you resolve the problem, deploy the application again. |
Explanation | Annotated ServerEndpoint is invalid because more than one @OnClose methods are defined in Annotated Endpoint class. WebSocket application is not deployed successfully. |
Action | Fix Annotated ServerEndpoint class by defining only one @OnClose method. After you resolve the problem, deploy the application again. |
Explanation | Invalid parameter type found in @OnClose method. @OnClose method can have only optional Session, optional CloseReason and optional @PathParam parameters. |
Action | Fix Annotated ServerEndpoint class by removing invalid parameter type in @OnClose method. After you resolve the problem, deploy the application again. |
Explanation | Annotated ServerEndpoint is invalid because more than one @OnError method is defined in Annotated Endpoint class. WebSocket application is not deployed successfully. |
Action | Fix Annotated ServerEndpoint class by defining only one @OnError method. After you resolve the problem, deploy the application again. |
Explanation | Invalid parameter type found in @OnError method. @OnError method can have only mandatory Throwable, optional Session and optional @PathParam parameters. |
Action | Fix Annotated ServerEndpoint class by removing invalid parameter type in @OnError method. After you resolve the problem, deploy the application again. |
Explanation | Annotated ServerEndpoint is invalid because @OnError method is missing mandatory parameter of type Throwable. WebSocket application is not deployed successfully. |
Action | Fix Annotated ServerEndpoint class by adding mandatory parameter of type Throwable in @OnError method. After you resolve the problem, deploy the application again. |
Explanation | Invalid parameter type found in @OnMessage method with pong message type. WebSocket application is not deployed successfully. |
Action | Fix Annotated ServerEndpoint class by removing invalid parameter type in @OnMessage method. After you resolve the problem, deploy the application again. |
Explanation | Annotated ServerEndpoint is invalid because @OnMessage method has more than one binary message type parameter. WebSocket application is not deployed successfully. |
Action | Fix Annotated ServerEndpoint class by defining only one binary message type parameter. After you resolve the problem, deploy the application again. |
Explanation | Decoder class used in Annotated ServerEndpoint class must be public, concrete, and have a public no-args constructor. |
Action | Fix decoder class to be public, concrete, and have a public no-args constructor. After you resolve the problem, deploy the application again. |
Explanation | Annotated ServerEndpoint is invalid because @OnMessage method has more than one message type parameter. WebSocket application is not deployed successfully. |
Action | Fix @OnMessage method by defining only one message type parameter as per javax.websocket.OnMessage API documentation. After you resolve the problem, deploy the application again. |
Explanation | Invalid parameter type found in @OnMessage method with binary message type. WebSocket application is not deployed successfully. |
Action | Fix @OnMessage method by removing invalid parameter type according to javax.websocket.OnMessage API documentation. After you resolve the problem, deploy the application again. |
Explanation | Annotated ServerEndpoint is invalid because @OnMessage method has more than one text message type parameter. WebSocket application is not deployed successfully. |
Action | Fix @OnMessage method by defining only one text message type parameter according to javax.websocket.OnMessage API documentation. After you resolve the problem, deploy the application again. |
Explanation | Invalid parameter type found in @OnMessage method with text message type. WebSocket application is not deployed successfully. |
Action | Fix @OnMessage method by removing invalid parameter type according to javax.websocket.OnMessage API documentation. After you resolve the problem, deploy the application again. |
Explanation | @PathParam parameter does not have corresponding path segment in @ServerEndpoint URI. |
Action | Fix @PathParam parameter name to match one of the path segments in @ServerEndpoint URI. After you resolve the problem, deploy the application again. |
Explanation | @PathParam annotation does not have value. WebSocket application is not deployed successfully. |
Action | Fix @PathParam annotation by adding the value to the annotation. After you resolve the problem, deploy the application again. |
Explanation | @PathParam parameter has invalid type. WebSocket application is not deployed successfully. |
Action | Fix @PathParam annotation type to be either String, any Java primitive type, or boxed version. After you resolve the problem, deploy the application again. |
Explanation | Converting path @PathParam parameter with matching segment from ServerEndpoint URI failed due to invalid type. Endpoint method is not executed successfully. |
Action | Make sure incoming ServerEndpoint URI segment is a data type match for corresponding @PathParam parameter. |
Explanation | Exception occurred while reading an incoming WebSocket message because no more byte available to read. |
Action | Check incoming WebSocket message data for correctness. |
Explanation | Unable to execute WebSocket client request because the client is sending a message to ServerEndpoint which does not have @OnMessage method or MessageHandler for this type of message defined. |
Action | Either notify the client or add @OnMessage method to Annotated Server Endpoint, or add a MessageHandler, to be able to serve the client request and deploy the application again. |
Explanation | Unable to execute WebSocket client request because IOException occurred calling onMessage while decoding message data. |
Action | Check incoming message data and check the decoder. |
Explanation | Unable to execute WebSocket request because of problem creating new instance of decoder class. |
Action | Check the decoder class. |
Explanation | Exception occurred while reading an incoming WebSocket message because of an error processing FIN value of 1. |
Action | Check incoming WebSocket message frame data for correctness. |
Explanation | Exception occurred while reading an incoming WebSocket message because of an error processing FIN value of 0. |
Action | Check incoming WebSocket message frame data for correctness. |
Explanation | Exception occurred while reading an incoming WebSocket message because of an invalid opcode in the message frame. |
Action | Check incoming WebSocket message frame data for correctness. |
Explanation | Exception occurred while reading an incoming WebSocket message because of an invalid continue opcode with unfragmented message. |
Action | Check incoming WebSocket message frame data for correctness. |
Explanation | Exception occurred while reading an incoming WebSocket message because the mask flag is not set correctly in the message frame. |
Action | Check incoming WebSocket message frame data for correctness. |
Explanation | Exception occurred while reading an incoming WebSocket message because the Mask Flag is not set to a correct value in the message frame. |
Action | Check incoming WebSocket message frame data for correctness. |
Explanation | Annotated ServerEndpoint is invalid because more than one server endpoints have the same URI. WebSocket application is not deployed successfully. |
Action | Define unique ServerEndpoint URIs in WebSocket application. After you resolve the problem, deploy the application again. |
Explanation | Exception occurred while reading an incoming WebSocket message because of an invalid non-zero opcode on non-first frame. |
Action | Check incoming WebSocket message frame data for correctness. |
Explanation | Annotated ServerEndpoint is invalid because more than one @OnOpen method is defined in Annotated Endpoint class. WebSocket application is not deployed successfully. |
Action | Fix Annotated ServerEndpoint class by defining only one @OnOpen method. After you resolve the problem, deploy the application again. |
Explanation | WebSocket message can not exceed maxMessageSize defined in @OnMessage annotation. |
Action | Check the client to send WebSocket message smaller than maxMessageSize defined in @OnMessage or increase maxMessageSize in @OnMessage and deploy the application again. |
Explanation | The WebSocket session timed out. WebSocket sessions become inactive when messages are not sent or received within the number of seconds specified by the maxIdleTimeout setting. |
Action | Check why the client is not sending or receiving messages. If necessary, increase the maxIdleTimeout setting using the Session.setMaxIdleTimeout() API. |
Explanation | Outgoing WebSocket operations require a 101 response code for WebSocket operations. |
Action | Use the invalid response code to determine if the target endpoint is a valid and running WebSocket endpoint and to determine the cause of the failure on the outgoing WebSocket request. |
Explanation | Outgoing WebSocket operations require that the target server returns a valid WebSocket accept key for WebSocket operations. |
Action | Verify that the target server is compliant with the WebSocket protocol. |
Explanation | A valid endpoint is required for an outgoing WebSocket request. |
Action | Check that the ClientEndpoint parameter used in the connectToServer method of the WebSocket API call is an annotated client endpoint. |
Explanation | Valid WebSocket schemes are ws or wss. |
Action | Use a valid scheme during an outgoing WebSocket request. |
Explanation | The Configuration class was not created during an outgoing request, possibly because the public zero argument constructor of the Configurator class did not exist or was not accessible. |
Action | Verify the correctness of the configurator class and that the class has an accessible public zero argument constructor. |
Explanation | The exception occurred when the endpoint attempted to connect to the target server during an outgoing WebSocket request. |
Action | Use exception details to determine the cause and fix the problem. |
Explanation | A valid endpoint class is required for an outgoing WebSocket request. |
Action | Verify that the Endpoint parameter that is used in the connectToServer method of the WebSocket API call extends a WebSocket endpoint class. |
Explanation | The WebSocket ServerEndpoint with the specified URI is available for the WebSocket client to use. |
Action | No action is required. |
Explanation | The WebSocket ServerEndpoints with the specified context path are unavailable to service the WebSocket client. |
Action | For information about why the ServerEndpoints are not available, see the Liberty profile server logs and trace. |
Explanation | Security must be enabled to process outgoing secure WebSocket requests. |
Action | Enable security. |
Explanation | WebSocket endpoints must be added before the WebSocket application starts. |
Action | Add WebSocket endpoints before the WebSocket application starts. |
Explanation | The exception occurred during endpoint class creation. |
Action | Use exception details to determine the cause and fix the problem. |
Explanation | When the server attempted to access the specified endpoint class, an error occurred. |
Action | Review the exception details to determine why the endpoint class cannot be accessed, and fix the problem. |
Explanation | ServerEndpoint is invalid because Endpoint URI is either null or does not start with / in endpoint class. WebSocket application is not available for requests. |
Action | Define non null Endpoint URI beginning with /. After you resolve the problem, deploy the application again. |