June 2020 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-13621) GSoC-2020 : Adding latest Wildfly Release 20.0.0.Final in EAT

by Loukas Kopanias (Jira)

[ https://issues.redhat.com/browse/WFLY-13621?page=com.atlassian.jira.plugi... ] Loukas Kopanias updated WFLY-13621: ----------------------------------- Git Pull Request: https://github.com/EAT-JBCOMMUNITY/EAT/pull/4 > GSoC-2020 : Adding latest Wildfly Release 20.0.0.Final in EAT > ------------------------------------------------------------- > > Key: WFLY-13621 > URL: https://issues.redhat.com/browse/WFLY-13621 > Project: WildFly > Issue Type: Task > Components: Test Suite > Reporter: Loukas Kopanias > Priority: Major > > This is a task of Loukas Kopanias for the 1st Phase of GSoC 2020. > All testcases and configuration files in EAT updated to run successfully on the latest released version of Wildfly (currently 20.0.0.Final). -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13621) GSoC-2020 : Adding latest Wildfly Release 20.0.0.Final in EAT

by Loukas Kopanias (Jira)

Loukas Kopanias created WFLY-13621: -------------------------------------- Summary: GSoC-2020 : Adding latest Wildfly Release 20.0.0.Final in EAT Key: WFLY-13621 URL: https://issues.redhat.com/browse/WFLY-13621 Project: WildFly Issue Type: Task Components: Test Suite Reporter: Loukas Kopanias This is a task of Loukas Kopanias for the 1st Phase of GSoC 2020. All testcases and configuration files in EAT updated to run successfully on the latest released version of Wildfly (currently 20.0.0.Final). -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13621) GSoC-2020 : Adding latest Wildfly Release 20.0.0.Final in EAT

by Loukas Kopanias (Jira)

[ https://issues.redhat.com/browse/WFLY-13621?page=com.atlassian.jira.plugi... ] Loukas Kopanias resolved WFLY-13621. ------------------------------------ Resolution: Done > GSoC-2020 : Adding latest Wildfly Release 20.0.0.Final in EAT > ------------------------------------------------------------- > > Key: WFLY-13621 > URL: https://issues.redhat.com/browse/WFLY-13621 > Project: WildFly > Issue Type: Task > Components: Test Suite > Reporter: Loukas Kopanias > Priority: Major > > This is a task of Loukas Kopanias for the 1st Phase of GSoC 2020. > All testcases and configuration files in EAT updated to run successfully on the latest released version of Wildfly (currently 20.0.0.Final). -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 6 months

1
0
0 / 0

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

by Wolfgang Mayer (Jira)

Wolfgang Mayer created WFLY-13620: ------------------------------------- Summary: 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 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, 6 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13603) Cache associated with default module throws NPE on start

by Brian Stansberry (Jira)

[ https://issues.redhat.com/browse/WFLY-13603?page=com.atlassian.jira.plugi... ] Brian Stansberry updated WFLY-13603: ------------------------------------ Fix Version/s: 20.0.1.Final > Cache associated with default module throws NPE on start > -------------------------------------------------------- > > Key: WFLY-13603 > URL: https://issues.redhat.com/browse/WFLY-13603 > Project: WildFly > Issue Type: Bug > Components: Clustering > Affects Versions: 20.0.0.Final > Reporter: Paul Ferraro > Assignee: Paul Ferraro > Priority: Critical > Fix For: 21.0.0.Beta1, 20.0.1.Final > > > {noformat} > 2020-06-11 13:57:16,198 ERROR [org.jboss.msc.service.fail] (ServerService Thread Pool -- 90) MSC000001: Failed to start service org.wildfly.clustering.infinispan.cache.security.MyApplicationRealm: org.jboss.msc.service.StartException in service org.wildfly.clustering.infinispan.cache.security.MyApplicationRealm: org.infinispan.commons.CacheConfigurationException: Failed to construct component org.infinispan.container.impl.InternalDataContainer, path org.infinispan.container.impl.InternalDataContainer > << org.infinispan.stats.impl.StatsCollector > << org.infinispan.AdvancedCache > at org.wildfly.clustering.service.FunctionalService.start(FunctionalService.java:66) > at org.wildfly.clustering.service.AsyncServiceConfigurator$AsyncService.lambda$start$0(AsyncServiceConfigurator.java:117) > at org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35) > at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1982) > at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1486) > at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1377) > at java.lang.Thread.run(Thread.java:748) > at org.jboss.threads.JBossThread.run(JBossThread.java:485) > Caused by: org.infinispan.commons.CacheConfigurationException: Failed to construct component org.infinispan.container.impl.InternalDataContainer, path org.infinispan.container.impl.InternalDataContainer > << org.infinispan.stats.impl.StatsCollector > << org.infinispan.AdvancedCache > at org.infinispan.factories.impl.BasicComponentRegistryImpl.doInstantiateWrapper(BasicComponentRegistryImpl.java:189) > at org.infinispan.factories.impl.BasicComponentRegistryImpl.instantiateWrapper(BasicComponentRegistryImpl.java:176) > at org.infinispan.factories.impl.BasicComponentRegistryImpl.getComponent0(BasicComponentRegistryImpl.java:141) > at org.infinispan.factories.impl.WireContext.get(WireContext.java:20) > at org.infinispan.stats.impl.CorePackageImpl$2.wire(CorePackageImpl.java:43) > at org.infinispan.stats.impl.CorePackageImpl$2.wire(CorePackageImpl.java:39) > at org.infinispan.factories.impl.BasicComponentRegistryImpl.invokeInjection(BasicComponentRegistryImpl.java:334) > at org.infinispan.factories.impl.BasicComponentRegistryImpl.doWireWrapper(BasicComponentRegistryImpl.java:231) > at org.infinispan.factories.impl.BasicComponentRegistryImpl.wireWrapper(BasicComponentRegistryImpl.java:212) > at org.infinispan.factories.impl.BasicComponentRegistryImpl.getComponent0(BasicComponentRegistryImpl.java:147) > at org.infinispan.factories.impl.WireContext.get(WireContext.java:20) > at org.infinispan.cache.impl.CorePackageImpl$3.wire(CorePackageImpl.java:75) > at org.infinispan.cache.impl.CorePackageImpl$3.wire(CorePackageImpl.java:73) > at org.infinispan.factories.impl.BasicComponentRegistryImpl.invokeInjection(BasicComponentRegistryImpl.java:334) > at org.infinispan.factories.impl.BasicComponentRegistryImpl.wireDependencies(BasicComponentRegistryImpl.java:242) > at org.infinispan.cache.impl.EncoderCache.wireRealCache(EncoderCache.java:125) > at org.infinispan.cache.impl.CorePackageImpl$4.wire(CorePackageImpl.java:94) > at org.infinispan.cache.impl.CorePackageImpl$4.wire(CorePackageImpl.java:90) > at org.infinispan.factories.impl.BasicComponentRegistryImpl.invokeInjection(BasicComponentRegistryImpl.java:334) > at org.infinispan.factories.impl.BasicComponentRegistryImpl.doWireWrapper(BasicComponentRegistryImpl.java:231) > at org.infinispan.factories.impl.BasicComponentRegistryImpl.wireWrapper(BasicComponentRegistryImpl.java:212) > at org.infinispan.factories.impl.BasicComponentRegistryImpl.registerComponent(BasicComponentRegistryImpl.java:371) > at org.infinispan.factories.impl.BasicComponentRegistry.registerComponent(BasicComponentRegistry.java:100) > at org.infinispan.factories.InternalCacheFactory.createSimpleCache(InternalCacheFactory.java:151) > at org.infinispan.factories.InternalCacheFactory.createCache(InternalCacheFactory.java:81) > at org.infinispan.manager.DefaultCacheManager.wireAndStartCache(DefaultCacheManager.java:696) > at org.infinispan.manager.DefaultCacheManager.createCache(DefaultCacheManager.java:645) > at org.infinispan.manager.DefaultCacheManager.internalGetCache(DefaultCacheManager.java:530) > at org.infinispan.manager.DefaultCacheManager.getCache(DefaultCacheManager.java:511) > at org.infinispan.manager.DefaultCacheManager.getCache(DefaultCacheManager.java:504) > at org.jboss.as.clustering.infinispan.DefaultCacheContainer.getCache(DefaultCacheContainer.java:92) > at org.wildfly.clustering.infinispan.spi.service.CacheServiceConfigurator.get(CacheServiceConfigurator.java:77) > at org.wildfly.clustering.infinispan.spi.service.CacheServiceConfigurator.get(CacheServiceConfigurator.java:55) > at org.wildfly.clustering.service.FunctionalService.start(FunctionalService.java:63) > ... 7 more > Caused by: java.lang.NullPointerException > at org.wildfly.clustering.infinispan.spi.DataContainerFactory.createBoundedDataContainer(DataContainerFactory.java:113) > at org.wildfly.clustering.infinispan.spi.DataContainerFactory.construct(DataContainerFactory.java:72) > at org.infinispan.factories.impl.BasicComponentRegistryImpl.doInstantiateWrapper(BasicComponentRegistryImpl.java:186) > ... 40 more > {noformat} -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13613) SIGSEGV in libaio when running RHEL 7.8

by Brian Stansberry (Jira)

[ https://issues.redhat.com/browse/WFLY-13613?page=com.atlassian.jira.plugi... ] Brian Stansberry resolved WFLY-13613. ------------------------------------- Fix Version/s: 21.0.0.Beta1 Resolution: Done [~ehugonnet] I'm resolving under the assumption the artemis native upgrade fixes this > SIGSEGV in libaio when running RHEL 7.8 > --------------------------------------- > > Key: WFLY-13613 > URL: https://issues.redhat.com/browse/WFLY-13613 > Project: WildFly > Issue Type: Bug > Components: JMS > Reporter: Bartosz Spyrko-Smietanko > Assignee: Emmanuel Hugonnet > Priority: Major > Fix For: 21.0.0.Beta1 > > > AMQ 7 sporadically crashes with a SIGSEGV in the libaio native library in method SubmitInfo: > {code} > # > # A fatal error has been detected by the Java Runtime Environment: > # > # SIGSEGV (0xb) at pc=0x00007f3e985c6855, pid=113988, tid=0x00007f3e30aa8700 > # > # JRE version: OpenJDK Runtime Environment (8.0_252-b09) (build 1.8.0_252-b09) > # Java VM: OpenJDK 64-Bit Server VM (25.252-b09 mixed mode linux-amd64 compressed oops) > # Problematic frame: > # j org.apache.activemq.artemis.nativo.jlibaio.LibaioContext.done(Lorg/apache/activemq/artemis/nativo/jlibaio/SubmitInfo;)V+1 > # > # Failed to write core dump. Core dumps have been disabled. To enable core dumping, try "ulimit -c unlimited" before starting Java again > # > # If you would like to submit a bug report, please visit: > # http://bugreport.java.com/bugreport/crash.jsp > # > {code} > This appears to be related to the JVM version and / or virtualization environments. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13592) jndi-view doen't show values for EJB in java:jboss/exported

by Brian Stansberry (Jira)

[ https://issues.redhat.com/browse/WFLY-13592?page=com.atlassian.jira.plugi... ] Brian Stansberry updated WFLY-13592: ------------------------------------ Summary: jndi-view doen't show values for EJB in java:jboss/exported (was: [GSS] (7.3.z) jndi-view doen't show values for EJB in java:jboss/exported) > jndi-view doen't show values for EJB in java:jboss/exported > ------------------------------------------------------------ > > Key: WFLY-13592 > URL: https://issues.redhat.com/browse/WFLY-13592 > Project: WildFly > Issue Type: Bug > Components: EJB, Naming > Reporter: Parul Sharma > Assignee: Parul Sharma > Priority: Major > Fix For: 21.0.0.Beta1 > > > jndi-view() show values as '?' for EJB on java:jboss/exported tree. > These values could be seen on EAP 6.4. > This can be reproduced on EAP 7.3.1 and 7.2.8. > I attached a reproducer and these results as follows. > reproducer.zip > jndi_view_result_731.txt > jndi_view_result_6422.txt > > EAP 7.3.1 / 7.2.8 > {code} > [standalone@localhost:9990 /] /subsystem=naming:jndi-view() > ... > "java:jboss/exported" => { > "ejb2-1.0" => { > "class-name" => "javax.naming.Context", > "children" => { > "GreeterEJB!com.example.GreeterEJBHome" => { > "class-name" => "java.lang.Object", > "value" => "?" > }, > "GreeterEJB!com.example.GreeterEJBRemote" => { > "class-name" => "java.lang.Object", > "value" => "?" > } > } > }, > "ejb3-1.0" => { > "class-name" => "javax.naming.Context", > "children" => {"GreeterEJB!com.example.GreeterRemote" => { > "class-name" => "java.lang.Object", > "value" => "?" > }} > } > }, > {code} > > EAP 6.4 > {code} > "java:jboss/exported" => { > "ejb2-1.0" => { > "class-name" => "javax.naming.Context", > "children" => { > "GreeterEJB!com.example.GreeterEJBHome" => { > "class-name" => "com.example.GreeterEJBHome", > "value" => "Proxy for remote EJB EJBHomeLocator{appName='', moduleName='ejb2-1.0', distinctName='', beanName='GreeterEJB', view='interface com.example.GreeterEJBHome'}" > }, > "GreeterEJB!com.example.GreeterEJBRemote" => { > "class-name" => "com.example.GreeterEJBRemote", > "value" => "Proxy for remote EJB StatelessEJBLocator{appName='', moduleName='ejb2-1.0', distinctName='', beanName='GreeterEJB', view='interface com.example.GreeterEJBRemote'}" > } > } > }, > "ejb3-1.0" => { > "class-name" => "javax.naming.Context", > "children" => {"GreeterEJB!com.example.GreeterRemote" => { > "class-name" => "com.example.GreeterRemote", > "value" => "Proxy for remote EJB StatelessEJBLocator{appName='', moduleName='ejb3-1.0', distinctName='', beanName='GreeterEJB', view='interface com.example.GreeterRemote'}" > }} > } > }, > {code} > > Additionally, > If EJB3 doesn't have @Remote, values are '?' in 'java:global' and 'java:app' similarly. > The following behaviour is not changed from 6.4. But it seems a sililar behavir as the above. > I attached the reproducer and these results as follows. > reproducer_without_remote_if.zip > jndi_view_result_no_remoteif_731.txt > jndi_view_result_no_remoteif_6422.txt > EAP 7.3.1 > {code} > "java:global" => { > ... > "ejb3-1.0" => { > "class-name" => "javax.naming.Context", > "children" => { > "GreeterEJB" => { > "class-name" => "com.example.GreeterEJB", > "value" => "?" > }, > "GreeterEJB!com.example.GreeterEJB" => { > "class-name" => "com.example.GreeterEJB", > "value" => "?" > } > } > } > } > }, > "applications" => { > "ejb3-1.0.jar" => { > "java:app" => { > ... > "ejb3-1.0" => { > "class-name" => "javax.naming.Context", > "children" => { > "GreeterEJB" => { > "class-name" => "com.example.GreeterEJB", > "value" => "?" > }, > "GreeterEJB!com.example.GreeterEJB" => { > "class-name" => "com.example.GreeterEJB", > "value" => "?" > } > } > } > }, > "modules" => undefined > }, > {code} -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13594) Upgrade Artemis Native to 1.0.2

by Brian Stansberry (Jira)

[ https://issues.redhat.com/browse/WFLY-13594?page=com.atlassian.jira.plugi... ] Brian Stansberry resolved WFLY-13594. ------------------------------------- Resolution: Duplicate Issue > Upgrade Artemis Native to 1.0.2 > ------------------------------- > > Key: WFLY-13594 > URL: https://issues.redhat.com/browse/WFLY-13594 > Project: WildFly > Issue Type: Component Upgrade > Components: JMS > Affects Versions: 20.0.0.Final > Reporter: Emmanuel Hugonnet > Assignee: Emmanuel Hugonnet > Priority: Major > > Because of a fix in the kernel, libaio is now returning duplicate events -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 6 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5451) Upgrade pmml-model version

by Donato Marrazzo (Jira)

[ https://issues.redhat.com/browse/DROOLS-5451?page=com.atlassian.jira.plug... ] Donato Marrazzo commented on DROOLS-5451: ----------------------------------------- Hi [~jomarko] I attached a pmml 4.4 [^logistic.pmml] here the spec: [http://dmg.org/pmml/v4-4/GeneralStructure.html] > Upgrade pmml-model version > -------------------------- > > Key: DROOLS-5451 > URL: https://issues.redhat.com/browse/DROOLS-5451 > Project: Drools > Issue Type: Task > Reporter: Gabriele Cardosi > Assignee: Gabriele Cardosi > Priority: Major > Labels: TrustyAI > Attachments: logistic.pmml > > > Current org.jpmml:pmml-model version inside kie-parent pom.xml is 1.4.11, > that does not support PMML version 4.4 > > Upgrade it to last version 1.5.1 -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 6 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5451) Upgrade pmml-model version

by Donato Marrazzo (Jira)

[ https://issues.redhat.com/browse/DROOLS-5451?page=com.atlassian.jira.plug... ] Donato Marrazzo updated DROOLS-5451: ------------------------------------ Attachment: logistic.pmml > Upgrade pmml-model version > -------------------------- > > Key: DROOLS-5451 > URL: https://issues.redhat.com/browse/DROOLS-5451 > Project: Drools > Issue Type: Task > Reporter: Gabriele Cardosi > Assignee: Gabriele Cardosi > Priority: Major > Labels: TrustyAI > Attachments: logistic.pmml > > > Current org.jpmml:pmml-model version inside kie-parent pom.xml is 1.4.11, > that does not support PMML version 4.4 > > Upgrade it to last version 1.5.1 -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 6 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 June 2020