[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=12822871#comment-12822871 ] 

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,

I'm sorry I've found out that my previous statement is not true. 

The problem with reloading the server set with JDBC driver still occur in some cases. But there is a new error now. I'm running on EAP 6.2.0.ER6.

>From the log it seems to me as a timing issue. Time to time the data source could be bound after the transactions subsystem is started.

Console log:
15:05:13,272 INFO  [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-4) JBAS010403: Deploying JDBC-compliant driver class oracle.jdbc.OracleDriver (version 11.2)
15:05:13,283 INFO  [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-3) JBAS010400: Bound data source [java:jboss/datasources/jdbc-store]
15:05:13,284 ERROR [stderr] (Transaction Expired Entry Monitor) Exception in thread "Transaction Expired Entry Monitor" com.arjuna.ats.arjuna.exceptions.FatalError: com.arjuna.ats.internal.arjuna.objectstore.jdbc.accessors.DataSourceJDBCAccess at 1fc261da : javax.naming.NameNotFoundException: Error looking up datasources/jdbc-store, service service jboss.naming.context.java.jboss.datasources.jdbc-store is not started
15:05:13,285 ERROR [stderr] (Transaction Expired Entry Monitor)         at com.arjuna.ats.internal.arjuna.objectstore.jdbc.accessors.DataSourceJDBCAccess.getConnection(DataSourceJDBCAccess.java:55)
15:05:13,285 ERROR [stderr] (Transaction Expired Entry Monitor)         at com.arjuna.ats.internal.arjuna.objectstore.jdbc.JDBCImple_driver.allObjUids(JDBCImple_driver.java:316)
15:05:13,286 ERROR [stderr] (Transaction Expired Entry Monitor)         at com.arjuna.ats.internal.arjuna.objectstore.jdbc.JDBCStore.allObjUids(JDBCStore.java:179)
15:05:13,286 INFO  [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-1) JBAS010400: Bound data source [java:jboss/datasources/ExampleDS]
15:05:13,286 ERROR [stderr] (Transaction Expired Entry Monitor)         at com.arjuna.ats.internal.arjuna.objectstore.jdbc.JDBCStore.allObjUids(JDBCStore.java:119)
15:05:13,287 ERROR [stderr] (Transaction Expired Entry Monitor)         at com.arjuna.ats.internal.arjuna.recovery.ExpiredTransactionStatusManagerScanner.scan(ExpiredTransactionStatusManagerScanner.java:81)
15:05:13,287 ERROR [stderr] (Transaction Expired Entry Monitor)         at com.arjuna.ats.internal.arjuna.recovery.ExpiredEntryMonitor.run(ExpiredEntryMonitor.java:171)
15:05:13,288 ERROR [stderr] (Transaction Expired Entry Monitor) Caused by: javax.naming.NameNotFoundException: Error looking up datasources/jdbc-store, service service jboss.naming.context.java.jboss.datasources.jdbc-store is not started
15:05:13,288 ERROR [stderr] (Transaction Expired Entry Monitor)         at org.jboss.as.naming.ServiceBasedNamingStore.lookup(ServiceBasedNamingStore.java:132)
15:05:13,288 ERROR [stderr] (Transaction Expired Entry Monitor)         at org.jboss.as.naming.ServiceBasedNamingStore.lookup(ServiceBasedNamingStore.java:80)
15:05:13,288 ERROR [stderr] (Transaction Expired Entry Monitor)         at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:197)
15:05:13,289 ERROR [stderr] (Transaction Expired Entry Monitor)         at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:174)
15:05:13,289 ERROR [stderr] (Transaction Expired Entry Monitor)         at org.jboss.as.naming.InitialContext.lookup(InitialContext.java:122)
15:05:13,289 ERROR [stderr] (Transaction Expired Entry Monitor)         at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:183)
15:05:13,289 ERROR [stderr] (Transaction Expired Entry Monitor)         at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:179)
15:05:13,289 ERROR [stderr] (Transaction Expired Entry Monitor)         at javax.naming.InitialContext.lookup(InitialContext.java:411)
15:05:13,290 ERROR [stderr] (Transaction Expired Entry Monitor)         at com.arjuna.ats.internal.arjuna.objectstore.jdbc.accessors.DataSourceJDBCAccess.getConnection(DataSourceJDBCAccess.java:53)
15:05:13,290 ERROR [stderr] (Transaction Expired Entry Monitor)         ... 5 more
15:05:13,317 INFO  [org.jboss.as.server] (ServerService Thread Pool -- 26) JBAS018559: Deployed "oracle11gR2-jdbc-driver.jar" (runtime-name : "oracle11gR2-jdbc-driver.jar")
                
> 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