December 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (ELY-1913) Upgrade com.nimbusds:nimbus-jose-jwt to 8.2.1

by Darran Lofthouse (Jira)

Darran Lofthouse created ELY-1913: ------------------------------------- Summary: Upgrade com.nimbusds:nimbus-jose-jwt to 8.2.1 Key: ELY-1913 URL: https://issues.redhat.com/browse/ELY-1913 Project: WildFly Elytron Issue Type: Component Upgrade Components: Testsuite Reporter: Darran Lofthouse Assignee: Darran Lofthouse This is only a test dependency but we are a long way behind. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ELYWEB-81) Upgrade JOSE JET to 7.9

by Darran Lofthouse (Jira)

Darran Lofthouse created ELYWEB-81: -------------------------------------- Summary: Upgrade JOSE JET to 7.9 Key: ELYWEB-81 URL: https://issues.redhat.com/browse/ELYWEB-81 Project: Elytron Web Issue Type: Component Upgrade Components: Parent Reporter: Darran Lofthouse Assignee: Darran Lofthouse -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ELYWEB-81) Upgrade JOSE JWT to 7.9

by Darran Lofthouse (Jira)

[ https://issues.redhat.com/browse/ELYWEB-81?page=com.atlassian.jira.plugin... ] Darran Lofthouse updated ELYWEB-81: ----------------------------------- Summary: Upgrade JOSE JWT to 7.9 (was: Upgrade JOSE JET to 7.9) > Upgrade JOSE JWT to 7.9 > ----------------------- > > Key: ELYWEB-81 > URL: https://issues.redhat.com/browse/ELYWEB-81 > Project: Elytron Web > Issue Type: Component Upgrade > Components: Parent > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Priority: Major > -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFWIP-281) MP Fault Tolerance - EAR deployment fails with WELD-000049: Unable to invoke void io.smallrye.faulttolerance.HystrixInitializer.onStartup()

by Miroslav Novak (Jira)

Miroslav Novak created WFWIP-281: ------------------------------------ Summary: MP Fault Tolerance - EAR deployment fails with WELD-000049: Unable to invoke void io.smallrye.faulttolerance.HystrixInitializer.onStartup() Key: WFWIP-281 URL: https://issues.redhat.com/browse/WFWIP-281 Project: WildFly WIP Issue Type: Bug Components: MP Fault Tolerance Reporter: Miroslav Novak Assignee: Radoslav Husar If EAR deployment contains MP FT module then deployment fails with: {code} 9 INFO [io.smallrye.metrics] (MSC service thread 1-1) MicroProfile: Metrics activated 15:01:56,436 INFO [io.smallrye.faulttolerance.HystrixExtension] (MSC service thread 1-1) MicroProfile: Fault Tolerance activated 15:01:56,530 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 78) WFLYCLINF0002: Started client-mappings cache from ejb container 15:01:57,109 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 78) WFLYUT0021: Registered web context: '/first-module' for server 'default-server' 15:01:57,161 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 78) WFLYUT0021: Registered web context: '/second-module' for server 'default-server' 15:01:57,168 ERROR [org.jboss.threads.errors] (ServerService Thread Pool -- 22) Thread Thread[ServerService Thread Pool -- 22,5,ServerService ThreadGroup] threw an uncaught exception: org.jboss.weld.exceptions.WeldException: WELD-000049: Unable to invoke void io.smallrye.faulttolerance.HystrixInitializer.onStartup() on io.smallrye.faulttolerance.HystrixInitializer@126bab84 at org.jboss.weld.injection.producer.DefaultLifecycleCallbackInvoker.invokeMethods(DefaultLifecycleCallbackInvoker.java:85) at org.jboss.weld.injection.producer.DefaultLifecycleCallbackInvoker.postConstruct(DefaultLifecycleCallbackInvoker.java:66) at org.jboss.weld.injection.producer.BasicInjectionTarget.postConstruct(BasicInjectionTarget.java:122) at org.jboss.weld.bean.ManagedBean.create(ManagedBean.java:174) at org.jboss.weld.contexts.AbstractContext.get(AbstractContext.java:96) at org.jboss.weld.bean.ContextualInstanceStrategy$DefaultContextualInstanceStrategy.get(ContextualInstanceStrategy.java:100) at org.jboss.weld.bean.ContextualInstanceStrategy$ApplicationScopedContextualInstanceStrategy.get(ContextualInstanceStrategy.java:140) at org.jboss.weld.bean.ContextualInstance.get(ContextualInstance.java:67) at org.jboss.weld.event.ObserverMethodImpl.getReceiver(ObserverMethodImpl.java:360) at org.jboss.weld.event.ObserverMethodImpl.getReceiverIfExists(ObserverMethodImpl.java:347) at org.jboss.weld.event.ObserverMethodImpl.sendEvent(ObserverMethodImpl.java:305) at org.jboss.weld.event.ObserverMethodImpl.notify(ObserverMethodImpl.java:286) at javax.enterprise.inject.spi.ObserverMethod.notify(ObserverMethod.java:124) at org.jboss.weld.util.Observers.notify(Observers.java:166) at org.jboss.weld.event.ObserverNotifier.notifySyncObservers(ObserverNotifier.java:285) at org.jboss.weld.event.ObserverNotifier.notify(ObserverNotifier.java:273) at org.jboss.weld.event.ObserverNotifier.fireEvent(ObserverNotifier.java:177) at org.jboss.weld.bootstrap.BeanDeploymentModule.fireEvent(BeanDeploymentModule.java:93) at org.jboss.weld.bootstrap.WeldStartup.endInitialization(WeldStartup.java:582) at org.jboss.weld.bootstrap.WeldBootstrap.endInitialization(WeldBootstrap.java:100) at org.jboss.as.weld.WeldStartCompletionService$1.run(WeldStartCompletionService.java:108) 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: java.lang.reflect.InvocationTargetException 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.jboss.weld.injection.producer.DefaultLifecycleCallbackInvoker.invokeMethods(DefaultLifecycleCallbackInvoker.java:83) ... 26 more Caused by: java.lang.IllegalArgumentException: WFLYWELD0049: Error injecting resource into CDI managed bean. Can't find a resource named java:comp/DefaultManagedThreadFactory defined on javax.enterprise.concurrent.ManagedThreadFactory io.smallrye.faulttolerance.DefaultHystrixConcurrencyStrategy.managedThreadFactory at org.jboss.as.weld.services.bootstrap.WeldResourceInjectionServices.resolveResource(WeldResourceInjectionServices.java:238) at org.jboss.as.weld.services.bootstrap.WeldResourceInjectionServices$1.createResource(WeldResourceInjectionServices.java:183) at org.jboss.weld.injection.AbstractResourceInjection.getResourceReference(AbstractResourceInjection.java:49) at org.jboss.weld.injection.AbstractResourceInjection.injectResourceReference(AbstractResourceInjection.java:63) at org.jboss.weld.util.Beans.injectEEFields(Beans.java:309) at org.jboss.weld.injection.producer.ResourceInjector$1.proceed(ResourceInjector.java:68) at org.jboss.weld.injection.InjectionContextImpl.run(InjectionContextImpl.java:48) at org.jboss.weld.injection.producer.ResourceInjector.inject(ResourceInjector.java:71) at org.jboss.weld.injection.producer.BasicInjectionTarget.inject(BasicInjectionTarget.java:117) at org.jboss.weld.bean.ManagedBean.create(ManagedBean.java:161) at org.jboss.weld.contexts.unbound.DependentContextImpl.get(DependentContextImpl.java:70) at org.jboss.weld.bean.ContextualInstanceStrategy$DefaultContextualInstanceStrategy.get(ContextualInstanceStrategy.java:100) at org.jboss.weld.bean.ContextualInstance.get(ContextualInstance.java:50) at org.jboss.weld.manager.BeanManagerImpl.getReference(BeanManagerImpl.java:694) at org.jboss.weld.bean.builtin.InstanceImpl.getBeanInstance(InstanceImpl.java:252) at org.jboss.weld.bean.builtin.InstanceImpl.get(InstanceImpl.java:114) at io.smallrye.faulttolerance.HystrixInitializer.onStartup(HystrixInitializer.java:56) ... 31 more Caused by: javax.naming.NameNotFoundException: java:comp/DefaultManagedThreadFactory at org.jboss.as.naming.InitialContext$DefaultInitialContext.findContext(InitialContext.java:191) at org.jboss.as.naming.InitialContext$DefaultInitialContext.lookup(InitialContext.java:235) at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:193) at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:189) at javax.naming.InitialContext.lookup(InitialContext.java:417) at javax.naming.InitialContext.lookup(InitialContext.java:417) at org.jboss.as.weld.services.bootstrap.WeldResourceInjectionServices.resolveResource(WeldResourceInjectionServices.java:236) ... 47 more {code} This issue does not allow to deploy EAR with MP FT module. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ELYWEB-80) Upgrade Undertow to 2.0.28.Final

by Darran Lofthouse (Jira)

Darran Lofthouse created ELYWEB-80: -------------------------------------- Summary: Upgrade Undertow to 2.0.28.Final Key: ELYWEB-80 URL: https://issues.redhat.com/browse/ELYWEB-80 Project: Elytron Web Issue Type: Component Upgrade Components: Undertow Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: 1.7.0.CR3 -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBEE-200) License.txt missing

by Eduardo Martins (Jira)

[ https://issues.redhat.com/browse/JBEE-200?page=com.atlassian.jira.plugin.... ] Eduardo Martins resolved JBEE-200. ---------------------------------- Resolution: Done > License.txt missing > -------------------- > > Key: JBEE-200 > URL: https://issues.redhat.com/browse/JBEE-200 > Project: JBoss Enterprise Spec APIs > Issue Type: Bug > Components: jboss-javaee-specs > Reporter: Eduardo Martins > Assignee: Eduardo Martins > Priority: Major > -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4860) Increase Unit test in the HA-Core and HA-remote to pass SonarCloud Checks

by Massimiliano Dessi (Jira)

Massimiliano Dessi created DROOLS-4860: ------------------------------------------ Summary: Increase Unit test in the HA-Core and HA-remote to pass SonarCloud Checks Key: DROOLS-4860 URL: https://issues.redhat.com/browse/DROOLS-4860 Project: Drools Issue Type: Task Reporter: Massimiliano Dessi Assignee: Massimiliano Dessi -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4860) Increase Unit test in the HA-Core and HA-remote to pass SonarCloud Checks

by Massimiliano Dessi (Jira)

[ https://issues.redhat.com/browse/DROOLS-4860?page=com.atlassian.jira.plug... ] Massimiliano Dessi updated DROOLS-4860: --------------------------------------- Sprint: 2019 Week 50-52 (from Dec 9) > Increase Unit test in the HA-Core and HA-remote to pass SonarCloud Checks > ------------------------------------------------------------------------- > > Key: DROOLS-4860 > URL: https://issues.redhat.com/browse/DROOLS-4860 > Project: Drools > Issue Type: Task > Reporter: Massimiliano Dessi > Assignee: Massimiliano Dessi > Priority: Major > -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4664) Scenario Background Table row duplication

by Yeser Amer (Jira)

[ https://issues.redhat.com/browse/DROOLS-4664?page=com.atlassian.jira.plug... ] Yeser Amer updated DROOLS-4664: ------------------------------- Story Points: (was: 1) > Scenario Background Table row duplication > ----------------------------------------- > > Key: DROOLS-4664 > URL: https://issues.redhat.com/browse/DROOLS-4664 > Project: Drools > Issue Type: Bug > Components: Scenario Simulation and Testing > Affects Versions: 7.29.0.Final > Reporter: Jozef Marko > Assignee: Jozef Marko > Priority: Major > > Currently the Scenario Background table row duplication doesn't work, for more details, see the [comment|https://github.com/kiegroup/drools-wb/pull/1239#issuecomment-5436...]. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4665) Scenario Background toolbar buttons state

by Yeser Amer (Jira)

[ https://issues.redhat.com/browse/DROOLS-4665?page=com.atlassian.jira.plug... ] Yeser Amer updated DROOLS-4665: ------------------------------- Story Points: (was: 5) > Scenario Background toolbar buttons state > ----------------------------------------- > > Key: DROOLS-4665 > URL: https://issues.redhat.com/browse/DROOLS-4665 > Project: Drools > Issue Type: Bug > Components: Scenario Simulation and Testing > Affects Versions: 7.29.0.Final > Reporter: Jozef Marko > Assignee: Jozef Marko > Priority: Major > > The Scenario Background tab disable some toolbar buttons, however they stay disabled depending on the order of selecting editor tabs. See the [comment|https://github.com/kiegroup/drools-wb/pull/1239#discussion_r33636...]. -- 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 December 2019