[
https://issues.apache.org/jira/browse/AMQ-7118?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16735270#comment-16735270
]
Alan Protasio commented on AMQ-7118:
------------------------------------
I think just found the problem...
The test is relying in the size of the hostname of your host...
Ex (long hostname):
sudo hostname hostnamehostnamehostname
Running org.apache.activemq.bugs.AMQ7118Test
Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 2.483 sec <<<
FAILURE! - in org.apache.activemq.bugs.AMQ7118Test
testCompaction(org.apache.activemq.bugs.AMQ7118Test) Time elapsed: 2.094 sec
<<< FAILURE!
java.lang.AssertionError: expected:<21> but was:<22>
at org.junit.Assert.fail(Assert.java:88)
at org.junit.Assert.failNotEquals(Assert.java:834)
at org.junit.Assert.assertEquals(Assert.java:645)
at org.junit.Assert.assertEquals(Assert.java:631)
at org.apache.activemq.bugs.AMQ7118Test.checkFiles(AMQ7118Test.java:193)
at org.apache.activemq.bugs.AMQ7118Test.testCompaction(AMQ7118Test.java:116)
Ex (short hostname):
sudo hostname hostname
Running org.apache.activemq.bugs.AMQ7118Test
Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 15.718 sec <<<
FAILURE! - in org.apache.activemq.bugs.AMQ7118Test
testCompaction(org.apache.activemq.bugs.AMQ7118Test) Time elapsed: 15.372 sec
<<< FAILURE!
org.junit.ComparisonFailure: expected:<db-3[3].log> but was:<db-3[0].log>
at org.junit.Assert.assertEquals(Assert.java:115)
at org.junit.Assert.assertEquals(Assert.java:144)
at org.apache.activemq.bugs.AMQ7118Test.checkFiles(AMQ7118Test.java:194)
at org.apache.activemq.bugs.AMQ7118Test.testCompaction(AMQ7118Test.java:135)
But the test runs successfully with if i set the hostname to "hostnamehostname"
sudo hostname hostnamehostname
-------------------------------------------------------
T E S T S
-------------------------------------------------------
Running org.apache.activemq.bugs.AMQ7118Test
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 23.281 sec - in
org.apache.activemq.bugs.AMQ7118Test
Results :
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0
> KahaDB store limit can be exceeded with durable subscribers.
> ------------------------------------------------------------
>
> Key: AMQ-7118
> URL: https://issues.apache.org/jira/browse/AMQ-7118
> Project: ActiveMQ
> Issue Type: Bug
> Components: KahaDB
> Affects Versions: 5.16.0, 5.15.8
> Environment: JDK 8
> Reporter: Jamie goodyear
> Priority: Critical
> Fix For: 5.16.0, 5.15.8
>
> Attachments: kahaCommands.jpg
>
>
> KahaDB store limit can be exceeded with durable subscribers.
> AMQ with store limit set, we can observe that the usage continues to increase
> AFTER PFC is engaged. Given time, this growth stabilizes. The issue of having
> exceeded the store limit remains.
> See below output from KahaDB dump in attachments:
> This appears to be caused by checkpointAckMessageFileMap. The log files are
> not GC'd, and the KAHA_ACK_MESSAGE_FILE_MAP_COMMAND is replicated and the DB
> log files continue to expand - this can become exponential. Side effect of
> also not checking storage size in checkpoint update can cause the DB log
> files to exceed any set limits. The real critical part is the duplicated and
> leaking Kaha messages which appears to happen with durable subscribers.
>
>
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
