|ConnectionClosedException|| Obsolete. |
Deprecated. Not used.
Exception raised when the Gateway closes the client connection, typically due to a fatal error
Exception raised when the JMS Connection to the server is dropped during operation
Exception raised when the JMS Connection could not be established with the server
Exception raised when the JMS Connection is interrupted between Gateway and JMS Server
Exception raised when the JMS Connection is restored. When a connection is either interrupted(between the Gateway and the JMS Broker/Server) or dropped(between the JMS Client and the Gateway), the client will try to restore the connection periodically.
When the connection is either interrupted or dropped, the temporary destinations are automatically deleted. When the connection is eventually restored, JMS Client will have to do some internal book-keeping to make sure that the that the Gateway, JMS Broker/Server, and the JMS Client are all in sync. As part of this internal book-keeping, the JMS Client will automatically do the following:
Wraps a generic exception inside a JMSException
Exception raised when an operation could not complete because the Connection was not established
Exception thrown when a reconnect was attempted but failed
JMS Client implementation of ConnectionFactory. Used to create a connection with a JMS provider via a WebSocket connection. Also provides the ability to set the Gateway location dynamically
Various Stomp connection properties
Exception raised when a JMS Transaction has reported back as not committed prior to connection close. It is possible that the transaction was committed by the broker, but a network interruption caused the receipt to be lost in flight.
Exception raised when a JMS Transaction is rolled back due to an error