[JBoss JIRA] (ISPN-5997) JMX operation ClusterCacheStats.resetStatistics() not working
by Tristan Tarrant (Jira)
[ https://issues.jboss.org/browse/ISPN-5997?page=com.atlassian.jira.plugin.... ]
Tristan Tarrant updated ISPN-5997:
----------------------------------
Sprint: Sprint 9.4.0.Beta1, Sprint 9.4.0.CR1, Sprint 9.4.0.CR3, Sprint 10.0.0.Alpha1, Sprint 10.0.0.Alpha2, Sprint 9.4.0.Final, Sprint 10.0.0.Alpha0, Sprint 10.0.0.Beta1, DataGrid Sprint #31, DataGrid Sprint #32, DataGrid Sprint #33 (was: Sprint 9.4.0.Beta1, Sprint 9.4.0.CR1, Sprint 9.4.0.CR3, Sprint 10.0.0.Alpha1, Sprint 10.0.0.Alpha2, Sprint 9.4.0.Final, Sprint 10.0.0.Alpha0, Sprint 10.0.0.Beta1, DataGrid Sprint #31, DataGrid Sprint #32)
> JMX operation ClusterCacheStats.resetStatistics() not working
> -------------------------------------------------------------
>
> Key: ISPN-5997
> URL: https://issues.jboss.org/browse/ISPN-5997
> Project: Infinispan
> Issue Type: Bug
> Components: Server
> Affects Versions: 8.1.0.CR1
> Reporter: Jiří Holuša
> Assignee: Vladimir Blagojevic
> Priority: Major
>
> Environment: 2 servers started in domain mode (ISPN 8.1.0.CR1).
> Having some clustered cache, inserted/read some entries (just to create some statistics).
> When connected via JMX (e.g. through JConsole, see https://issues.jboss.org/browse/ISPN-5983 ) to one of the servers, I execute resetStatistics() operation on ClusterCacheStats MBean (object name: jboss.datagrid-infinispan:type=Cache,name="<cache-name>",manager="<cache-container-name>",component=ClusterCacheStats) and nothing happens, the cluster statistics are not reset.
> To actually reset the statistics, I have to connect to each of the servers in domain individually and call resetStatistics() on Statistics MBean, which deletes "a portion" of statistics of that particular server to the cluster stats.
> I would expect ClusterCacheStats.resetStatistics() to do exactly the same: call Statistics.resetStatistics() on each server.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
5 years, 4 months
[JBoss JIRA] (ISPN-9990) Integrationtests missing java.se module
by Tristan Tarrant (Jira)
[ https://issues.jboss.org/browse/ISPN-9990?page=com.atlassian.jira.plugin.... ]
Tristan Tarrant updated ISPN-9990:
----------------------------------
Sprint: Sprint 10.0.0.Beta1, DataGrid Sprint #31, DataGrid Sprint #32, DataGrid Sprint #33 (was: Sprint 10.0.0.Beta1, DataGrid Sprint #31, DataGrid Sprint #32)
> Integrationtests missing java.se module
> ---------------------------------------
>
> Key: ISPN-9990
> URL: https://issues.jboss.org/browse/ISPN-9990
> Project: Infinispan
> Issue Type: Bug
> Components: Test Suite - Server
> Affects Versions: 10.0.0.Beta1
> Reporter: Ryan Emerson
> Assignee: Ryan Emerson
> Priority: Major
> Fix For: 9.4.10.Final, 10.0.0.Beta3
>
>
> standalone.sh adds the required {{--add-modules java.se}} to the JVM args for most tests, however if the the container is managed by the test this is not present.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
5 years, 4 months
[JBoss JIRA] (ISPN-9991) infinispan-remote integration tests inconsistent naming
by Tristan Tarrant (Jira)
[ https://issues.jboss.org/browse/ISPN-9991?page=com.atlassian.jira.plugin.... ]
Tristan Tarrant updated ISPN-9991:
----------------------------------
Sprint: Sprint 10.0.0.Beta1, DataGrid Sprint #31, DataGrid Sprint #32, DataGrid Sprint #33 (was: Sprint 10.0.0.Beta1, DataGrid Sprint #31, DataGrid Sprint #32)
> infinispan-remote integration tests inconsistent naming
> -------------------------------------------------------
>
> Key: ISPN-9991
> URL: https://issues.jboss.org/browse/ISPN-9991
> Project: Infinispan
> Issue Type: Bug
> Components: Test Suite - Server
> Affects Versions: 10.0.0.Beta1
> Reporter: Ryan Emerson
> Assignee: Ryan Emerson
> Priority: Major
> Fix For: 10.0.0.Beta3
>
>
> RemoteAllTest and JCacheFailoverIT results in tests not being executed together, but as separate lifecycle, results in no logs being saved for RemoteAllTest
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
5 years, 4 months
[JBoss JIRA] (ISPN-10142) Wildfly modules integrationtests ignore branding
by Tristan Tarrant (Jira)
[ https://issues.jboss.org/browse/ISPN-10142?page=com.atlassian.jira.plugin... ]
Tristan Tarrant updated ISPN-10142:
-----------------------------------
Sprint: Sprint 10.0.0.Beta1, DataGrid Sprint #31, DataGrid Sprint #32, DataGrid Sprint #33 (was: Sprint 10.0.0.Beta1, DataGrid Sprint #31, DataGrid Sprint #32)
> Wildfly modules integrationtests ignore branding
> ------------------------------------------------
>
> Key: ISPN-10142
> URL: https://issues.jboss.org/browse/ISPN-10142
> Project: Infinispan
> Issue Type: Bug
> Components: Test Suite - Server
> Affects Versions: 9.4.12.Final, 10.0.0.Beta3
> Reporter: Dan Berindei
> Assignee: Dan Berindei
> Priority: Major
> Labels: testsuite_failure
> Fix For: 9.4.14.Final, 10.0.0.Beta4
>
>
> {{standalone-test.xml}} uses module {{org.infinispan.extension:ispn-${infinispan.core.schema.version}}}, ignoring the branding. The module name should be {{org.infinispan.extension:${infinispan.module.slot}}}.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
5 years, 4 months
[JBoss JIRA] (ISPN-10161) ThreadLeakChecker is blocking PolarionJUnitXMLReporter to generate the reports
by Tristan Tarrant (Jira)
[ https://issues.jboss.org/browse/ISPN-10161?page=com.atlassian.jira.plugin... ]
Tristan Tarrant updated ISPN-10161:
-----------------------------------
Sprint: DataGrid Sprint #30, DataGrid Sprint #31, DataGrid Sprint #32, DataGrid Sprint #33 (was: DataGrid Sprint #30, DataGrid Sprint #31, DataGrid Sprint #32)
> ThreadLeakChecker is blocking PolarionJUnitXMLReporter to generate the reports
> ------------------------------------------------------------------------------
>
> Key: ISPN-10161
> URL: https://issues.jboss.org/browse/ISPN-10161
> Project: Infinispan
> Issue Type: Bug
> Affects Versions: 9.4.12.Final, 10.0.0.Final
> Reporter: Diego Lovison
> Assignee: Dan Berindei
> Priority: Critical
>
> When we have Leaked threads we are throwing a new RuntimeException that is preventing the next listener to be running.
> From `master` execute `rm -rf hibernate/cache-v51/target/surefire-reports/ && rm -rf hibernate/cache-v53/target/surefire-reports/ && mvn verify -pl hibernate/cache-v51,hibernate/cache-v53 -Dtest=MultiTenancyTest -fae`
> After that, check the hibernate/cache-v53/target/surefire-reports/ folder, you will see no reports there.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
5 years, 4 months
[JBoss JIRA] (ISPN-10254) Modularize Spring Boot Starter Docs
by Tristan Tarrant (Jira)
[ https://issues.jboss.org/browse/ISPN-10254?page=com.atlassian.jira.plugin... ]
Tristan Tarrant updated ISPN-10254:
-----------------------------------
Sprint: DataGrid Sprint #32, DataGrid Sprint #33 (was: DataGrid Sprint #32)
> Modularize Spring Boot Starter Docs
> -----------------------------------
>
> Key: ISPN-10254
> URL: https://issues.jboss.org/browse/ISPN-10254
> Project: Infinispan
> Issue Type: Enhancement
> Components: Documentation-Core
> Reporter: Donald Naro
> Assignee: Donald Naro
> Priority: Major
> Fix For: 10.0.0.CR2
>
> Attachments: sb_starter.png
>
>
> In 9.4.x and 7.3.x the doc source for the Spring Boot Starter is different for upstream and downstream.
> * Modularize the Spring Boot Starter doc source upstream.
> * Include the Spring Boot Starter docs on the community site (infinispan.org/documentation).
> * Remove the Spring Boot Starter productization docs from infinispan/documentation/src/main/asciidoc.
> This task removes duplication of content with downstream source. Also brings the user experience for Spring Boot Starter docs into alignment with the strategy for ISPN 10.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
5 years, 4 months
[JBoss JIRA] (IPROTO-106) OriginatingClasses annotation should be located in a runtime jar, not in the annotation processor jar
by Tristan Tarrant (Jira)
[ https://issues.jboss.org/browse/IPROTO-106?page=com.atlassian.jira.plugin... ]
Tristan Tarrant updated IPROTO-106:
-----------------------------------
Sprint: DataGrid Sprint #31, DataGrid Sprint #32, DataGrid Sprint #33 (was: DataGrid Sprint #31, DataGrid Sprint #32)
> OriginatingClasses annotation should be located in a runtime jar, not in the annotation processor jar
> ------------------------------------------------------------------------------------------------------
>
> Key: IPROTO-106
> URL: https://issues.jboss.org/browse/IPROTO-106
> Project: Infinispan ProtoStream
> Issue Type: Bug
> Reporter: Nistor Adrian
> Assignee: Nistor Adrian
> Priority: Major
> Fix For: 4.3.0.Alpha9
>
>
> The annotation processor is a compile time dependency, so OriginatingClasses annotation is not loadable at runtime, but this does not create a classloading issue because the retention of the annotation is CLASS, so not actually needed at runtime. All good at runtime. But javadoc generation does not work, failing due to missing dependency unless we add it explicitly, which is cumbersome.
> This is already leading to failures in Infinispan https://ci.infinispan.org/job/Infinispan/job/master/1304/consoleFull#1277...
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
5 years, 4 months