Problem:
- Product Name: VisiBroker
- Product Version: 7.0, 8.0
- Product Component: VisiNotify
- Platform/OS Version: ALL
- JDK/Compiler Version: ALL
How to clean up orphan VisiNotify proxy objects
When VisiNotify suppliers/consumers are killed without disconnect_<> invocations from the application. The proxy objects are not clean up in the Visinotify.
Here are the sample steps to re-create the problem:
- go to example in ${VBROKERDIR}/examples/vbroker/notify/basic_java
- modify seqPushSupplier.java to comment out "consumer.disconnect_sequence_push_consumer()" line
- run seqPushSupplier example
- as ProxyPushConsumer servant is not properly cleaned up, it will be there after an hour
- if this example is run X times, X number of orphan ProxyPushConsumer servant will be created and left alone
- this can also be viewed from VBConsole
Resolution:
The way to clean up the resources are:
- Shutdown Consumer/Supplier, visinotify and osagent.
- delete the visinotify.dir in the /bin to cleanup the cache.
Author: Foo Chee Yong
Old KB# 29972
#VisiBroker
#notificationservice
#Security