MuleClient.send doesn´t respect the specified timeout

Details

  • Type: Bug Bug
  • Status: Closed Closed
  • Priority: Major Major
  • Resolution: Won't Fix or Usage Issue
  • Affects Version/s: 1.2
  • Fix Version/s: None
  • Component/s: Modules: MuleClient
  • Labels:
  • Environment:

    JBoss 3.2.1
    Mule 1.2

  • User impact:
    Medium
  • Similar Issues:
    None

Description

The timeout parameter for the send method (MuleClient) is ignored. It always waits for the response in 10 seconds whatever i put in the timeout. The endpoint is a JMS endpoint (from mule extras)

result = client.send(endPoint, serializable, null, 600000);

Issue Links

relates to

Bug - A problem which impairs or prevents the functions of the product. MULE-447 TCP Timeout Config Problem

  • Major - Major loss of function.
  • 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
Hide
Permalink
Julian de Anquin added a comment -

On line 227 of MuleSession.java, the timeout is read like this int timeout = event.getIntProperty(MuleProperties.MULE_EVENT_TIMEOUT_PROPERTY, -1);
so, line 639 of MuleClient.java shoud be event.setIntProperty(MuleProperties.MULE_EVENT_TIMEOUT_PROPERTY,timeout);
instead of event.setTimeout(timeout);
Attached is the .patch to solve it if you think its correct.

There are other places where the time out gets set event.setTimeout(timeout), should evaluate how it gets read in other places? or shoud change it to?
Hope it helps
Cheers
Julian

Show
Julian de Anquin added a comment - On line 227 of MuleSession.java, the timeout is read like this int timeout = event.getIntProperty(MuleProperties.MULE_EVENT_TIMEOUT_PROPERTY, -1); so, line 639 of MuleClient.java shoud be event.setIntProperty(MuleProperties.MULE_EVENT_TIMEOUT_PROPERTY,timeout); instead of event.setTimeout(timeout); Attached is the .patch to solve it if you think its correct. There are other places where the time out gets set event.setTimeout(timeout), should evaluate how it gets read in other places? or shoud change it to? Hope it helps Cheers Julian
Hide
Permalink
Holger Hoffstaette added a comment -

This is not as easy as it looks; see http://www.nabble.com/Q-about-event.setTimeout---its-relation-to-setting-the-timeout-on-the-message-tf2080473.html for more information.

Show
Holger Hoffstaette added a comment - This is not as easy as it looks; see http://www.nabble.com/Q-about-event.setTimeout---its-relation-to-setting-the-timeout-on-the-message-tf2080473.html for more information.
Hide
Permalink
Ross Mason added a comment -

giving this visibility since I don't see a test for it

Show
Ross Mason added a comment - giving this visibility since I don't see a test for it
Hide
Permalink
Ramiro Rinaudo added a comment -

Closed due inactivity. Please reopen if this is still an issue for you on 3.2.1

Show
Ramiro Rinaudo added a comment - Closed due inactivity. Please reopen if this is still an issue for you on 3.2.1

People

  • Assignee:
    Unassigned
    Reporter:
    Fernando Rodrigues
Vote (1)
Watch (1)

Dates

  • Created:
    Updated:
    Resolved: