[JBoss JIRA] (ISPN-5552) Cannot start persistence cache: CacheException
by Tristan Tarrant (JIRA)
[ https://issues.jboss.org/browse/ISPN-5552?page=com.atlassian.jira.plugin.... ]
Tristan Tarrant commented on ISPN-5552:
---------------------------------------
You'd better ask on the forum https://developer.jboss.org/en/infinispan/content?filterID=contentstatus[...
> Cannot start persistence cache: CacheException
> ----------------------------------------------
>
> Key: ISPN-5552
> URL: https://issues.jboss.org/browse/ISPN-5552
> Project: Infinispan
> Issue Type: Bug
> Affects Versions: 6.0.3.Final
> Environment: WildFly 8.2.0 / Linux
> Reporter: Veli Cris
>
> Hi,
> I have the following configuration for persistence cache (MySQL) and when I try to start the cache I get CacheException error. Basically what I want is to save the records from cache called 'mycache' in MySQL table called 'bean.bean_session'. Thank you.
> org.infinispan.commons.CacheException: Unable to invoke method public void org.infinispan.persistence.manager.PersistenceManagerImpl.start() on object of type PersistenceManagerImpl
> ConfigurationBuilder builder = new ConfigurationBuilder();
> Configuration config = builder.persistence()
> .addStore(JdbcBinaryStoreConfigurationBuilder.class)
> .fetchPersistentState(false)
> .ignoreModifications(false)
> .purgeOnStartup(false)
> .table()
> .dropOnExit(true)
> .createOnStart(true)
> .tableNamePrefix("bean_session")
> .idColumnName("id").idColumnType("INT(11)")
> .dataColumnName("string").dataColumnType("TEXT")
> .timestampColumnName("timestamp").timestampColumnType("TIMESTAMP")
> .connectionPool()
> .connectionUrl("jdbc:mysql://localhost:3306/bean")
> .username("root").password("1234567")
> .driverClass("com.mysql.jdbc.Driver").build();
> DefaultCacheManager manager = new DefaultCacheManager();
> manager.defineConfiguration("mycache", config);
> Cache cache = manager.getCache("mycache");
> cache.put("1", "1");
> cache.put("2", "2");
> cache.put("3", "3");
> cache.start();
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
9 years
[JBoss JIRA] (ISPN-5010) Improve remote listener performance
by Galder Zamarreño (JIRA)
[ https://issues.jboss.org/browse/ISPN-5010?page=com.atlassian.jira.plugin.... ]
Galder Zamarreño resolved ISPN-5010.
------------------------------------
Fix Version/s: (was: 8.0.0.Final)
Resolution: Deferred
Some improvements have been added as part of ISPN-5523, but the real performance improvements will arrive when events can be more fine grained, once the functionality underlying ISPN-5545 allows for remote listeners to selectively decide which keys and which operations they want to receive events on.
> Improve remote listener performance
> -----------------------------------
>
> Key: ISPN-5010
> URL: https://issues.jboss.org/browse/ISPN-5010
> Project: Infinispan
> Issue Type: Enhancement
> Components: Remote Protocols
> Affects Versions: 7.0.2.Final
> Reporter: Galder Zamarreño
> Assignee: Galder Zamarreño
>
> We've run some performance tests and we've noticed remote listeners have a too negative effect on get/put/remove operations, particularly as number of listeners added by clients increase. This JIRA encompasses different pieces of work to improve this:
> * Make server-side clustered listener async. By doing so, the operations are detached from the actual server-side listener part when the notification is sent to clients. Async listener executor is configured with 1 thread, so order is still maintained.
> * Batching at the server-side clustered listener side. Instead of sending each event as it comes, apply time/size based batching to reduce number of system calls to flush sockets to clients.
> * Further improvements might come from bundling listeners added by same client, but this is more complicated to achieve, since only those listeners that have similar characteristics can be bundled, e.g. have same filter/converter settings. Also, whether to use a single connection for all listeners or maintain separate ones still would need to be decided. (see ISPN-4491)
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
9 years
[JBoss JIRA] (ISPN-5553) Functional Java 8 API
by Galder Zamarreño (JIRA)
Galder Zamarreño created ISPN-5553:
--------------------------------------
Summary: Functional Java 8 API
Key: ISPN-5553
URL: https://issues.jboss.org/browse/ISPN-5553
Project: Infinispan
Issue Type: Feature Request
Reporter: Galder Zamarreño
Assignee: Galder Zamarreño
Fix For: 8.0.0.Final
Infinispan 8 is baselining on Java 8 and that enables a more advanced , functional, APIs to be built instead of relying on the traditional Map-like APIs. Such APIs, taking lambda functions, can improve on the current APIs in the following way:
* Being able to provide a write operation, where the operation is defined as a lambda, better enables conditional (CAS) like operations that are based in functions other than equality, e.g. version equality. If this functions can be executed atomically, they provide a better solution for Hot Rod version-based replace operations that currently can cause some weird behaviour (ISPN-4972)
* When operations are defined as lambdas, it's easier to move towards a model that tracks/replicates operations leading to state, rather than replicating state itself. This makes it easier to implement more-efficiently replicated alternative data structures, such as counts, lists...etc, and paths the way towards CRDTs, particularly CmRDT (Commutative Replicated Data Types) or operation-based CRDTs.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
9 years
[JBoss JIRA] (ISPN-5551) Infinispan AS modules artifact should include JBoss Marshalling
by Horia Chiorean (JIRA)
[ https://issues.jboss.org/browse/ISPN-5551?page=com.atlassian.jira.plugin.... ]
Horia Chiorean commented on ISPN-5551:
--------------------------------------
{quote}
As long as the container provided JBMAR is compatible with the Infinispan integration code - and all nodes consistently use the same version of JBMAR - I don't see why it would be a problem?
{quote}
This is not the case with Wildfly 8.2.0: {{jboss-marshalling-1.4.9.Final.jar}} from Wildfly seems to not be compatible with {{org.jboss.marshalling:jboss-marshalling-osgi:jar:1.4.10.Final}} which is what IPSN 7.2.0.Final requires.
Since the ISPN Maven artifact is a "generic" AS artifact, I would expect it to have all of ISPN's required dependencies bundled, as opposed to expecting that a container provides a certain version of a component.
> Infinispan AS modules artifact should include JBoss Marshalling
> ---------------------------------------------------------------
>
> Key: ISPN-5551
> URL: https://issues.jboss.org/browse/ISPN-5551
> Project: Infinispan
> Issue Type: Bug
> Affects Versions: 7.2.2.Final
> Reporter: Horia Chiorean
> Assignee: Tristan Tarrant
> Fix For: 8.0.0.Alpha2, 7.2.3.Final, 8.0.0.Final
>
>
> Infinispan 7 provides the following Maven artifact:
> {code:xml}
> <dependency>
> <groupId>org.infinispan</groupId>
> <artifactId>infinispan-as-embedded-modules</artifactId>
> <type>zip</type>
> </dependency>
> {code}
> which can be used (and is used by ModeShape) when running in a JBoss AS instance.
> However, this artifact does not contain the version of JBoss Marshalling that a particular version of Infinspan requires but rather picks up the {{main}} version which is available in the container:
> {code:xml}
> <module name="org.jboss.marshalling"/>
> <module name="org.jboss.marshalling.river" services="import"/>
> {code}
> Because of this, when deploying Infinispan 7.2.x in Wildfly 8.2.0, Infinispan will pick up the version of marshalling delivered by Wildfly (1.4.9.Final instead of 1.4.10.Final) causing class cast exceptions like:
> {code:java}
> Caused by: java.lang.ClassCastException: java.lang.String cannot be cast to org.jboss.marshalling.Externalizer
> at org.jboss.marshalling.river.RiverUnmarshaller.doReadClassDescriptor(RiverUnmarshaller.java:1012)
> at org.jboss.marshalling.river.RiverUnmarshaller.doReadNewObject(RiverUnmarshaller.java:1256)
> at org.jboss.marshalling.river.RiverUnmarshaller.doReadObject(RiverUnmarshaller.java:276)
> at org.jboss.marshalling.river.RiverUnmarshaller.doReadObject(RiverUnmarshaller.java:209)
> at org.jboss.marshalling.AbstractObjectInput.readObject(AbstractObjectInput.java:41)
> at org.infinispan.commons.marshall.jboss.AbstractJBossMarshaller.objectFromObjectStream(AbstractJBossMarshaller.java:135) [infinispan-commons.jar:7.2.0.Final]
> at org.infinispan.marshall.core.VersionAwareMarshaller.objectFromByteBuffer(VersionAwareMarshaller.java:101) [infinispan-core.jar:7.2.0.Final]
> at org.infinispan.commons.marshall.AbstractDelegatingMarshaller.objectFromByteBuffer(AbstractDelegatingMarshaller.java:80) [infinispan-commons.jar:7.2.0.Final]
> at org.infinispan.marshall.core.MarshalledEntryImpl.unmarshall(MarshalledEntryImpl.java:114) [infinispan-core.jar:7.2.0.Final]
> ... 162 more
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
9 years
[JBoss JIRA] (ISPN-5552) Cannot start persistence cache: CacheException
by Veli Cris (JIRA)
[ https://issues.jboss.org/browse/ISPN-5552?page=com.atlassian.jira.plugin.... ]
Veli Cris commented on ISPN-5552:
---------------------------------
Hi Tristan you are absolutely right. This is not actually an issue, I managed to use infinispan cache store with Datasources (jndi).
I have another question and I don't know where to ask: Is there any possibility to store data column as simple String and not as Serializable object in database?
> Cannot start persistence cache: CacheException
> ----------------------------------------------
>
> Key: ISPN-5552
> URL: https://issues.jboss.org/browse/ISPN-5552
> Project: Infinispan
> Issue Type: Bug
> Affects Versions: 6.0.3.Final
> Environment: WildFly 8.2.0 / Linux
> Reporter: Veli Cris
>
> Hi,
> I have the following configuration for persistence cache (MySQL) and when I try to start the cache I get CacheException error. Basically what I want is to save the records from cache called 'mycache' in MySQL table called 'bean.bean_session'. Thank you.
> org.infinispan.commons.CacheException: Unable to invoke method public void org.infinispan.persistence.manager.PersistenceManagerImpl.start() on object of type PersistenceManagerImpl
> ConfigurationBuilder builder = new ConfigurationBuilder();
> Configuration config = builder.persistence()
> .addStore(JdbcBinaryStoreConfigurationBuilder.class)
> .fetchPersistentState(false)
> .ignoreModifications(false)
> .purgeOnStartup(false)
> .table()
> .dropOnExit(true)
> .createOnStart(true)
> .tableNamePrefix("bean_session")
> .idColumnName("id").idColumnType("INT(11)")
> .dataColumnName("string").dataColumnType("TEXT")
> .timestampColumnName("timestamp").timestampColumnType("TIMESTAMP")
> .connectionPool()
> .connectionUrl("jdbc:mysql://localhost:3306/bean")
> .username("root").password("1234567")
> .driverClass("com.mysql.jdbc.Driver").build();
> DefaultCacheManager manager = new DefaultCacheManager();
> manager.defineConfiguration("mycache", config);
> Cache cache = manager.getCache("mycache");
> cache.put("1", "1");
> cache.put("2", "2");
> cache.put("3", "3");
> cache.start();
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
9 years