Uploaded image for project: 'AMQ Broker'
  1. AMQ Broker
  2. ENTMQBR-606

Migration - Artemis journal must be multiply of disc sector size

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Obsolete
    • Icon: Major Major
    • AMQ 7.0.1.GA
    • A-MQ 7.0.0.ER16
    • None
    • None

      In EAP 7.0 attribute journal-file-size had to be multiply of 512.
      In EAP 7.1 attribute journal-file-size must be multiply of disc sector size which can be 512, 4096 or in case of NFS it depends on mount option rsize, and wsize.

      So if configuration for EAP 7.0 contained journal-file-size which could not be divided by 4096 then EAP 7.1 will not start with this configuration and fail:

      14:02:16,028 ERROR [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 73) AMQ224000: Failure in initialisation: java.lang.IllegalArgumentException: Invalid journal-file-size 10240, It should be multiple of 32768
      	at org.apache.activemq.artemis.core.journal.impl.JournalImpl.<init>(JournalImpl.java:257) [artemis-journal-1.5.3.002-redhat-1.jar:1.5.3.002-redhat-1]
      	at org.apache.activemq.artemis.core.persistence.impl.journal.JournalStorageManager.init(JournalStorageManager.java:145) [artemis-server-1.5.3.002-redhat-1.jar:1.5.3.002-redhat-1]
      	at org.apache.activemq.artemis.core.persistence.impl.journal.AbstractJournalStorageManager.<init>(AbstractJournalStorageManager.java:216) [artemis-server-1.5.3.002-redhat-1.jar:1.5.3.002-redhat-1]
      	at org.apache.activemq.artemis.core.persistence.impl.journal.JournalStorageManager.<init>(JournalStorageManager.java:104) [artemis-server-1.5.3.002-redhat-1.jar:1.5.3.002-redhat-1]
      	at org.apache.activemq.artemis.core.server.impl.ActiveMQServerImpl.createStorageManager(ActiveMQServerImpl.java:1863) [artemis-server-1.5.3.002-redhat-1.jar:1.5.3.002-redhat-1]
      	at org.apache.activemq.artemis.core.server.impl.ActiveMQServerImpl.initialisePart1(ActiveMQServerImpl.java:2000) [artemis-server-1.5.3.002-redhat-1.jar:1.5.3.002-redhat-1]
      	at org.apache.activemq.artemis.core.server.impl.LiveOnlyActivation.run(LiveOnlyActivation.java:62) [artemis-server-1.5.3.002-redhat-1.jar:1.5.3.002-redhat-1]
      	at org.apache.activemq.artemis.core.server.impl.ActiveMQServerImpl.internalStart(ActiveMQServerImpl.java:520) [artemis-server-1.5.3.002-redhat-1.jar:1.5.3.002-redhat-1]
      	at org.apache.activemq.artemis.core.server.impl.ActiveMQServerImpl.start(ActiveMQServerImpl.java:469) [artemis-server-1.5.3.002-redhat-1.jar:1.5.3.002-redhat-1]
      	at org.apache.activemq.artemis.jms.server.impl.JMSServerManagerImpl.start(JMSServerManagerImpl.java:412) [artemis-jms-server-1.5.3.002-redhat-1.jar:1.5.3.002-redhat-1]
      	at org.wildfly.extension.messaging.activemq.jms.JMSService.doStart(JMSService.java:199) [wildfly-messaging-activemq-7.1.0.Alpha1-redhat-13.jar:7.1.0.Alpha1-redhat-13]
      	at org.wildfly.extension.messaging.activemq.jms.JMSService.access$000(JMSService.java:63) [wildfly-messaging-activemq-7.1.0.Alpha1-redhat-13.jar:7.1.0.Alpha1-redhat-13]
      	at org.wildfly.extension.messaging.activemq.jms.JMSService$1.run(JMSService.java:97) [wildfly-messaging-activemq-7.1.0.Alpha1-redhat-13.jar:7.1.0.Alpha1-redhat-13]
      	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) [rt.jar:1.8.0_111]
      	at java.util.concurrent.FutureTask.run(FutureTask.java:266) [rt.jar:1.8.0_111]
      	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [rt.jar:1.8.0_111]
      	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [rt.jar:1.8.0_111]
      	at java.lang.Thread.run(Thread.java:745) [rt.jar:1.8.0_111]
      	at org.jboss.threads.JBossThread.run(JBossThread.java:320) [jboss-threads-2.2.1.Final-redhat-1.jar:2.2.1.Final-redhat-1]
      

      This issue is caused by https://issues.apache.org/jira/browse/ARTEMIS-937.

      Artemis should be clever in this and round value of journal-file-size to nearest value divisible by disc sector size (alignment) automatically.

      This is blocker from migration point of view from EAP 6.4/EAP 7.0 -> EAP 7.1.

            rh-ee-ataylor Andy Taylor
            mtaylor1@redhat.com Martyn Taylor (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: