[prev in list] [next in list] [prev in thread] [next in thread] 

List:       activemq-dev
Subject:    [GitHub] activemq-artemis issue #595: [ARTEMIS-591] Wrong XAException return code whe...
From:       bayern39 <git () git ! apache ! org>
Date:       2016-06-30 7:22:00
Message-ID: 20160630072200.F2CA8DFF03 () git1-us-west ! apache ! org
[Download RAW message or body]

Github user bayern39 commented on the issue:

    https://github.com/apache/activemq-artemis/pull/595
  
    @clebertsuconic  Hi clebert, i have considered your comment,what do you mean is \
that the RM can only   find the old transactions whose lifetime are older than the \
default transaction timeout by means of scanning the started transactions every \
transaction-timeout-scan-period time,so it can not find the time out transactions \
whose privacy attribute of  timeout  is not default transaction timeout in server and \
smaller than  default transaction timeout. So when the smaller time out transaction \
is over, the server can not find it  immediately ,it must await the RM scans \
it.Right?   
    I have communicated with the origin issue reporter,the reason why he posed the \
issue is not as a trouble of specific Artemis behavior,the issue is about asking for \
Artemis being better compliant with XA specification in error code.So i am \
considering whether it is needed to change the  Artemis behavior , because the \
present solution seems have not influence.We can still configure the  \
transaction-timeout-scan-period  with small value to cope with self-defined timeout \
attribute.This is my point, maybe have some mistakes,What do you think about it? 


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---


[prev in list] [next in list] [prev in thread] [next in thread]