Uploaded image for project: 'WildFly'
  1. WildFly
  2. WFLY-10860

jdbc-network-timeout is set in seconds instead of milliseconds causing Artemis to fail on Critical IO Error when jdbc store is used

    XMLWordPrintable

Details

    • Bug
    • Status: Closed (View Workflow)
    • Blocker
    • Resolution: Done
    • None
    • 14.0.0.Final
    • JMS
    • None

    Description

      jdbc-network-timeout is set in seconds instead of milliseconds in:
      https://github.com/wildfly/wildfly/blob/master/messaging-activemq/src/main/java/org/wildfly/extension/messaging/activemq/ServerAdd.java#L580

      This line must be removed as before it is:

      long networkTimeout = SECONDS.toMillis(JOURNAL_JDBC_NETWORK_TIMEOUT.resolveModelAttribute(context, model).asInt());
              // ARTEMIS-1493: Artemis API is not correct. the value must be in millis but it requires an int instead of a long.
      storageConfiguration.setJdbcNetworkTimeout((int)networkTimeout);
      

      which sets this timeout properly in milliseconds.

      Attachments

        Activity

          People

            jmesnil1@redhat.com Jeff Mesnil
            mnovak1@redhat.com Miroslav Novak
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: