November 2019 - infinispan-issues

[JBoss JIRA] (ISPN-10889) Error building infinispan on ppc64le

by Rashmi Salgaonkar (Jira)

Rashmi Salgaonkar created ISPN-10889: ---------------------------------------- Summary: Error building infinispan on ppc64le Key: ISPN-10889 URL: https://issues.jboss.org/browse/ISPN-10889 Project: Infinispan Issue Type: Bug Reporter: Rashmi Salgaonkar Apache Maven 3.6.2 Java version: 11.0.5 OS: linux-ppc64le Error building infinispan:- [INFO] Alternative client marshallers ..................... SKIPPED [INFO] Infinispan Common Marshaller Test Classes .......... SKIPPED [INFO] Infinispan Kryo Marshaller Bridge .................. SKIPPED [INFO] Infinispan Kryo Marshaller Bridge Bundle ........... SKIPPED [INFO] Infinispan Protostuff Marshaller Bridge ............ SKIPPED [INFO] Infinispan Protostuff Marshaller Bridge Bundle ..... SKIPPED [INFO] Infinispan Hibernate 5.1 Cache ..................... SKIPPED [INFO] ------------------------------------------------------------------------ [INFO] BUILD FAILURE [INFO] ------------------------------------------------------------------------ [INFO] Total time: 48.824 s [INFO] Finished at: 2019-11-01T10:46:39Z [INFO] ------------------------------------------------------------------------ [ERROR] Failed to execute goal org.infinispan.maven-plugins:proto-schema-compatibility:1.0.1.Final:proto-schema-compatibility-check (default) on project infinispan-commons: *OS not supported. Unable to find a protolock binary for the classifier linux-ppcle_64 *-> [Help 1] [ERROR] [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch. [ERROR] Re-run Maven using the -X switch to enable full debug logging. [ERROR] [ERROR] For more information about the errors and possible solutions, please read the following articles: [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException [ERROR] [ERROR] After correcting the problems, you can resume the build with the command [ERROR] mvn <args> -rf :infinispan-commons bash-4.4# I was able to build https://github.com/infinispan/infinispan-maven-plugins repo. I need details on how I can generate the architecture specific protolock binary file. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10888) Genereated MetricIDs like CacheManager_CacheManager_numberOfCreatedCaches should be avoided

by Nistor Adrian (Jira)

