[openorb-general] NullPointerException

[Jefferson S.J. G. <jg...@nt...>]

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