March 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (JBEE-199) Upgrade JSF API 2.3 to version 2.3.9.SP01

by Eduardo Martins (Jira)

[ https://issues.jboss.org/browse/JBEE-199?page=com.atlassian.jira.plugin.s... ] Eduardo Martins updated JBEE-199: --------------------------------- Git Pull Request: https://github.com/jboss/jboss-javaee-specs/pull/13 > Upgrade JSF API 2.3 to version 2.3.9.SP01 > ----------------------------------------- > > Key: JBEE-199 > URL: https://issues.jboss.org/browse/JBEE-199 > Project: JBoss JavaEE Spec APIs > Issue Type: Enhancement > Reporter: Eduardo Martins > Assignee: Eduardo Martins > Priority: Major > > Latest JBoss server releases uses a newer 2.3.9.SP01 version for dependency org.jboss.spec.javax.faces:jboss-jsf-api_2.3_spec, and jboss specs BOMs should depend on same version. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBEE-199) Upgrade JSF API 2.3 to version 2.3.9.SP01

by Eduardo Martins (Jira)

Eduardo Martins created JBEE-199: ------------------------------------ Summary: Upgrade JSF API 2.3 to version 2.3.9.SP01 Key: JBEE-199 URL: https://issues.jboss.org/browse/JBEE-199 Project: JBoss JavaEE Spec APIs Issue Type: Enhancement Reporter: Eduardo Martins Assignee: Eduardo Martins Latest JBoss server releases uses a newer 2.3.9.SP01 version for dependency org.jboss.spec.javax.faces:jboss-jsf-api_2.3_spec, and jboss specs BOMs should depend on same version. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JGRP-2340) SocketFactory missing createSocketChannel(String service_name) and close(SocketChannel)

by Paul Ferraro (Jira)

Paul Ferraro created JGRP-2340: ---------------------------------- Summary: SocketFactory missing createSocketChannel(String service_name) and close(SocketChannel) Key: JGRP-2340 URL: https://issues.jboss.org/browse/JGRP-2340 Project: JGroups Issue Type: Bug Affects Versions: 4.0.19 Reporter: Paul Ferraro Assignee: Bela Ban NioConnection should defer to the SocketFactory to create (with a service_name) and close its SocketChannel. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JGRP-2339) SocketFactory missing close(ServerSocketChannel)

by Paul Ferraro (Jira)

Paul Ferraro created JGRP-2339: ---------------------------------- Summary: SocketFactory missing close(ServerSocketChannel) Key: JGRP-2339 URL: https://issues.jboss.org/browse/JGRP-2339 Project: JGroups Issue Type: Bug Affects Versions: 4.0.19 Reporter: Paul Ferraro Assignee: Bela Ban JGroups SocketFactory contains methods for creating named ServerSocketChannels, however, there is no corresponding close(ServerSocketChannel) method. WF relies on the SocketFactory to register JGroups sockets with its SocketBindingManager, so that the management layer can report which sockets are connected, to which address/port are they are bound, etc. The close(...) methods are necessary to unregister from the SocketBindingManager. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11926) Upgrade ejb-client to 4.0.16.Final

by Kabir Khan (Jira)

[ https://issues.jboss.org/browse/WFLY-11926?page=com.atlassian.jira.plugin... ] Kabir Khan updated WFLY-11926: ------------------------------ Git Pull Request: https://github.com/wildfly/wildfly/pull/12194 > Upgrade ejb-client to 4.0.16.Final > ---------------------------------- > > Key: WFLY-11926 > URL: https://issues.jboss.org/browse/WFLY-11926 > Project: WildFly > Issue Type: Component Upgrade > Components: EJB > Reporter: Kabir Khan > Assignee: Tomasz Adamski > Priority: Blocker > Fix For: 17.0.0.Beta1 > > > [~tomekadamski] Please link the issues fixed to this -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11927) Upgrade ejb-client to 4.0.16.Final

by Kabir Khan (Jira)

Kabir Khan created WFLY-11927: --------------------------------- Summary: Upgrade ejb-client to 4.0.16.Final Key: WFLY-11927 URL: https://issues.jboss.org/browse/WFLY-11927 Project: WildFly Issue Type: Component Upgrade Components: EJB Reporter: Kabir Khan Assignee: Tomasz Adamski Fix For: 17.0.0.Beta1 [~tomekadamski] Please link the issues fixed to this -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11926) Upgrade ejb-client to 4.0.16.Final

by Kabir Khan (Jira)

[ https://issues.jboss.org/browse/WFLY-11926?page=com.atlassian.jira.plugin... ] Kabir Khan resolved WFLY-11926. ------------------------------- Fix Version/s: 17.0.0.Beta1 Resolution: Done > Upgrade ejb-client to 4.0.16.Final > ---------------------------------- > > Key: WFLY-11926 > URL: https://issues.jboss.org/browse/WFLY-11926 > Project: WildFly > Issue Type: Component Upgrade > Components: EJB > Reporter: Kabir Khan > Assignee: Tomasz Adamski > Priority: Blocker > Fix For: 17.0.0.Beta1 > > > [~tomekadamski] Please link the issues fixed to this -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11926) Upgrade ejb-client to 4.0.16.Final

by Kabir Khan (Jira)

Kabir Khan created WFLY-11926: --------------------------------- Summary: Upgrade ejb-client to 4.0.16.Final Key: WFLY-11926 URL: https://issues.jboss.org/browse/WFLY-11926 Project: WildFly Issue Type: Component Upgrade Components: EJB Reporter: Kabir Khan Assignee: Tomasz Adamski [~tomekadamski] Please link the issues fixed to this -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11906) Managed Executor Task Fails with CDI if created from Batchlet

by Cheng Fang (Jira)

[ https://issues.jboss.org/browse/WFLY-11906?page=com.atlassian.jira.plugin... ] Cheng Fang commented on WFLY-11906: ----------------------------------- Yes, I will look into any problems in batch subsystem. > Managed Executor Task Fails with CDI if created from Batchlet > ------------------------------------------------------------- > > Key: WFLY-11906 > URL: https://issues.jboss.org/browse/WFLY-11906 > Project: WildFly > Issue Type: Bug > Components: Batch, CDI / Weld, Concurrency Utilities > Affects Versions: 16.0.0.Final > Environment: Java 8 > Reporter: Cody Lerum > Assignee: Cheng Fang > Priority: Major > > This previously was working (verified in reproducer) on Wildfly 14.0.1 > Inside of a batchlet if a Managed Executor Task is executed and that Task uses CDI.current() an exception is thrown > {code:java} > 11:00:02,343 ERROR [stderr] (EE-ManagedExecutorService-default-Thread-1) java.lang.IllegalStateException: WFLYWELD0039: Singleton not set for ModuleClassLoader for Module "org.jboss.as.ee" version 16.0.0.Final from local module loader @78e94dcf (finder: local module finder @233fe9b6 (roots: V:\opt\wildfly-16.0.0.Final\modules,V:\opt\wildfly-16.0.0.Final\modules\system\layers\base)). This means that you are trying to access a weld deployment with a Thread Context ClassLoader that is not associated with the deployment. > 11:00:02,344 ERROR [stderr] (EE-ManagedExecutorService-default-Thread-1) at org.jboss.as.weld.services.ModuleGroupSingletonProvider$TCCLSingleton.get(ModuleGroupSingletonProvider.java:77) > 11:00:02,344 ERROR [stderr] (EE-ManagedExecutorService-default-Thread-1) at org.jboss.as.weld.services.ModuleGroupSingletonProvider$TCCLSingleton.get(ModuleGroupSingletonProvider.java:134) > 11:00:02,344 ERROR [stderr] (EE-ManagedExecutorService-default-Thread-1) at org.jboss.weld.Container.instance(Container.java:57) > 11:00:02,344 ERROR [stderr] (EE-ManagedExecutorService-default-Thread-1) at org.jboss.as.weld.WeldProvider.getCDI(WeldProvider.java:69) > 11:00:02,344 ERROR [stderr] (EE-ManagedExecutorService-default-Thread-1) at javax.enterprise.inject.spi.CDI.lambda$getCDIProvider$0(CDI.java:87) > 11:00:02,345 ERROR [stderr] (EE-ManagedExecutorService-default-Thread-1) at java.util.stream.ReferencePipeline$2$1.accept(ReferencePipeline.java:174) > 11:00:02,345 ERROR [stderr] (EE-ManagedExecutorService-default-Thread-1) at java.util.TreeMap$KeySpliterator.tryAdvance(TreeMap.java:2770) > 11:00:02,345 ERROR [stderr] (EE-ManagedExecutorService-default-Thread-1) at java.util.stream.ReferencePipeline.forEachWithCancel(ReferencePipeline.java:126) > 11:00:02,345 ERROR [stderr] (EE-ManagedExecutorService-default-Thread-1) at java.util.stream.AbstractPipeline.copyIntoWithCancel(AbstractPipeline.java:498) > 11:00:02,345 ERROR [stderr] (EE-ManagedExecutorService-default-Thread-1) at java.util.stream.AbstractPipeline.copyInto(AbstractPipeline.java:485) > 11:00:02,345 ERROR [stderr] (EE-ManagedExecutorService-default-Thread-1) at java.util.stream.AbstractPipeline.wrapAndCopyInto(AbstractPipeline.java:471) > 11:00:02,346 ERROR [stderr] (EE-ManagedExecutorService-default-Thread-1) at java.util.stream.FindOps$FindOp.evaluateSequential(FindOps.java:152) > 11:00:02,346 ERROR [stderr] (EE-ManagedExecutorService-default-Thread-1) at java.util.stream.AbstractPipeline.evaluate(AbstractPipeline.java:234) > 11:00:02,346 ERROR [stderr] (EE-ManagedExecutorService-default-Thread-1) at java.util.stream.ReferencePipeline.findFirst(ReferencePipeline.java:464) > 11:00:02,346 ERROR [stderr] (EE-ManagedExecutorService-default-Thread-1) at javax.enterprise.inject.spi.CDI.getCDIProvider(CDI.java:88) > 11:00:02,346 ERROR [stderr] (EE-ManagedExecutorService-default-Thread-1) at javax.enterprise.inject.spi.CDI.current(CDI.java:64) > 11:00:02,346 ERROR [stderr] (EE-ManagedExecutorService-default-Thread-1) at com.outjected.demo.DemoTask.run(DemoTask.java:27) > 11:00:02,347 ERROR [stderr] (EE-ManagedExecutorService-default-Thread-1) at org.jboss.as.ee.concurrent.ControlPointUtils$ControlledRunnable.run(ControlPointUtils.java:105) > 11:00:02,347 ERROR [stderr] (EE-ManagedExecutorService-default-Thread-1) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) > 11:00:02,347 ERROR [stderr] (EE-ManagedExecutorService-default-Thread-1) at java.util.concurrent.FutureTask.run$$$capture(FutureTask.java:266) > 11:00:02,347 ERROR [stderr] (EE-ManagedExecutorService-default-Thread-1) at java.util.concurrent.FutureTask.run(FutureTask.java) > 11:00:02,348 ERROR [stderr] (EE-ManagedExecutorService-default-Thread-1) at org.glassfish.enterprise.concurrent.internal.ManagedFutureTask.run(ManagedFutureTask.java:141) > 11:00:02,348 ERROR [stderr] (EE-ManagedExecutorService-default-Thread-1) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) > 11:00:02,348 ERROR [stderr] (EE-ManagedExecutorService-default-Thread-1) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) > 11:00:02,348 ERROR [stderr] (EE-ManagedExecutorService-default-Thread-1) at java.lang.Thread.run(Thread.java:748) > 11:00:02,349 ERROR [stderr] (EE-ManagedExecutorService-default-Thread-1) at org.glassfish.enterprise.concurrent.ManagedThreadFactoryImpl$ManagedThread.run(ManagedThreadFactoryImpl.java:250) > 11:00:02,349 ERROR [stderr] (EE-ManagedExecutorService-default-Thread-1) at org.jboss.as.ee.concurrent.service.ElytronManagedThreadFactory$ElytronManagedThread.run(ElytronManagedThreadFactory.java:85) > {code} -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11925) Add documentation to the "Using the Elytron Subsystem" section on the attributes that can be specified when configuring server and client SSLContexts

by Farah Juma (Jira)

[ https://issues.jboss.org/browse/WFLY-11925?page=com.atlassian.jira.plugin... ] Farah Juma updated WFLY-11925: ------------------------------ Summary: Add documentation to the "Using the Elytron Subsystem" section on the attributes that can be specified when configuring server and client SSLContexts (was: Add documentation to the "Using the Elytron Subsystem" on the attributes that can be specified when configuring server and client SSLContexts) > Add documentation to the "Using the Elytron Subsystem" section on the attributes that can be specified when configuring server and client SSLContexts > ----------------------------------------------------------------------------------------------------------------------------------------------------- > > Key: WFLY-11925 > URL: https://issues.jboss.org/browse/WFLY-11925 > Project: WildFly > Issue Type: Task > Components: Security > Reporter: Farah Juma > Assignee: Farah Juma > Priority: Major > > Add documentation to the "Using the Elytron Subsystem" section on the attributes that can be specified when configuring a {{server-ssl-context}} and a {{client-ssl-context}}. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 8 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 March 2019