Exception in other endpoint when own shuts down
Status: Beta
Brought to you by:
rjan
I ran into an issue in serveral situations while testing churn in OSGi/R-OSGi enabled p2p applications. When one side of the channel is being shut down, it sends a LeaseUpdateMessage.SERVICE_REMOVED to the other side. While the handle message method for this case initially checks if the channel has already been disposed, there seems to be a chance that the channel is open during the check but closed when the control flow reaches the getRemoteAddress() some lines below. This causes an exception to be thrown. The error does not seem to influence the state of the running R-OSGi but may be irritating when displayed.
accidently posted in the support requests -> moved to bugs