[WSCOMMONS-466] AbstractTransportListener.GenericObserver may start listening for services when the transport is stopped

• Type: Bug
• Status: Resolved
• Priority: Critical
• Resolution: Fixed
• Fix Version/s: Transports 1.0
• Component/s: Transport
• Assignee: Andreas Veithen
• Reporter: Andreas Veithen
• Created: 08/May/09 23:42
• Updated: 10/May/09 12:08
• Resolved: 10/May/09 12:08

Description

Scenario:

• The transport has been initialized, but not yet started.
• A service (configured for the transport) is deployed.

Result:

• The transport will start listening for messages. This is wrong because the transport is stopped.
• When the transport is started, it will start listening "twice". E.g. AbstractPollingTransportListener will schedule two polls for the same service.

Issue Links

• blocks: SYNAPSE-542 Sample 254 fails with "Could not rename ..."