Further tests show, that fault is apparently NOT in DefaultReportManager or DefaultSubscriptionManager,...
Devices that become unavailable and than available again are not reliably detected by BICEPSClient
Memory leak in DefaultMessage2SOAPGenerator
NPE in BICEPSProxyUtils
DefaultSubscriptionManager is prone to ConcurrentModificationExceptions
The handling of the bye seems to block within "handleDeviceLeftNetwork" in class...
Bye-Message does not lead to deviceRemoved-call
Concurrency issues with parallel subscribe/unsubscribe