[JBoss JIRA] (ISPN-2766) Improve and adapt notification model to fit JSR107 notification model
by Galder Zamarreño (JIRA)
[ https://issues.jboss.org/browse/ISPN-2766?page=com.atlassian.jira.plugin.... ]
Galder Zamarreño updated ISPN-2766:
-----------------------------------
Component/s: JCache
> Improve and adapt notification model to fit JSR107 notification model
> ---------------------------------------------------------------------
>
> Key: ISPN-2766
> URL: https://issues.jboss.org/browse/ISPN-2766
> Project: Infinispan
> Issue Type: Sub-task
> Components: JCache, Listeners
> Affects Versions: 5.2.0.CR3
> Reporter: Vladimir Blagojevic
> Assignee: Galder Zamarreño
> Fix For: 5.3.0.Alpha1
>
>
> Out current notification (listener) model does not fit JSR 107 notification model and thus needs a slight adaptation in order to implement JSR 107.
> More specifically the problem is with JSR107 CacheEntryCreatedListener and CacheEntryExpiredListener.
> The first one is not easy to implement because we need both key/value pair for jsr listener and our CacheEntryCreatedEvent does not provide value.
> The second is related to CacheEntryExpired event. True, spec is not rigorous that such an event has to be fired immediately after an entry has expired but eventually (which might be on access). However, we do not have such an event at all as of now.
>
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 10 months
[JBoss JIRA] (ISPN-1697) Empty Infinispan config starting transport
by Galder Zamarreño (JIRA)
[ https://issues.jboss.org/browse/ISPN-1697?page=com.atlassian.jira.plugin.... ]
Galder Zamarreño resolved ISPN-1697.
------------------------------------
Fix Version/s: (was: 5.3.0.Final)
Resolution: Duplicate Issue
> Empty Infinispan config starting transport
> ------------------------------------------
>
> Key: ISPN-1697
> URL: https://issues.jboss.org/browse/ISPN-1697
> Project: Infinispan
> Issue Type: Bug
> Reporter: Galder Zamarreño
> Assignee: Galder Zamarreño
>
> Note: I think ISPN-1691 and ISPN-1692 will fix this (This failure happens without them applied). Making a note just in case...
> Running the testsuite I see:
> {code} <failure message="Unknown warning discovered in file minimal.xml: JOIN(dhcp-144-239-26807) sent to dhcp-144-239-47868 timed out (after 3000 ms),
> retrying" type="java.lang.AssertionError">java.lang.AssertionError: Unknown warning discovered in file minimal.xml: JOIN(dhcp-144-239-26807) sent to dhcp-144-
> 239-47868 timed out (after 3000 ms), retrying
> at org.infinispan.config.SampleConfigFilesCorrectnessTest.testConfigWarnings(SampleConfigFilesCorrectnessTest.java:80)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> {code}
> minimal.xml has no global configuration (nor transport) defined, so why on earth does a JOIN happen?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 10 months
[JBoss JIRA] (ISPN-2761) Write tests for the RHQ plugin
by Tristan Tarrant (JIRA)
[ https://issues.jboss.org/browse/ISPN-2761?page=com.atlassian.jira.plugin.... ]
Tristan Tarrant reassigned ISPN-2761:
-------------------------------------
Assignee: Tristan Tarrant (was: Mircea Markus)
> Write tests for the RHQ plugin
> ------------------------------
>
> Key: ISPN-2761
> URL: https://issues.jboss.org/browse/ISPN-2761
> Project: Infinispan
> Issue Type: Task
> Components: JMX, reporting and management
> Affects Versions: 5.2.0.CR3
> Reporter: Dan Berindei
> Assignee: Tristan Tarrant
> Fix For: 6.0.0.Final
>
>
> The RHQ plugin doesn't have any functional tests at the moment. The InfinispanRhqTest class just starts a cache manager and waits for someone to start RHQ manually and connect to it.
> Instead we should have a test that creates a {{CacheComponent}} instance and invokes several operations on it, reads attributes etc.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 10 months