[jbossts-issues] [JBoss JIRA] (JBTM-1938) Caching of datasource for JDBC store incompatible with WildFly :reload operation

[RH Bugzilla Integration (JIRA)]

    [ https://issues.jboss.org/browse/JBTM-1938?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12823117#comment-12823117 ] 

RH Bugzilla Integration commented on JBTM-1938:
-----------------------------------------------

Ondrej Chaloupka <ochaloup at redhat.com> made a comment on [bug 1009931|https://bugzilla.redhat.com/show_bug.cgi?id=1009931]

Hi Tom,

I agree this is different issue which is related to module dependency management in AS rather than to transactions subsystem.
Just to clarify the problem happens to me just after the reload. I didn't experience the problem after the initial load. But it could be a coincidence.

I will report this problem as a new bz and I will verify this one.

Thanks
Ondra
                
> Caching of datasource for JDBC store incompatible with WildFly :reload operation
> --------------------------------------------------------------------------------
>
>                 Key: JBTM-1938
>                 URL: https://issues.jboss.org/browse/JBTM-1938
>             Project: JBoss Transaction Manager
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Recovery
>            Reporter: Tom Jenkinson
>            Assignee: Tom Jenkinson
>             Fix For: 4.17.11, 5.0.0.M5
>
>
> The JDBC object store makes a performance optimization to cache the datasource it obtains connections from. Unfortunately this is not compatible with WildFly :reload (see linked bugzilla for stack trace).
> Without further performance constraints I have moved to obtaining a reference each time. If there are performance issues we might need to provide a way for the subsystem to invalidate the cached reference when :reload is called.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira