[jacorb-developer] Typed Push Consumer will reconnect after second Supplier failure
Troy Hicks
troy.a.hicks at gmail.com
Wed May 23 03:40:16 CEST 2012
I have a typed push consumer that senses the failure of the supplier
via the disconnect_push_consumer() method, when the supplier app is
stopped and started, and will reconnect and receive events via the
event channel. However, when the supplier is stopped and started a
second time, the consumer will again sense the failure of the
supplier, but it will not successfully reconnect and fails when I call
the ProxyPushSupplier.connect_push_consumer(....) method with the
following exception:
Exception:
"org.omg.ProtableServer.CurrentPackage.NoContext:
IDL:omg.org/ProtableServer/Current/NoContext:1.0"
Code snippet:
// NPES-.OVERLAYS-.Overlay_ev-active
cds.CosTypedEventChannelAdmin.TypedConsumerAdmin
ttypeConsumerAdmin
= teventChannel.for_consumers();
cds.CosEventChannelAdmin.ProxyPushSupplier tproxyPushSupplier
= ttypeConsumerAdmin.obtain_typed_push_supplier("Overlay_ev");
tproxyPushSupplier.connect_push_consumer(
cds.CosTypedEventComm.TypedPushConsumerHelper.narrow(
ODSClientIF.instance.poa.servant_to_reference(this)));
// fails here the second time around....
connectedToEventService = true;
How might I improve my application to survive the supplier going away
and then coming back whether due to a network outage or stopping and
starting the supplier?
Any help would be greatly appreciated,
Troy
More information about the jacorb-developer
mailing list