You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Yakov Zhdanov (JIRA)" <ji...@apache.org> on 2015/06/19 10:07:00 UTC
[jira] [Updated] (IGNITE-1035) JTA treats the timeout value in
seconds than Ignite uses mSec
[ https://issues.apache.org/jira/browse/IGNITE-1035?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Yakov Zhdanov updated IGNITE-1035:
----------------------------------
Assignee: (was: Artem Shutak)
> JTA treats the timeout value in seconds than Ignite uses mSec
> -------------------------------------------------------------
>
> Key: IGNITE-1035
> URL: https://issues.apache.org/jira/browse/IGNITE-1035
> Project: Ignite
> Issue Type: Bug
> Reporter: Yakov Zhdanov
> Fix For: 1.1.4
>
>
> JTA treats the timeout value in seconds than Ignite uses mSec, effectively reducing the specified (in the container) value by 1000 times
> Need to check if this is the case and add multiplier if necessary.
> User list thread:
> http://apache-ignite-users.70518.x6.nabble.com/Ignite-as-L2-cache-in-JBoss6-tp538.html
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)