JIRA

  • Log In Access more options
    • Online Help
    • GreenHopper Help
    • Agile Answers
    • Use Agile By Default
    • Keyboard Shortcuts
    • About JIRA
    • JIRA Credits
    • What’s New
  • Dashboards Access more options (Alt+d)
  • Projects Access more options (Alt+p)
  • Issues Access more options (Alt+i)
  • Agile Access more options (Alt+g)
  • Create Issue
  • Mule
  • MULE-3566

Mule doesn't start the actual JMS connection

  • Agile Board
  • More Actions
  • Views
    • XML
    • Word
    • Printable

Details

  • Type: Bug Bug
  • Status: Closed Closed
  • Priority: To be reviewed To be reviewed
  • Resolution: Won't Fix or Usage Issue
  • Affects Version/s: 2.0.2
  • Fix Version/s: None
  • Component/s: Transport: JMS
  • Labels:
    None
  • Environment:

    Linux Ubuntu 8.04, i386, Java 6

  • User impact:
    Low
  • Similar Issues:
    None

Description

Mule doesn't actually seem to start the JMS connection to the broker. This is caused by the following code in JMSConnector:

connection = createConnection();
if (!started.get())
{
connection.start();
}

  • Options
    • Sort By Name
    • Sort By Date
    • Ascending
    • Descending
    • Download All

Attachments

  1. Text File
    JmsConnector.patch
    21/Jul/08 04:32 PM
    0.4 kB
    Jeroen Benckhuijsen

Activity

Ascending order - Click to sort in descending order
  • All
  • Comments
  • Work Log
  • History
  • Activity
  • Transitions
  • Commits
  • Source
  • Builds
Hide
Permalink
Jeroen Benckhuijsen added a comment - 21/Jul/08 04:32 PM

Patch fixing the issue

Show
Jeroen Benckhuijsen added a comment - 21/Jul/08 04:32 PM Patch fixing the issue
Hide
Permalink
Andrew Perepelytsya added a comment - 02/Oct/08 04:27 PM

Jeroen, could you please provide more info? After reviewing the code it doesn't look like a problem to me, the connection is started in the doStart() method.

Show
Andrew Perepelytsya added a comment - 02/Oct/08 04:27 PM Jeroen, could you please provide more info? After reviewing the code it doesn't look like a problem to me, the connection is started in the doStart() method.
Hide
Permalink
Jeroen Benckhuijsen added a comment - 03/Oct/08 02:44 AM

Andrew, doStart() indeeds does the starting already, Therefore, it's just a minor issue as the original code tries to start an already started connection. However, the code is a bit strange, so this fix is just for clarity (i.e. only start the connection is it HASN'T been started already).

Original: if (started.get())
New: if (!started.get()) <-- Mind the !

Show
Jeroen Benckhuijsen added a comment - 03/Oct/08 02:44 AM Andrew, doStart() indeeds does the starting already, Therefore, it's just a minor issue as the original code tries to start an already started connection. However, the code is a bit strange, so this fix is just for clarity (i.e. only start the connection is it HASN'T been started already). Original: if (started.get()) New: if (!started.get()) <-- Mind the !
Hide
Permalink
Andrew Perepelytsya added a comment - 03/Oct/08 10:55 AM

The 'started' variable refers to the JmsConnector, and not the connection itself. While their lifecycles mostly match, they are not guaranteed to be always the same.

Show
Andrew Perepelytsya added a comment - 03/Oct/08 10:55 AM The 'started' variable refers to the JmsConnector, and not the connection itself. While their lifecycles mostly match, they are not guaranteed to be always the same.

People

  • Assignee:
    Andrew Perepelytsya
    Reporter:
    Jeroen Benckhuijsen
Vote (0)
Watch (0)

Dates

  • Created:
    21/Jul/08 04:31 PM
    Updated:
    03/Oct/08 10:55 AM
    Resolved:
    02/Oct/08 04:27 PM

Agile

  • View on Board
  • Atlassian JIRA (v5.0.7#734-sha1:8ad78a6)
  • Report a problem
  • Powered by a free Atlassian JIRA open source license for MuleForge. Try JIRA - bug tracking software for your team.