.
>
> Thanks
> Jaspreet
>
>
>
>
> --
> View this message in context: http://activemq.2283324.n4.
> nabble.com/Where-can-I-find-the-JMS-connection-reconnection-logic-in-
> activemq-client-source-tp4720765.html
> Sent from the ActiveMQ - User mailing list archive at Nabble.com.
>
nks
Jaspreet
--
View this message in context:
http://activemq.2283324.n4.nabble.com/Where-can-I-find-the-JMS-connection-reconnection-logic-in-activemq-client-source-tp4720765.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
econnectAttempts() on the ServerLocator object
before you use it.
>
> There's a couple of other parameters you can configure to control
reconnection (e.g. retryInterval,
> retryIntervalMultiplier).
>
> You can also check out the "reattach-node" example shipped with Artemis
to see a working example.
>
>
> Justin
ther parameters you can configure to control reconnection
(e.g. retryInterval, retryIntervalMultiplier).
You can also check out the "reattach-node" example shipped with Artemis to see
a working example.
Justin
- Original Message -
From: "Marko Asplund"
To: "
Hi,
How do I get an Artemis client session to automatically reconnect after a
transient network disconnect or a server restart?
Messages are consumed using the Artemis Core API message handler, so
consumer processes are long-running and only create an Artemis client
session at startup.
Currently,
2 and vice versa.
If broker1 and broker2 are running and broker1 is disconnected (knock off
LAN) then client connect to broker2 after a delay of 10-15 seconds and not
immediately, the connection to broker1 is down immediately using
InactivityMonitor but the reconnection has a delay. There is a way i
ECT will not be send
until reattempts are done, which are infinite attempts !
How can I get notified for both these events?
Thanks.
--
View this message in context:
http://activemq.2283324.n4.nabble.com/ActiveMQ-Artemis-Reconnection-Disconnect-notification-tp4714293.html
Sent from the ActiveMQ
connectors.
--
View this message in context:
http://activemq.2283324.n4.nabble.com/JMS-to-JMS-bridge-reconnection-dispatching-not-working-in-simple-conditions-tp4684887p4685246.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
Hmm, it looks like there are two reentrant locks.
Are there 2 brokers running in the same JVM connecting over a network
connector with the VM transport?
--
View this message in context:
http://activemq.2283324.n4.nabble.com/JMS-to-JMS-bridge-reconnection-dispatching-not-working-in-simple
the same
thread.
--
View this message in context:
http://activemq.2283324.n4.nabble.com/JMS-to-JMS-bridge-reconnection-dispatching-not-working-in-simple-conditions-tp4684887p4685180.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
to the discussion
> below:
>
> http://activemq.2283324.n4.nabble.com/JMS-to-JMS-bridge-reconnection-dispatching-not-working-in-simple-conditions-tp4684887p4684969.html
> To unsubscribe from JMS to JMS bridge reconnection dispatching not
> working in simple conditions, click here
>
, the next step that I would try is grabbing a stack trace.
Is you don't want to do that, no worries. Other than leading to the
annoyance of needing a kill -9, is there any other impact?
--
View this message in context:
http://activemq.2283324.n4.nabble.com/JMS-to-JMS-bridge-reconnec
g here? Is there a flag I missed in my configuration?
Is there a migration guide that I didn't see?
I can supply test cases for this, logs, heap dumps or thread dumps if it
helps getting this fixed.
--
View this message in context:
http://activemq.2283324.n4.nabble.com/JMS-to-JMS-brid
Hi, I'm testing ActiveMQ 5.10 trying to migrate from 5.6 in hopes to fix a
variety of dispatching issues I've been dealing with for a while. I'm
running the following topology to verify producer/consumer dispatching on
reconnection works as it does in 5.6. This is my topo
le.com/Failover-reconnection-questions-tp3826592p3832930.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
values for both ReconnectDelay values and the same
happens.
Any idea?
--
View this message in context:
http://activemq.2283324.n4.nabble.com/Failover-reconnection-questions-tp3826592p3827219.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
values for both ReconnectDelay values and the same
happens.
Any idea?
--
View this message in context:
http://activemq.2283324.n4.nabble.com/Failover-reconnection-questions-tp3826592p3827215.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
o, if before stopping the second broker, i start again the first one, the
> same happens, the program crashes.
>
> I'd like to know if this is the right behaviour and, in that case, if
> something can be done to make it work as i want.
>
>
>
> --
> View this message in context:
> http://activemq.2283324.n4.nabble.com/Failover-reconnection-questions-tp3826592p3826592.html
> Sent from the ActiveMQ - User mailing list archive at Nabble.com.
>
--
http://fusesource.com
http://blog.garytully.com
is is the right behaviour and, in that case, if
something can be done to make it work as i want.
--
View this message in context:
http://activemq.2283324.n4.nabble.com/Failover-reconnection-questions-tp3826592p3826592.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
http://activemq.2283324.n4.nabble.com/Reconnection-tp3221099p3221099.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
orker threads supposed
to be actually doing something? Is there something I should be doing in my
code to tell it to shut these down properly, or to have the ActiveMQ client
library do its own reconnection without me having to do much if any work?
This is all on v5.1. My sysadmin is rather cons
on, but any
>> exception is
>> captured when the PC lost the network link. If I stop the
>> messagebroker the
>> exception occurs, but with link lost not. How can I resolve it?
>>
>> --
>> View this message in context:
>> http://www.nabble.c
t;> exception is
>> captured when the PC lost the network link. If I stop the
>> messagebroker the
>> exception occurs, but with link lost not. How can I resolve it?
>>
>> --
>> View this message in context:
>> http://www.nabble.com/Reconnectio
p the
messagebroker the
exception occurs, but with link lost not. How can I resolve it?
--
View this message in context:
http://www.nabble.com/Reconnection-tp22663516p22677750.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
---
Mit freundlichen Grüssen - Kind Regards
Andreas
>
>
> --
> Tim Bish
> http://fusesource.com
> http://timbish.blogspot.com/
>
>
>
>
>
--
View this message in context:
http://www.nabble.com/Reconnection-tp22663516p22725563.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
On Thu, 2009-03-26 at 02:11 -0700, dongabda wrote:
> Yes, I'm using the excepcionListener and onException, but any exception is
> captured when the PC lost the network link. If I stop the messagebroker the
> exception occurs, but with link lost not. How can I resolve it?
>
What OS are you
Yes, I'm using the excepcionListener and onException, but any exception is
captured when the PC lost the network link. If I stop the messagebroker the
exception occurs, but with link lost not. How can I resolve it?
--
View this message in context:
http://www.nabble.com/Reconne
On Tue, 2009-03-24 at 00:46 -0700, dongabda wrote:
> Hi,
> I saw that the consumer doesn't give any exception, it apparently works
> without net link, but after restore the link the consumer doesn't receive
> nothing. How can I know if the connection is down? How can I reconnect it? I
> saw the CMS
message.
>> Why? What can I do to continue receiving messages?
>> --
>> View this message in context:
>> http://www.nabble.com/Reconnection-tp22663516p22663516.html
>> Sent from the ActiveMQ - User mailing list archive at Nabble.com.
>>
>
> ---
> Mit freundli
the link, the consumer never
receives any message.
Why? What can I do to continue receiving messages?
--
View this message in context:
http://www.nabble.com/Reconnection-tp22663516p22663516.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
---
Mit freundlichen Grüssen - Kind
,
producer and consumer) if the consumer or producer lost the link, any
exception is launched, and after restore the link, the consumer never
receives any message.
Why? What can I do to continue receiving messages?
--
View this message in context:
http://www.nabble.com/Reconnection
t;
> Rob
>
>
--
View this message in context:
http://www.nabble.com/reconnection-to-unavailable-broker-causing-thread-memory-leak-tp13143554s2354p15561399.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
.
Any idea if and where that is fixed in 5.0? I'd like to backport the fix if
possible as I can't upgrade to 5.0 at this point.
--
View this message in context:
http://www.nabble.com/reconnection-to-unavailable-broker-causing-thread-memory-leak-tf4603206s2354.html#a13522716
Sent from th
this issue has been resolved in 5.0.0.4-fuse.
Regards,
Roger
--
View this message in context: http://www.nabble.com/reconnection-to-
unavailable-broker-causing-thread-memory-leak-
tf4603206s2354.html#a13356427
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
Whate is 5.0.0.4-fuse?? All of the snapshot builds are by date.
Thanks,
Fred
Roger Bryant wrote:
>
> Apparently this issue has been resolved in 5.0.0.4-fuse.
>
> Regards,
>
> Roger
>
>
>
>
--
View this message in context:
http://www.nabble.com/reco
Apparently this issue has been resolved in 5.0.0.4-fuse.
Regards,
Roger
--
View this message in context:
http://www.nabble.com/reconnection-to-unavailable-broker-causing-thread-memory-leak-tf4603206s2354.html#a13298013
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
; bug. I intend to follow up on it in the next few days and will keep you
> posted.
>
> Rgds,
>
> Roger
>
>
--
View this message in context:
http://www.nabble.com/reconnection-to-unavailable-broker-causing-thread-memory-leak-tf4603206s2354.html#a13254130
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
://www.nabble.com/reconnection-to-unavailable-broker-causing-thread-memory-leak-tf4603206s2354.html#a13230140
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
er of threads is
growing by about a dozen or more after every failed reconnection. This
accounts for the memory leak because of all the threads.
I'm posting to see if this is an old issue or a new introduced issue as I'm
running the top of head from 5.0 build 20071008.215641-19. I don't
50904165-1:0, brokerURL = tcp://emv137:61616,
slaveBroker = false, masterBroker = false, faultTolerantConfiguration =
false, networkConnection = false, duplexConnection = false, peerBrokerInfos
= [], brokerName = emv137, connectionId = 0}
Thanks.
--
View this message in context:
http://www.nabble.
;
> Could you try a recent 4.1-SNAPSHOT?
>
> It might be worth reading the last comment on this issue...
> http://issues.apache.org/activemq/browse/AMQ-734
>
> basically in new versions failover=true is no longer required
> --
>
> James
> ---
> http:/
On 3/8/07, drvillo <[EMAIL PROTECTED]> wrote:
Hi
I have just found out myself the same...
I would like to have some clarification on this as
either the wording failover is misleading, or there
is something weird going on here.
If I specify failover=true in my networkConnector
I can see that t
t;>>>> *_No broker-config.xml_*
>>>>> *__*
>>>>>
>>>>>
>>>>> If the servers are on line during all the operations, everything goes
>>>>> well : messages are published and received by all.
>>>>> The problems came when I disconnected Server 1.
>>>>> a) Server 3 published a message on its topic : server 2 received it.
>>>>> But
>>>>> when server 1 came back online, it did *not* get the message.
>>>>> b) Server 1 sent a message on its queue and then came back online :
>>>>> Server 3 did not receive it.
>>>>>
>>>>>
>>>>> 2) Thinking it may be due to
>>>>> http://issues.apache.org/activemq/browse/AMQ-895,
>>>>> <http://issues.apache.org/activemq/browse/AMQ-895>I've used the patch
>>>>> for ActiveMQ 4.0.2 with the same configuration files but the problem
>>>>> still remains.
>>>>>
>>>>>
>>>>> 3) My third tests was with ActiveMQ 4.1. The configuration was
>>>>> quite the same :
>>>>> *_activemq.xml, Server 1 :
>>>>> _*(...)
>>>>>
>>>>>>>>> uri="tcp://localhost:61616" brokerName="${hostname}"/>
>>>>>
>>>>>
>>>>>
>>>>>>>>> uri="static://(tcp://100.29.191.227:61616)" failover="true"
>>>>> networkTTL="255" brokerName="${hostname}"/>
>>>>>
>>>>> (...)
>>>>>
>>>>> *_Server 2 :_*
>>>>> (...)
>>>>>>>>> uri="static://(tcp://100.29.191.227:61616)" failover="true"
>>>>> networkTTL="255" brokerName="${hostname}"/>
>>>>> (...)
>>>>>
>>>>> *_Server 3 :_*
>>>>> (...)
>>>>>>>>> uri="static://(tcp://100.29.191.225:61616,tcp://100.29.191.226:61616)"
>>>>> failover="true" networkTTL="255" brokerName="${hostname}"/>
>>>>> (...)
>>>>> *__*
>>>>> All servers stayed online during the test. No disconnection
>>>>> Server 3 published a message on its topic.
>>>>> Server 2 received it.
>>>>> Server 1 sometimes receives the messages, but does not
>>>>> receive messages at all.
>>>>>
>>>>> Am I missing something ?
>>>>>
>>>>>
>>>>>
>>>>>
>>>>
>>>>
>>>
>>>
>>
>>
>
>
>
--
View this message in context:
http://www.nabble.com/Disconnection-and-reconnection-in-a-network-of-brokers-tf2704774s2354.html#a9372086
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
43 matches
Mail list logo
