Re: Jconsole Topic and Queue

Hey, Waiting for a response... -- View this message in context: http://activemq.2283324.n4.nabble.com/Jconsole-Topic-and-Queue-tp4672799p4673139.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.

Re: Discarded messages and Expired messages.

one operates at the broker level, the other at the destination level. Also, messages that fail redelivery go to the dlq so not processing expired at the policy level just eliminates some. It all depends on what you want to achieve? what do you wish for? On 22 October 2013 14:48, Sophia Wright

Persistent message througput when using sessions/connections

Hello, we are trying to achieve hight througput using persistent messages together with sync send and queues. However we realised there are some limitations that could be maybe resolved or explained but you. Scenario 1 - Speed ok , unusable with springs integration Consumers and producers are

Big difference in throughput when using dedicated connection vs sessions and sendsync pers messages.

Hello, we are trying to achieve hight througput using persistent messages together with sync send and queues. However we realised there are some limitations that could be maybe resolved or explained but you. Scenario 1 - Speed ok , unusable with springs integration Consumers and producers are

Re: Replicated LevelDB Store filling up memory

One of the slaves falling way behind is probably the reason your seeing that. There is a JMX MBean (with object name attributes 'Service=PersistenceAdapter,view=Replication' that provides a 'slaves' attribute which will tell you each slaves journal replication 'position' which you can then

Re: Stuck messages : Pending Queue Size stopped to be dispatched to Dispatched Queue Size

Hi, i upgraded yesterday to 5.9.0 version and i can't reproduce the problem of stuck messages. -- View this message in context: http://activemq.2283324.n4.nabble.com/Stuck-messages-Pending-Queue-Size-stopped-to-be-dispatched-to-Dispatched-Queue-Size-tp4673046p4673153.html Sent from the

Re: Transport Connection EOFs

I believe that those exceptions occur when a client does not disconnect from the broker gracefully. Verify that your client is making the appropriate close call on the connection. Do you have STOMP based clients that are frequently connecting and disconnecting? Thanks, Paul On Wed, Oct 23, 2013

non-persistence msgs very slow with levedb

We see only 1-4 per second msgs when we use leveldb and msg are non-persistence and consumers are running. With kahadb the rate is 6000 msgper/sec. what could be the reason for this big difference and leveldb should even play a role since there are non-persistence msg right? -- View this

Re: Failover on no allocated disk space left?

Thanks ceposta. I was hoping that there was either an official solution to the issue or that it was a confirmed bug. I hope this gets reviewed in the future because failover behaviour should be consistent even in such a case. -- View this message in context:

No ERROR level logs when failover is triggered

Hi I currently have a 5.8.0 PooledConnectionFactory configured with 2 different brokers using the failover protocol. I have noticed that when the client fails to connect to first broker (Or any at all should all of them be down) it will silently keep retrying in the background. Most of this

Re: No ERROR level logs when failover is triggered

On 10/23/2013 02:45 PM, ByteFlinger wrote: Hi I currently have a 5.8.0 PooledConnectionFactory configured with 2 different brokers using the failover protocol. I have noticed that when the client fails to connect to first broker (Or any at all should all of them be down) it will silently keep

Re: Are Scheduled Messages persistent ?

I am having this same problem myself. Was there any resolution? -- View this message in context: http://activemq.2283324.n4.nabble.com/Are-Scheduled-Messages-persistent-tp4665977p4673163.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.

Re: Failover on no allocated disk space left?

it may make sense to have an option to determine the type of exception we throw when we are resource constrained. ResourceAllocation is a jms exception so it bubbles up to the app. But we could have an IO exception in that case that would trigger failover. If the persistence adapter hits a real

Re: Message Queue Slows Down after 2 million plus message

What size are the messages? What persistence store (KahaDB, LevelDB, JDBC) are you using? Are you using 5.7.0 Apache release or other? On Oct 22, 2013, at 3:34 PM, wcpolicarpio walter.policar...@morgansolar.com wrote: Hi Everyone, I have a message queue named amq570queue, after

Re: Transport Connection EOFs

Confirmed.. if you don't clean up your session and connection cleanly, the broker will warn for you. Its usually indicative of a client that is mis-coded. Look for exceptions being thrown.. a lot of times folks don't have the finally { } block defined to clean up JMS objects. Also.. check out

Re: Persistent message througput when using sessions/connections

Hi Michal- Lot of stuff to try to cover here.. but in short.. performance tuning is a tough thing to cover in an email. 1. Separate the testing of perf through the broker from your app, so you can get a baseline. Look into the activemq-perf tooling. 2. 40 producers and 40 consumers into one

Re: non-persistence msgs very slow with levedb

Double check that you aren't hitting a memory limit and the broker swapping the messages to the temp store. Either way, it shouldn't be that much slower. Do you have a reproducible unit test that you could share to open a ticket? On Oct 23, 2013, at 12:52 PM, kal123 kpfininf...@gmail.com