[jboss-jira] [JBoss JIRA] (WFWIP-116) jdbc-network-timeout is set in seconds instead of milliseconds causing Artemis to fail on Critical IO Error when jdbc store is used

[Miroslav Novak (JIRA)]

     [ https://issues.jboss.org/browse/WFWIP-116?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Miroslav Novak updated WFWIP-116:
---------------------------------
    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:
{code}
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);
{code}
which sets this timeout properly in milliseconds.

  was:
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 is:
{code}
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);
{code}
which sets this timeout properly in milliseconds.



> jdbc-network-timeout is set in seconds instead of milliseconds causing Artemis to fail on Critical IO Error when jdbc store is used
> -----------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: WFWIP-116
>                 URL: https://issues.jboss.org/browse/WFWIP-116
>             Project: WildFly WIP
>          Issue Type: Bug
>          Components: JMS
>            Reporter: Miroslav Novak
>            Assignee: Jeff Mesnil
>            Priority: Blocker
>
> 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:
> {code}
> 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);
> {code}
> which sets this timeout properly in milliseconds.



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