NullPointerException during Bus deactivation
|Assignee:||J. Wienke||% Done:|
Exception in thread "main" java.lang.NullPointerException at rsb.transport.socket.BusBase.deactivate(BusBase.java:254) at rsb.transport.socket.BusClient.deactivate(BusClient.java:89) at rsb.transport.socket.RefCountingBus.deactivate(RefCountingBus.java:102) at rsb.transport.socket.SocketConnectorUtility.deactivate(SocketConnectorUtility.java:230) at rsb.transport.socket.SocketOutConnector.deactivate(SocketOutConnector.java:89) at rsb.eventprocessing.RouteConfiguratorUtility.deactivate(RouteConfiguratorUtility.java:116) at rsb.eventprocessing.DefaultOutRouteConfigurator.deactivate(DefaultOutRouteConfigurator.java:67) at rsb.Informer$InformerStateActive.deactivate(Informer.java:121) at rsb.Informer.deactivate(Informer.java:269) at rsb.informer.main(informer.java:82)
fixes #1602: exception during bus deactivation
Fix a threading error causing a NPE during deactivation.
Merge branch 'bug-1602'
#1 Updated by J. Wienke over 9 years ago
- Status changed from New to In Progress
- Assignee set to J. Wienke
I will have a look at this
#2 Updated by J. Wienke over 9 years ago
- Description updated (diff)
#3 Updated by J. Wienke over 9 years ago
- Status changed from In Progress to Feedback
- % Done changed from 0 to 60
Jan, could you please check whether the proposed experimental patch in a respective bug branch cures the problem. There is not real chance to test this behavior as it is related to the exact timing of the shutdown sequence but I think I found a potential interleaving of threads we did not think of so far.
#4 Updated by J. Wienke over 9 years ago
- Status changed from Feedback to Resolved
- % Done changed from 60 to 100
Applied in changeset rsb-java|commit:bf47320e919c339966f432372c61f08f977f2190.
#5 Updated by J. Wienke over 9 years ago
I had no chance to formally verify this fix as I could never reproduce the original error. Even after running a loop for one day. Hopefully this helps.