Uploaded image for project: 'WildFly'
  1. WildFly
  2. WFLY-2789

Remote client transaction timeout values are overwrote by hardcoded values

    XMLWordPrintable

Description

    The EJB3 interceptor is not using client values for timeouts, this is a problem for users trying to use EJB for transaction propagation.

    Refer to the code in https://github.com/wildfly/wildfly/blob/master/ejb3/src/main/java/org/jboss/as/ejb3/remote/EJBRemoteTransactionPropagatingInterceptor.java:
    private void createOrResumeXidTransaction(final XidTransactionID xidTransactionID) throws Exception {
    final TransactionManager transactionManager = this.ejbRemoteTransactionsRepository.getTransactionManager();
    final Transaction alreadyCreatedTx = this.ejbRemoteTransactionsRepository.getImportedTransaction(xidTransactionID);
    if (alreadyCreatedTx != null)

    { // resume the already created tx transactionManager.resume(alreadyCreatedTx); }

    else

    { // begin a new tx and add it to the tx repository // TODO: Fix the tx timeout (which currently is passed as 300 seconds) final Transaction newSubOrdinateTx = this.ejbRemoteTransactionsRepository.importTransaction(xidTransactionID, 300); // associate this tx with the thread transactionManager.resume(newSubOrdinateTx); }

    }

    Attachments

      Issue Links

        is duplicated by

        Bug - A problem that impairs or prevents the functions of the product. WFLY-2852 JBoss 7 - EJB Remote Transaction Timeout

        • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
        • Closed
        is related to

        Bug - A problem that impairs or prevents the functions of the product. WFLY-5348 Propagate transaction timeout value for distributed transaction when using JTA and EJB remoting

        • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
        • Closed
        relates to

        Bug - A problem that impairs or prevents the functions of the product. JBEAP-4632 JTA does not set transaction timeout for XAResource for propagated transactions

        • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
        • Closed

        Activity

          People

            dlloyd@redhat.com David Lloyd
            rhn-support-jolee Johnathon Lee
            Votes:
            0 Vote for this issue
            Watchers:
            7 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: