Re: Conntecting to a remote broker.

2013-02-27 Thread Andreas Calvo
jboss, glassfish, etc. -- View this message in context: http://activemq.2283324.n4.nabble.com/Conntecting-to-a-remote-broker-tp4664053.html Sent from the ActiveMQ - User mailing list archive at Nabble.com. -- Andreas Calvo Gómez Systems Engineer Scytl Secure Electronic Voting Plaça Gal·la

Re: Understanding NoB

2013-02-11 Thread Andreas Calvo Gómez
Missing part On 11/02/13 15:25, Andreas Calvo Gómez wrote: Hello, In the following scenario: - 4 machines (A1, A2, A3 and CB1) - 3 of them (A1, A2 and A3) under the same broadcast domain, with an embedded broker (persistent), a local consumer (durable subscriber) and a local producer, with

Understanding NoB

2013-02-11 Thread Andreas Calvo Gómez
Hello, In the following scenario: - 4 machines (A1, A2, A3 and CB1) - 3 of them (A1, A2 and A3) under the same broadcast domain, with an embedded broker (persistent), a local consumer (durable subscriber) and a local producer, with multicast enabled and static network connector (SSL) to a centr

Re: maxInactivityDuration

2013-02-04 Thread Andreas Calvo Gómez
Mohit, The clients will take that parameter and used it to monitor connections. On 01/02/13 21:58, Mohit Anchlia wrote: If I set maxInactivityDuration to 0 on server and leave clients with some value then which overrides? Would server override client in this case? -- Andreas Calvo Gómez

Re: Channel was inactive for too long error

2013-02-01 Thread Andreas Calvo Gómez
Take a look at http://activemq.apache.org/configuring-wire-formats.html to see an example. On 31/01/13 20:46, Mohit Anchlia wrote: Thanks! but I am not even able to add maxInactivityDuration to the uri. Is there a workaround for that? On Thu, Jan 31, 2013 at 11:17 AM, Andreas Calvo Gómez

Re: Channel was inactive for too long error

2013-01-31 Thread Andreas Calvo Gómez
Sorry, I meant 5.1.2 on the other computer, run ant producer -Dtopic=true -Dmax=99 On 31/01/13 20:17, Andreas Calvo Gómez wrote: 5.1.2 on the other computer, run ant consumer -Dtopic=true -Dmax=99 -- Andreas Calvo Gómez Systems Engineer Scytl Secure Electronic Voting Plaça Gal·la

Re: Channel was inactive for too long error

2013-01-31 Thread Andreas Calvo Gómez
Exception: Broker: BROKER - Client: CLIENT already connected on URI) and pending message will not flow to reach the desired number. On 31/01/13 20:01, Mohit Anchlia wrote: If this is closed I am assuming there is a workaround. On Thu, Jan 31, 2013 at 10:52 AM, Andreas Calvo Gómez < an

Re: Channel was inactive for too long error

2013-01-31 Thread Andreas Calvo Gómez
ug files, is anyone aware of this? It also appears others either disable it or increase the inactivity period as workaround. -- *Christian Posta* http://www.christianposta.com/blog twitter: @christianposta -- *Christian Posta* http://www.christianposta.com/blog twitter: @christianposta -

Pending Queue Size does not flush

2012-10-25 Thread Andreas Calvo Gómez
Hello, We are facing a behavior where subscribers' Pending Queue Size increases, it seems that no ACKs are dispatched and flow ratio decreases almost to zero. Our topology is somehow peculiar: We have several places, each one containing multiple machines. Each machine has a local broker with a

Re: #AMQ-3353: Durable subscribers on durable topics don't receive messages after network disconnect

2012-09-07 Thread Andreas Calvo
Wrong link: https://issues.apache.org/jira/browse/AMQ-3353 El vie 07 sep 2012 11:57:12 CEST, Andreas Calvo escribió: Hi, We are still affected by this issue. Taking a look at the code, it seems that upon undesired disconnection and reconnection, all durable subscribers affected are lost. Using

#AMQ-3353: Durable subscribers on durable topics don't receive messages after network disconnect

2012-09-07 Thread Andreas Calvo
Hi, We are still affected by this issue. Taking a look at the code, it seems that upon undesired disconnection and reconnection, all durable subscribers affected are lost. Using JMX we're able to see how the NC is lost and not successfully recreated. However, we've identified that even standa

