[
https://issues.jboss.org/browse/ISPN-1649?page=com.atlassian.jira.plugin....
]
Manik Surtani commented on ISPN-1649:
-------------------------------------
I cannot seem to recreate this problem. Tried by using the unit test and XML config file
as defined in
https://gist.github.com/1578904 and using a current Infinispan snapshot
(post-CR2, and pre-CR3).
Could you please try again with CR2 as well as with the latest snapshot from master, and
reopen if this is still an issue?
JDBC cache loader "dropTablesOnExit" does not work
--------------------------------------------------
Key: ISPN-1649
URL:
https://issues.jboss.org/browse/ISPN-1649
Project: Infinispan
Issue Type: Bug
Components: Loaders and Stores
Affects Versions: 5.1.0.CR1
Environment: ISPN 5.1.x, Java 7, H2 DB on Linux
Reporter: dex chen
Assignee: Mircea Markus
I configure my JDBC cache loader with H2 engine using filesystem as store. I set the
"dropTablesOnExit" to "true", but I still see the tables/and the data
after I stop the cache. Basically, "dropTablesOnExist" has no effect.
sample config:
<loader
class="org.infinispan.loaders.jdbc.stringbased.JdbcStringBasedCacheStore"
fetchPersistentState="true"
purgeOnStartup="false">
<properties>
<property name="stringsTableNamePrefix"
value="ISPN_STRING_TABLE"/>
<property name="idColumnName"
value="ID_COLUMN"/>
<property name="dataColumnName"
value="DATA_COLUMN"/>
<property name="timestampColumnName"
value="TIMESTAMP_COLUMN"/>
<property name="timestampColumnType"
value="BIGINT"/>
<property name="connectionFactoryClass"
value="org.infinispan.loaders.jdbc.connectionfactory.PooledConnectionFactory"/>
<property name="connectionUrl"
value="jdbc:h2:file:/tmp/testStore;DB_CLOSE_DELAY=-1"/>
<property name="userName" value="sa"/>
<property name="driverClass"
value="org.h2.Driver"/>
<property name="idColumnType"
value="VARCHAR(255)"/>
<property name="dataColumnType" value="BINARY"/>
<property name="dropTableOnExit" value="true"/>
<property name="createTableOnStart"
value="true"/>
</properties>
</loader>
--
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