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

[Miroslav Novak (JIRA)]

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

Miroslav Novak edited comment on WFLY-10688 at 7/18/18 9:32 AM:
----------------------------------------------------------------

[~kabirkhan] Erich is on PTO. This is not a blocker for beta however this must get fixed to WF14.


was (Author: mnovak):
[~kabirkhan] Erich is on PTO. This is not a blocker for beta as however this must get fixed to WF14.

> 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
>              Labels: blocker-WF14
>             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)