[JBoss JIRA] (ISPN-1846) Use correct version of Transactions API
by Sanne Grinovero (JIRA)
Sanne Grinovero created ISPN-1846:
-------------------------------------
Summary: Use correct version of Transactions API
Key: ISPN-1846
URL: https://issues.jboss.org/browse/ISPN-1846
Project: Infinispan
Issue Type: Component Upgrade
Affects Versions: 5.1.1.FINAL, 5.1.0.FINAL
Reporter: Sanne Grinovero
Assignee: Manik Surtani
Fix For: 5.2.0.ALPHA1, 5.2.0.FINAL
As discuseed on mailing list:
>From Pete Muir:
{quote}
On 7 Feb 2012, at 14:22, Sanne Grinovero wrote:
> I'm having the transactions API defined by both the following packages:
>
> Hibernate core depends on:
>
> <parent>
> <groupId>org.jboss.spec</groupId>
> <artifactId>jboss-specs-parent</artifactId>
> <version>1.0.0.Beta2</version>
> </parent>
> <groupId>org.jboss.spec.javax.transaction</groupId>
> <artifactId>jboss-transaction-api_1.1_spec</artifactId>
> <version>1.0.0.Final</version>
This is the new (correct) location.
>
> Infinispan core depends on:
>
> <parent>
> <groupId>org.jboss.javaee</groupId>
> <artifactId>jboss-javaee-parent</artifactId>
> <version>5.2.0.Beta1</version>
> </parent>
> <groupId>org.jboss.javaee</groupId>
> <artifactId>jboss-transaction-api</artifactId>
> <version>1.0.1.GA</version>
>
> I'd like to introduce some consistency, especially since some project use both.
> Which one should we use ?
This is way out of date.
>
> AS 7.1 [master]
> is using
> <dependency>
> <groupId>org.jboss.spec.javax.transaction</groupId>
> <artifactId>jboss-transaction-api_1.1_spec</artifactId>
> <version>1.0.0.Final</version>
> </dependency>
>
> So I guess Infinispan should pick the same?
{quote}
--
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
12 years, 10 months
[JBoss JIRA] (ISPN-1860) HotRod client topology info can get out of sync with the server topology info
by Dan Berindei (JIRA)
Dan Berindei created ISPN-1860:
----------------------------------
Summary: HotRod client topology info can get out of sync with the server topology info
Key: ISPN-1860
URL: https://issues.jboss.org/browse/ISPN-1860
Project: Infinispan
Issue Type: Bug
Components: Cache Server
Affects Versions: 5.1.1.FINAL
Reporter: Dan Berindei
Assignee: Manik Surtani
Fix For: 5.2.0.FINAL
Say we have a HotRod cluster with a JGroups view A1 [A, B]. A client makes a get request to A, and it receives topology id 1, with nodes [A, B].
Another node C joins the HotRod cluster, and the JGroups view becomes A2 [A, B, C]. It takes a certain time for C to finish joining the topology cache, so for a limited amount of time the topology cache on A only contains [A, B].
If the client makes another get request during this time interval, it will receive topology id 2, but still with nodes [A, B]. So its consistent hash will not contain C.
Future requests from the same client will send topology id 2 to the server, so the server will believe that the client's CH is [A, B, C] and won't send another topology update until another JGroups view is installed (because of a join, leave, or merge).
Note that this can happen even if the client had C in its initial host list, because topology updates override the initial host list.
--
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
12 years, 10 months
[JBoss JIRA] (ISPN-1859) CacheManager.defineConfiguration override doesn't work for hash configuration values
by William Burns (JIRA)
William Burns created ISPN-1859:
-----------------------------------
Summary: CacheManager.defineConfiguration override doesn't work for hash configuration values
Key: ISPN-1859
URL: https://issues.jboss.org/browse/ISPN-1859
Project: Infinispan
Issue Type: Bug
Affects Versions: 5.1.1.FINAL
Reporter: William Burns
Assignee: Manik Surtani
While testing some stuff for ISPN-1837, I found that the hash configuration for DIST doesn't override properly when using the defineConfiguration method on the DefaultCacheManager. The problem is that the OverrideConfigurationVisitor doesn't copy over the activated value, so when the config is copied it over it doesn't think the hash configuration was touched and subsequently skips it.
The interesting thing is that L1 should also be broken, but because of how the LegacyConfigurationAdaptor works it actually activates L1 no matter what, since it will either enable or disable it.
Also the override works properly if the default has a setting for the hash configuration.
I have a testNG that very easily shows this.
--
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
12 years, 10 months
[JBoss JIRA] (ISPN-1868) enable() method is missing after async() in "ConfigurationBuilder Programmatic Configuration API"
by Christophe Domas (JIRA)
Christophe Domas created ISPN-1868:
--------------------------------------
Summary: enable() method is missing after async() in "ConfigurationBuilder Programmatic Configuration API"
Key: ISPN-1868
URL: https://issues.jboss.org/browse/ISPN-1868
Project: Infinispan
Issue Type: Bug
Components: Demos and Tutorials
Affects Versions: 5.1.1.FINAL
Reporter: Christophe Domas
Assignee: Manik Surtani
In
doc: https://docs.jboss.org/author/display/ISPN/Configuring+cache+programmatic...
section: "Configuring Infinispan with one or several chained persistent stores is simple too:"
I think enable() is missing after async() in the following code (with infinispan-5.1.1):
actual doc:
{code}
Configuration config = new ConfigurationBuilder()
.loaders()
.shared(false).passivation(false).preload(false)
.addFileCacheStore().location("/tmp").streamBufferSize(1800).async().threadPoolSize(20).build();
{code}
corrected doc:
{code}
Configuration config = new ConfigurationBuilder()
.loaders()
.shared(false).passivation(false).preload(false)
.addFileCacheStore().location("/tmp").streamBufferSize(1800).async().enable().threadPoolSize(20).build();
{code}
I added a comment on the page you can remove (I spent so much time to understand why it didn't works that I've filled a ticket to ask for toString() methods in configuration objects: ISPN-1861)
--
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
12 years, 10 months