[JBoss JIRA] (ISPN-2145) No descriptions for invalid jgroups configuration files
by Galder Zamarreño (JIRA)
[ https://issues.jboss.org/browse/ISPN-2145?page=com.atlassian.jira.plugin.... ]
Galder Zamarreño updated ISPN-2145:
-----------------------------------
Fix Version/s: 7.1.0.Alpha1
(was: 7.0.0.Final)
> No descriptions for invalid jgroups configuration files
> -------------------------------------------------------
>
> Key: ISPN-2145
> URL: https://issues.jboss.org/browse/ISPN-2145
> Project: Infinispan
> Issue Type: Bug
> Components: Core
> Affects Versions: 5.1.2.FINAL, 7.0.0.CR1
> Environment: Any
> Reporter: Dmitry Udalov
> Assignee: Tristan Tarrant
> Fix For: 7.1.0.Alpha1
>
>
> Can't find error's description for invalid jgroups configuration files. Shuffling elements of the file (why not!) makes it invalid, but log-files only report the existence of the error and you have to debug it to figure out the problem. It would be easier if the class JGroupsTransport also reports the exception, not just a generic message in blocks like
> } catch (Exception e) {
> log.errorCreatingChannelFromConfigFile(cfg);
> throw new CacheException(e);
> }
> As a result log-file contains a lot of generic messages without explaining the problem, which in my case was quite helpful:
> java.lang.Exception: events [GET_DIGEST SET_DIGEST FIND_INITIAL_MBRS FIND_ALL_VIEWS ] are required by GMS, but not provided by any of the protocols below it
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 5 months
[JBoss JIRA] (ISPN-3198) Allow multiple versions of entries to be stored
by Galder Zamarreño (JIRA)
[ https://issues.jboss.org/browse/ISPN-3198?page=com.atlassian.jira.plugin.... ]
Galder Zamarreño updated ISPN-3198:
-----------------------------------
Fix Version/s: 7.1.0.Alpha1
(was: 7.0.0.Final)
> Allow multiple versions of entries to be stored
> -----------------------------------------------
>
> Key: ISPN-3198
> URL: https://issues.jboss.org/browse/ISPN-3198
> Project: Infinispan
> Issue Type: Feature Request
> Components: Core
> Affects Versions: 5.3.0.Final
> Reporter: Manik Surtani
> Assignee: Mircea Markus
> Labels: leads, versioning
> Fix For: 7.1.0.Alpha1
>
>
> Storing multiple versions of a given entry will pave the way for eventual consistency based on vector clocks as well as the ability for API-controlled versioning.
> Will require that each entry is a structure that contains multiple actual entries ordered by version.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 5 months
[JBoss JIRA] (ISPN-3199) API to manipulate multiple versions of an entry
by Galder Zamarreño (JIRA)
[ https://issues.jboss.org/browse/ISPN-3199?page=com.atlassian.jira.plugin.... ]
Galder Zamarreño updated ISPN-3199:
-----------------------------------
Fix Version/s: 7.1.0.Alpha1
(was: 7.0.0.Final)
> API to manipulate multiple versions of an entry
> -----------------------------------------------
>
> Key: ISPN-3199
> URL: https://issues.jboss.org/browse/ISPN-3199
> Project: Infinispan
> Issue Type: Feature Request
> Components: Core
> Affects Versions: 5.3.0.Final
> Reporter: Manik Surtani
> Assignee: Mircea Markus
> Labels: leads
> Fix For: 7.1.0.Alpha1
>
>
> In addition to the existing API, the following will be needed to allow user applications to directly control versioning. E.g.,
> {code}
> put(K key, EntryVersion version);
> get(K key, EntryVersion version);
> getLatest(K key, EntryVersion upperBound);
> evict(K key, EntryVersion upTo);
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 5 months