[jira] [Commented] (ARTEMIS-4238) transaction timeout ActivationConfigProperty is no longer working

["Justin Bertram (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/ARTEMIS-4238?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17711076#comment-17711076 ] 

Justin Bertram commented on ARTEMIS-4238:
-----------------------------------------

For what it's worth the functionality of the {{transactionTimeout}} activation configuration property was removed _on purpose_ due to the fact that the RA was using the transaction manager to set the timeout. This was reported via ARTEMIS-3707 and ARTEMIS-1487. The transaction manager is to be used by the *application server* and not by components like resource adapters. Java/Jakarta EE servers can and should have a way to set the transaction timeout for EJBs in general and MDBs in particular.

That said, I can appreciate that some users rely on this behavior so it arguably should have been deprecated and removed later instead of having the functionality removed completely all at once.

> transaction timeout ActivationConfigProperty is no longer working
> -----------------------------------------------------------------
>
>                 Key: ARTEMIS-4238
>                 URL: https://issues.apache.org/jira/browse/ARTEMIS-4238
>             Project: ActiveMQ Artemis
>          Issue Type: Bug
>          Components: JMS
>    Affects Versions: 2.28.0
>            Reporter: Emmanuel Hugonnet
>            Priority: Major
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> ARTEMIS-3707 has created a regression where the transactionTimeout ActivationConfigProperty is no  longer working properly



--
This message was sent by Atlassian Jira
(v8.20.10#820010)