January 2020 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-12957) MP Fault tolerance tests are failing on Ubuntu

by Radoslav Husar (Jira)

[ https://issues.redhat.com/browse/WFLY-12957?page=com.atlassian.jira.plugi... ] Radoslav Husar updated WFLY-12957: ---------------------------------- Affects Version/s: No Release (was: 18.0.0.Beta1) > MP Fault tolerance tests are failing on Ubuntu > ---------------------------------------------- > > Key: WFLY-12957 > URL: https://issues.redhat.com/browse/WFLY-12957 > Project: WildFly > Issue Type: Bug > Components: MP Fault Tolerance, Test Suite > Affects Versions: No Release > Reporter: Emmanuel Hugonnet > Assignee: Emmanuel Hugonnet > Priority: Major > Fix For: 19.0.0.Beta1 > > > Environment variables with dots in their name are not supported on Ubuntu making the fault tolerance tests fail. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11728) Microprofile rest client - redeployment WELD-001414: Bean name is ambiguous.

by Brian Stansberry (Jira)

[ https://issues.redhat.com/browse/WFLY-11728?page=com.atlassian.jira.plugi... ] Brian Stansberry commented on WFLY-11728: ----------------------------------------- [~ron_sigal] Yes; I'll resolve it. > Microprofile rest client - redeployment WELD-001414: Bean name is ambiguous. > ---------------------------------------------------------------------------- > > Key: WFLY-11728 > URL: https://issues.redhat.com/browse/WFLY-11728 > Project: WildFly > Issue Type: Bug > Components: REST > Affects Versions: 15.0.1.Final > Reporter: Andrej Petras > Assignee: Ronald Sigal > Priority: Critical > Labels: Microprofile, resteasy-client > Fix For: 18.0.1.Final, 19.0.0.Beta1 > > > {noformat} > 09:35:25,936 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-4) MSC000001: Failed to start service jboss.deployment.unit."mp-client-1.0.0-SNAPSHOT.war".WeldStartService: org.jboss.msc.service.StartException in service jboss.deployment.unit."mp-client-1.0.0-SNAPSHOT.war".WeldStartService: Failed to start service > at org.jboss.msc@1.4.5.Final//org.jboss.msc.service.ServiceControllerImpl$StartTask.execute(ServiceControllerImpl.java:1730) > at org.jboss.msc@1.4.5.Final//org.jboss.msc.service.ServiceControllerImpl$ControllerTask.run(ServiceControllerImpl.java:1558) > at org.jboss.threads@2.3.2.Final//org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35) > at org.jboss.threads@2.3.2.Final//org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1985) > at org.jboss.threads@2.3.2.Final//org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1487) > at org.jboss.threads@2.3.2.Final//org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1378) > at java.base/java.lang.Thread.run(Thread.java:834) > Caused by: org.jboss.weld.exceptions.DeploymentException: WELD-001414: Bean name is ambiguous. Name org.lorislab.mp.client.api.TestRestService resolves to beans: [org.jboss.resteasy.cdi.microprofile.RestClientDelegateBean@2a357dc2, org.jboss.resteasy.cdi.microprofile.RestClientDelegateBean@59b2b6ec] > at org.jboss.weld.core@3.0.5.Final//org.jboss.weld.bootstrap.Validator.validateBeanName(Validator.java:653) > at org.jboss.weld.core@3.0.5.Final//org.jboss.weld.bootstrap.ConcurrentValidator$5.doWork(ConcurrentValidator.java:121) > at org.jboss.weld.core@3.0.5.Final//org.jboss.weld.bootstrap.ConcurrentValidator$5.doWork(ConcurrentValidator.java:119) > at org.jboss.weld.core@3.0.5.Final//org.jboss.weld.executor.IterativeWorkerTaskFactory$1.call(IterativeWorkerTaskFactory.java:62) > at org.jboss.weld.core@3.0.5.Final//org.jboss.weld.executor.IterativeWorkerTaskFactory$1.call(IterativeWorkerTaskFactory.java:55) > at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264) > at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128) > at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628) > at java.base/java.lang.Thread.run(Thread.java:834) > at org.jboss.threads@2.3.2.Final//org.jboss.threads.JBossThread.run(JBossThread.java:485) > 09:35:25,941 ERROR [org.jboss.as.controller.management-operation] (DeploymentScanner-threads - 2) WFLYCTL0013: Operation ("full-replace-deployment") failed - address: ([]) - failure description: {"WFLYCTL0080: Failed services" => {"jboss.deployment.unit.\"mp-client-1.0.0-SNAPSHOT.war\".WeldStartService" => "Failed to start service > Caused by: org.jboss.weld.exceptions.DeploymentException: WELD-001414: Bean name is ambiguous. Name org.lorislab.mp.client.api.TestRestService resolves to beans: [org.jboss.resteasy.cdi.microprofile.RestClientDelegateBean@2a357dc2, org.jboss.resteasy.cdi.microprofile.RestClientDelegateBean@59b2b6ec]"}} > {noformat} -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11728) Microprofile rest client - redeployment WELD-001414: Bean name is ambiguous.

by Brian Stansberry (Jira)

[ https://issues.redhat.com/browse/WFLY-11728?page=com.atlassian.jira.plugi... ] Brian Stansberry resolved WFLY-11728. ------------------------------------- Fix Version/s: 18.0.1.Final Resolution: Done > Microprofile rest client - redeployment WELD-001414: Bean name is ambiguous. > ---------------------------------------------------------------------------- > > Key: WFLY-11728 > URL: https://issues.redhat.com/browse/WFLY-11728 > Project: WildFly > Issue Type: Bug > Components: REST > Affects Versions: 15.0.1.Final > Reporter: Andrej Petras > Assignee: Ronald Sigal > Priority: Critical > Labels: Microprofile, resteasy-client > Fix For: 19.0.0.Beta1, 18.0.1.Final > > > {noformat} > 09:35:25,936 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-4) MSC000001: Failed to start service jboss.deployment.unit."mp-client-1.0.0-SNAPSHOT.war".WeldStartService: org.jboss.msc.service.StartException in service jboss.deployment.unit."mp-client-1.0.0-SNAPSHOT.war".WeldStartService: Failed to start service > at org.jboss.msc@1.4.5.Final//org.jboss.msc.service.ServiceControllerImpl$StartTask.execute(ServiceControllerImpl.java:1730) > at org.jboss.msc@1.4.5.Final//org.jboss.msc.service.ServiceControllerImpl$ControllerTask.run(ServiceControllerImpl.java:1558) > at org.jboss.threads@2.3.2.Final//org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35) > at org.jboss.threads@2.3.2.Final//org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1985) > at org.jboss.threads@2.3.2.Final//org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1487) > at org.jboss.threads@2.3.2.Final//org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1378) > at java.base/java.lang.Thread.run(Thread.java:834) > Caused by: org.jboss.weld.exceptions.DeploymentException: WELD-001414: Bean name is ambiguous. Name org.lorislab.mp.client.api.TestRestService resolves to beans: [org.jboss.resteasy.cdi.microprofile.RestClientDelegateBean@2a357dc2, org.jboss.resteasy.cdi.microprofile.RestClientDelegateBean@59b2b6ec] > at org.jboss.weld.core@3.0.5.Final//org.jboss.weld.bootstrap.Validator.validateBeanName(Validator.java:653) > at org.jboss.weld.core@3.0.5.Final//org.jboss.weld.bootstrap.ConcurrentValidator$5.doWork(ConcurrentValidator.java:121) > at org.jboss.weld.core@3.0.5.Final//org.jboss.weld.bootstrap.ConcurrentValidator$5.doWork(ConcurrentValidator.java:119) > at org.jboss.weld.core@3.0.5.Final//org.jboss.weld.executor.IterativeWorkerTaskFactory$1.call(IterativeWorkerTaskFactory.java:62) > at org.jboss.weld.core@3.0.5.Final//org.jboss.weld.executor.IterativeWorkerTaskFactory$1.call(IterativeWorkerTaskFactory.java:55) > at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264) > at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128) > at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628) > at java.base/java.lang.Thread.run(Thread.java:834) > at org.jboss.threads@2.3.2.Final//org.jboss.threads.JBossThread.run(JBossThread.java:485) > 09:35:25,941 ERROR [org.jboss.as.controller.management-operation] (DeploymentScanner-threads - 2) WFLYCTL0013: Operation ("full-replace-deployment") failed - address: ([]) - failure description: {"WFLYCTL0080: Failed services" => {"jboss.deployment.unit.\"mp-client-1.0.0-SNAPSHOT.war\".WeldStartService" => "Failed to start service > Caused by: org.jboss.weld.exceptions.DeploymentException: WELD-001414: Bean name is ambiguous. Name org.lorislab.mp.client.api.TestRestService resolves to beans: [org.jboss.resteasy.cdi.microprofile.RestClientDelegateBean@2a357dc2, org.jboss.resteasy.cdi.microprofile.RestClientDelegateBean@59b2b6ec]"}} > {noformat} -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12712) Upgrade RESTEasy to 3.10.0.Final

by Ronald Sigal (Jira)

[ https://issues.redhat.com/browse/WFLY-12712?page=com.atlassian.jira.plugi... ] Ronald Sigal commented on WFLY-12712: ------------------------------------- Note that WFLY-11728 / RESTEASY-2386 was fixed in RESTEasy release 3.9.1.Final, so it's already in Wildfly. I'm unlinking this from incorporating WFLY-11728 > Upgrade RESTEasy to 3.10.0.Final > -------------------------------- > > Key: WFLY-12712 > URL: https://issues.redhat.com/browse/WFLY-12712 > Project: WildFly > Issue Type: Task > Reporter: Ronald Sigal > Assignee: Ronald Sigal > Priority: Major > Fix For: 19.0.0.Beta1 > > -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11728) Microprofile rest client - redeployment WELD-001414: Bean name is ambiguous.

by Ronald Sigal (Jira)

[ https://issues.redhat.com/browse/WFLY-11728?page=com.atlassian.jira.plugi... ] Ronald Sigal commented on WFLY-11728: ------------------------------------- Actually, RESTEASY-2386 was fixed in RESTEasy release 3.9.1.Final, so this should be closed, right? > Microprofile rest client - redeployment WELD-001414: Bean name is ambiguous. > ---------------------------------------------------------------------------- > > Key: WFLY-11728 > URL: https://issues.redhat.com/browse/WFLY-11728 > Project: WildFly > Issue Type: Bug > Components: REST > Affects Versions: 15.0.1.Final > Reporter: Andrej Petras > Assignee: Ronald Sigal > Priority: Critical > Labels: Microprofile, resteasy-client > Fix For: 19.0.0.Beta1 > > > {noformat} > 09:35:25,936 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-4) MSC000001: Failed to start service jboss.deployment.unit."mp-client-1.0.0-SNAPSHOT.war".WeldStartService: org.jboss.msc.service.StartException in service jboss.deployment.unit."mp-client-1.0.0-SNAPSHOT.war".WeldStartService: Failed to start service > at org.jboss.msc@1.4.5.Final//org.jboss.msc.service.ServiceControllerImpl$StartTask.execute(ServiceControllerImpl.java:1730) > at org.jboss.msc@1.4.5.Final//org.jboss.msc.service.ServiceControllerImpl$ControllerTask.run(ServiceControllerImpl.java:1558) > at org.jboss.threads@2.3.2.Final//org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35) > at org.jboss.threads@2.3.2.Final//org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1985) > at org.jboss.threads@2.3.2.Final//org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1487) > at org.jboss.threads@2.3.2.Final//org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1378) > at java.base/java.lang.Thread.run(Thread.java:834) > Caused by: org.jboss.weld.exceptions.DeploymentException: WELD-001414: Bean name is ambiguous. Name org.lorislab.mp.client.api.TestRestService resolves to beans: [org.jboss.resteasy.cdi.microprofile.RestClientDelegateBean@2a357dc2, org.jboss.resteasy.cdi.microprofile.RestClientDelegateBean@59b2b6ec] > at org.jboss.weld.core@3.0.5.Final//org.jboss.weld.bootstrap.Validator.validateBeanName(Validator.java:653) > at org.jboss.weld.core@3.0.5.Final//org.jboss.weld.bootstrap.ConcurrentValidator$5.doWork(ConcurrentValidator.java:121) > at org.jboss.weld.core@3.0.5.Final//org.jboss.weld.bootstrap.ConcurrentValidator$5.doWork(ConcurrentValidator.java:119) > at org.jboss.weld.core@3.0.5.Final//org.jboss.weld.executor.IterativeWorkerTaskFactory$1.call(IterativeWorkerTaskFactory.java:62) > at org.jboss.weld.core@3.0.5.Final//org.jboss.weld.executor.IterativeWorkerTaskFactory$1.call(IterativeWorkerTaskFactory.java:55) > at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264) > at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128) > at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628) > at java.base/java.lang.Thread.run(Thread.java:834) > at org.jboss.threads@2.3.2.Final//org.jboss.threads.JBossThread.run(JBossThread.java:485) > 09:35:25,941 ERROR [org.jboss.as.controller.management-operation] (DeploymentScanner-threads - 2) WFLYCTL0013: Operation ("full-replace-deployment") failed - address: ([]) - failure description: {"WFLYCTL0080: Failed services" => {"jboss.deployment.unit.\"mp-client-1.0.0-SNAPSHOT.war\".WeldStartService" => "Failed to start service > Caused by: org.jboss.weld.exceptions.DeploymentException: WELD-001414: Bean name is ambiguous. Name org.lorislab.mp.client.api.TestRestService resolves to beans: [org.jboss.resteasy.cdi.microprofile.RestClientDelegateBean@2a357dc2, org.jboss.resteasy.cdi.microprofile.RestClientDelegateBean@59b2b6ec]"}} > {noformat} -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12963) Use maven project.groupId for wildfly-microprofile-jwt-smallrye dependencies

by Brian Stansberry (Jira)

[ https://issues.redhat.com/browse/WFLY-12963?page=com.atlassian.jira.plugi... ] Brian Stansberry updated WFLY-12963: ------------------------------------ Attachment: (was: Не подтвержден 871729.crdownload) > Use maven project.groupId for wildfly-microprofile-jwt-smallrye dependencies > ---------------------------------------------------------------------------- > > Key: WFLY-12963 > URL: https://issues.redhat.com/browse/WFLY-12963 > Project: WildFly > Issue Type: Task > Components: Build System > Reporter: Yeray Borges > Assignee: Yeray Borges > Priority: Minor > Fix For: 19.0.0.Beta1 > > > The use of maven property ${project.groupid} instead of the hardcoded org.wildfly group id facilitates the transition to the product branches. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JGRP-2434) Support multiple TShark fields parser

by Diego Lovison (Jira)

Diego Lovison created JGRP-2434: ----------------------------------- Summary: Support multiple TShark fields parser Key: JGRP-2434 URL: https://issues.redhat.com/browse/JGRP-2434 Project: JGroups Issue Type: Enhancement Affects Versions: 5.0 Reporter: Diego Lovison Assignee: Bela Ban In other to achieve what I was looking for that is: have the time in front of the line.. it required too many changes in {{Util::parse}} Changes * Need to be divide the {{short version=dis.readShort();}} into the {{dis.read()}} to identify the {{\t}} * {{Util::parse}} is used in GossipRouter Why have a diff parser Prevent changing production code Easy to create/add more fields related only with TShark It reuse the {{Util::parse}} -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JGRP-2434) Support multiple TShark fields parser

by Diego Lovison (Jira)

[ https://issues.redhat.com/browse/JGRP-2434?page=com.atlassian.jira.plugin... ] Diego Lovison reassigned JGRP-2434: ----------------------------------- Assignee: Diego Lovison (was: Bela Ban) > Support multiple TShark fields parser > ------------------------------------- > > Key: JGRP-2434 > URL: https://issues.redhat.com/browse/JGRP-2434 > Project: JGroups > Issue Type: Enhancement > Affects Versions: 5.0 > Reporter: Diego Lovison > Assignee: Diego Lovison > Priority: Major > > In other to achieve what I was looking for that is: have the time in front of the line.. it required too many changes in {{Util::parse}} > Changes > * Need to be divide the {{short version=dis.readShort();}} into the {{dis.read()}} to identify the {{\t}} > * {{Util::parse}} is used in GossipRouter > Why have a diff parser > Prevent changing production code > Easy to create/add more fields related only with TShark > It reuse the {{Util::parse}} -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JGRP-2434) Support multiple TShark fields parser

by Diego Lovison (Jira)

[ https://issues.redhat.com/browse/JGRP-2434?page=com.atlassian.jira.plugin... ] Diego Lovison updated JGRP-2434: -------------------------------- Description: In other to achieve what I was looking for that is: have the time in front of the line.. it required too many changes in {{Util::parse}} Changes * Need to be divide the {{short version=dis.readShort();}} into the {{dis.read()}} to identify the {{\t}} * {{Util::parse}} is used in GossipRouter Why have a diff parser * Prevent changing production code * Easy to create/add more fields related only with TShark * It reuse the {{Util::parse}} was: In other to achieve what I was looking for that is: have the time in front of the line.. it required too many changes in {{Util::parse}} Changes * Need to be divide the {{short version=dis.readShort();}} into the {{dis.read()}} to identify the {{\t}} * {{Util::parse}} is used in GossipRouter Why have a diff parser Prevent changing production code Easy to create/add more fields related only with TShark It reuse the {{Util::parse}} > Support multiple TShark fields parser > ------------------------------------- > > Key: JGRP-2434 > URL: https://issues.redhat.com/browse/JGRP-2434 > Project: JGroups > Issue Type: Enhancement > Affects Versions: 5.0 > Reporter: Diego Lovison > Assignee: Diego Lovison > Priority: Major > > In other to achieve what I was looking for that is: have the time in front of the line.. it required too many changes in {{Util::parse}} > Changes > * Need to be divide the {{short version=dis.readShort();}} into the {{dis.read()}} to identify the {{\t}} > * {{Util::parse}} is used in GossipRouter > Why have a diff parser > * Prevent changing production code > * Easy to create/add more fields related only with TShark > * It reuse the {{Util::parse}} -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12963) Use maven project.groupId for wildfly-microprofile-jwt-smallrye dependencies

by Николай Гордуз (Jira)

[ https://issues.redhat.com/browse/WFLY-12963?page=com.atlassian.jira.plugi... ] Николай Гордуз updated WFLY-12963: ---------------------------------- Attachment: Не подтвержден 871729.crdownload > Use maven project.groupId for wildfly-microprofile-jwt-smallrye dependencies > ---------------------------------------------------------------------------- > > Key: WFLY-12963 > URL: https://issues.redhat.com/browse/WFLY-12963 > Project: WildFly > Issue Type: Task > Components: Build System > Reporter: Yeray Borges > Assignee: Yeray Borges > Priority: Minor > Fix For: 19.0.0.Beta1 > > Attachments: Не подтвержден 871729.crdownload > > > The use of maven property ${project.groupid} instead of the hardcoded org.wildfly group id facilitates the transition to the product branches. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira January 2020