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:

  • Recreate the temporary destination objects on the client.
  • Recreate the associated MessageProducer and MessageConsumer objects on the client.
  • Re-send any messages that named a temporary destination in the JMSReplyTo property(which is set using Message.setJMSReplyTo() method/function).
  • Raise ConnectionRestoredException by invoking the ExceptionListener.onException() API so that the application code gets a chance to deal with the situation for any application specific functionality.

Namespace:  Kaazing.JMS.Stomp
Assembly:  Kaazing.JMS (in Kaazing.JMS.dll)

Syntax

Visual Basic
Public Class ConnectionRestoredException _
	Inherits GenericException
C#
public class ConnectionRestoredException : GenericException
Visual C++
public ref class ConnectionRestoredException : public GenericException

Inheritance Hierarchy

System..::..Object
  System..::..Exception
    Kaazing.JMS..::..JMSException
      Kaazing.JMS.Stomp..::..GenericException
        Kaazing.JMS.Stomp..::..ConnectionRestoredException

See Also