[jboss-jira] [JBoss JIRA] (WFLY-10688) Bad unit conversion of jdbc-network-timeout attribute

[Erich Duda (JIRA)]

    [ https://issues.jboss.org/browse/WFLY-10688?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13604981#comment-13604981 ] 

Erich Duda commented on WFLY-10688:
-----------------------------------

I tried to build WF from your PR branch but I still see following warning message in the log.

{code}
jdbc-network-timeout isn't properly configured: the recommended value is <= jdbc-lock-expiration
{code}

I think that problem is here \[1\]. The {{ActiveMQDefaultConfiguration.getDefaultJdbcNetworkTimeout()}} returns value in milliseconds but measurement unit is set to seconds. 

In Artemis upgrade branch, you fixed this issue by this change \[2\].

\[1\] https://github.com/wildfly/wildfly/pull/11355/files#diff-ad6d616ebe61ee6d1fdd687e5ca0caf7L271
\[2\] https://github.com/jmesnil/wildfly/commit/be3af696141c9a6755583a5d1ab82f851955cc64

> Bad unit conversion of jdbc-network-timeout attribute
> -----------------------------------------------------
>
>                 Key: WFLY-10688
>                 URL: https://issues.jboss.org/browse/WFLY-10688
>             Project: WildFly
>          Issue Type: Bug
>          Components: JMS
>    Affects Versions: 13.0.0.Final
>            Reporter: Erich Duda
>            Assignee: Jeff Mesnil
>            Priority: Blocker
>
> In the messaging subsystem there is an attribute {{jdbc-network-timeout}} with default value 20 seconds. However this parameter is passed to ActiveMQ Artemis as 20 000 000 milliseconds (20 000 seconds).
> For reproducing the issue just configure JDBC persistence store and attach debugger with breakpoint on {{AbstractJDBCDriver::connect}}.
> *Blocker* priority was set because it is regression against Wildfly 12.



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