[ https://issues.apache.org/activemq/browse/AMQ-526?page=all ]
Fritz Oconer reassigned AMQ-526:
Assignee: Fritz Oconer (was: Adrian Co)
> get TwoBrokerMulticastQueueTest to work
> ---
>
> Key: AMQ-526
Journaled JDBC checkpoint fails with java.io.IOException: Already started.
--
Key: AMQ-1063
URL: https://issues.apache.org/activemq/browse/AMQ-1063
Project: ActiveMQ
Iss
[
https://issues.apache.org/activemq/browse/AMQ-821?page=comments#action_37493 ]
[EMAIL PROTECTED] commented on AMQ-821:
Do not fix this using the unsafe keyword. If necessary, hard code the value.
The size of all primitives except Int
both would be perfect!
On 19 Nov 2006, at 20:07, [EMAIL PROTECTED] wrote:
Done. AMQ-1061. I put it is an critical for 4.2.0.
BTW, do you prefer discussing issues here or should they be
directly entered
in the tracker?
Thanks.
rajdavies wrote:
interesting - it appears that the paged
Memory usage jumps > 100% with durable subscription and stays there
---
Key: AMQ-1061
URL: https://issues.apache.org/activemq/browse/AMQ-1061
Project: ActiveMQ
Issue Type: Bug
Done. AMQ-1061. I put it is an critical for 4.2.0.
BTW, do you prefer discussing issues here or should they be directly entered
in the tracker?
Thanks.
rajdavies wrote:
>
> interesting - it appears that the paged in size of messages should
> also take into account the outstanding memory u
Using the store pending cursor, activemq.xml configured to use 200M of RAM
and Kaha store. JVM started with options -Xms512M -Xmx512M -Xmn100M.
Messages are 10KB in size, prefetch is default.
I am seeing the memory usage immediately jump up really high (>100) as soon
as a durable consumer is ac
Hi Jason,
On 19 Nov 2006, at 13:50, [EMAIL PROTECTED] wrote:
rajdavies wrote:
so the discussion is probably better on the dev list.
Apologies, I accidentally posted to the wrong one.
rajdavies wrote:
Now this is functionality that is due for official release in 4.2
Okay, so now I
rajdavies wrote:
> so the discussion is probably better on the dev list.
Apologies, I accidentally posted to the wrong one.
rajdavies wrote:
> Now this is functionality that is due for official release in 4.2
Okay, so now I understand why I cou