| Summary | PushProxySuppliers can be removed from the Notification Service |
|---|---|
| Article Number | 34091 |
| Environment | Orbix 6.3 All supported platforms |
| Question/Problem Description | PushProxySupplier deleted from Notification Service PushProxySupplier removed from Notification Service Proxy suppliers no longer registered in Notification Service Push proxy supplier missing |
| Clarifying Information |
Consumers receive messages from the event channel through a proxy supplier. Each consumer on the channel has its own proxy supplier.
|
| Error Message | |
| Defect/Enhancement Number | |
| Cause |
A client consumer can disconnect from the event channel by invoking the disconnect operation on its proxy supplier. This operation terminates the connection between the consumer and its target proxy supplier. The event channel then releases all resources allocated to support its connection to the consumer, including destruction of the target proxy supplier.
Each proxy supplier interface supports a disconnect operation. For example, disconnect_structured_push_supplier() is defined in StructuredProxyPushSupplier.
|
| Resolution | |
| Workaround | |
| Notes | For more information on Orbix Notification and Events, please see the Orbix Enterprise Messaging Guide. Orbix Enterprise Messaging Guide, "Disconnecting From the Event Channel", Chapter 4, section 4 All Orbix 6.3 documentation can be found here. |
| Attachment |
| Created date: | 17 August 2012 |
|---|---|
| Last Modified: | 12 February 2013 |
| Last Published: | 17 August 2012 |
| First Published date: | 17 August 2012 |
#KnowledgeDocs
#Orbix
