September 2009 - infinispan-issues

[JBoss JIRA] Commented: (ISPN-25) JGroups ships with an XSD schema. Use this schema when validating configurations.

by Vladimir Blagojevic (JIRA)

[ https://jira.jboss.org/jira/browse/ISPN-25?page=com.atlassian.jira.plugin... ] Vladimir Blagojevic commented on ISPN-25: ----------------------------------------- Note: This issue is actually resolved after 2.8.0.CR2 or later JGroups release becomes integrated with Infinispan > JGroups ships with an XSD schema. Use this schema when validating configurations. > ---------------------------------------------------------------------------------- > > Key: ISPN-25 > URL: https://jira.jboss.org/jira/browse/ISPN-25 > Project: Infinispan > Issue Type: Feature Request > Components: Configuration, RPC > Reporter: Manik Surtani > Assignee: Vladimir Blagojevic > Fix For: 4.0.0.CR1, 4.0.0.GA > > -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 7 months

1
0
0 / 0

[JBoss JIRA] Resolved: (ISPN-25) JGroups ships with an XSD schema. Use this schema when validating configurations.

by Vladimir Blagojevic (JIRA)

[ https://jira.jboss.org/jira/browse/ISPN-25?page=com.atlassian.jira.plugin... ] Vladimir Blagojevic resolved ISPN-25. ------------------------------------- Resolution: Done Resolved in JGroups 2.8.0.CR2 and after. Simply set system property "jgroups.xml.validation" to true. By default it is false - i.e no validation is done. > JGroups ships with an XSD schema. Use this schema when validating configurations. > ---------------------------------------------------------------------------------- > > Key: ISPN-25 > URL: https://jira.jboss.org/jira/browse/ISPN-25 > Project: Infinispan > Issue Type: Feature Request > Components: Configuration, RPC > Reporter: Manik Surtani > Assignee: Vladimir Blagojevic > Fix For: 4.0.0.CR1, 4.0.0.GA > > -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 7 months

1
0
0 / 0

[JBoss JIRA] Resolved: (ISPN-181) Specify node name in JGroups channel

by Vladimir Blagojevic (JIRA)

[ https://jira.jboss.org/jira/browse/ISPN-181?page=com.atlassian.jira.plugi... ] Vladimir Blagojevic resolved ISPN-181. -------------------------------------- Resolution: Done http://fisheye.jboss.org/changelog/Infinispan/?cs=849 http://lists.jboss.org/pipermail/infinispan-dev/2009-September/001438.html > Specify node name in JGroups channel > ------------------------------------ > > Key: ISPN-181 > URL: https://jira.jboss.org/jira/browse/ISPN-181 > Project: Infinispan > Issue Type: Feature Request > Affects Versions: 4.0.0.BETA1 > Reporter: Manik Surtani > Assignee: Vladimir Blagojevic > Fix For: 4.0.0.CR1, 4.0.0.GA > > > Should be a simple configuration element (perhaps in <transport ... >) where node-name can be specified, and passed in to the JGroups channel (channel.setName()) for clearer logging. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 7 months

1
0
0 / 0

[JBoss JIRA] Resolved: (ISPN-182) Allow users to set node name in configuration

by Manik Surtani (JIRA)

[ https://jira.jboss.org/jira/browse/ISPN-182?page=com.atlassian.jira.plugi... ] Manik Surtani resolved ISPN-182. -------------------------------- Fix Version/s: (was: 4.0.0.GA) (was: 4.0.0.CR1) Resolution: Duplicate Issue See ISPN-181 > Allow users to set node name in configuration > --------------------------------------------- > > Key: ISPN-182 > URL: https://jira.jboss.org/jira/browse/ISPN-182 > Project: Infinispan > Issue Type: Feature Request > Components: Configuration > Affects Versions: 4.0.0.BETA1 > Reporter: Manik Surtani > Assignee: Vladimir Blagojevic > > Perhaps in the <transport... /> element, as nodeName. If set, this value should be passed in to channel.setName() (or not set if null). This allows JGroups to provide clearer logging. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 7 months

1
0
0 / 0

[JBoss JIRA] Work started: (ISPN-32) Integrate Query API

by Navin Surtani (JIRA)

[ https://jira.jboss.org/jira/browse/ISPN-32?page=com.atlassian.jira.plugin... ] Work on ISPN-32 started by Navin Surtani. > Integrate Query API > ------------------- > > Key: ISPN-32 > URL: https://jira.jboss.org/jira/browse/ISPN-32 > Project: Infinispan > Issue Type: Feature Request > Components: Querying > Affects Versions: 4.0.0.BETA1 > Reporter: Manik Surtani > Assignee: Navin Surtani > Fix For: 4.0.0.CR1, 4.0.0.GA > > > Grab this from JBCS -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 7 months

1
0
0 / 0

[JBoss JIRA] Commented: (ISPN-46) Feature comparison with other products

by Thomas Louis (JIRA)

[ https://jira.jboss.org/jira/browse/ISPN-46?page=com.atlassian.jira.plugin... ] Thomas Louis commented on ISPN-46: ---------------------------------- One big point (for me) in this comparison matrix would be, how easy the products supports messaging. I like the way GigaSpaces does this by simply listen to the space (aka cache, grid, whatever) with a matching template. The listener gets triggered when an objects appears that matches the template. The listener can be triggered within the transaction or asynchronously behind it. It's an very easy, comfortable and highly scalable way of implementing a process chain. But I can only mention what the way is, gigaspaces does this and I'm very interested if this is possible with the other products too. > Feature comparison with other products > -------------------------------------- > > Key: ISPN-46 > URL: https://jira.jboss.org/jira/browse/ISPN-46 > Project: Infinispan > Issue Type: Task > Reporter: Mircea Markus > Assignee: Mircea Markus > Fix For: 4.0.0.CR1, 4.0.0.GA > > > Compare (feature wise) against other products: > - Coherence, Terracotta and gigaspaces, hadoop, mogileFS -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 7 months

1
0
0 / 0

[JBoss JIRA] Commented: (ISPN-46) Feature comparison with other products

by Thomas Louis (JIRA)

[ https://jira.jboss.org/jira/browse/ISPN-46?page=com.atlassian.jira.plugin... ] Thomas Louis commented on ISPN-46: ---------------------------------- Please take a look at http://www.hazelcast.com/. It should be added to comparison. > Feature comparison with other products > -------------------------------------- > > Key: ISPN-46 > URL: https://jira.jboss.org/jira/browse/ISPN-46 > Project: Infinispan > Issue Type: Task > Reporter: Mircea Markus > Assignee: Mircea Markus > Fix For: 4.0.0.CR1, 4.0.0.GA > > > Compare (feature wise) against other products: > - Coherence, Terracotta and gigaspaces, hadoop, mogileFS -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 7 months

1
0
0 / 0

[JBoss JIRA] Created: (ISPN-191) Invalid configuration in /etc/config-samples/all.xml

by Galder Zamarreno (JIRA)

Invalid configuration in /etc/config-samples/all.xml ---------------------------------------------------- Key: ISPN-191 URL: https://jira.jboss.org/jira/browse/ISPN-191 Project: Infinispan Issue Type: Bug Components: Configuration Affects Versions: 4.0.0.BETA1 Reporter: Galder Zamarreno Assignee: Galder Zamarreno Fix For: 4.0.0.CR1 I just tried to create a cache with $INFINISPAN_HOME/etc/config-samples/all.xml config file, but I'm getting a XML parse exception: http://pastie.org/614523 When I remove batchSize="1000" attribute from that file (line 170), everything works. Bad config sample? -- Marek Goldmann JBoss by Red Hat -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 7 months

1
1
0 / 0

[JBoss JIRA] Created: (ISPN-158) Verify eviction and marshalled values interaction

by Galder Zamarreno (JIRA)

Verify eviction and marshalled values interaction ------------------------------------------------- Key: ISPN-158 URL: https://jira.jboss.org/jira/browse/ISPN-158 Project: Infinispan Issue Type: Task Components: Eviction Affects Versions: 4.0.0.ALPHA6 Reporter: Galder Zamarreno Assignee: Galder Zamarreno Fix For: 4.0.0.BETA1 Here's a further thought - we also need to test the eviction thread with marshalled values. Well, not necessarily the eviction *thread* per-se, but eviction being invoked via the EvictionManager.processEviction() API - which is used by the eviction thread as well as any external management thread that may wish to schedule eviction. My reason for concern is that this retrieves keys in order of evictability by querying the data container (which is ordered) directly. Now if these keys are marshalled values, what happens when the EvictionManager calls cache.evict(key)? What *should* happen is that the MarshalledValueInerceptor detects that the key is a marshalled value already, and does not bother with further wrapping and unwrapping. However I don't think we currently have a unit test for this. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 7 months

2
4
0 / 0

[JBoss JIRA] Created: (ISPN-145) No transport and singleton store enabled should not be allowed

by Galder Zamarreno (JIRA)

No transport and singleton store enabled should not be allowed -------------------------------------------------------------- Key: ISPN-145 URL: https://jira.jboss.org/jira/browse/ISPN-145 Project: Infinispan Issue Type: Bug Components: Loaders and Stores Affects Versions: 4.0.0.ALPHA6 Reporter: Galder Zamarreno Assignee: Galder Zamarreno Fix For: 4.0.0.BETA1 Throw configuration exception if singleton store configured without transport having been configured. It makes no sense to have singleton store enabled when there's no transport. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 7 months

3
6
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues September 2009