[ARTEMIS-687] AMQ222114: Unable to delete group binding info <groupid.messageId>: java.lang.IllegalStateException: Cannot find tx with id -1

• Type: Bug
• Status: Closed
• Priority: Minor
• Resolution: Duplicate
• Affects Version/s: 1.3.0
• Fix Version/s: 1.4.0
• Component/s: Broker
• Labels: failover logging reliability

Environment

artemis running inside an ubuntu docker container

• Assignee: Justin Bertram
• Reporter: david galloway
• Created: 18/Aug/16 09:58
• Updated: 03/Nov/16 20:41
• Resolved: 02/Sep/16 13:49

Description

This error is intermittently generated by artemis

2016-08-18 09:42:27,376 WARN  [org.apache.activemq.artemis.core.server] AMQ222114: Unable to delete group binding info 1bd53269-76bb-43a7-8024-bb8e70273c14494.ed051cbd-b410-493d-8c93-0af844264fa6: java.lang.IllegalStateException: Cannot find tx with id -1
	at org.apache.activemq.artemis.core.journal.impl.JournalImpl.appendCommitRecord(JournalImpl.java:1013) [artemis-journal-1.3.0.jar:1.3.0]
	at org.apache.activemq.artemis.core.journal.impl.JournalBase.appendCommitRecord(JournalBase.java:112) [artemis-journal-1.3.0.jar:1.3.0]
	at org.apache.activemq.artemis.core.journal.impl.JournalImpl.appendCommitRecord(JournalImpl.java:79) [artemis-journal-1.3.0.jar:1.3.0]
	at org.apache.activemq.artemis.core.persistence.impl.journal.AbstractJournalStorageManager.commitBindings(AbstractJournalStorageManager.java:650) [artemis-server-1.3.0.jar:1.3.0]
	at org.apache.activemq.artemis.core.server.group.impl.LocalGroupingHandler$GroupIdReaper.run(LocalGroupingHandler.java:449) [artemis-server-1.3.0.jar:1.3.0]
	at org.apache.activemq.artemis.utils.OrderedExecutorFactory$OrderedExecutor$ExecutorTask.run(OrderedExecutorFactory.java:103) [artemis-core-client-1.3.0.jar:1.3.0]
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [rt.jar:1.8.0_66]
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [rt.jar:1.8.0_66]
	at java.lang.Thread.run(Thread.java:745) [rt.jar:1.8.0_66]

this is artemis running as a single node

does not affect sending of message, but looks like some poorly implemented cleanup inside artemis.

When artmis is restarted, we see these warnings (1 for each of the above IllegalStateExceptions)

2016-08-18 14:10:16,554 WARN  [org.apache.activemq.artemis.journal] AMQ142015: Uncommitted transaction with id 4,295,204,073 found and discarded
2016-08-18 14:10:16,556 WARN  [org.apache.activemq.artemis.journal] AMQ142015: Uncommitted transaction with id 4,295,205,074 found and discarded
2016-08-18 14:10:16,558 WARN  [org.apache.activemq.artemis.journal] AMQ142015: Uncommitted transaction with id 4,295,206,075 found and discarded
2016-08-18 14:10:16,564 WARN  [org.apache.activemq.artemis.journal] AMQ142015: Uncommitted transaction with id 4,295,207,076 found and discarded
2016-08-18 14:10:16,565 WARN  [org.apache.activemq.artemis.journal] AMQ142015: Uncommitted transaction with id 4,295,208,077 found and discarded

Here is our broker.xml (nothing up our sleeves.., not real ips, ports or topic names etc.)

broker.xml

<?xml version="1.0" encoding="UTF-8" ?>

<configuration xmlns="urn:activemq" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="urn:activemq /schema/artemis-configuration.xsd">

  <jms xmlns="urn:activemq:jms">
    <queue name="DLQ"/>
    <queue name="ExpiryQueue"/>
    <topic name="organisation.internal.systemTopic"/>
  </jms>

  <core xmlns="urn:activemq:core">

    <name>192.168.56.101</name>

    <persistence-enabled>true</persistence-enabled>

    <journal-type>ASYNCIO</journal-type>

    <paging-directory>/var/lib/artemis/data/paging</paging-directory>

    <bindings-directory>/var/lib/artemis/data/bindings</bindings-directory>

    <journal-directory>/var/lib/artemis/data/journal</journal-directory>

    <large-messages-directory>/var/lib/artemis/data/large-messages</large-messages-directory>

    <connectors>
      <connector name="invm-connector">vm://0</connector>
      <connector name="server0-connector">tcp://10.10.10.100:345467</connector>
    </connectors>

    <acceptors>
      <acceptor name="invm-acceptor">vm://0</acceptor>
      <acceptor name="artemis">tcp://0.0.0.0:345467</acceptor>
    </acceptors>

    <mask-password>true</mask-password>
    <password-codec>com.organisation.artemis.MaskedPasswordDecoder</password-codec>


    <security-settings>
      <security-setting match="jms.*.organisation.internal.*">
        <permission type="createNonDurableQueue" roles="admin, client"/>
        <permission type="deleteNonDurableQueue" roles="admin"/>
        <permission type="createDurableQueue" roles="admin, client"/>
        <permission type="deleteDurableQueue" roles="admin"/>
        <permission type="consume" roles="admin, client"/>
        <permission type="send" roles="admin, client"/>
        <!-- we need this otherwise ./artemis data imp wouldn't work -->
        <permission type="manage" roles="admin"/>
      </security-setting>
    </security-settings>

    <address-settings>
      <!--default for catch all-->
      <address-setting match="#">
        <dead-letter-address>jms.queue.DLQ</dead-letter-address>
        <expiry-address>jms.queue.ExpiryQueue</expiry-address>
        <redelivery-delay>0</redelivery-delay>
        <max-size-bytes>10485760</max-size-bytes>
        <message-counter-history-day-limit>10</message-counter-history-day-limit>
        <address-full-policy>BLOCK</address-full-policy>
        <auto-create-jms-queues>false</auto-create-jms-queues>
        <auto-delete-jms-queues>false</auto-delete-jms-queues>
        <auto-create-jms-topics>false</auto-create-jms-topics>
        <auto-delete-jms-topics>false</auto-delete-jms-topics>
      </address-setting>
    </address-settings>

  </core>
</configuration>

Issue Links

• duplicates: ARTEMIS-699 Reaper seems to clog up the journal, and messages fail to deliver
• is duplicated by: ARTEMIS-699 Reaper seems to clog up the journal, and messages fail to deliver