[jboss-jira] [JBoss JIRA] (WFLY-10688) Bad unit conversion of jdbc-network-timeout attribute
Erich Duda (JIRA)
issues at jboss.org
Tue Jul 10 09:36:00 EDT 2018
[ https://issues.jboss.org/browse/WFLY-10688?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13603028#comment-13603028 ]
Erich Duda commented on WFLY-10688:
-----------------------------------
[~jmesnil] This issue was fixed in your integration branch with Artemis 2.x but it is still present in Wildfly master.
> 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
> Reporter: Erich Duda
> Assignee: Jeff Mesnil
> Priority: Blocker
> Labels: feature-branch-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.
> The issue was hit with Artemis 2.5.0 with https://github.com/jmesnil/wildfly/tree/WFLY-9407_upgrade_artemis_2.4.0_with_prefix (commit 51dd8102f103ccb0470a3cfc8713d3f9bdb1b65d)
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
More information about the jboss-jira
mailing list