small applications to retrieve/resend all messages

2012-09-06 Thread Andreas Calvo
Hi, I want to create a small application that listens in a specific topic and react if some consumer request either a missing message or all transmitted messages. This comes because using ActiveMQ along with retroactive consumer is limited to the subscription recovery policy, which cannot be un

hub-n-spoke with updateClusterClients' failover support over brokers

2012-02-03 Thread Andreas Calvo
Hi, Is it possible to update the list of running brokers for another brokers? Taking the next scenario: consumer/producer 1 < - > embedded broker 1 < - > broker A < - > broker B < - > embedded broker 1 < - > consumer/producer 2 The main goal is to give a list of running brokers to embedded broke

Re: Durable subscriptions not surviving network disconnect

2011-07-21 Thread Andreas Calvo
Thank you for answering. This is the scenario: (embedded) broker A <---> standalone broker B <---> (embedded) broker C it is a hub-and-spoke network of brokers, so broker B gets and dispatches all messages. we start establishing the connection for all the brokers and start sending messages from

Re: Durable subscriptions not surviving network disconnect

2011-07-20 Thread Andreas Calvo
We've been playing a little bit more, and we faced another issue. Having a network of brokers, two of them embedded on a java application connect to a central standalone activemq server, when we disconnect one of the embedded brokers from the network, it does not get the pending messages from the

Re: Durable subscriptions not surviving network disconnect

2011-07-06 Thread Andreas Calvo
Attached to JIRA issue: https://issues.apache.org/jira/browse/AMQ-3353 However, we've found that closing the session and reopening it solves the problem. -- View this message in context: http://activemq.2283324.n4.nabble.com/Durable-subscriptions-not-surviving-network-disconnect-tp3586149p364827

Re: Durable subscriptions not surviving network disconnect

2011-07-05 Thread Andreas Calvo
This JUnit test reproduces the error: http://pastebin.com/RXCVHzGt -- View this message in context: http://activemq.2283324.n4.nabble.com/Durable-subscriptions-not-surviving-network-disconnect-tp3586149p3646615.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.

Re: Durable subscriptions not surviving network disconnect

2011-07-05 Thread Andreas Calvo
I've started a JUnit Test case. Since it's the first time, it's not clean, may be buggy and the behavior is not what I really expected, but maybe it's a start. org.apache.activemq.usecases.DurableSubscriberWithNetworkDisconnectTest: http://pastebin.com/kr9uu0uE -- View this message in context:

Re: Durable subscriptions not surviving network disconnect

2011-07-01 Thread Andreas Calvo
Thanks Gary. I'm using ConnectionInfo and RemoveInfo to detect (re)connections. However, I'm trying to tell the client to (re)subscribe againt to the topic, like if I restarted the whole client, but it's not working. I've been playing with TransportListener and some advisory message (don't know w

Re: Durable subscriptions not surviving network disconnect

2011-06-30 Thread Andreas Calvo
Sorry for the late response. There is already a Jira issue (https://issues.apache.org/jira/browse/AMQ-3353). While I do know how to reproduce it using multicast brokers and producer and consumer from the example directory, I do not know how to make a junit case. If it's not difficult, I could try

Re: AMQ-3353 Durable subscribers on durable topics don't receive messages after network disconnect

2011-06-23 Thread Andreas Calvo
Same here. Seems to be a common problem with latest activemq versions -- View this message in context: http://activemq.2283324.n4.nabble.com/AMQ-3353-Durable-subscribers-on-durable-topics-don-t-receive-messages-after-network-disconnect-tp3582806p3619480.html Sent from the ActiveMQ - User mailing

Re: Durable subscriptions not surviving network disconnect

2011-06-23 Thread Andreas Calvo
We've been stuck with the same problem (in a different scenario). We've tried to replicate the same behavior using the examples on activemq (ant producer, ant consumer, and static-network-broker), and, as Joe said, the activemq seems to reconnect just fine, but the clients get stuck. -- View this

embedded broker autoreconnect

2011-06-22 Thread Andreas Calvo
I'm trying to get a simple embedded broker to connect thru multicast. However, after the consumer starts receiving messages, if a network problem happens (I disconnect the host from the network), the connection from the client to the embedded broker never recovers. So, it stops getting all the new