[jbossts-issues] [JBoss JIRA] (JBTM-2863) Bug in SPI for tracking transaction state association changes

Michael Musgrove (JIRA) issues at jboss.org
Wed Mar 22 11:32:00 EDT 2017

     [ https://issues.jboss.org/browse/JBTM-2863?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Michael Musgrove closed JBTM-2863.
    Resolution: Won't Fix

The primary use case for this feature was JPA which has since been rewritten to use WFTC notifications instead. I am closing this bug as "will not fix" and have deprecated the feature (see JBTM-2869).

> Bug in SPI for tracking transaction state association changes
> -------------------------------------------------------------
>                 Key: JBTM-2863
>                 URL: https://issues.jboss.org/browse/JBTM-2863
>             Project: JBoss Transaction Manager
>          Issue Type: Bug
>          Components: SPI
>    Affects Versions: 5.5.3.Final
>            Reporter: Michael Musgrove
>            Assignee: Michael Musgrove
>             Fix For: 5.later
> JBTM-2343 introduced a feature for observing transaction state changes (requested by JPA). Listeners register interest in particular events (ASSOCIATED and DISASSOCIATING). However, BaseTransactionManagerDelegate will notify listeners for either event even if they only subscribed for one of them. For example if a listener subscribes for thread to transaction associations only it will also receive disassociation notifications.
> In addition, the current event types are restricted to a single java enum (org.jboss.tm.listener.EventType). Since java enums are not extensible the solution needs to be tweaked so that we can easily add new event types.

This message was sent by Atlassian JIRA

More information about the jbossts-issues mailing list