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

    Details

    • Type: Bug
    • Status: Resolved (View Workflow)
    • Priority: Blocker
    • Resolution: Done
    • Affects Version/s: None
    • Fix Version/s: 14.0.0.Final
    • Component/s: JMS
    • Labels:
      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.

        Gliffy Diagrams

          Attachments

            Activity

              People

              • Assignee:
                jmesnil Jeff Mesnil
                Reporter:
                mnovak Miroslav Novak
              • Votes:
                0 Vote for this issue
                Watchers:
                1 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: