Some transport dispatchers send messages even when the connector has been stopped

Details

  • User impact:
    Medium
  • Similar Issues:
    None

Description

This happens with vm where there is no transport implementation that is started/stopped. Even is the transport doesn't send messages because the transport implementation is not started, the connector still allows dispatchers to be created and allows send/dispatch to be call and rather than failing with a mule exception fails with a transport exception because transport is not started.

Issue Links

is duplicated by

Bug - A problem which impairs or prevents the functions of the product. MULE-4320 It is possible to create a message dispatcher and attempt to send an event before the connector is started

  • Critical - Crashes, loss of data, severe memory leak.
  • Closed - The issue is considered finished, the resolution is correct. Issues which are not closed can be reopened.
relates to

Bug - A problem which impairs or prevents the functions of the product. MULE-4264 Connectors should check lifecycle and throw exception when attempts to send/dispatch/request are made on a stopped/stopping connector

  • Critical - Crashes, loss of data, severe memory leak.
  • Closed - The issue is considered finished, the resolution is correct. Issues which are not closed can be reopened.

Task - A task that needs to be done. MULE-3679 Review connector lifecyle

  • Major - Major loss of function.
  • Closed - The issue is considered finished, the resolution is correct. Issues which are not closed can be reopened.

Improvement - An improvement or enhancement to an existing feature or task. MULE-2980 Connector lifecycle needs clarification

  • Minor - Minor loss of function, or other problem where easy workaround is present.
  • Closed - The issue is considered finished, the resolution is correct. Issues which are not closed can be reopened.

Activity

Ascending order - Click to sort in descending order
Daniel Feist made changes -
Field Original Value New Value
Priority To be reviewed [ 6 ] Major [ 3 ]
Fix Version/s Bug Backlog (2.1.x, 2.2.x) [ 10522 ]
Daniel Feist made changes -
Link This issue relates to MULE-4264 [ MULE-4264 ]
Daniel Feist made changes -
Link This issue relates to MULE-3679 [ MULE-3679 ]
Daniel Feist made changes -
Link This issue relates to MULE-2980 [ MULE-2980 ]
Daniel Feist made changes -
Link This issue is duplicated by MULE-4320 [ MULE-4320 ]
Daniel Feist made changes -
Description This happens with vm where there is no transport implementation that is started/stopped. Even is the transport doesn't send messages because the transport implementation is not started, the connector still allows dispatchers to be created and allows send/dispatch to be call and rather than failing with a mule exception fails with a transport exception because transport is not started.
Ross Mason made changes -
Assignee Ross Mason [ ross ]
Ross Mason made changes -
Status Open [ 1 ] Closed [ 6 ]
Fix Version/s 3.0.0-RC1 [ 10859 ]
Fix Version/s Bug Backlog [ 10522 ]
Resolution Fixed [ 1 ]
Transition Time In Source Status Execution Times Last Executer Last Execution Date
Open Open Closed Closed
518d 2m 1 Ross Mason 12/Aug/10 12:51 PM
This list may be incomplete, as errors occurred whilst retrieving source from linked applications:
  • Repository mule on http://foo.bar/ failed: Error in remote call to 'FishEye 0 (http://foo.bar/)' (http://foo.bar) [AbstractRestCommand{path='/rest-service-fe/changeset-v1/listChangesets/', params={expand=changesets[-21:-1].revisions[0:29], comment=MULE-4254, p4JobFixed=MULE-4254, rep=mule}, methodType=GET}] : java.net.UnknownHostException: foo.bar

People

  • Assignee:
    Ross Mason
    Reporter:
    Daniel Feist
Vote (0)
Watch (1)

Dates

  • Created:
    Updated:
    Resolved: