[JBoss JIRA] (ISPN-3509) Infinispan does not support postgresplus database
by Mircea Markus (JIRA)
[ https://issues.jboss.org/browse/ISPN-3509?page=com.atlassian.jira.plugin.... ]
Mircea Markus updated ISPN-3509:
--------------------------------
Priority: Critical (was: Major)
> Infinispan does not support postgresplus database
> -------------------------------------------------
>
> Key: ISPN-3509
> URL: https://issues.jboss.org/browse/ISPN-3509
> Project: Infinispan
> Issue Type: Bug
> Components: Loaders and Stores
> Affects Versions: 6.0.0.Alpha3, 6.0.0.Alpha4
> Reporter: Vitalii Chepeliuk
> Assignee: Mircea Markus
> Priority: Critical
> Fix For: 6.0.0.Beta2, 6.0.0.Final
>
> Attachments: server.log
>
>
> When I run our functional tests inside EAP server against postgresplus database following error occured
> 17:19:12,893 ERROR [org.infinispan.interceptors.InvocationContextInterceptor] (pool-1-thread-1) ISPN000136: Execution error: org.infinispan.commons.CacheConfigurationException: Unable to detect database type from JDBC driver name or connection metadata. Please provide this manually using the 'databaseType' property in your configuration. Supported database type strings are [MYSQL, POSTGRES, DERBY, HSQL, H2, SQLITE, DB2, DB2_390, INFORMIX, INTERBASE, FIREBIRD, SQL_SERVER, ACCESS, ORACLE, SYBASE]
> at org.infinispan.loaders.jdbc.TableManipulation.getDatabaseType(TableManipulation.java:412) [infinispan-cachestore-jdbc.jar:6.0.0.Alpha4-redhat-1]
> Jenkins job https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/JDG/view/FUNC/job/e...
>
--
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
11 years, 3 months
[JBoss JIRA] (ISPN-3414) Infinispan ignores DatabaseType configuration
by Mircea Markus (JIRA)
[ https://issues.jboss.org/browse/ISPN-3414?page=com.atlassian.jira.plugin.... ]
Mircea Markus updated ISPN-3414:
--------------------------------
Labels: jdg62blocker (was: )
> Infinispan ignores DatabaseType configuration
> ----------------------------------------------
>
> Key: ISPN-3414
> URL: https://issues.jboss.org/browse/ISPN-3414
> Project: Infinispan
> Issue Type: Bug
> Components: Configuration
> Affects Versions: 6.0.0.Alpha2
> Reporter: Vitalii Chepeliuk
> Assignee: Tristan Tarrant
> Priority: Critical
> Labels: jdg62blocker
> Fix For: 6.0.0.Beta2
>
> Attachments: standalone.xml
>
>
> When I configure DefaultCacheManager with following configuration
> {code:title=Configurator.java|borderStyle=solid}
> ConfigurationBuilder bld = new ConfigurationBuilder();
> bld.clustering().cacheMode(CacheMode.LOCAL)
> .loaders().passivation(passivation).preload(preload).shared(false)
> .addLoader(JdbcMixedCacheStoreConfigurationBuilder.class).fetchPersistentState(false).purgeOnStartup(false)
> .databaseType(DatabaseType.MYSQL)
> .stringTable()
> .dropOnExit(false)
> .createOnStart(true)
> .tableNamePrefix("ISPN6Alpha2_STRING")
> .idColumnName("ID").idColumnType("VARCHAR(255)")
> .dataColumnName("DATA").dataColumnType("VARBINARY(1000)")
> .timestampColumnName("TIMESTAMP").timestampColumnType("BIGINT")
> .binaryTable()
> .dropOnExit(false)
> .createOnStart(true)
> .tableNamePrefix("ISPN6Alpha2_BINARY")
> .idColumnName("ID").idColumnType("VARCHAR(255)")
> .dataColumnName("DATA").dataColumnType("VARBINARY(1000)")
> .timestampColumnName("TIMESTAMP").timestampColumnType("BIGINT")
> .dataSource()
> .jndiUrl("java:jboss/datasources/ExampleDS");
> {code}
> And here is TableManipulation class with getDatabaseType() method
> {code:title=TableManipulation.java|borderStyle=solid}
> private DatabaseType getDatabaseType() {
> databaseType = config.databaseType();
> System.out.println(">>>>>>> databaseType "+ databaseType);
> if (databaseType == null) {
> // need to guess from the database type!
> Connection connection = null;
> ...
> {code}
> *Got the following output when test is running*
> !!!!! is printed from my client code
> >>>>> is printed from infinispan(TableManipulation.java)
> -----
> [java] 10:59:07,347 INFO [stdout] (pool-1-thread-1) !!!!!!! databasetype MYSQL
> [java] 10:59:07,500 INFO [org.infinispan.factories.GlobalComponentRegistry] (pool-1-thread-1) ISPN000128: Infinispan version: Infinispan 'Infinium' 6.0.0.Alpha2-redhat-1
> [java] 10:59:09,851 INFO [stdout] (pool-1-thread-1) >>>>>>> databaseType null
> [java] 10:59:11,953 INFO [stdout] (pool-1-thread-1) >>>>>>> databaseType null
> [java] 10:59:12,644 INFO [stdout] (pool-1-thread-1) >>>>>>> databaseType null
> [java] 10:59:12,645 INFO [stdout] (pool-1-thread-1) >>>>>>> databaseType null
> [java] 10:59:13,393 INFO [org.infinispan.jmx.CacheJmxRegistration] (pool-1-thread-1) ISPN000031: MBeans were successfully registered to the platform MBean server.
> [java] 10:59:24,780 INFO [stdout] (pool-1-thread-1) >>>>>>> databaseType null
> [java] 10:59:24,954 INFO [stdout] (pool-1-thread-1) >>>>>>> databaseType null
> [java] 10:59:25,260 INFO [stdout] (pool-1-thread-1) >>>>>>> databaseType null
> [java] 10:59:29,679 INFO [stdout] (pool-1-thread-1) >>>>>>> databaseType null
> [java] 10:59:29,680 INFO [stdout] (pool-1-thread-1) >>>>>>> databaseType null
> [java] 10:59:29,843 INFO [stdout] (pool-1-thread-1) >>>>>>> databaseType null
> [java] 10:59:29,844 INFO [stdout] (pool-1-thread-1) >>>>>>> databaseType null
> [java] 10:59:30,002 INFO [org.infinispan.jmx.CacheJmxRegistration] (pool-1-thread-1) ISPN000031: MBeans were successfully registered to the platform MBean server.
> [java] 10:59:38,626 INFO [stdout] (pool-1-thread-1) >>>>>>> databaseType null
> [java] 10:59:38,776 INFO [stdout] (pool-1-thread-1) >>>>>>> databaseType null
> [java] 10:59:41,806 INFO [org.jboss.arquillian.testenricher.cdi.container.BeanManagerProducer] (pool-1-thread-1) BeanManager not found.
> [java] 10:59:41,813 INFO [stdout] (pool-1-thread-1) !!!!!!! databasetype MYSQL
> [java] 10:59:41,848 INFO [stdout] (pool-1-thread-1) >>>>>>> databaseType null
> [java] 10:59:41,848 INFO [stdout] (pool-1-thread-1) >>>>>>> databaseType null
> [java] 10:59:42,018 INFO [stdout] (pool-1-thread-1) >>>>>>> databaseType null
> [java] 10:59:42,020 INFO [stdout] (pool-1-thread-1) >>>>>>> databaseType null
> [java] 10:59:42,176 INFO [org.infinispan.jmx.CacheJmxRegistration] (pool-1-thread-1) ISPN000031: MBeans were successfully registered to the platform MBean server.
> [java] 10:59:52,364 INFO [stdout] (pool-1-thread-1) >>>>>>> databaseType null
> [java] 10:59:52,515 INFO [stdout] (pool-1-thread-1) >>>>>>> databaseType null
> [java] 10:59:52,667 INFO [stdout] (pool-1-thread-1) >>>>>>> databaseType null
> [java] 10:59:57,155 INFO [stdout] (pool-1-thread-1) >>>>>>> databaseType null
> -----
> *And other issue with postgresqlplus92 DB, infinispan cannt recognize it like DatabaseType.POSTGRES* here is a link on our jenkins job https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/edg-60-jdbc-cache-st...
> -----
> [java] ^[[0m^[[0m10:53:45,198 INFO [stdout] (pool-1-thread-1) !!!!!!! databasetype POSTGRES
> [java] ^[[0m^[[0m10:53:45,348 INFO [org.infinispan.factories.GlobalComponentRegistry] (pool-1-thread-1) ISPN000128: Infinispan version: Infinispan 'Infinium' 6.0.0.Alpha2-redhat-1
> [java] ^[[0m^[[0m10:53:46,845 INFO [stdout] (pool-1-thread-1) >>>>>>> databaseType null
> [java] ^[[0m^[[0m10:53:48,939 INFO [stdout] (pool-1-thread-1) >>>>>>> databaseType null
> [java] ^[[0m^[[0m10:53:50,429 INFO [stdout] (pool-1-thread-1) >>>>>>> databaseType null
> [java] ^[[0m^[[0m10:53:51,456 INFO [stdout] (pool-1-thread-1) >>>>>>> databaseType null
> [java] ^[[0m^[[0m10:53:52,994 INFO [org.infinispan.jmx.CacheJmxRegistration] (pool-1-thread-1) ISPN000031: MBeans were successfully registered to the platform MBean server.
> [java] ^[[0m^[[0m10:53:59,232 INFO [stdout] (pool-1-thread-1) >>>>>>> databaseType null
> [java] ^[[0m^[[0m10:53:59,414 INFO [stdout] (pool-1-thread-1) >>>>>>> databaseType null
> [java] ^[[0m^[[0m10:54:01,807 INFO [stdout] (pool-1-thread-1) >>>>>>> databaseType null
> [java] ^[[0m^[[0m10:54:04,020 INFO [stdout] (pool-1-thread-1) >>>>>>> databaseType null
> [java] ^[[0m^[[0m10:54:06,084 INFO [stdout] (pool-1-thread-1) >>>>>>> databaseType null
> [java] ^[[0m^[[0m10:54:07,275 INFO [stdout] (pool-1-thread-1) >>>>>>> databaseType null
> [java] ^[[0m^[[0m10:54:08,303 INFO [stdout] (pool-1-thread-1) >>>>>>> databaseType null
> [java] ^[[0m^[[0m10:54:09,509 INFO [org.infinispan.jmx.CacheJmxRegistration] (pool-1-thread-1) ISPN000031: MBeans were successfully registered to the platform MBean server.
> [java] ^[[0m^[[0m10:54:13,520 INFO [stdout] (pool-1-thread-1) >>>>>>> databaseType null
> [java] ^[[0m^[[0m10:54:13,693 INFO [stdout] (pool-1-thread-1) >>>>>>> databaseType null
> [java] ^[[0m^[[0m10:54:16,104 INFO [org.jboss.arquillian.testenricher.cdi.container.BeanManagerProducer] (pool-1-thread-1) BeanManager not found.
> [java] ^[[0m^[[0m10:54:16,111 INFO [stdout] (pool-1-thread-1) !!!!!!! databasetype POSTGRES
> [java] ^[[0m^[[0m10:54:16,148 INFO [stdout] (pool-1-thread-1) >>>>>>> databaseType null
> [java] ^[[0m^[[0m10:54:18,180 INFO [stdout] (pool-1-thread-1) >>>>>>> databaseType null
> [java] ^[[0m^[[0m10:54:19,352 INFO [stdout] (pool-1-thread-1) >>>>>>> databaseType null
> [java] ^[[0m^[[0m10:54:20,358 INFO [stdout] (pool-1-thread-1) >>>>>>> databaseType null
> [java] ^[[0m^[[0m10:54:21,531 INFO [org.infinispan.jmx.CacheJmxRegistration] (pool-1-thread-1) ISPN000031: MBeans were successfully registered to the platform MBean server.
> [java] ^[[0m^[[0m10:54:26,078 INFO [stdout] (pool-1-thread-1) >>>>>>> databaseType null
> [java] ^[[0m^[[0m10:54:26,256 INFO [stdout] (pool-1-thread-1) >>>>>>> databaseType null
> [java] ^[[0m^[[0m10:54:27,419 INFO [stdout] (pool-1-thread-1) >>>>>>> databaseType null
> [java] ^[[0m^[[31m10:54:57,421 ERROR [org.infinispan.loaders.jdbc.connectionfactory.ManagedConnectionFactory] (pool-1-thread-1) ISPN008018: Sql failure retrieving connection from datasource: java.sql.SQLException: javax.resource.ResourceException: IJ000453: Unable to get managed connection for java:jboss/datasources/ExampleDS
> [java] at org.jboss.jca.adapters.jdbc.WrapperDataSource.getConnection(WrapperDataSource.java:147)
> [java] at org.infinispan.loaders.jdbc.connectionfactory.ManagedConnectionFactory.getConnection(ManagedConnectionFactory.java:82) [infinispan-cachestore-jdbc.jar:6.0.0.Alpha2-redhat-1]
> [java] at org.infinispan.loaders.jdbc.TableManipulation.getDatabaseType(TableManipulation.java:396) [infinispan-cachestore-jdbc.jar:6.0.0.Alpha2-redhat-1]
> [java] at org.infinispan.loaders.jdbc.TableManipulation.getSelectRowSql(TableManipulation.java:193) [infinispan-cachestore-jdbc.jar:6.0.0.Alpha2-redhat-1]
> [java] at org.infinispan.loaders.jdbc.binary.JdbcBinaryCacheStore.loadBucket(JdbcBinaryCacheStore.java:247) [infinispan-cachestore-jdbc.jar:6.0.0.Alpha2-redhat-1]
> -----
--
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
11 years, 3 months
[JBoss JIRA] (ISPN-3414) Infinispan ignores DatabaseType configuration
by Mircea Markus (JIRA)
[ https://issues.jboss.org/browse/ISPN-3414?page=com.atlassian.jira.plugin.... ]
Mircea Markus updated ISPN-3414:
--------------------------------
Assignee: Mircea Markus (was: Tristan Tarrant)
> Infinispan ignores DatabaseType configuration
> ----------------------------------------------
>
> Key: ISPN-3414
> URL: https://issues.jboss.org/browse/ISPN-3414
> Project: Infinispan
> Issue Type: Bug
> Components: Configuration
> Affects Versions: 6.0.0.Alpha2
> Reporter: Vitalii Chepeliuk
> Assignee: Mircea Markus
> Priority: Critical
> Labels: jdg62blocker
> Fix For: 6.0.0.Beta2
>
> Attachments: standalone.xml
>
>
> When I configure DefaultCacheManager with following configuration
> {code:title=Configurator.java|borderStyle=solid}
> ConfigurationBuilder bld = new ConfigurationBuilder();
> bld.clustering().cacheMode(CacheMode.LOCAL)
> .loaders().passivation(passivation).preload(preload).shared(false)
> .addLoader(JdbcMixedCacheStoreConfigurationBuilder.class).fetchPersistentState(false).purgeOnStartup(false)
> .databaseType(DatabaseType.MYSQL)
> .stringTable()
> .dropOnExit(false)
> .createOnStart(true)
> .tableNamePrefix("ISPN6Alpha2_STRING")
> .idColumnName("ID").idColumnType("VARCHAR(255)")
> .dataColumnName("DATA").dataColumnType("VARBINARY(1000)")
> .timestampColumnName("TIMESTAMP").timestampColumnType("BIGINT")
> .binaryTable()
> .dropOnExit(false)
> .createOnStart(true)
> .tableNamePrefix("ISPN6Alpha2_BINARY")
> .idColumnName("ID").idColumnType("VARCHAR(255)")
> .dataColumnName("DATA").dataColumnType("VARBINARY(1000)")
> .timestampColumnName("TIMESTAMP").timestampColumnType("BIGINT")
> .dataSource()
> .jndiUrl("java:jboss/datasources/ExampleDS");
> {code}
> And here is TableManipulation class with getDatabaseType() method
> {code:title=TableManipulation.java|borderStyle=solid}
> private DatabaseType getDatabaseType() {
> databaseType = config.databaseType();
> System.out.println(">>>>>>> databaseType "+ databaseType);
> if (databaseType == null) {
> // need to guess from the database type!
> Connection connection = null;
> ...
> {code}
> *Got the following output when test is running*
> !!!!! is printed from my client code
> >>>>> is printed from infinispan(TableManipulation.java)
> -----
> [java] 10:59:07,347 INFO [stdout] (pool-1-thread-1) !!!!!!! databasetype MYSQL
> [java] 10:59:07,500 INFO [org.infinispan.factories.GlobalComponentRegistry] (pool-1-thread-1) ISPN000128: Infinispan version: Infinispan 'Infinium' 6.0.0.Alpha2-redhat-1
> [java] 10:59:09,851 INFO [stdout] (pool-1-thread-1) >>>>>>> databaseType null
> [java] 10:59:11,953 INFO [stdout] (pool-1-thread-1) >>>>>>> databaseType null
> [java] 10:59:12,644 INFO [stdout] (pool-1-thread-1) >>>>>>> databaseType null
> [java] 10:59:12,645 INFO [stdout] (pool-1-thread-1) >>>>>>> databaseType null
> [java] 10:59:13,393 INFO [org.infinispan.jmx.CacheJmxRegistration] (pool-1-thread-1) ISPN000031: MBeans were successfully registered to the platform MBean server.
> [java] 10:59:24,780 INFO [stdout] (pool-1-thread-1) >>>>>>> databaseType null
> [java] 10:59:24,954 INFO [stdout] (pool-1-thread-1) >>>>>>> databaseType null
> [java] 10:59:25,260 INFO [stdout] (pool-1-thread-1) >>>>>>> databaseType null
> [java] 10:59:29,679 INFO [stdout] (pool-1-thread-1) >>>>>>> databaseType null
> [java] 10:59:29,680 INFO [stdout] (pool-1-thread-1) >>>>>>> databaseType null
> [java] 10:59:29,843 INFO [stdout] (pool-1-thread-1) >>>>>>> databaseType null
> [java] 10:59:29,844 INFO [stdout] (pool-1-thread-1) >>>>>>> databaseType null
> [java] 10:59:30,002 INFO [org.infinispan.jmx.CacheJmxRegistration] (pool-1-thread-1) ISPN000031: MBeans were successfully registered to the platform MBean server.
> [java] 10:59:38,626 INFO [stdout] (pool-1-thread-1) >>>>>>> databaseType null
> [java] 10:59:38,776 INFO [stdout] (pool-1-thread-1) >>>>>>> databaseType null
> [java] 10:59:41,806 INFO [org.jboss.arquillian.testenricher.cdi.container.BeanManagerProducer] (pool-1-thread-1) BeanManager not found.
> [java] 10:59:41,813 INFO [stdout] (pool-1-thread-1) !!!!!!! databasetype MYSQL
> [java] 10:59:41,848 INFO [stdout] (pool-1-thread-1) >>>>>>> databaseType null
> [java] 10:59:41,848 INFO [stdout] (pool-1-thread-1) >>>>>>> databaseType null
> [java] 10:59:42,018 INFO [stdout] (pool-1-thread-1) >>>>>>> databaseType null
> [java] 10:59:42,020 INFO [stdout] (pool-1-thread-1) >>>>>>> databaseType null
> [java] 10:59:42,176 INFO [org.infinispan.jmx.CacheJmxRegistration] (pool-1-thread-1) ISPN000031: MBeans were successfully registered to the platform MBean server.
> [java] 10:59:52,364 INFO [stdout] (pool-1-thread-1) >>>>>>> databaseType null
> [java] 10:59:52,515 INFO [stdout] (pool-1-thread-1) >>>>>>> databaseType null
> [java] 10:59:52,667 INFO [stdout] (pool-1-thread-1) >>>>>>> databaseType null
> [java] 10:59:57,155 INFO [stdout] (pool-1-thread-1) >>>>>>> databaseType null
> -----
> *And other issue with postgresqlplus92 DB, infinispan cannt recognize it like DatabaseType.POSTGRES* here is a link on our jenkins job https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/edg-60-jdbc-cache-st...
> -----
> [java] ^[[0m^[[0m10:53:45,198 INFO [stdout] (pool-1-thread-1) !!!!!!! databasetype POSTGRES
> [java] ^[[0m^[[0m10:53:45,348 INFO [org.infinispan.factories.GlobalComponentRegistry] (pool-1-thread-1) ISPN000128: Infinispan version: Infinispan 'Infinium' 6.0.0.Alpha2-redhat-1
> [java] ^[[0m^[[0m10:53:46,845 INFO [stdout] (pool-1-thread-1) >>>>>>> databaseType null
> [java] ^[[0m^[[0m10:53:48,939 INFO [stdout] (pool-1-thread-1) >>>>>>> databaseType null
> [java] ^[[0m^[[0m10:53:50,429 INFO [stdout] (pool-1-thread-1) >>>>>>> databaseType null
> [java] ^[[0m^[[0m10:53:51,456 INFO [stdout] (pool-1-thread-1) >>>>>>> databaseType null
> [java] ^[[0m^[[0m10:53:52,994 INFO [org.infinispan.jmx.CacheJmxRegistration] (pool-1-thread-1) ISPN000031: MBeans were successfully registered to the platform MBean server.
> [java] ^[[0m^[[0m10:53:59,232 INFO [stdout] (pool-1-thread-1) >>>>>>> databaseType null
> [java] ^[[0m^[[0m10:53:59,414 INFO [stdout] (pool-1-thread-1) >>>>>>> databaseType null
> [java] ^[[0m^[[0m10:54:01,807 INFO [stdout] (pool-1-thread-1) >>>>>>> databaseType null
> [java] ^[[0m^[[0m10:54:04,020 INFO [stdout] (pool-1-thread-1) >>>>>>> databaseType null
> [java] ^[[0m^[[0m10:54:06,084 INFO [stdout] (pool-1-thread-1) >>>>>>> databaseType null
> [java] ^[[0m^[[0m10:54:07,275 INFO [stdout] (pool-1-thread-1) >>>>>>> databaseType null
> [java] ^[[0m^[[0m10:54:08,303 INFO [stdout] (pool-1-thread-1) >>>>>>> databaseType null
> [java] ^[[0m^[[0m10:54:09,509 INFO [org.infinispan.jmx.CacheJmxRegistration] (pool-1-thread-1) ISPN000031: MBeans were successfully registered to the platform MBean server.
> [java] ^[[0m^[[0m10:54:13,520 INFO [stdout] (pool-1-thread-1) >>>>>>> databaseType null
> [java] ^[[0m^[[0m10:54:13,693 INFO [stdout] (pool-1-thread-1) >>>>>>> databaseType null
> [java] ^[[0m^[[0m10:54:16,104 INFO [org.jboss.arquillian.testenricher.cdi.container.BeanManagerProducer] (pool-1-thread-1) BeanManager not found.
> [java] ^[[0m^[[0m10:54:16,111 INFO [stdout] (pool-1-thread-1) !!!!!!! databasetype POSTGRES
> [java] ^[[0m^[[0m10:54:16,148 INFO [stdout] (pool-1-thread-1) >>>>>>> databaseType null
> [java] ^[[0m^[[0m10:54:18,180 INFO [stdout] (pool-1-thread-1) >>>>>>> databaseType null
> [java] ^[[0m^[[0m10:54:19,352 INFO [stdout] (pool-1-thread-1) >>>>>>> databaseType null
> [java] ^[[0m^[[0m10:54:20,358 INFO [stdout] (pool-1-thread-1) >>>>>>> databaseType null
> [java] ^[[0m^[[0m10:54:21,531 INFO [org.infinispan.jmx.CacheJmxRegistration] (pool-1-thread-1) ISPN000031: MBeans were successfully registered to the platform MBean server.
> [java] ^[[0m^[[0m10:54:26,078 INFO [stdout] (pool-1-thread-1) >>>>>>> databaseType null
> [java] ^[[0m^[[0m10:54:26,256 INFO [stdout] (pool-1-thread-1) >>>>>>> databaseType null
> [java] ^[[0m^[[0m10:54:27,419 INFO [stdout] (pool-1-thread-1) >>>>>>> databaseType null
> [java] ^[[0m^[[31m10:54:57,421 ERROR [org.infinispan.loaders.jdbc.connectionfactory.ManagedConnectionFactory] (pool-1-thread-1) ISPN008018: Sql failure retrieving connection from datasource: java.sql.SQLException: javax.resource.ResourceException: IJ000453: Unable to get managed connection for java:jboss/datasources/ExampleDS
> [java] at org.jboss.jca.adapters.jdbc.WrapperDataSource.getConnection(WrapperDataSource.java:147)
> [java] at org.infinispan.loaders.jdbc.connectionfactory.ManagedConnectionFactory.getConnection(ManagedConnectionFactory.java:82) [infinispan-cachestore-jdbc.jar:6.0.0.Alpha2-redhat-1]
> [java] at org.infinispan.loaders.jdbc.TableManipulation.getDatabaseType(TableManipulation.java:396) [infinispan-cachestore-jdbc.jar:6.0.0.Alpha2-redhat-1]
> [java] at org.infinispan.loaders.jdbc.TableManipulation.getSelectRowSql(TableManipulation.java:193) [infinispan-cachestore-jdbc.jar:6.0.0.Alpha2-redhat-1]
> [java] at org.infinispan.loaders.jdbc.binary.JdbcBinaryCacheStore.loadBucket(JdbcBinaryCacheStore.java:247) [infinispan-cachestore-jdbc.jar:6.0.0.Alpha2-redhat-1]
> -----
--
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
11 years, 3 months
[JBoss JIRA] (ISPN-3504) LevelDB Cache store in server doesn't keep data between restarts
by Mircea Markus (JIRA)
[ https://issues.jboss.org/browse/ISPN-3504?page=com.atlassian.jira.plugin.... ]
Mircea Markus updated ISPN-3504:
--------------------------------
Status: Resolved (was: Pull Request Sent)
Resolution: Done
> LevelDB Cache store in server doesn't keep data between restarts
> ----------------------------------------------------------------
>
> Key: ISPN-3504
> URL: https://issues.jboss.org/browse/ISPN-3504
> Project: Infinispan
> Issue Type: Bug
> Components: Loaders and Stores
> Affects Versions: 6.0.0.Alpha4
> Reporter: Michal Linhard
> Assignee: Tristan Tarrant
> Labels: jdg62blocker
> Fix For: 6.0.0.Beta2
>
>
> I have config with passivation="false" purge="false"
> and expect data to survive restarts which doesn't happen.
> {code}
> <cache-container name="default" default-cache="default"
> listener-executor="infinispan-listener">
> <local-cache name="default" start="EAGER" batching="false">
> <locking isolation="REPEATABLE_READ" acquire-timeout="20000"
> concurrency-level="500" striping="false" />
> <transaction mode="NONE" />
> <leveldb-store path="temp-leveldb" block-size="1024"
> cache-size="50000" clear-threshold="100000" passivation="false"
> purge="false" >
> <expiration path="temp-leveldb-expired" queue-size="2000" />
> <compression type="SNAPPY" />
> <implementation type="JAVA" />
> </leveldb-store>
> </local-cache>
> <local-cache name="memcachedCache" start="EAGER" batching="false">
> <locking isolation="REPEATABLE_READ" acquire-timeout="20000"
> concurrency-level="500" striping="false" />
> <transaction mode="NONE" />
> </local-cache>
> </cache-container>
> {code}
> failing test:
> https://code.engineering.redhat.com/gerrit/gitweb?p=jdg-functional-tests....;
> hb=8e1b8a10fed5de5bf3bb9ec6fbc46857e1666798
> for JDG 6.2.0.DR4
--
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
11 years, 3 months
[JBoss JIRA] (ISPN-3504) LevelDB Cache store in server doesn't keep data between restarts
by Mircea Markus (JIRA)
[ https://issues.jboss.org/browse/ISPN-3504?page=com.atlassian.jira.plugin.... ]
Mircea Markus updated ISPN-3504:
--------------------------------
Labels: jdg62blocker (was: )
> LevelDB Cache store in server doesn't keep data between restarts
> ----------------------------------------------------------------
>
> Key: ISPN-3504
> URL: https://issues.jboss.org/browse/ISPN-3504
> Project: Infinispan
> Issue Type: Bug
> Components: Loaders and Stores
> Affects Versions: 6.0.0.Alpha4
> Reporter: Michal Linhard
> Assignee: Tristan Tarrant
> Labels: jdg62blocker
> Fix For: 6.0.0.Beta2
>
>
> I have config with passivation="false" purge="false"
> and expect data to survive restarts which doesn't happen.
> {code}
> <cache-container name="default" default-cache="default"
> listener-executor="infinispan-listener">
> <local-cache name="default" start="EAGER" batching="false">
> <locking isolation="REPEATABLE_READ" acquire-timeout="20000"
> concurrency-level="500" striping="false" />
> <transaction mode="NONE" />
> <leveldb-store path="temp-leveldb" block-size="1024"
> cache-size="50000" clear-threshold="100000" passivation="false"
> purge="false" >
> <expiration path="temp-leveldb-expired" queue-size="2000" />
> <compression type="SNAPPY" />
> <implementation type="JAVA" />
> </leveldb-store>
> </local-cache>
> <local-cache name="memcachedCache" start="EAGER" batching="false">
> <locking isolation="REPEATABLE_READ" acquire-timeout="20000"
> concurrency-level="500" striping="false" />
> <transaction mode="NONE" />
> </local-cache>
> </cache-container>
> {code}
> failing test:
> https://code.engineering.redhat.com/gerrit/gitweb?p=jdg-functional-tests....;
> hb=8e1b8a10fed5de5bf3bb9ec6fbc46857e1666798
> for JDG 6.2.0.DR4
--
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
11 years, 3 months
[JBoss JIRA] (ISPN-3431) Lost version info during state transfer causes overwrite of newer data that joining node has read from store
by Mircea Markus (JIRA)
[ https://issues.jboss.org/browse/ISPN-3431?page=com.atlassian.jira.plugin.... ]
Mircea Markus updated ISPN-3431:
--------------------------------
Summary: Lost version info during state transfer causes overwrite of newer data that joining node has read from store (was: Lost version info during state transfer causes overwtite of newer data that joining node has read from store)
> Lost version info during state transfer causes overwrite of newer data that joining node has read from store
> ------------------------------------------------------------------------------------------------------------
>
> Key: ISPN-3431
> URL: https://issues.jboss.org/browse/ISPN-3431
> Project: Infinispan
> Issue Type: Bug
> Components: State transfer
> Affects Versions: 6.0.0.Alpha3
> Environment: uname -s ; cat /etc/redhat-release ; java -version
> Linux
> Red Hat Enterprise Linux Server release 5.9 (Tikanga)
> java version "1.6.0_30"
> Java(TM) SE Runtime Environment (build 1.6.0_30-b12)
> Java HotSpot(TM) 64-Bit Server VM (build 20.5-b03, mixed mode)
> Reporter: Nikolay Martynov
> Assignee: Pedro Ruivo
> Priority: Critical
> Fix For: 6.0.0.CR1
>
>
> When state transfer sends data to newly joining node no version information is provided despite the fact that this information is available to the cluster (for example, loaded from store). When newly joining node has loaded from its store newer version of data than cluster has then this newer version of data is overwritten because no version information is provided during state transfer.
> Scenario:
> {noformat}
> 1. Start node1, node2, node3
> 2. Put {A=>A1} from node1
> 3. Put {B=>B1} from node2
> 4. Put {C=>C1} from node3
> 5. Gracefully shutdown node1 saving the data
> 6. Gracefully shutdown node2 saving the data
> 7. Put {C=>C2} from node3
> 8. Gracefully shutdown node3 saving the data
> 9. Start node1 loading the data
> 10. Start node2 loading the data
> 11. Start node3 loading the data
> {noformat}
> Loaded from store on node3 - version information shows its newer than nodes 1 and 2 have:
> {noformat}
> org.infinispan.interceptors.CallInterceptor
> Executing command: PutKeyValueCommand{key=C, value=C2, flags=[CACHE_MODE_LOCAL, SKIP_LOCKING, SKIP_CACHE_STORE, SKIP_INDEXING, SKIP_OWNERSHIP_CHECK, IGNORE_RETURN_VALUES], putIfAbsent=false, metadata=EmbeddedMetadata{version=SimpleClusteredVersion{topologyId=8, version=2}}, successful=true, ignorePreviousValue=false}.
> {noformat}
> During state transfer older value C1 is received with version information being null:
> {noformat}
> org.infinispan.statetransfer.StateTransferInterceptor
> handleNonTxWriteCommand for command PutKeyValueCommand{key=C, value=C1, flags=[CACHE_MODE_LOCAL, SKIP_REMOTE_LOOKUP, PUT_FOR_STATE_TRANSFER, SKIP_SHARED_CACHE_STORE, SKIP_OWNERSHIP_CHECK, IGNORE_RETURN_VALUES, SKIP_XSITE_BACKUP], putIfAbsent=false, metadata=EmbeddedMetadata{version=null}, successful=true, ignorePreviousValue=false}
> {noformat}
> As a result newer value is replaced with older:
> {noformat}
> org.infinispan.interceptors.EntryWrappingInterceptor
> About to commit entry ClusteredRepeatableReadEntry(323f265b){key=C, value=C1, oldValue=C2, isCreated=false, isChanged=true, isRemoved=false, isValid=true, skipRemoteGet=true, metadata=EmbeddedMetadata{version=SimpleClusteredVersion{topologyId=8, version=2}}}
> {noformat}
> As far as i can see, any key on any node that it didnt written but has received during resync has version=null after loading from store.
> Config:
> {code:xml}
> <?xml version="1.0" encoding="UTF-8"?>
> <!--
> This is just a very simplistic example configuration file. For more information, please see
> http://docs.jboss.org/infinispan/5.3/configdocs/infinispan-config-5.3.html
> -->
> <infinispan
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
> xsi:schemaLocation="urn:infinispan:config:6.0 http://docs.jboss.org/infinispan/schemas/infinispan-config-6.0.xsd"
> xmlns="urn:infinispan:config:6.0">
> <global>
> <globalJmxStatistics enabled="true" jmxDomain="Infinispan" />
> <transport>
> <properties>
> <property name="configurationFile" value="jgroups.xml" />
> </properties>
> </transport>
> </global>
> <namedCache name="routing_table">
> <clustering mode="REPL">
> <stateTransfer awaitInitialTransfer="true" fetchInMemoryState="true"/>
> <sync replTimeout="1000"/>
> <!--async useReplQueue="true" replQueueMaxElements="100" /-->
> </clustering>
> <loaders passivation="false" shared="false" preload="true">
> <singleFileStore
> location="target/routing_table${infinispan.store_name:not_specified}/">
> </singleFileStore>
> </loaders>
> <versioning enabled="true" versioningScheme="SIMPLE"/>
> <transaction
> transactionMode="TRANSACTIONAL"
> autoCommit="true"
> transactionManagerLookupClass="org.infinispan.transaction.lookup.GenericTransactionManagerLookup"
> lockingMode="OPTIMISTIC"
> />
> <locking
> writeSkewCheck="true"
> isolationLevel="REPEATABLE_READ"/>
> </namedCache>
> </infinispan>
> {code}
--
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
11 years, 3 months
[JBoss JIRA] (ISPN-3431) Lost version info during state transfer causes overwrite of newer data that joining node has read from store
by Mircea Markus (JIRA)
[ https://issues.jboss.org/browse/ISPN-3431?page=com.atlassian.jira.plugin.... ]
Mircea Markus updated ISPN-3431:
--------------------------------
Labels: jdg62blocker (was: )
> Lost version info during state transfer causes overwrite of newer data that joining node has read from store
> ------------------------------------------------------------------------------------------------------------
>
> Key: ISPN-3431
> URL: https://issues.jboss.org/browse/ISPN-3431
> Project: Infinispan
> Issue Type: Bug
> Components: State transfer
> Affects Versions: 6.0.0.Alpha3
> Environment: uname -s ; cat /etc/redhat-release ; java -version
> Linux
> Red Hat Enterprise Linux Server release 5.9 (Tikanga)
> java version "1.6.0_30"
> Java(TM) SE Runtime Environment (build 1.6.0_30-b12)
> Java HotSpot(TM) 64-Bit Server VM (build 20.5-b03, mixed mode)
> Reporter: Nikolay Martynov
> Assignee: Pedro Ruivo
> Priority: Critical
> Labels: jdg62blocker
> Fix For: 6.0.0.CR1
>
>
> When state transfer sends data to newly joining node no version information is provided despite the fact that this information is available to the cluster (for example, loaded from store). When newly joining node has loaded from its store newer version of data than cluster has then this newer version of data is overwritten because no version information is provided during state transfer.
> Scenario:
> {noformat}
> 1. Start node1, node2, node3
> 2. Put {A=>A1} from node1
> 3. Put {B=>B1} from node2
> 4. Put {C=>C1} from node3
> 5. Gracefully shutdown node1 saving the data
> 6. Gracefully shutdown node2 saving the data
> 7. Put {C=>C2} from node3
> 8. Gracefully shutdown node3 saving the data
> 9. Start node1 loading the data
> 10. Start node2 loading the data
> 11. Start node3 loading the data
> {noformat}
> Loaded from store on node3 - version information shows its newer than nodes 1 and 2 have:
> {noformat}
> org.infinispan.interceptors.CallInterceptor
> Executing command: PutKeyValueCommand{key=C, value=C2, flags=[CACHE_MODE_LOCAL, SKIP_LOCKING, SKIP_CACHE_STORE, SKIP_INDEXING, SKIP_OWNERSHIP_CHECK, IGNORE_RETURN_VALUES], putIfAbsent=false, metadata=EmbeddedMetadata{version=SimpleClusteredVersion{topologyId=8, version=2}}, successful=true, ignorePreviousValue=false}.
> {noformat}
> During state transfer older value C1 is received with version information being null:
> {noformat}
> org.infinispan.statetransfer.StateTransferInterceptor
> handleNonTxWriteCommand for command PutKeyValueCommand{key=C, value=C1, flags=[CACHE_MODE_LOCAL, SKIP_REMOTE_LOOKUP, PUT_FOR_STATE_TRANSFER, SKIP_SHARED_CACHE_STORE, SKIP_OWNERSHIP_CHECK, IGNORE_RETURN_VALUES, SKIP_XSITE_BACKUP], putIfAbsent=false, metadata=EmbeddedMetadata{version=null}, successful=true, ignorePreviousValue=false}
> {noformat}
> As a result newer value is replaced with older:
> {noformat}
> org.infinispan.interceptors.EntryWrappingInterceptor
> About to commit entry ClusteredRepeatableReadEntry(323f265b){key=C, value=C1, oldValue=C2, isCreated=false, isChanged=true, isRemoved=false, isValid=true, skipRemoteGet=true, metadata=EmbeddedMetadata{version=SimpleClusteredVersion{topologyId=8, version=2}}}
> {noformat}
> As far as i can see, any key on any node that it didnt written but has received during resync has version=null after loading from store.
> Config:
> {code:xml}
> <?xml version="1.0" encoding="UTF-8"?>
> <!--
> This is just a very simplistic example configuration file. For more information, please see
> http://docs.jboss.org/infinispan/5.3/configdocs/infinispan-config-5.3.html
> -->
> <infinispan
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
> xsi:schemaLocation="urn:infinispan:config:6.0 http://docs.jboss.org/infinispan/schemas/infinispan-config-6.0.xsd"
> xmlns="urn:infinispan:config:6.0">
> <global>
> <globalJmxStatistics enabled="true" jmxDomain="Infinispan" />
> <transport>
> <properties>
> <property name="configurationFile" value="jgroups.xml" />
> </properties>
> </transport>
> </global>
> <namedCache name="routing_table">
> <clustering mode="REPL">
> <stateTransfer awaitInitialTransfer="true" fetchInMemoryState="true"/>
> <sync replTimeout="1000"/>
> <!--async useReplQueue="true" replQueueMaxElements="100" /-->
> </clustering>
> <loaders passivation="false" shared="false" preload="true">
> <singleFileStore
> location="target/routing_table${infinispan.store_name:not_specified}/">
> </singleFileStore>
> </loaders>
> <versioning enabled="true" versioningScheme="SIMPLE"/>
> <transaction
> transactionMode="TRANSACTIONAL"
> autoCommit="true"
> transactionManagerLookupClass="org.infinispan.transaction.lookup.GenericTransactionManagerLookup"
> lockingMode="OPTIMISTIC"
> />
> <locking
> writeSkewCheck="true"
> isolationLevel="REPEATABLE_READ"/>
> </namedCache>
> </infinispan>
> {code}
--
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
11 years, 3 months
[JBoss JIRA] (ISPN-3348) Unable to read entries from SingleFileCacheStore after server restart
by Mircea Markus (JIRA)
[ https://issues.jboss.org/browse/ISPN-3348?page=com.atlassian.jira.plugin.... ]
Mircea Markus updated ISPN-3348:
--------------------------------
Labels: jdg62blocker (was: )
> Unable to read entries from SingleFileCacheStore after server restart
> ---------------------------------------------------------------------
>
> Key: ISPN-3348
> URL: https://issues.jboss.org/browse/ISPN-3348
> Project: Infinispan
> Issue Type: Bug
> Components: Server
> Affects Versions: 6.0.0.Alpha1
> Reporter: Martin Gencur
> Assignee: Galder Zamarreño
> Priority: Critical
> Labels: jdg62blocker
> Fix For: 6.0.0.Beta2
>
>
> Using the following configuration:
> {code:xml}
> <subsystem xmlns="urn:infinispan:server:core:5.3" default-cache-container="default">
> <cache-container name="default" default-cache="default" listener-executor="infinispan-listener" eviction-executor="infinispan-eviction" replication-queue-executor="infinispan-repl-queue">
> <local-cache name="default" start="EAGER">
> <locking isolation="NONE" acquire-timeout="30000" concurrency-level="1000" striping="false"/>
> <transaction mode="NONE"/>
> <store class="org.infinispan.loaders.file.SingleFileCacheStore" passivation="false" preload="false" purge="false">
> <property name="location">${java.io.tmpdir}/single-file-cache-store</property>
> <property name="maxEntries">2</property>
> </store>
> </local-cache>
> </cache-container>
> </subsystem>
> {code}
> ...it is not possible to retrieve the cache entry from the cache store after server restart, as demonstrated by the following test:
> {code:java}
> RemoteCache<String, String> rc = rcm.getCache();
> rc.clear();
> assertNull(rc.get("k1"));
> rc.put("k1", "v1");
> rc.put("k2", "v2");
> rc.put("k3", "v3");
> assertEquals("v1", rc.get("k1"));
> assertEquals("v2", rc.get("k2"));
> assertEquals("v3", rc.get("k3"));
> controller.kill(CONTAINER);
> controller.start(CONTAINER);
> assertEquals("v2", rc.get("k2"));
> //^^^fails here - unable to find k2
> assertEquals("v3", rc.get("k3"));
> assertNull(rc.get("k1")); //maxEntries was 2, this entry should be lost as the oldest entries are removed
> controller.stop(CONTAINER);
> {code}
> Note that preload is set to false for this test. When I set it to true, the test passes.
> I tried to modify BaseCacheStoreFunctionalTest#testPreloadAndExpiry, disable "preload" and retrieve the cache entries after server restart by calling cache.get() (not from DataContainer) and the test passed (I ran SingleFileCacheStoreFunctionalTest which extends BaseCacheStoreFunctionalTest). So it seems the bug is related to the server distribution.
--
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
11 years, 3 months