[ https://issues.jboss.org/browse/ISPN-10888?page=com.atlassian.jira.plugin... ] Nistor Adrian updated ISPN-10888: --------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/7534 > Genereated MetricIDs like CacheManager_CacheManager_numberOfCreatedCaches should be avoided > ------------------------------------------------------------------------------------------- > > Key: ISPN-10888 > URL: https://issues.jboss.org/browse/ISPN-10888 > Project: Infinispan > Issue Type: Bug > Components: JMX, reporting and management > Affects Versions: 10.0.0.Final > Reporter: Nistor Adrian > Assignee: Nistor Adrian > Priority: Major > Fix For: 10.1.0.Beta1, 10.0.2.Final > > > Must avoid situations where ObjectName's type and component keys are equal, like in CacheManager_CacheManager_numberOfCreatedCaches. Same for Cache. > In these cases do not add both, just one. > Also, need to remove eventual dots from names. Replace them with the standard replacement character in MP metrics: ' _' -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10883) [REST] Simultaneous call to stop don't stop the servers

by Gustavo Fernandes (Jira)

[ https://issues.jboss.org/browse/ISPN-10883?page=com.atlassian.jira.plugin... ] Gustavo Fernandes commented on ISPN-10883: ------------------------------------------ Probably the ServerResource when asked to stop the server, should never use the cluster executor to stop itself and simply do it locally (like it was on CR3) > [REST] Simultaneous call to stop don't stop the servers > ------------------------------------------------------- > > Key: ISPN-10883 > URL: https://issues.jboss.org/browse/ISPN-10883 > Project: Infinispan > Issue Type: Bug > Components: REST, Server > Affects Versions: 10.0.0.Final, 10.0.1.Final > Reporter: Gustavo Fernandes > Assignee: Tristan Tarrant > Priority: Major > > This was observed in a cluster of 3 servers in the same machine, listening on ports 11222, 11322, 11422. A script would call stop on each of the server individually: > http://localhost:11222/rest/v2/server?action=stop > http://localhost:11322/rest/v2/server?action=stop > http://localhost:11422/rest/v2/server?action=stop > All the commands return code 200 but the servers are not stopped, the processes are still alive. > This is a regression from 10.0.0.CR3 where those ops were working correctly. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10888) Genereated MetricIDs like CacheManager_CacheManager_numberOfCreatedCaches should be avoided

by Nistor Adrian (Jira)

[ https://issues.jboss.org/browse/ISPN-10888?page=com.atlassian.jira.plugin... ] Nistor Adrian updated ISPN-10888: --------------------------------- Summary: Genereated MetricIDs like CacheManager_CacheManager_numberOfCreatedCaches should be avoided (was: Aotomtically genereated MetricIDs lik CacheManager_CacheManager_numberOfCreatedCaches should be avoided) > Genereated MetricIDs like CacheManager_CacheManager_numberOfCreatedCaches should be avoided > ------------------------------------------------------------------------------------------- > > Key: ISPN-10888 > URL: https://issues.jboss.org/browse/ISPN-10888 > Project: Infinispan > Issue Type: Bug > Components: JMX, reporting and management > Affects Versions: 10.0.0.Final > Reporter: Nistor Adrian > Assignee: Nistor Adrian > Priority: Major > Fix For: 10.1.0.Beta1, 10.0.2.Final > > > Must avoid situations where ObjectName's type and component keys are equal, like in CacheManager_CacheManager_numberOfCreatedCaches. Same for Cache. > In these cases do not add both, just one. > Also, need to remove eventual dots from names. Replace them with the standard replacement character in MP metrics: ' _' -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10888) Aotomtically genereated MetricIDs lik CacheManager_CacheManager_numberOfCreatedCaches should be avoided

by Nistor Adrian (Jira)

Nistor Adrian created ISPN-10888: ------------------------------------ Summary: Aotomtically genereated MetricIDs lik CacheManager_CacheManager_numberOfCreatedCaches should be avoided Key: ISPN-10888 URL: https://issues.jboss.org/browse/ISPN-10888 Project: Infinispan Issue Type: Bug Components: JMX, reporting and management Affects Versions: 10.0.0.Final Reporter: Nistor Adrian Assignee: Nistor Adrian Fix For: 10.1.0.Beta1, 10.0.2.Final Must avoid situations where ObjectName's type and component keys are equal, like in CacheManager_CacheManager_numberOfCreatedCaches. Same for Cache. In these cases do not add both, just one. Also, need to remove eventual dots from names. Replace them with the standard replacement character in MP metrics: ' _' -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10888) Aotomtically genereated MetricIDs lik CacheManager_CacheManager_numberOfCreatedCaches should be avoided

by Nistor Adrian (Jira)

[ https://issues.jboss.org/browse/ISPN-10888?page=com.atlassian.jira.plugin... ] Nistor Adrian updated ISPN-10888: --------------------------------- Status: Open (was: New) > Aotomtically genereated MetricIDs lik CacheManager_CacheManager_numberOfCreatedCaches should be avoided > ------------------------------------------------------------------------------------------------------- > > Key: ISPN-10888 > URL: https://issues.jboss.org/browse/ISPN-10888 > Project: Infinispan > Issue Type: Bug > Components: JMX, reporting and management > Affects Versions: 10.0.0.Final > Reporter: Nistor Adrian > Assignee: Nistor Adrian > Priority: Major > Fix For: 10.1.0.Beta1, 10.0.2.Final > > > Must avoid situations where ObjectName's type and component keys are equal, like in CacheManager_CacheManager_numberOfCreatedCaches. Same for Cache. > In these cases do not add both, just one. > Also, need to remove eventual dots from names. Replace them with the standard replacement character in MP metrics: ' _' -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10881) Deprecate GlobalJmxStatisticsConfiguration.allowDuplicateDomains

by Dan Berindei (Jira)

[ https://issues.jboss.org/browse/ISPN-10881?page=com.atlassian.jira.plugin... ] Dan Berindei updated ISPN-10881: -------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/7535 > Deprecate GlobalJmxStatisticsConfiguration.allowDuplicateDomains > ---------------------------------------------------------------- > > Key: ISPN-10881 > URL: https://issues.jboss.org/browse/ISPN-10881 > Project: Infinispan > Issue Type: Task > Components: Configuration, Core > Affects Versions: 10.0.0.Final > Reporter: Dan Berindei > Assignee: Dan Berindei > Priority: Major > Fix For: 10.1.0.Final > > > {{allowDuplicateDomains}} is just a crutch for tests. Applications rarely start more than one cache manager in the same JVM, and when they (e.g. multiple applications in an application server) do it's always a good idea to give each cache manager a unique name. > Our test suite doesn't really need {{allowDuplicateDomains}} either: {{TestCacheManagerFactory}} adds a UUID to the domain name, unless the test has explicitly set a (presumably unique) domain name. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10887) GlobalJmxStatisticsConfiguration.allowDuplicateDomains is not implemented atomically and can fail frequently

by Nistor Adrian (Jira)

[ https://issues.jboss.org/browse/ISPN-10887?page=com.atlassian.jira.plugin... ] Nistor Adrian updated ISPN-10887: --------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/7534 > GlobalJmxStatisticsConfiguration.allowDuplicateDomains is not implemented atomically and can fail frequently > ------------------------------------------------------------------------------------------------------------ > > Key: ISPN-10887 > URL: https://issues.jboss.org/browse/ISPN-10887 > Project: Infinispan > Issue Type: Bug > Components: JMX, reporting and management > Affects Versions: 10.0.0.Final > Reporter: Nistor Adrian > Assignee: Nistor Adrian > Priority: Major > Fix For: 10.1.0.Beta1, 10.0.2.Final > > > The feature is supposed to allow detection of an already occupied jmx domain and generate a new unique one by adding an increasing number suffix. The implementation polls the MBeanServer registry using queryNames until a free domain is found. The unique domain generation and the registration of the first MBean to occupy it is not atomic, so multiple CacheManagers starting up concurrently can mistakenly pick up the same domain. > This can be fixed by making it atomic, by not using queryNames and instead directly registering the first bean, retrying if InstanceAlreadyExistsException. The first bean has to be picked identically by all cache managers. We'll pick first the cache manager itself and register the other components afterwards. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10887) GlobalJmxStatisticsConfiguration.allowDuplicateDomains is not implemented atomically and can fail frequently

by Nistor Adrian (Jira)

[ https://issues.jboss.org/browse/ISPN-10887?page=com.atlassian.jira.plugin... ] Nistor Adrian updated ISPN-10887: --------------------------------- Fix Version/s: 10.1.0.Beta1 10.0.2.Final > GlobalJmxStatisticsConfiguration.allowDuplicateDomains is not implemented atomically and can fail frequently > ------------------------------------------------------------------------------------------------------------ > > Key: ISPN-10887 > URL: https://issues.jboss.org/browse/ISPN-10887 > Project: Infinispan > Issue Type: Bug > Components: JMX, reporting and management > Affects Versions: 10.0.0.Final > Reporter: Nistor Adrian > Assignee: Nistor Adrian > Priority: Major > Fix For: 10.1.0.Beta1, 10.0.2.Final > > > The feature is supposed to allow detection of an already occupied jmx domain and generate a new unique one by adding an increasing number suffix. The implementation polls the MBeanServer registry using queryNames until a free domain is found. The unique domain generation and the registration of the first MBean to occupy it is not atomic, so multiple CacheManagers starting up concurrently can mistakenly pick up the same domain. > This can be fixed by making it atomic, by not using queryNames and instead directly registering the first bean, retrying if InstanceAlreadyExistsException. The first bean has to be picked identically by all cache managers. We'll pick first the cache manager itself and register the other components afterwards. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10887) GlobalJmxStatisticsConfiguration.allowDuplicateDomains is not implemented atomically and can fail frequently

by Nistor Adrian (Jira)

[ https://issues.jboss.org/browse/ISPN-10887?page=com.atlassian.jira.plugin... ] Nistor Adrian updated ISPN-10887: --------------------------------- Status: Open (was: New) > GlobalJmxStatisticsConfiguration.allowDuplicateDomains is not implemented atomically and can fail frequently > ------------------------------------------------------------------------------------------------------------ > > Key: ISPN-10887 > URL: https://issues.jboss.org/browse/ISPN-10887 > Project: Infinispan > Issue Type: Bug > Components: JMX, reporting and management > Affects Versions: 10.0.0.Final > Reporter: Nistor Adrian > Assignee: Nistor Adrian > Priority: Major > Fix For: 10.1.0.Beta1, 10.0.2.Final > > > The feature is supposed to allow detection of an already occupied jmx domain and generate a new unique one by adding an increasing number suffix. The implementation polls the MBeanServer registry using queryNames until a free domain is found. The unique domain generation and the registration of the first MBean to occupy it is not atomic, so multiple CacheManagers starting up concurrently can mistakenly pick up the same domain. > This can be fixed by making it atomic, by not using queryNames and instead directly registering the first bean, retrying if InstanceAlreadyExistsException. The first bean has to be picked identically by all cache managers. We'll pick first the cache manager itself and register the other components afterwards. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 2 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues November 2019