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

[Kabir Khan (JIRA)]

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

Kabir Khan commented on WFLY-10688:
-----------------------------------

[~eduda] is this a blocker for the beta or just for WF14?

If it is not for the beta please add the blocker-WF14 label so it is clear when looking at https://issues.jboss.org/issues/?filter=12335707 that it is not for the beta (actually this is no longer an issue now that I have resolved it). If it is for the beta, I guess we ought to clone it into a JBEAP issue and [~jmesnil] backports it.

> 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
>             Fix For: 14.0.0.CR1
>
>
> 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)