From: Michael R. <mic...@en...> - 2003-03-25 10:01:17
|
Please send this question to the openorb-users mailing list. The openorb-general list is not followed by many people... You need to be subscribed to openorb-users before posting... Michael Jefferson S.J. Gan wrote: >Jefferson wrote: > > We are currently using Notification Service-1.3.0. And this exception >occurs. I don't know if this is an error on our side. But does anyone know >what this exception means ><===============================================================> >java.lang.NullPointerException > at org.openorb.notify.persistence.ConnectionInfoHelper.write(Unknown >Sou >rce) > at >file.org.openorb.notify.persistence.ConsumerAdminBase.write(Unknown S >ource) > at >file.org.openorb.notify.persistence.ConsumerAdminHomeBase.flush(Unkno >wn Source) > at >file.org.openorb.notify.persistence.ConsumerAdminBase.flushIncarnatio >n(Unknown Source) > at >file.org.openorb.notify.persistence.ConsumerAdminBase.push_suppliers( >Unknown Source) > at >org.openorb.notify.impl.ConsumerAdminImpl.reportPushConsumerDisconnec >tion(Unknown Source) > at >org.openorb.notify.impl.StructuredProxyPushSupplierImpl.disconnect_st >ructured_push_supplier(Unknown Source) > at >org.openorb.notify.impl.StructuredProxyPushSupplierImpl.reportClientD >isconnection(Unknown Source) > at org.openorb.notify.queue.StructuredPusher.dispatchEvent(Unknown >Sourc >e) > at org.openorb.notify.queue.Pusher.doDelivery(Unknown Source) > at org.openorb.notify.queue.Pusher.pushEvent(Unknown Source) > at >org.openorb.notify.impl.StructuredProxyPushSupplierImpl.dispatchEvent >(Unknown Source) > at org.openorb.notify.queue.EventQueueReceiver.doDelivery(Unknown >Source >) > at org.openorb.notify.queue.EventQueueReceiver.pushEvent(Unknown >Source) > at org.openorb.notify.impl.ConsumerAdminImpl.dispatchEvent(Unknown >Sourc >e) > at org.openorb.notify.queue.EventQueueReceiver.doDelivery(Unknown >Source >) > at org.openorb.notify.queue.EventQueueReceiver.run(Unknown Source) ><===============================================================> > Is there a limitation on the notification service of having the same >subnet? ... for example 171.38.61.101 is the server and where notification >service is running, should the client be only at 171.38.61 subnet mask... >Because we have encountered receiving event through notification service if >they have different subnet mask. > Our current setup was the supplier for notifications is in the different >subnet with the consumer. We send notification first, then all is >successful, so then we close the application for consumer then run the >application for consumer and connect it again. Then the next time we send >notification, the exception above appears. Do anyone know what might be the >problem? > >Thank you very much > > > > >------------------------------------------------------- >This SF.net email is sponsored by:Crypto Challenge is now open! >Get cracking and register here for some mind boggling fun and >the chance of winning an Apple iPod: >http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0031en >_______________________________________________ >openorb-general mailing list >ope...@li... >https://lists.sourceforge.net/lists/listinfo/openorb-general > > |