[JBoss JIRA] (ISPN-3486) Jdbc-store doesn't work with Sybase database
by Tristan Tarrant (JIRA)
[ https://issues.jboss.org/browse/ISPN-3486?page=com.atlassian.jira.plugin.... ]
Tristan Tarrant reassigned ISPN-3486:
-------------------------------------
Assignee: (was: Mircea Markus)
> Jdbc-store doesn't work with Sybase database
> --------------------------------------------
>
> Key: ISPN-3486
> URL: https://issues.jboss.org/browse/ISPN-3486
> Project: Infinispan
> Issue Type: Bug
> Components: Loaders and Stores
> Affects Versions: 5.3.0.Final
> Environment: WildFly 8.0.0.Alpha4
> Reporter: Tomas Remes
>
> It's not possible to deploy appplication using following jdbc cache configuration with defined Sybase datasource:
> {noformat}
> <binary-keyed-jdbc-store datasource="java:jboss/datasources/testDS" preload="true" passivation="false" purge="false">
> <binary-keyed-table prefix="stringbased">
> <id-column name="id" type="VARCHAR(500)"/>
> <data-column name="datum" type="BINARY"/>
> <timestamp-column name="version" type="BIGINT"/>
> </binary-keyed-table>
> </binary-keyed-jdbc-store>
> {noformat}
> Problem is that it cannot create table executing following statement:
> CREATE TABLE "b_repl"(id VARCHAR(255) NOT NULL, datum VARBINARY(10000), ver BIGINT, PRIMARY KEY (id))
> Correct statement in this configuration is the one without quotation marks. So the deployment fails on WildFly with following exception:
> {noformat}
> 10:07:08,920 ERROR [org.infinispan.loaders.jdbc.TableManipulation] (ServerService Thread Pool -- 57) ISPN008011: Error while creating table; used DDL statement: 'CREATE TABLE "stringbased_default_host_mystore"(id VARCHAR(500) NOT NULL, datum BINARY, version BIGINT, PRIMARY KEY (id))': java.sql.SQLException: Incorrect syntax near '('.
> at com.sybase.jdbc4.jdbc.SybConnection.getAllExceptions(SybConnection.java:2780)
> at com.sybase.jdbc4.jdbc.SybStatement.handleSQLE(SybStatement.java:2665)
> at com.sybase.jdbc4.jdbc.SybStatement.nextResult(SybStatement.java:295)
> at com.sybase.jdbc4.jdbc.SybStatement.nextResult(SybStatement.java:272)
> at com.sybase.jdbc4.jdbc.SybStatement.updateLoop(SybStatement.java:2515)
> at com.sybase.jdbc4.jdbc.SybStatement.executeUpdate(SybStatement.java:2499)
> at com.sybase.jdbc4.jdbc.SybStatement.executeUpdate(SybStatement.java:577)
> at org.jboss.jca.adapters.jdbc.WrappedStatement.executeUpdate(WrappedStatement.java:375)
> at org.infinispan.loaders.jdbc.TableManipulation.executeUpdateSql(TableManipulation.java:167)
> at org.infinispan.loaders.jdbc.TableManipulation.createTable(TableManipulation.java:143)
> at org.infinispan.loaders.jdbc.TableManipulation.start(TableManipulation.java:245)
> at org.infinispan.loaders.jdbc.binary.JdbcBinaryCacheStore.doConnectionFactoryInitialization(JdbcBinaryCacheStore.java:514)
> at org.infinispan.loaders.jdbc.binary.JdbcBinaryCacheStore.start(JdbcBinaryCacheStore.java:102)
> at org.infinispan.loaders.CacheLoaderManagerImpl.start(CacheLoaderManagerImpl.java:155)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [rt.jar:1.7.0_21]
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) [rt.jar:1.7.0_21]
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) [rt.jar:1.7.0_21]
> at java.lang.reflect.Method.invoke(Method.java:601) [rt.jar:1.7.0_21]
> at org.infinispan.util.ReflectionUtil.invokeAccessibly(ReflectionUtil.java:205)
> at org.infinispan.factories.AbstractComponentRegistry$PrioritizedMethod.invoke(AbstractComponentRegistry.java:889)
> at org.infinispan.factories.AbstractComponentRegistry.invokeStartMethods(AbstractComponentRegistry.java:658)
> at org.infinispan.factories.AbstractComponentRegistry.internalStart(AbstractComponentRegistry.java:647)
> at org.infinispan.factories.AbstractComponentRegistry.start(AbstractComponentRegistry.java:550)
> at org.infinispan.factories.ComponentRegistry.start(ComponentRegistry.java:221)
> at org.infinispan.CacheImpl.start(CacheImpl.java:691)
> at org.infinispan.manager.DefaultCacheManager.wireAndStartCache(DefaultCacheManager.java:685)
> at org.infinispan.manager.DefaultCacheManager.createCache(DefaultCacheManager.java:648)
> at org.infinispan.manager.DefaultCacheManager.getCache(DefaultCacheManager.java:544)
> at org.infinispan.manager.DefaultCacheManager.getCache(DefaultCacheManager.java:558)
> at org.jboss.as.clustering.infinispan.DefaultEmbeddedCacheManager.getCache(DefaultEmbeddedCacheManager.java:109)
> at org.jboss.as.clustering.infinispan.DefaultEmbeddedCacheManager.getCache(DefaultEmbeddedCacheManager.java:100)
> at org.jboss.as.clustering.infinispan.subsystem.CacheService.start(CacheService.java:78)
> at org.jboss.as.clustering.msc.AsynchronousService$1.run(AsynchronousService.java:82)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_21]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_21]
> at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_21]
> at org.jboss.threads.JBossThread.run(JBossThread.java:122)
> 10:07:08,941 ERROR [org.jboss.msc.service.fail] (ServerService Thread Pool -- 54) MSC000001: Failed to start service jboss.infinispan.web.repl: org.jboss.msc.service.StartException in service jboss.infinispan.web.repl: org.infinispan.CacheException: Unable to invoke method public void org.infinispan.loaders.CacheLoaderManagerImpl.start() on object of type CacheLoaderManagerImpl
> at org.jboss.as.clustering.msc.AsynchronousService$1.run(AsynchronousService.java:87) [wildfly-clustering-common-8.0.0.Alpha4.jar:8.0.0.Alpha4]
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_21]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_21]
> at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_21]
> at org.jboss.threads.JBossThread.run(JBossThread.java:122) [jboss-threads-2.1.0.Final.jar:2.1.0.Final]
> Caused by: org.infinispan.CacheException: Unable to invoke method public void org.infinispan.loaders.CacheLoaderManagerImpl.start() on object of type CacheLoaderManagerImpl
> at org.infinispan.util.ReflectionUtil.invokeAccessibly(ReflectionUtil.java:207)
> at org.infinispan.factories.AbstractComponentRegistry$PrioritizedMethod.invoke(AbstractComponentRegistry.java:889)
> at org.infinispan.factories.AbstractComponentRegistry.invokeStartMethods(AbstractComponentRegistry.java:658)
> at org.infinispan.factories.AbstractComponentRegistry.internalStart(AbstractComponentRegistry.java:647)
> at org.infinispan.factories.AbstractComponentRegistry.start(AbstractComponentRegistry.java:550)
> at org.infinispan.factories.ComponentRegistry.start(ComponentRegistry.java:221)
> at org.infinispan.CacheImpl.start(CacheImpl.java:691)
> at org.infinispan.manager.DefaultCacheManager.wireAndStartCache(DefaultCacheManager.java:685)
> at org.infinispan.manager.DefaultCacheManager.createCache(DefaultCacheManager.java:648)
> at org.infinispan.manager.DefaultCacheManager.getCache(DefaultCacheManager.java:544)
> at org.infinispan.manager.DefaultCacheManager.getCache(DefaultCacheManager.java:558)
> at org.jboss.as.clustering.infinispan.DefaultEmbeddedCacheManager.getCache(DefaultEmbeddedCacheManager.java:109)
> at org.jboss.as.clustering.infinispan.DefaultEmbeddedCacheManager.getCache(DefaultEmbeddedCacheManager.java:100)
> at org.jboss.as.clustering.infinispan.subsystem.CacheService.start(CacheService.java:78)
> at org.jboss.as.clustering.msc.AsynchronousService$1.run(AsynchronousService.java:82) [wildfly-clustering-common-8.0.0.Alpha4.jar:8.0.0.Alpha4]
> ... 4 more
> Caused by: org.infinispan.CacheException: Unable to start cache loaders
> at org.infinispan.loaders.CacheLoaderManagerImpl.start(CacheLoaderManagerImpl.java:163)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [rt.jar:1.7.0_21]
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) [rt.jar:1.7.0_21]
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) [rt.jar:1.7.0_21]
> at java.lang.reflect.Method.invoke(Method.java:601) [rt.jar:1.7.0_21]
> at org.infinispan.util.ReflectionUtil.invokeAccessibly(ReflectionUtil.java:205)
> ... 18 more
> Caused by: org.infinispan.loaders.CacheLoaderException: java.sql.SQLException: Incorrect syntax near '('.
> at org.infinispan.loaders.jdbc.TableManipulation.executeUpdateSql(TableManipulation.java:170)
> at org.infinispan.loaders.jdbc.TableManipulation.createTable(TableManipulation.java:143)
> at org.infinispan.loaders.jdbc.TableManipulation.start(TableManipulation.java:245)
> at org.infinispan.loaders.jdbc.binary.JdbcBinaryCacheStore.doConnectionFactoryInitialization(JdbcBinaryCacheStore.java:514)
> at org.infinispan.loaders.jdbc.binary.JdbcBinaryCacheStore.start(JdbcBinaryCacheStore.java:102)
> at org.infinispan.loaders.CacheLoaderManagerImpl.start(CacheLoaderManagerImpl.java:155)
> ... 23 more
> Caused by: java.sql.SQLException: Incorrect syntax near '('.
> at com.sybase.jdbc4.jdbc.SybConnection.getAllExceptions(SybConnection.java:2780)
> at com.sybase.jdbc4.jdbc.SybStatement.handleSQLE(SybStatement.java:2665)
> at com.sybase.jdbc4.jdbc.SybStatement.nextResult(SybStatement.java:295)
> at com.sybase.jdbc4.jdbc.SybStatement.nextResult(SybStatement.java:272)
> at com.sybase.jdbc4.jdbc.SybStatement.updateLoop(SybStatement.java:2515)
> at com.sybase.jdbc4.jdbc.SybStatement.executeUpdate(SybStatement.java:2499)
> at com.sybase.jdbc4.jdbc.SybStatement.executeUpdate(SybStatement.java:577)
> at org.jboss.jca.adapters.jdbc.WrappedStatement.executeUpdate(WrappedStatement.java:375)
> at org.infinispan.loaders.jdbc.TableManipulation.executeUpdateSql(TableManipulation.java:167)
> ... 28 more
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 2 months
[JBoss JIRA] (ISPN-2710) Huge amount of OOB threads during performance test
by Tristan Tarrant (JIRA)
[ https://issues.jboss.org/browse/ISPN-2710?page=com.atlassian.jira.plugin.... ]
Tristan Tarrant reassigned ISPN-2710:
-------------------------------------
Assignee: (was: Mircea Markus)
> Huge amount of OOB threads during performance test
> --------------------------------------------------
>
> Key: ISPN-2710
> URL: https://issues.jboss.org/browse/ISPN-2710
> Project: Infinispan
> Issue Type: Feature Request
> Components: Core
> Affects Versions: 5.2.0.CR1
> Reporter: Robert Stupp
> Priority: Minor
>
> While running our performance test (as described in ISPN-2240), two of the four servers are running at 80 to 100% CPU - while the others just run at 10%.
> Before that phenomenom a huge amount (several 100s) of threads has been created (all called {{OOB-xxxx}}.
> The performance test just reads cached data - there was no cache put operation at that time.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 2 months
[JBoss JIRA] (ISPN-2444) the incoming local xsite commands don't check if the local cache is started
by Tristan Tarrant (JIRA)
[ https://issues.jboss.org/browse/ISPN-2444?page=com.atlassian.jira.plugin.... ]
Tristan Tarrant reassigned ISPN-2444:
-------------------------------------
Assignee: (was: Mircea Markus)
> the incoming local xsite commands don't check if the local cache is started
> ----------------------------------------------------------------------------
>
> Key: ISPN-2444
> URL: https://issues.jboss.org/browse/ISPN-2444
> Project: Infinispan
> Issue Type: Feature Request
> Components: Cross-Site Replication
> Affects Versions: 5.2.0.Beta2, 5.2.0.Final
> Reporter: Mircea Markus
>
> Currently the CommandAwareRpcDispatcher is using different handles for commands received from a remote site(InboundInvocationHandler) vs the commands received from the local site(BackupReceiverRepository).
> For the commands received from the remote site, there's no check to see if the receiving cache is started, as it is in the case of commands received from the local site (that's handled in InboundInvocationHandler.handle).
> This Jira is about checking if the cache that's suposed to process a command originated from a remote site is started. If it is not started, we should throw an exception to signal that the backup call was not successful.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 2 months
[JBoss JIRA] (ISPN-2625) Verify Cross-site transfer performace
by Tristan Tarrant (JIRA)
[ https://issues.jboss.org/browse/ISPN-2625?page=com.atlassian.jira.plugin.... ]
Tristan Tarrant reassigned ISPN-2625:
-------------------------------------
Assignee: (was: Mircea Markus)
> Verify Cross-site transfer performace
> -------------------------------------
>
> Key: ISPN-2625
> URL: https://issues.jboss.org/browse/ISPN-2625
> Project: Infinispan
> Issue Type: Task
> Components: Cross-Site Replication
> Affects Versions: 5.2.0.Beta5
> Reporter: Radim Vansa
> Attachments: jgroups-lon-nyc-sfo-belaban.xml, jgroups-site.xml, lon-tx-optimistic-xs-to-nyc-async.xml, nyc-tx-optimistic-xs-from-lon.xml
>
>
> The performance of asynchronous cross-site transfer is questionable. In QA lab we got 2x-4x slower reads (GET) than in no-XS scenario and write (PUT) performance equivalent to those of synchronous XS. While the code cannot be reliably profiled with instrumentation, trace logs also radically slow down the test we have not identified any particular bug that should cause this issue.
> Therefore, I'd like to ask someone from the core developers to try to reproduce such test results and provide his test description together with achieved results.
> We have used three-node cluster in distributed mode with optimistic transactions, replicating to another three-node cluster with the same configuration. Physically the nodes were in the same cluster without any delay element. The logical clusters used different multicast addresses in their JGroups configuration.
> Each node started 10 threads which issued PUT/GET requests in a loop with 1:4 ratio. Each request was wrapped in single transaction. The test was benchmarking the average duration of each operation during 10 minute period preceded by 3 minute warmup with identical configuration but not accounted into performance results.
> JGroups configurations as well as Infinispan configuration will be enclosed.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 2 months
[JBoss JIRA] (ISPN-3751) PutFromLoadValidator read stale data from the cache.
by Tristan Tarrant (JIRA)
[ https://issues.jboss.org/browse/ISPN-3751?page=com.atlassian.jira.plugin.... ]
Tristan Tarrant reassigned ISPN-3751:
-------------------------------------
Assignee: (was: Mircea Markus)
> PutFromLoadValidator read stale data from the cache.
> ----------------------------------------------------
>
> Key: ISPN-3751
> URL: https://issues.jboss.org/browse/ISPN-3751
> Project: Infinispan
> Issue Type: Bug
> Components: Transactions
> Affects Versions: 4.2.1.FINAL
> Reporter: Flemming Harms
>
> Hi,
>
> This problem actual started as a investigation on the JBoss Cache in a cluster, but we believe this also exists in Infinispan. We able to reproduce it with Infinispan also. It's a combination of a problem in the Hibernate 2LC and Infinispan so I might not be the right place to create this jira.
> This is what we have been able to find out so far. "When an invalidation event arrived on node #2 there is no callback to the 2LC layer that will make sure to call invalidate. Another problem we discover was if a collection is invalidated on node #1 twice in a row the second time no invalidation event is broadcasts to node #2, and that’s a problem because in between invalidation event #1 and #2 the PutFromLoadValidator is called on node #2 and this makes it read stale data from the cache.
> The forum link contains a possible patch for Infinispan and Hibernate 2LC, but there might be other areas in the code the patch could introduce a problem for
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 2 months
[JBoss JIRA] (ISPN-57) Support Google App Engine
by Tristan Tarrant (JIRA)
[ https://issues.jboss.org/browse/ISPN-57?page=com.atlassian.jira.plugin.sy... ]
Tristan Tarrant reassigned ISPN-57:
-----------------------------------
Assignee: (was: Mircea Markus)
> Support Google App Engine
> -------------------------
>
> Key: ISPN-57
> URL: https://issues.jboss.org/browse/ISPN-57
> Project: Infinispan
> Issue Type: Feature Request
> Components: Core
> Reporter: Adrian Cole
>
> Google App Engine for Java is a restricted JVM. It prevents such things as file access and thread creation. Currently, Infinispan requires at least thread creation and depending on the cachestore mechanism, potentially file as well.
> This is a container to investigate other related issues that may prevent Infinispan from running on GAE.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 2 months
[JBoss JIRA] (ISPN-3099) Util.loadClass() still swallows NoClassDefFoundError
by Tristan Tarrant (JIRA)
[ https://issues.jboss.org/browse/ISPN-3099?page=com.atlassian.jira.plugin.... ]
Tristan Tarrant reassigned ISPN-3099:
-------------------------------------
Assignee: (was: Mircea Markus)
> Util.loadClass() still swallows NoClassDefFoundError
> ----------------------------------------------------
>
> Key: ISPN-3099
> URL: https://issues.jboss.org/browse/ISPN-3099
> Project: Infinispan
> Issue Type: Feature Request
> Components: Core
> Affects Versions: 5.2.5.Final
> Environment: Windows, JBoss EAP 5
> Reporter: Bert Jacobs
> Attachments: report-infinispan-logging.patch
>
>
> My log contains stack traces like the following:
> {code}
> Caused by: org.infinispan.CacheConfigurationException: Unable to instantiate class org.infinispan.loaders.bdbje.BdbjeCacheStore
> at org.infinispan.util.Util.loadClass(Util.java:101)
> at org.infinispan.util.Util.getInstance(Util.java:222)
> at org.infinispan.configuration.parsing.Parser51.parseLoader(Parser51.java:440)
> at org.infinispan.configuration.parsing.Parser51.parseLoaders(Parser51.java:418)
> at org.infinispan.configuration.parsing.Parser51.parseCache(Parser51.java:189)
> at org.infinispan.configuration.parsing.Parser51.parseNamedCache(Parser51.java:148)
> at org.infinispan.configuration.parsing.Parser51.readElement(Parser51.java:115)
> at org.infinispan.configuration.parsing.Parser51.readElement(Parser51.java:84)
> at org.jboss.staxmapper.XMLMapperImpl.processNested(XMLMapperImpl.java:110)
> at org.jboss.staxmapper.XMLMapperImpl.parseDocument(XMLMapperImpl.java:69)
> at org.infinispan.configuration.parsing.ParserRegistry.parse(ParserRegistry.java:77)
> ... 73 more
> Caused by: java.lang.ClassNotFoundException: org.infinispan.loaders.bdbje.BdbjeCacheStore
> at java.net.URLClassLoader$1.run(URLClassLoader.java:202)
> at java.security.AccessController.doPrivileged(Native Method)
> at java.net.URLClassLoader.findClass(URLClassLoader.java:190)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:306)
> at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:301)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:247)
> at java.lang.Class.forName0(Native Method)
> at java.lang.Class.forName(Class.java:249)
> at org.infinispan.util.Util.loadClassStrict(Util.java:138)
> at org.infinispan.util.Util.loadClass(Util.java:99)
> ... 83 more
> {code}
> However, this ClassNotFoundException comes from the System classloader, but the code still swallows the following Error:
> {code}
> Caused by: org.infinispan.CacheConfigurationException: Unable to instantiate class org.infinispan.loaders.bdbje.BdbjeCacheStore
> at org.infinispan.util.Util.loadClass(Util.java:101)
> [SNIP - see above]
> at org.infinispan.configuration.parsing.ParserRegistry.parse(ParserRegistry.java:77)
> ... 73 more
> Caused by: java.lang.ClassNotFoundException: org.infinispan.loaders.bdbje.BdbjeCacheStore
> at org.infinispan.util.Util.loadClassStrict(Util.java:150)
> at org.infinispan.util.Util.loadClass(Util.java:99)
> ... 83 more
> Caused by: java.lang.NoClassDefFoundError: com/sleepycat/collections/TransactionWorker
> at java.lang.Class.forName0(Native Method)
> at java.lang.Class.forName(Class.java:249)
> at org.infinispan.util.Util.loadClassStrict(Util.java:138)
> ... 84 more
> Caused by: java.lang.ClassNotFoundException: com.sleepycat.collections.TransactionWorker from BaseClassLoader@3598d24f{vfsfile:/D:/App/Java/jboss/brms-standalone-5.3.0/jboss-as/server/lettergen-ds-default/deploy/modeshape-datastore.ear/}
> at org.jboss.classloader.spi.base.BaseClassLoader.loadClass(BaseClassLoader.java:477)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:247)
> ... 87 more
> {code}
> It is this error which is actually important: the BdbjeCacheStore class was found but it cannot be loaded because the sleepycat jar is not on the classpath. It is impossible to see this without changing the code.
> The commits for ISPN-2559 did not properly fix this problem. The Error should be logged in all cases because the ClassNotFoundException will also happen in almost every case: the last search ClassLoader is the System ClassLoader which will likely never have the searched class.
> Once again: please log all NoClassDefFoundErrors (suppressing Errors is bad in any case) or at least handle them *before* handling any ClassNotFoundExceptions. The attached patch does exactly that.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 2 months