July 2020 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-13664) CLustering TS: Infinispan Server test driver intermittently fails to start the server

by Radoslav Husar (Jira)

Radoslav Husar created WFLY-13664: ------------------------------------- Summary: CLustering TS: Infinispan Server test driver intermittently fails to start the server Key: WFLY-13664 URL: https://issues.redhat.com/browse/WFLY-13664 Project: WildFly Issue Type: Bug Components: Clustering, Test Suite Affects Versions: 20.0.1.Final Reporter: Radoslav Husar Assignee: Radoslav Husar Reported by [~dlofthouse]: {noformat} 2020-07-13 09:52:19,289 FATAL (main) [org.infinispan.SERVER] ISPN080028: Infinispan Server failed to start java.util.concurrent.ExecutionException: org.infinispan.manager.EmbeddedCacheManagerStartupException: org.infinispan.commons.CacheConfigurationException: ISPN000512: Cannot acquire lock '/home/darranl/src/community/wildfly/testsuite/integration/clustering/target/infinispan-server-10.1.8.Final/server/data/___global.lck' for persistent global state at java.util.concurrent.CompletableFuture.reportGet(CompletableFuture.java:357) at java.util.concurrent.CompletableFuture.get(CompletableFuture.java:1908) at org.infinispan.server.Bootstrap.runInternal(Bootstrap.java:139) at org.infinispan.server.tool.Main.run(Main.java:98) at org.infinispan.server.Bootstrap.main(Bootstrap.java:39) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at org.infinispan.server.loader.Loader.main(Loader.java:71) Caused by: org.infinispan.manager.EmbeddedCacheManagerStartupException: org.infinispan.commons.CacheConfigurationException: ISPN000512: Cannot acquire lock '/home/darranl/src/community/wildfly/testsuite/integration/clustering/target/infinispan-server-10.1.8.Final/server/data/___global.lck' for persistent global state at org.infinispan.manager.DefaultCacheManager.internalStart(DefaultCacheManager.java:760) at org.infinispan.manager.DefaultCacheManager.start(DefaultCacheManager.java:726) at org.infinispan.server.SecurityActions.lambda$startCacheManager$1(SecurityActions.java:51) at org.infinispan.security.Security.doPrivileged(Security.java:46) at org.infinispan.server.SecurityActions.doPrivileged(SecurityActions.java:31) at org.infinispan.server.SecurityActions.startCacheManager(SecurityActions.java:54) at org.infinispan.server.Server.run(Server.java:286) ... 8 more Caused by: org.infinispan.commons.CacheConfigurationException: ISPN000512: Cannot acquire lock '/home/darranl/src/community/wildfly/testsuite/integration/clustering/target/infinispan-server-10.1.8.Final/server/data/___global.lck' for persistent global state at org.infinispan.globalstate.impl.GlobalStateManagerImpl.acquireGlobalLock(GlobalStateManagerImpl.java:84) at org.infinispan.globalstate.impl.GlobalStateManagerImpl.start(GlobalStateManagerImpl.java:64) at org.infinispan.globalstate.impl.CorePackageImpl$1.start(CorePackageImpl.java:34) at org.infinispan.globalstate.impl.CorePackageImpl$1.start(CorePackageImpl.java:27) at org.infinispan.factories.impl.BasicComponentRegistryImpl.invokeStart(BasicComponentRegistryImpl.java:587) at org.infinispan.factories.impl.BasicComponentRegistryImpl.doStartWrapper(BasicComponentRegistryImpl.java:578) at org.infinispan.factories.impl.BasicComponentRegistryImpl.startWrapper(BasicComponentRegistryImpl.java:547) at org.infinispan.factories.impl.BasicComponentRegistryImpl.access$700(BasicComponentRegistryImpl.java:30) at org.infinispan.factories.impl.BasicComponentRegistryImpl$ComponentWrapper.running(BasicComponentRegistryImpl.java:770) at org.infinispan.factories.AbstractComponentRegistry.internalStart(AbstractComponentRegistry.java:341) at org.infinispan.factories.AbstractComponentRegistry.start(AbstractComponentRegistry.java:237) at org.infinispan.manager.DefaultCacheManager.internalStart(DefaultCacheManager.java:755) ... 14 more {noformat} -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13664) CLustering TS: Infinispan Server test driver intermittently fails to start the server

by Radoslav Husar (Jira)

