activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "james strachan (JIRA)" <>
Subject [jira] Commented: (AMQ-641) JMS is a asynchronous interface ,blocking is not allow.
Date Fri, 17 Mar 2006 11:09:27 GMT
    [ ] 

james strachan commented on AMQ-641:

OK I'm with you now - you are happy for the method to be synchronous - and when there is a
network problem you want it to fail with an exception right? Your issue appears to be that
the amount of time before a network error becomes apparent is too long right?

In that case - I'd take off the failover: prefix and just ensure that you set the TCP timeouts
 to something small enough so you get an error in whatever timeframe suits you.

if you try the latest SNAPSHOT build, we have a 'connectionTimeout' property that sets the
maximum amount of time you are prepared to wait before you declare a TCP socket connection

So try


then you should get an error within a second of trying to connect/send if there is a network

>  JMS is a asynchronous interface ,blocking is not allow.
> --------------------------------------------------------
>          Key: AMQ-641
>          URL:
>      Project: ActiveMQ
>         Type: Bug

>   Components: JMS client, Connector
>     Versions: 3.2.2, 4.0 M4
>  Environment: winxp jdk1.4.2 jdk 1.5.6
>     Reporter: tao

> If I use failover:tcp//.... in the jms client,
> That all method will be blocked when net or activemq error.
> This  is not a good idea.My application will be blocked. 
> And If I use tcp//.... in the jms client,Sometimes ,send(message) method will be blocked,also
not return.
>  JMS is a asynchronous interface ,blocking is not allow at any condition.

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:

View raw message