April 2014 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-4114) AuthAndEncryptProtocolTest fails with InvalidKeyException

by Martin Gencur (JIRA)

[ https://issues.jboss.org/browse/ISPN-4114?page=com.atlassian.jira.plugin.... ] Martin Gencur closed ISPN-4114. ------------------------------- Resolution: Won't Fix The test was changed so that it no longer tests AUTH protocol. This protocol was replaced by OAUTH once. This problem occurred when testing the AUTH protocol so I think this issue can be closed. > AuthAndEncryptProtocolTest fails with InvalidKeyException > --------------------------------------------------------- > > Key: ISPN-4114 > URL: https://issues.jboss.org/browse/ISPN-4114 > Project: Infinispan > Issue Type: Bug > Components: Test Suite - Server > Reporter: Jakub Markos > Assignee: Mircea Markus > Attachments: clustered-auth-with-encrypt.xml, clustered-auth-wrong-certificate.xml, clustered-auth.xml > > > The test is here: https://github.com/infinispan/infinispan/blob/master/server/integration/t... > and fails during the servers startup with this error: > {code} > 16:03:36,517 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-4) MSC000001: Failed to start service jboss.jgroups.channel.clustered: org.jboss.msc.service.StartException in service jboss.jgroups.channel.clustered: java.security.InvalidKeyException: No installed provider supports this key: sun.security.provider.DSAPublicKeyImpl > at org.jboss.as.clustering.jgroups.subsystem.ChannelService.start(ChannelService.java:74) > at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811) [jboss-msc-1.0.4.GA-redhat-1.jar:1.0.4.GA-redhat-1] > at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746) [jboss-msc-1.0.4.GA-redhat-1.jar:1.0.4.GA-redhat-1] > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) [rt.jar:1.7.0_06] > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) [rt.jar:1.7.0_06] > at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_06] > Caused by: java.security.InvalidKeyException: No installed provider supports this key: sun.security.provider.DSAPublicKeyImpl > at javax.crypto.Cipher.chooseProvider(Cipher.java:878) [jce.jar:1.7.0_04-ea] > at javax.crypto.Cipher.init(Cipher.java:1653) [jce.jar:1.7.0_04-ea] > at javax.crypto.Cipher.init(Cipher.java:1549) [jce.jar:1.7.0_04-ea] > at org.jgroups.auth.X509Token.setCertificate(X509Token.java:188) > at org.jgroups.protocols.AUTH.init(AUTH.java:83) > at org.jgroups.stack.ProtocolStack.initProtocolStack(ProtocolStack.java:847) > at org.jgroups.stack.ProtocolStack.setup(ProtocolStack.java:467) > at org.jgroups.JChannel.init(JChannel.java:824) > at org.jgroups.JChannel.<init>(JChannel.java:158) > at org.jboss.as.clustering.jgroups.MuxChannel.<init>(MuxChannel.java:37) > at org.jboss.as.clustering.jgroups.JChannelFactory.createChannel(JChannelFactory.java:81) > at org.jboss.as.clustering.jgroups.subsystem.ChannelService.start(ChannelService.java:69) > ... 5 more > {code} > The server config attached. -- 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, 12 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4206) Add test for distributed HotRod RollingUpgrades scenario

by Tomas Sykora (JIRA)

[ https://issues.jboss.org/browse/ISPN-4206?page=com.atlassian.jira.plugin.... ] Tomas Sykora updated ISPN-4206: ------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/2503 > Add test for distributed HotRod RollingUpgrades scenario > -------------------------------------------------------- > > Key: ISPN-4206 > URL: https://issues.jboss.org/browse/ISPN-4206 > Project: Infinispan > Issue Type: Task > Reporter: Tomas Sykora > Assignee: Tomas Sykora > > Test scenario with at least 2 source and 2 target nodes with clustered configuration. -- 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, 12 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4206) Add test for distributed HotRod RollingUpgrades scenario

by Tomas Sykora (JIRA)

Tomas Sykora created ISPN-4206: ---------------------------------- Summary: Add test for distributed HotRod RollingUpgrades scenario Key: ISPN-4206 URL: https://issues.jboss.org/browse/ISPN-4206 Project: Infinispan Issue Type: Task Reporter: Tomas Sykora Assignee: Tomas Sykora Test scenario with at least 2 source and 2 target nodes with clustered configuration. -- 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, 12 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4164) AuthAndEncryptProtocolTest fails

by Martin Gencur (JIRA)

[ https://issues.jboss.org/browse/ISPN-4164?page=com.atlassian.jira.plugin.... ] Martin Gencur updated ISPN-4164: -------------------------------- Issue Type: Bug (was: Feature Request) > AuthAndEncryptProtocolTest fails > -------------------------------- > > Key: ISPN-4164 > URL: https://issues.jboss.org/browse/ISPN-4164 > Project: Infinispan > Issue Type: Bug > Reporter: Ion Savin > Assignee: Martin Gencur > Fix For: 7.0.0.Alpha3 > > > Temporarily disabled: > AuthAndEncryptProtocolTest.testAlienNodeCannotJoin > AuthAndEncryptProtocolTest.testFriendlyNodeCanJoin > Failure details: > http://ci.infinispan.org/viewLog.html?buildId=7283&tab=buildResultsDiv&bu... > http://ci.infinispan.org/viewLog.html?buildId=7283&tab=buildResultsDiv&bu... -- 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, 12 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4196) Local transaction not removed from transaction table with keySet, entrySet, values operations

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/ISPN-4196?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on ISPN-4196: ----------------------------------------------- Adrian Nistor <anistor(a)redhat.com> changed the Status of [bug 1087281|https://bugzilla.redhat.com/show_bug.cgi?id=1087281] from POST to MODIFIED > Local transaction not removed from transaction table with keySet, entrySet, values operations > --------------------------------------------------------------------------------------------- > > Key: ISPN-4196 > URL: https://issues.jboss.org/browse/ISPN-4196 > Project: Infinispan > Issue Type: Bug > Components: Embedded Querying > Affects Versions: 7.0.0.Alpha1 > Reporter: Adrian Nistor > Assignee: Martin Gencur > Fix For: 7.0.0.Alpha4, 7.0.0.Final > > > The cleanup phase of FilesystemQueryDslIterationTest of this test is based on Cache.clear() and is very slow , taking about 30 seconds, or at least that's how much we gain if the cache cleanup is removed. Without the cleanup, this test takes about 2.5 seconds, so we need to investigate why Cache.clear() creates a problem here or in general. -- 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, 12 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4196) Local transaction not removed from transaction table with keySet, entrySet, values operations

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/ISPN-4196?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on ISPN-4196: ----------------------------------------------- Martin Gencur <mgencur(a)redhat.com> changed the Status of [bug 1087281|https://bugzilla.redhat.com/show_bug.cgi?id=1087281] from NEW to POST > Local transaction not removed from transaction table with keySet, entrySet, values operations > --------------------------------------------------------------------------------------------- > > Key: ISPN-4196 > URL: https://issues.jboss.org/browse/ISPN-4196 > Project: Infinispan > Issue Type: Bug > Components: Embedded Querying > Affects Versions: 7.0.0.Alpha1 > Reporter: Adrian Nistor > Assignee: Martin Gencur > Fix For: 7.0.0.Alpha4, 7.0.0.Final > > > The cleanup phase of FilesystemQueryDslIterationTest of this test is based on Cache.clear() and is very slow , taking about 30 seconds, or at least that's how much we gain if the cache cleanup is removed. Without the cleanup, this test takes about 2.5 seconds, so we need to investigate why Cache.clear() creates a problem here or in general. -- 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, 12 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4196) Local transaction not removed from transaction table with keySet, entrySet, values operations

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/ISPN-4196?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration updated ISPN-4196: ------------------------------------------ Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1087281 > Local transaction not removed from transaction table with keySet, entrySet, values operations > --------------------------------------------------------------------------------------------- > > Key: ISPN-4196 > URL: https://issues.jboss.org/browse/ISPN-4196 > Project: Infinispan > Issue Type: Bug > Components: Embedded Querying > Affects Versions: 7.0.0.Alpha1 > Reporter: Adrian Nistor > Assignee: Martin Gencur > Fix For: 7.0.0.Alpha4, 7.0.0.Final > > > The cleanup phase of FilesystemQueryDslIterationTest of this test is based on Cache.clear() and is very slow , taking about 30 seconds, or at least that's how much we gain if the cache cleanup is removed. Without the cleanup, this test takes about 2.5 seconds, so we need to investigate why Cache.clear() creates a problem here or in general. -- 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, 12 months

1
0
0 / 0

[JBoss JIRA] (ISPN-2454) The current SQL query that checks table existence is under optimized on big database

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/ISPN-2454?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration updated ISPN-2454: ------------------------------------------ Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1087236 > The current SQL query that checks table existence is under optimized on big database > ------------------------------------------------------------------------------------ > > Key: ISPN-2454 > URL: https://issues.jboss.org/browse/ISPN-2454 > Project: Infinispan > Issue Type: Enhancement > Components: Loaders and Stores > Affects Versions: 5.1.0.FINAL > Reporter: Nicolas Filotto > Assignee: Tristan Tarrant > Labels: jdg, jdg6 > Fix For: 5.2.0.Beta4 > > > Last year I proposed an enhancement allowing to use the implicit db schema to ease life of end-user, unfortunately it seems that it affects the startup time of the product when the tables contain a lot of rows. Indeed the query can take several seconds to return a result. > The idea of this task would be to optimize this query for all supported databases in order to avoid this drawback. -- 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, 12 months

1
0
0 / 0

[JBoss JIRA] (ISPN-1204) Make JDBC cache store use implicit schemas for database tables

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/ISPN-1204?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration updated ISPN-1204: ------------------------------------------ Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1087218 > Make JDBC cache store use implicit schemas for database tables > -------------------------------------------------------------- > > Key: ISPN-1204 > URL: https://issues.jboss.org/browse/ISPN-1204 > Project: Infinispan > Issue Type: Enhancement > Components: Loaders and Stores > Reporter: Nicolas Filotto > Assignee: Galder Zamarreño > Fix For: 5.1.0.BETA1, 5.1.0.FINAL > > > The current code checks if a table exists thanks to con.getMetaData().getTables(...) which is totally DB schema dependent, your code allow us to specify the schema by prefixing the table name with the name of the schema in the config which is not really convenient in practice especially if we have a lot of config files. You could easily make your code fully DB schema independent by replacing the method org.infinispan.loaders.jdbc.TableManipulation.tableExists(Connection connection, String tableName) with this content: > {code} > public boolean tableExists(Connection connection, String tableName) { > assertNotNull(getTableName(), "table name is mandatory"); > Statement stmt = null; > ResultSet trs = null; > try { > stmt = connection.createStatement(); > trs = stmt.executeQuery("SELECT count(*) FROM " + tableName); > return trs.next(); > } > catch (SQLException e) { > if (log.isTraceEnabled()) { > log.trace("SQLException occurs while checking the table " + tableName, e); > } > return false; > } > finally { > JdbcUtil.safeClose(trs); > JdbcUtil.safeClose(stmt); > } > } > {code} > I know that it is a much less elegant and standard approach but it allows to simplify so much the config that I think that it makes sense to at least think about at it more than one second. Feel free to resolve it as won't fix if you don't find it relevant. > NB1: We use the same approach in our product (EXOJCR-1374) with JBC and we successfully tested it on Oracle, MySQL, MS SQL, PostgreSQL, DB2 and Sybase > NB2: This patch works well on all listed DB only if auto commit is set to true which should be true in your case since it seems to be the exact same code as JBC -- 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, 12 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3689) Preloading fails with JdbcBinaryCacheStore on DB2

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/ISPN-3689?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration updated ISPN-3689: ------------------------------------------ Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1087209 > Preloading fails with JdbcBinaryCacheStore on DB2 > -------------------------------------------------- > > Key: ISPN-3689 > URL: https://issues.jboss.org/browse/ISPN-3689 > Project: Infinispan > Issue Type: Bug > Components: Loaders and Stores > Affects Versions: 5.2.7.Final, 6.0.0.CR1 > Environment: DB2 9.7.5 > Reporter: Nicolas Filotto > Assignee: Mircea Markus > Fix For: 7.0.0.Alpha4 > > > I use the {{JdbcBinaryCacheStore}} with preloading enabled, when I test it on DB2 I get an exception of type: > {code} > 06.11.2013 16:27:51 *ERROR* [main] DataManipulationHelper: ISPN008007: SQL error while fetching all StoredEntries (DataManipulationHelper.java, line 253) > com.ibm.db2.jcc.am.SqlSyntaxErrorException: DB2 SQL Error: SQLCODE=-104, SQLSTATE=42601, SQLERRMC=?;r_quota" FETCH FIRST;<space>, DRIVER=4.13.80 > at com.ibm.db2.jcc.am.id.a(id.java:677) > at com.ibm.db2.jcc.am.id.a(id.java:60) > at com.ibm.db2.jcc.am.id.a(id.java:127) > at com.ibm.db2.jcc.am.fo.c(fo.java:2653) > at com.ibm.db2.jcc.am.fo.d(fo.java:2641) > at com.ibm.db2.jcc.am.fo.a(fo.java:2090) > at com.ibm.db2.jcc.am.go.a(go.java:7639) > at com.ibm.db2.jcc.t4.cb.h(cb.java:141) > at com.ibm.db2.jcc.t4.cb.b(cb.java:41) > at com.ibm.db2.jcc.t4.q.a(q.java:32) > at com.ibm.db2.jcc.t4.sb.i(sb.java:135) > at com.ibm.db2.jcc.am.fo.ib(fo.java:2059) > at com.ibm.db2.jcc.am.go.sc(go.java:3555) > at com.ibm.db2.jcc.am.go.b(go.java:4344) > at com.ibm.db2.jcc.am.go.fc(go.java:741) > at com.ibm.db2.jcc.am.go.executeQuery(go.java:711) > at org.apache.commons.dbcp.DelegatingPreparedStatement.executeQuery(DelegatingPreparedStatement.java:96) > at org.apache.commons.dbcp.DelegatingPreparedStatement.executeQuery(DelegatingPreparedStatement.java:96) > at org.infinispan.loaders.jdbc.DataManipulationHelper.loadSome(DataManipulationHelper.java:245) > at org.infinispan.loaders.jdbc.binary.JdbcBinaryCacheStore.loadLockSafe(JdbcBinaryCacheStore.java:312) > at org.infinispan.loaders.LockSupportCacheStore.load(LockSupportCacheStore.java:167) > at org.infinispan.loaders.CacheLoaderManagerImpl.loadState(CacheLoaderManagerImpl.java:285) > at org.infinispan.loaders.CacheLoaderManagerImpl.preload(CacheLoaderManagerImpl.java:238) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:597) > at org.infinispan.util.ReflectionUtil.invokeAccessibly(ReflectionUtil.java:203) > at org.infinispan.factories.AbstractComponentRegistry$PrioritizedMethod.invoke(AbstractComponentRegistry.java:886) > at org.infinispan.factories.AbstractComponentRegistry.invokeStartMethods(AbstractComponentRegistry.java:657) > at org.infinispan.factories.AbstractComponentRegistry.internalStart(AbstractComponentRegistry.java:646) > at org.infinispan.factories.AbstractComponentRegistry.start(AbstractComponentRegistry.java:549) > at org.infinispan.factories.ComponentRegistry.start(ComponentRegistry.java:217) > at org.infinispan.CacheImpl.start(CacheImpl.java:582) > at org.infinispan.manager.DefaultCacheManager.wireAndStartCache(DefaultCacheManager.java:686) > at org.infinispan.manager.DefaultCacheManager.createCache(DefaultCacheManager.java:649) > at org.infinispan.manager.DefaultCacheManager.getCache(DefaultCacheManager.java:545) > {code} > I looks like you cannot use a parameter to set your query limit in case of DB2 9.7.5 at least -- 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, 12 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues April 2014