]
Jeff Mesnil moved WFWIP-116 to WFLY-10860:
------------------------------------------
Project: WildFly (was: WildFly WIP)
Key: WFLY-10860 (was: WFWIP-116)
Component/s: JMS
(was: JMS)
jdbc-network-timeout is set in seconds instead of milliseconds
causing Artemis to fail on Critical IO Error when jdbc store is used
-----------------------------------------------------------------------------------------------------------------------------------
Key: WFLY-10860
URL:
https://issues.jboss.org/browse/WFLY-10860
Project: WildFly
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/mai...
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.