[ https://issues.redhat.com/browse/WFLY-13664?page=com.atlassian.jira.plugi... ] Radoslav Husar updated WFLY-13664: ---------------------------------- Affects Version/s: 20.0.0.Final (was: 20.0.1.Final) > CLustering TS: Infinispan Server test driver intermittently fails to start the server > ------------------------------------------------------------------------------------- > > Key: WFLY-13664 > URL: https://issues.redhat.com/browse/WFLY-13664 > Project: WildFly > Issue Type: Bug > Components: Clustering, Test Suite > Affects Versions: 20.0.0.Final > Reporter: Radoslav Husar > Assignee: Radoslav Husar > Priority: Major > > Reported by [~dlofthouse]: > > {noformat} > 2020-07-13 09:52:19,289 FATAL (main) [org.infinispan.SERVER] ISPN080028: Infinispan Server failed to start java.util.concurrent.ExecutionException: org.infinispan.manager.EmbeddedCacheManagerStartupException: org.infinispan.commons.CacheConfigurationException: ISPN000512: Cannot acquire lock '/home/darranl/src/community/wildfly/testsuite/integration/clustering/target/infinispan-server-10.1.8.Final/server/data/___global.lck' for persistent global state > at java.util.concurrent.CompletableFuture.reportGet(CompletableFuture.java:357) > at java.util.concurrent.CompletableFuture.get(CompletableFuture.java:1908) > at org.infinispan.server.Bootstrap.runInternal(Bootstrap.java:139) > at org.infinispan.server.tool.Main.run(Main.java:98) > at org.infinispan.server.Bootstrap.main(Bootstrap.java:39) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:498) > at org.infinispan.server.loader.Loader.main(Loader.java:71) > Caused by: org.infinispan.manager.EmbeddedCacheManagerStartupException: org.infinispan.commons.CacheConfigurationException: ISPN000512: Cannot acquire lock '/home/darranl/src/community/wildfly/testsuite/integration/clustering/target/infinispan-server-10.1.8.Final/server/data/___global.lck' for persistent global state > at org.infinispan.manager.DefaultCacheManager.internalStart(DefaultCacheManager.java:760) > at org.infinispan.manager.DefaultCacheManager.start(DefaultCacheManager.java:726) > at org.infinispan.server.SecurityActions.lambda$startCacheManager$1(SecurityActions.java:51) > at org.infinispan.security.Security.doPrivileged(Security.java:46) > at org.infinispan.server.SecurityActions.doPrivileged(SecurityActions.java:31) > at org.infinispan.server.SecurityActions.startCacheManager(SecurityActions.java:54) > at org.infinispan.server.Server.run(Server.java:286) > ... 8 more > Caused by: org.infinispan.commons.CacheConfigurationException: ISPN000512: Cannot acquire lock '/home/darranl/src/community/wildfly/testsuite/integration/clustering/target/infinispan-server-10.1.8.Final/server/data/___global.lck' for persistent global state > at org.infinispan.globalstate.impl.GlobalStateManagerImpl.acquireGlobalLock(GlobalStateManagerImpl.java:84) > at org.infinispan.globalstate.impl.GlobalStateManagerImpl.start(GlobalStateManagerImpl.java:64) > at org.infinispan.globalstate.impl.CorePackageImpl$1.start(CorePackageImpl.java:34) > at org.infinispan.globalstate.impl.CorePackageImpl$1.start(CorePackageImpl.java:27) > at org.infinispan.factories.impl.BasicComponentRegistryImpl.invokeStart(BasicComponentRegistryImpl.java:587) > at org.infinispan.factories.impl.BasicComponentRegistryImpl.doStartWrapper(BasicComponentRegistryImpl.java:578) > at org.infinispan.factories.impl.BasicComponentRegistryImpl.startWrapper(BasicComponentRegistryImpl.java:547) > at org.infinispan.factories.impl.BasicComponentRegistryImpl.access$700(BasicComponentRegistryImpl.java:30) > at org.infinispan.factories.impl.BasicComponentRegistryImpl$ComponentWrapper.running(BasicComponentRegistryImpl.java:770) > at org.infinispan.factories.AbstractComponentRegistry.internalStart(AbstractComponentRegistry.java:341) > at org.infinispan.factories.AbstractComponentRegistry.start(AbstractComponentRegistry.java:237) > at org.infinispan.manager.DefaultCacheManager.internalStart(DefaultCacheManager.java:755) > ... 14 more {noformat} -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5502) DMN Generate Strongly Typed Output Set

by Luca Molteni (Jira)

[ https://issues.redhat.com/browse/DROOLS-5502?page=com.atlassian.jira.plug... ] Luca Molteni reassigned DROOLS-5502: ------------------------------------ Component/s: dmn engine Assignee: Luca Molteni (was: Mario Fusco) > DMN Generate Strongly Typed Output Set > -------------------------------------- > > Key: DROOLS-5502 > URL: https://issues.redhat.com/browse/DROOLS-5502 > Project: Drools > Issue Type: Enhancement > Components: dmn engine > Reporter: Luca Molteni > Assignee: Luca Molteni > Priority: Major > > Currently DMN output values are rapresented as a map. > > By levering the strongly typed functionality we can provide a strongly typed output that can be used in swagger to document the output of a REST endpoint -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5502) DMN Generate Strongly Typed Output Set

by Luca Molteni (Jira)

Luca Molteni created DROOLS-5502: ------------------------------------ Summary: DMN Generate Strongly Typed Output Set Key: DROOLS-5502 URL: https://issues.redhat.com/browse/DROOLS-5502 Project: Drools Issue Type: Enhancement Reporter: Luca Molteni Assignee: Mario Fusco Currently DMN output values are rapresented as a map. By levering the strongly typed functionality we can provide a strongly typed output that can be used in swagger to document the output of a REST endpoint -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5501) Move the POJO Generator library outside drools-model-compiler

by Luca Molteni (Jira)

Luca Molteni created DROOLS-5501: ------------------------------------ Summary: Move the POJO Generator library outside drools-model-compiler Key: DROOLS-5501 URL: https://issues.redhat.com/browse/DROOLS-5501 Project: Drools Issue Type: Enhancement Reporter: Luca Molteni Assignee: Luca Molteni As it's currently used also by the DMN -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13620) jaxrs-jwt: The parameters 'mainClass' are missing or invalid

by Ranabir Chakraborty (Jira)

[ https://issues.redhat.com/browse/WFLY-13620?page=com.atlassian.jira.plugi... ] Ranabir Chakraborty commented on WFLY-13620: -------------------------------------------- [~emmartins] Are you working on this? > jaxrs-jwt: The parameters 'mainClass' are missing or invalid > ------------------------------------------------------------- > > Key: WFLY-13620 > URL: https://issues.redhat.com/browse/WFLY-13620 > Project: WildFly > Issue Type: Bug > Components: Quickstarts > Affects Versions: 20.0.0.Final > Reporter: Wolfgang Mayer > Assignee: Eduardo Martins > Priority: Minor > > mvn exec:java fails > [INFO] Reactor Summary for Quickstart: jaxrs-jwt 20.0.0.Final: > [INFO] > [INFO] Quickstart: jaxrs-jwt .............................. FAILURE [ 0.361 s] > [INFO] Quickstart: jaxrs-jwt - client ..................... SKIPPED > [INFO] Quickstart: jaxrs-jwt - service .................... SKIPPED > [INFO] ------------------------------------------------------------------------ > [INFO] BUILD FAILURE > [INFO] ------------------------------------------------------------------------ > [INFO] Total time: 1.056 s > [INFO] Finished at: 2020-06-27T13:39:17+02:00 > [INFO] ------------------------------------------------------------------------ > [ERROR] Failed to execute goal org.codehaus.mojo:exec-maven-plugin:1.6.0:java (default-cli) on project jaxrs-jwt: The parameters 'mainClass' for goal org.codehaus.mojo:exec-maven-plugin:1.6.0:java are missing or invalid -> [Help 1] > [ERROR] > mvn -v > Apache Maven 3.6.3 > Maven home: /usr/share/maven > Java version: 14.0.1, vendor: Private Build, runtime: /usr/lib/jvm/java-14-openjdk-amd64 > Default locale: de_DE, platform encoding: UTF-8 > OS name: "linux", version: "5.4.0-39-generic", arch: "amd64", family: "unix" > Executing the clent directly via: > $JAVA_HOME/bin/java -classpath $CLASSPATH org.jboss.quickstarts.jaxrsjwt.client.JwtRestClient > Euns successfully indeed. So this seems to be an issue with the pom.xml -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5500) Workaround comment exists in kie-pmml/pom.xml file while the related issues are already fixed.

by Mario Fusco (Jira)

[ https://issues.redhat.com/browse/DROOLS-5500?page=com.atlassian.jira.plug... ] Mario Fusco resolved DROOLS-5500. --------------------------------- Resolution: Done > Workaround comment exists in kie-pmml/pom.xml file while the related issues are already fixed. > ---------------------------------------------------------------------------------------------- > > Key: DROOLS-5500 > URL: https://issues.redhat.com/browse/DROOLS-5500 > Project: Drools > Issue Type: Enhancement > Reporter: Tao Xiao > Assignee: Mario Fusco > Priority: Trivial > > In a research project, we analyzed the build file of repositories looking for comments with ready-to-be-addressed SATDs (self-admitted technical debt) that could be addressed. If the underlying issue is already resolved, the related code or comment can be removed or fixed. As we found an instance of this kind of asynchrony in kie-pmml/pom.xml, we decided to report the issue to contribute community. > A comment in drools-core/pom.xml file claims that it is workaround for > [https://github.com/mojohaus/jaxb2-maven-plugin/issues/43], and this issue has been closed long ago. > {quote} > {quote} > Comment location: [https://github.com/kiegroup/drools/blob/a8507fae382ec5d815cce03792aa18b00...] -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13662) Weld Conversation Context Logs when not using Conversation Context

by Matěj Novotný (Jira)

[ https://issues.redhat.com/browse/WFLY-13662?page=com.atlassian.jira.plugi... ] Matěj Novotný commented on WFLY-13662: -------------------------------------- Hi [~clerum], it looks like something is using conversation context, could even be some added internal module perhaps. Could you provide a bigger segment of the stacktrace? Or, better still, would you be able to provide a reproducer? FTR, WFLY 18 is Weld 3.1.2.Final while WFLY 20 is Weld 3.1.4.Final. Possible problematic issue could be WELD-2612, however it is hard to tell without reproducer. I am not seeing these failures in any tests weld or wfly have. > Weld Conversation Context Logs when not using Conversation Context > ------------------------------------------------------------------ > > Key: WFLY-13662 > URL: https://issues.redhat.com/browse/WFLY-13662 > Project: WildFly > Issue Type: Bug > Components: CDI / Weld, JSF > Affects Versions: 20.0.1.Final > Reporter: Cody Lerum > Assignee: Matěj Novotný > Priority: Major > > After upgrading to Widfly 20.0.1 from 18.0.1 I'm starting to receive show log errors regarding the CDI conversation context even though it is not used anywhere in the application. > These did not present in the same application in 18.0.1.Final > {code:java} > 020-07-10 15:42:47,561 ERROR [io.undertow.request] (default task-273) UT005023: Exception handling request to /s/c/voice/fax/view.xhtml: java.lang.NullPointerException2020-07-10 15:42:47,562 WARN [org.jboss.weld.Servlet] (default task-273) WELD-000717: Unable to deactivate context org.jboss.weld.module.web.context.http.LazyHttpConversationContextImpl@25333df0 when destroying request HttpServletRequestImpl [ GET /s/c/voice/fax/view.xhtml ] > 2020-07-10 15:42:48,165 WARN [org.jboss.weld.Conversation] (default task-273) WELD-000335: Conversation context is already active, most likely it was not cleaned up properly during previous request processing: HttpServletRequestImpl [ GET /i/ticket/46893 ] {code} -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5500) Workaround comment exists in kie-pmml/pom.xml file while the related issues are already fixed.

by Mario Fusco (Jira)

[ https://issues.redhat.com/browse/DROOLS-5500?page=com.atlassian.jira.plug... ] Mario Fusco updated DROOLS-5500: -------------------------------- Sprint: 2020 Week 28-30 (from Jul 6) > Workaround comment exists in kie-pmml/pom.xml file while the related issues are already fixed. > ---------------------------------------------------------------------------------------------- > > Key: DROOLS-5500 > URL: https://issues.redhat.com/browse/DROOLS-5500 > Project: Drools > Issue Type: Enhancement > Reporter: Tao Xiao > Assignee: Mario Fusco > Priority: Trivial > > In a research project, we analyzed the build file of repositories looking for comments with ready-to-be-addressed SATDs (self-admitted technical debt) that could be addressed. If the underlying issue is already resolved, the related code or comment can be removed or fixed. As we found an instance of this kind of asynchrony in kie-pmml/pom.xml, we decided to report the issue to contribute community. > A comment in drools-core/pom.xml file claims that it is workaround for > [https://github.com/mojohaus/jaxb2-maven-plugin/issues/43], and this issue has been closed long ago. > {quote} > {quote} > Comment location: [https://github.com/kiegroup/drools/blob/a8507fae382ec5d815cce03792aa18b00...] -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5500) Workaround comment exists in kie-pmml/pom.xml file while the related issues are already fixed.

by Tao Xiao (Jira)

Tao Xiao created DROOLS-5500: -------------------------------- Summary: Workaround comment exists in kie-pmml/pom.xml file while the related issues are already fixed. Key: DROOLS-5500 URL: https://issues.redhat.com/browse/DROOLS-5500 Project: Drools Issue Type: Enhancement Reporter: Tao Xiao Assignee: Mario Fusco In a research project, we analyzed the build file of repositories looking for comments with ready-to-be-addressed SATDs (self-admitted technical debt) that could be addressed. If the underlying issue is already resolved, the related code or comment can be removed or fixed. As we found an instance of this kind of asynchrony in kie-pmml/pom.xml, we decided to report the issue to contribute community. A comment in drools-core/pom.xml file claims that it is workaround for [https://github.com/mojohaus/jaxb2-maven-plugin/issues/43], and this issue has been closed long ago. {quote} {quote} Comment location: [https://github.com/kiegroup/drools/blob/a8507fae382ec5d815cce03792aa18b00...] -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 2 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira July 2020