Re: Messages are kept in Pending queue for durable topic subscribers.

2015-01-29 Thread mclaudio76
artnaseef wrote > OK, so first off, be cautious of the meaning of the broker statistics. > Negative consumer counts is definitely a concern and worthy of a bug > report (hopefully with a unit test that replicates the problem - or at > least simple instructions to reproduce it). But some of the ot

Re: Messages are kept in Pending queue for durable topic subscribers.

2015-01-28 Thread mclaudio76
Hi artnaseef, messages are meant to be simply notification of completion of remote jobs sent to the client. So, loss of messages hasn't much impact on the normal activity of the clients. This loss is detected by the fact that durable subscribers (which go off and on line) have in their "Pending qu

Re: Messages are kept in Pending queue for durable topic subscribers.

2015-01-22 Thread mclaudio76
It's a standalone broker. Unfortunately, I cannot reproduce the problem in a test enviroment, mainly because I cannot generate all the traffic the production broker has to support. Anyway, within the limits of a test simulation, the presence or not of Advisory topics seemed not to influence the beh

Re: Messages are kept in Pending queue for durable topic subscribers.

2015-01-22 Thread mclaudio76
tbain98 wrote > So what happens when the subscriber comes back online? Are other messages > delivered, just not the ones that were sent while the subscriber was > offline? After the subscriber comes back online, do you still see those > messages pending in the JMX stats and/or the web console? I

Messages are kept in Pending queue for durable topic subscribers.

2015-01-16 Thread mclaudio76
Hello everyone, I have some durable topic subscribers of a certain topic ABC. When a subscriber goes offline, from ActiveMQ console I can see that messages routed to topic ABC are listed - correctly - even in ABC:subscriber's pending queue. The problem is that many messages aren't sent to the subs

Re: Openwire transport listening on two or more different ports.

2015-01-14 Thread mclaudio76
OK, sorry... I wasn't able to find documentation by myself. -- View this message in context: http://activemq.2283324.n4.nabble.com/Openwire-transport-listening-on-two-or-more-different-ports-tp4689882p4689916.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.

Re: Openwire transport listening on two or more different ports.

2015-01-14 Thread mclaudio76
ok, but how ? is it just enough to place two definitions of openwire transport in configuration file ? Can you give me an example ? -- View this message in context: http://activemq.2283324.n4.nabble.com/Openwire-transport-listening-on-two-or-more-different-ports-tp4689882p4689911.html Sen

Openwire transport listening on two or more different ports.

2015-01-14 Thread mclaudio76
Good morning, i need your help on a configuration detail. Is it possibile to configurate ActiveMQ so that openwire protocol listens on both port A and port B, on the same interface ? Actually I have setup openwire transport as usual: I wonder if is possibile to specify two entry to have for exa

[Active MQ 5.10] [Bug?] Messages aren't dequeued when wildcards are used.

2014-12-30 Thread mclaudio76
Hi there, I need your precious help again. Scenario: I want to listen to all Advisory topics, read messages and, at the moment, I need only to print them. I wrote this code: -- private static String ADVISORY_TOPIC = "ActiveMQ.Adviso

Re: Programmatically reading ActiveMQ.Advisory.xyz topics

2014-12-29 Thread mclaudio76
Hi tbain98, thanks a lot for your reply. So, the only way to read those advisory messages is to create and connect with a subscriber; that's ok for me. I've noticed that if I restart the broker (and I'm going to perform such operation at every sunday midnight) Advisory topics & queues are automati

Programmatically reading ActiveMQ.Advisory.xyz topics

2014-12-28 Thread mclaudio76
Hi there, I just want to read ActiveMQ.Advisory.xyz topics programmatically and try to log them on a database for further analysis. The problem is that I don't want to create a listener so that I can receive and log messages as they arrive; I want just connect to the topic at a given moment and re