[jboss-jira] [JBoss JIRA] (WFWIP-72) Critical IO Error ... when starting Artemis in colocated topology with HA JDBC store

Miroslav Novak (JIRA) issues at jboss.org
Tue Jul 24 09:14:00 EDT 2018


Miroslav Novak created WFWIP-72:
-----------------------------------

             Summary: Critical IO Error ... when starting Artemis in colocated topology with HA JDBC store
                 Key: WFWIP-72
                 URL: https://issues.jboss.org/browse/WFWIP-72
             Project: WildFly WIP
          Issue Type: Bug
          Components: Artemis, JMS
            Reporter: Miroslav Novak
            Assignee: Martyn Taylor
            Priority: Blocker


One of the servers in collocated HA topology with JDBC store can fail on critical IO exception and stop itself.  

This was hit on Artemis 1.5.5.012 and WF: https://github.com/jmesnil/wildfly - WFLY-9513_messaging_jdbc_HA_shared-store branch. 

Test scenario:
* Start 2 WF/EAP servers in collocated topology with Artemis HA JDBC store
* Start client which are sending and consuming messages to/from queue from 1st server

Result:
There is intermittent failure when client start to send/receive messages on 1st server. 1st fails on Critical IO Error with exception:
{code}
10:19:27,965 WARN  [org.apache.activemq.artemis.journal] (Thread-0 (ActiveMQ-server-org.apache.activemq.artemis.core.server.impl.ActiveMQServerImpl$3 at 7de7cbe3)) AMQ142021: Error on IO callback, null
10:19:27,965 WARN  [org.apache.activemq.artemis.core.server] (Thread-0 (ActiveMQ-server-org.apache.activemq.artemis.core.server.impl.ActiveMQServerImpl$3 at 7de7cbe3)) AMQ222010: Critical IO Error, shutting down the server. file=org.apache.activemq.artemis.jdbc.store.file.JDBCSequentialFile at 407c5d8f, message=Error writing to JDBC file.: java.lang.NullPointerException
        at org.apache.activemq.artemis.jdbc.store.file.JDBCSequentialFile.internalWrite(JDBCSequentialFile.java:161) [artemis-jdbc-store-1.5.5.jbossorg-012.jar:1.5.5.jbossorg-012]
        at org.apache.activemq.artemis.jdbc.store.file.JDBCSequentialFile.internalWrite(JDBCSequentialFile.java:186) [artemis-jdbc-store-1.5.5.jbossorg-012.jar:1.5.5.jbossorg-012]
        at org.apache.activemq.artemis.jdbc.store.file.JDBCSequentialFile.lambda$scheduleWrite$1(JDBCSequentialFile.java:197) [artemis-jdbc-store-1.5.5.jbossorg-012.jar:1.5.5.jbossorg-012]
        at org.apache.activemq.artemis.utils.OrderedExecutorFactory$OrderedExecutor$ExecutorTask.run(OrderedExecutorFactory.java:122) [artemis-commons-1.5.5.jbossorg-012.jar:1.5.5.jbossorg-012]
        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) [rt.jar:1.8.0_171]
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) [rt.jar:1.8.0_171]
        at java.lang.Thread.run(Thread.java:748) [rt.jar:1.8.0_171]
{code}

NPE happens at {{JDBCSequentialFile.internalWrite}} line 161:
{code}
private synchronized int internalWrite(byte[] data, IOCallback callback) {
      try {
         open();
161         synchronized (writeLock) { <-- NPE is thrown here
...
{code}
. 

Attaching logs from the test.



--
This message was sent by Atlassian JIRA
(v7.5.0#75005)


More information about the jboss-jira mailing list