PubSub+ Messaging API for .NET
10.27.03
Session
The session event enumeration; this is returned with session event delegate EventArgs.
Definition
Namespace: SolaceSystems.Solclient.Messaging
Assembly: SolaceSystems.Solclient.Messaging (in SolaceSystems.Solclient.Messaging.dll) Version: 10.27.0
Assembly: SolaceSystems.Solclient.Messaging (in SolaceSystems.Solclient.Messaging.dll) Version: 10.27.0
C#
public enum SessionEventMembers
| UpNotice | 0 | The session is established. |
| DownError | 1 | The session was established and then went down. |
| ConnectFailedError | 2 | The session attempted to connect but was unsuccessful. |
| RejectedMessageError | 3 | The appliance rejected a published message. |
| SubscriptionError | 4 | The appliance rejected a subscription (add or remove). |
| MessageTooBigError | 5 | The API discarded a received message that exceeded the set session buffer size. |
| Acknowledgement | 6 | The oldest transmitted Persistent/Non-persistent message has been acknowledged. |
| AssuredDeliveryDown | 8 | Guaranteed Delivery publishing is not available. The guaranteed delivery capability on the session has been disabled by some action on the appliance. |
| TEUnsubscribeError | 9 | The Topic Endpoint unsubscribe request failed. |
| DTEUnsubscribeError | 9 |
Deprecated; TEUnsubscribeError replaces it.
Obsolete. |
| TEUnsubscribeOk | 10 | The Topic Endpoint unsubscribe request was successful. |
| DTEUnsubscribeOk | 10 |
Deprecated; TEUnsubscribeOk replaces it.
Obsolete. |
| CanSend | 11 | Send is no longer blocked. |
| Reconnecting | 12 | The session has gone down, and automatic reconnect attempt is in progress. |
| Reconnected | 13 | The automatic reconnect of session was successful, and the session was reestablished. |
| ProvisionError | 14 | The Endpoint provision/deprovision request failed. |
| ProvisionOk | 15 | The Endpoint provision/deprovision request completed. |
| SubscriptionOk | 16 | The subscribe or unsubscribe operation has succeeded. |
| VirtualRouterNameChanged | 17 | The appliance's Virtual Router Name changed during a reconnect operation. This might render existing queues or temporary topics invalid. |
| ModifyPropertyOk | 18 | The session property modification completed. |
| ModifyPropertyFail | 19 | The session property modification failed. |
| RepublishUnackedMessages | 20 | After successfully reconnecting a disconnected session, the SDK received an unknown publisher flow name response when reconnecting the GD publisher flow. If configured to auto-retry (GdReconnectFailAction) this event is generated to indicate how many unacknowledged messages are retransmitted on success. As the publisher state has been lost on failover, receiving this event may indicate that some messages have been duplicated in the system. |