[JBoss JIRA] (AS7-2700) Connections participating in transactions should not be eligable for idle-timeouts
by Nicklas Karlsson (Created) (JIRA)
Connections participating in transactions should not be eligable for idle-timeouts
----------------------------------------------------------------------------------
Key: AS7-2700
URL: https://issues.jboss.org/browse/AS7-2700
Project: Application Server 7
Issue Type: Bug
Components: JCA
Affects Versions: 7.1.0.Alpha1
Reporter: Nicklas Karlsson
Assignee: Jesper Pedersen
Scott Marlow:
I think the other part of the bug, is that connections shouldn't "idle-timeout" if they are enlisted into a transaction (which I believe should mean they are eligible for sharing).
In other words, I believe the following should work:
1. set idle-timeout-minutes=1 (currently this is 1 millisecond but 1 minute should also work).
2. JTA transaction begins.
3. Hibernate gets a non-xa resource X1 (database connection), enlists it into the transaction.
4. Hibernate inserts a row into a database table using X1.
5. Hibernate closes X1 which shouldn't make X1 eligible for idle-timeout handling, since it is still enlisted in the transaction.
6. Hibernate gets a non-xa resource, X1 should be returned. Imagine that two minutes has elapsed since the transaction started, X1 should not be idle-timed out.
7. Hibernate inserts another row into a database table using the resource that should still be X1. If the resource is not X1, the "ARJUNA12140: Adding multiple last resources is disallowed" error will occur.
8. The JTA transaction is committed successfully.
Maybe the IJ "idle-timeout" test case could simulate the above with a test case that doesn't run always but maybe is run selectively. I think the unit test will have to run for over a minute once the conversion error is fixed (e.g. since idle-timeout-minutes will be treated as minutes instead of milliseconds).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 8 months
[JBoss JIRA] (AS7-3192) Property expansion stopped working in datasource connection-url
by Stian Thorgersen (Created) (JIRA)
Property expansion stopped working in datasource connection-url
---------------------------------------------------------------
Key: AS7-3192
URL: https://issues.jboss.org/browse/AS7-3192
Project: Application Server 7
Issue Type: Bug
Affects Versions: 7.1.0.CR1b
Reporter: Stian Thorgersen
On 7.0.2.Final it was possible to use property expansion in the datasource connection-url, which is very useful for example when using embedded Apache Derby to specify that it should store the db in AS7's data directory.
The following worked fine on 7.0.2.Final, but stopped working in 7.1.0.CR1b (not tested on other 7.1.0.X versions):
{code}
<connection-url>jdbc:derby:${jboss.server.data.dir}/mydb;create=true</connection-url>
{code}
Without property expansion, and with property expansion not available for system-properties either (see AS7-2579) it is rather difficult to make sure the db for an embedded database is saved within the AS7 data directory.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 8 months
[JBoss JIRA] (AS7-3433) DataSource's <url-delimiter> value is ignored by AS7DataSourceDeployer
by Xi CHEN (JIRA)
Xi CHEN created AS7-3433:
----------------------------
Summary: DataSource's <url-delimiter> value is ignored by AS7DataSourceDeployer
Key: AS7-3433
URL: https://issues.jboss.org/browse/AS7-3433
Project: Application Server 7
Issue Type: Bug
Affects Versions: 7.1.0.CR1
Environment: JBoss 7.1.0.CR1, MS SQL Sever 2005/2008
Reporter: Xi CHEN
We try to use
<datasource ... >
<connection-url>jdbc:sqlserver://SERVER_ONE:1433;databaseName=MyDB|jdbc:sqlserver://SERVER_TWO:1433;databaseName=MyDB</connection-url>
<url-delimiter>|</url-delimiter>
...
</datasource>
to treate database failover case, but it doesn't work in JBoss 7.1.0.CR1. It just use the first connection url.
By looking at the code source of jboss connector ( in org.jboss.as.connector.subsystems.datasources.AbstractDataSourceService.java), I found the url-delimiter's value is never set into LocalManagedConnectionFactory.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 8 months