November 2016 - jboss-jira - Jboss List Archives

[JBoss JIRA] (ELY-368) Add optional Supplier<Provider[]> to realm implementations.

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-368?page=com.atlassian.jira.plugin.sy... ] Darran Lofthouse reassigned ELY-368: ------------------------------------ Assignee: Darran Lofthouse > Add optional Supplier<Provider[]> to realm implementations. > ----------------------------------------------------------- > > Key: ELY-368 > URL: https://issues.jboss.org/browse/ELY-368 > Project: WildFly Elytron > Issue Type: Enhancement > Reporter: David Lloyd > Assignee: Darran Lofthouse > Priority: Critical > Fix For: 1.1.0.Beta15 > > > Realms use key factories, certificate factories, password factories, etc. Most of the time they just use the default installed providers. Enhance the realms to accept an optional {{Supplier<Provider[]>}} which will be used to load these kinds of things. The default supplier should be {{Security::getProviders()}}. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7636) Remote method invocation produces java.lang.UnsupportedOperationException in application client container

by Farah Juma (JIRA)

[ https://issues.jboss.org/browse/WFLY-7636?page=com.atlassian.jira.plugin.... ] Farah Juma moved JBEAP-7423 to WFLY-7636: ----------------------------------------- Project: WildFly (was: JBoss Enterprise Application Platform) Key: WFLY-7636 (was: JBEAP-7423) Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1) Component/s: Application Client (was: Application Client) Affects Version/s: (was: 7.1.0.DR8) > Remote method invocation produces java.lang.UnsupportedOperationException in application client container > --------------------------------------------------------------------------------------------------------- > > Key: WFLY-7636 > URL: https://issues.jboss.org/browse/WFLY-7636 > Project: WildFly > Issue Type: Bug > Components: Application Client > Reporter: Farah Juma > Assignee: Farah Juma > > After ending a remote method invocation in application client container, the following exception is produced: > {code}[mjurc@tigris app-client]$ $JBOSS_HOME/bin/appclient.sh ear/target/jboss-app-client.ear#simpleClient.jar Hello from command line > . > . > . > 08:24:57,312 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0025: JBoss EAP 7.1.0.Alpha1 (WildFly Core 3.0.0.Alpha12-redhat-1) started in 1675ms - Started 230 of 234 services (19 services are lazy, passive or on-demand) > 08:24:57,316 INFO [org.jboss.as.server] (Thread-40) WFLYSRV0010: Deployed "jboss-app-client.ear" (runtime-name : "jboss-app-client.ear") > 08:24:57,327 INFO [org.jboss.ejb.client] (Thread-47) JBoss EJB Client version 3.0.0.Beta2 > 08:24:57,332 INFO [org.jboss.as.quickstarts.appclient.acc.client.Main] (Thread-47) Main started with arguments > 08:24:57,333 INFO [org.jboss.as.quickstarts.appclient.acc.client.Main] (Thread-47) [Hello, from, command, line] > 08:24:57,338 INFO [org.wildfly.security] (Thread-47) ELY00001: WildFly Elytron version 1.1.0.Beta13 > 08:24:57,390 INFO [org.jboss.remoting] (Thread-47) JBoss Remoting version 5.0.0.Beta7 > 08:24:57,420 INFO [org.xnio] (Thread-47) XNIO version 3.4.1.Final-redhat-1 > 08:24:57,431 INFO [org.xnio.nio] (Thread-47) XNIO NIO Implementation Version 3.4.1.Final-redhat-1 > 08:24:57,557 INFO [org.jboss.ejb.client.remoting] (Remoting (anonymous) task-5) EJBCLIENT000017: Received server version 2 and marshalling strategies [river] > 08:24:57,563 INFO [org.jboss.ejb.client.remoting] (Thread-47) EJBCLIENT000013: Successful version handshake completed for receiver context EJBReceiverContext{clientContext=org.jboss.ejb.client.EJBClientContext@7a5bd5ec, receiver=Remoting connection EJB receiver [connection=Remoting connection <2f5c9eb> on endpoint (anonymous) <3ccd44ca>,channel=jboss.ejb,nodename=tigris]} on channel Channel ID e8f58e71 (outbound) of Remoting connection 28455490 to localhost/127.0.0.1:8080 of endpoint (anonymous) <3ccd44ca> > 08:24:57,566 INFO [org.jboss.as.quickstarts.appclient.acc.client.interceptor.ClientInterceptor] (Thread-47) Adding jboss.node.name (tigris) to the invocation context > 08:24:57,614 INFO [org.jboss.as.quickstarts.appclient.acc.client.Main] (Thread-47) Hello from StatelessSessionBean@tigris > 08:24:57,615 INFO [org.jboss.as.quickstarts.appclient.acc.client.interceptor.ClientInterceptor] (Thread-47) Adding jboss.node.name (tigris) to the invocation context > 08:24:57,622 INFO [org.jboss.ejb.client.remoting] (Remoting (anonymous) task-9) EJBCLIENT000016: Channel Channel ID e8f58e71 (outbound) of Remoting connection 28455490 to localhost/127.0.0.1:8080 of endpoint (anonymous) <3ccd44ca> can no longer process messages > 08:24:57,632 ERROR [stderr] (Thread-47) Exception in thread "Thread-47" java.lang.UnsupportedOperationException: COM00100: Method "close" of class "org.jboss.remoting3.UncloseableEndpoint" is not implemented > 08:24:57,632 ERROR [stderr] (Thread-47) at org.wildfly.common.Assert.unsupported(Assert.java:373) > 08:24:57,633 ERROR [stderr] (Thread-47) at org.jboss.remoting3.UncloseableEndpoint.close(UncloseableEndpoint.java:231) > 08:24:57,633 ERROR [stderr] (Thread-47) at org.jboss.as.appclient.service.LazyConnectionContextSelector.close(LazyConnectionContextSelector.java:134) > 08:24:57,633 ERROR [stderr] (Thread-47) at org.jboss.as.appclient.service.ApplicationClientStartService$1.run(ApplicationClientStartService.java:143) > 08:24:57,633 ERROR [stderr] (Thread-47) at java.lang.Thread.run(Thread.java:745) > 08:24:57,640 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-7) WFLYJCA0010: Unbound data source [java:jboss/datasources/ExampleDS] > 08:24:57,642 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-8) WFLYJCA0019: Stopped Driver service with driver-name = h2 > 08:24:57,648 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) WFLYSRV0208: Stopped subdeployment (runtime-name: simpleClient.jar) in 15ms > 08:24:57,649 INFO [org.jboss.as.server.deployment] (MSC service thread 1-6) WFLYSRV0208: Stopped subdeployment (runtime-name: ejb.jar) in 15ms > 08:24:57,651 INFO [org.jboss.as.server.deployment] (MSC service thread 1-6) WFLYSRV0028: Stopped deployment jboss-app-client.ear (runtime-name: jboss-app-client.ear) in 17ms > 08:24:57,653 INFO [org.jboss.as] (MSC service thread 1-8) WFLYSRV0050: JBoss EAP 7.1.0.Alpha1 (WildFly Core 3.0.0.Alpha12-redhat-1) stopped in 20ms > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1998) Custom NameService by sun.net.spi.nameservice.provider.n doesn't work on WildFly

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1998?page=com.atlassian.jira.plugi... ] RH Bugzilla Integration commented on WFCORE-1998: ------------------------------------------------- Petr Jurak <pjurak(a)redhat.com> changed the Status of [bug 1395543|https://bugzilla.redhat.com/show_bug.cgi?id=1395543] from ASSIGNED to POST > Custom NameService by sun.net.spi.nameservice.provider.n doesn't work on WildFly > -------------------------------------------------------------------------------- > > Key: WFCORE-1998 > URL: https://issues.jboss.org/browse/WFCORE-1998 > Project: WildFly Core > Issue Type: Bug > Components: Modules > Affects Versions: 2.2.0.Final > Reporter: Osamu Nagano > Assignee: Osamu Nagano > Labels: downstream_dependency > Fix For: 3.0.0.Alpha13 > > Attachments: nameserviceProviderTest.zip > > > System property {{sun.net.spi.nameservice.provider.<n>}} allows a user to customize a NameService. It works on a standalone java, which is using JBoss Modules, if {{services="import"}} is added on sun.jdk module dependency and the sun.jdk module has the following additional dependencies. > {code} > <path name="sun/net/spi/nameservice"/> > <path name="sun/net/spi/nameservice/dns"/> > {code} > Though it doesn't work as a web application which has the same module path and the same dependency in jboss-deployment-structure.xml. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-2024) Optional JACC dependency to org.wildfly.security.elytron

by Pedro Igor (JIRA)

[ https://issues.jboss.org/browse/WFCORE-2024?page=com.atlassian.jira.plugi... ] Pedro Igor updated WFCORE-2024: ------------------------------- Description: Elytron provides its own JACC implementation. Add optional dependency javax.security.jacc.api to org.wildfly.security.elytron. (was: Add optional dependency javax.security.jacc.api to org.wildfly.security.elytron.) > Optional JACC dependency to org.wildfly.security.elytron > -------------------------------------------------------- > > Key: WFCORE-2024 > URL: https://issues.jboss.org/browse/WFCORE-2024 > Project: WildFly Core > Issue Type: Enhancement > Components: Security > Affects Versions: 3.0.0.Alpha12 > Reporter: Pedro Igor > Assignee: Pedro Igor > > Elytron provides its own JACC implementation. Add optional dependency javax.security.jacc.api to org.wildfly.security.elytron. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-2024) Optional JACC dependency to org.wildfly.security.elytron

by Pedro Igor (JIRA)

[ https://issues.jboss.org/browse/WFCORE-2024?page=com.atlassian.jira.plugi... ] Pedro Igor updated WFCORE-2024: ------------------------------- Description: Add optional dependency javax.security.jacc.api to org.wildfly.security.elytron. > Optional JACC dependency to org.wildfly.security.elytron > -------------------------------------------------------- > > Key: WFCORE-2024 > URL: https://issues.jboss.org/browse/WFCORE-2024 > Project: WildFly Core > Issue Type: Enhancement > Components: Security > Affects Versions: 3.0.0.Alpha12 > Reporter: Pedro Igor > Assignee: Pedro Igor > > Add optional dependency javax.security.jacc.api to org.wildfly.security.elytron. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-2025) CLI SSLContext Priority

by Darran Lofthouse (JIRA)

Darran Lofthouse created WFCORE-2025: ---------------------------------------- Summary: CLI SSLContext Priority Key: WFCORE-2025 URL: https://issues.jboss.org/browse/WFCORE-2025 Project: WildFly Core Issue Type: Task Components: CLI, Security Reporter: Darran Lofthouse Assignee: Darran Lofthouse Priority: Critical Fix For: 3.0.0.Alpha13 We have three different places an SSLContext could come from for the CLI: - # CLI Configuration # AuthenticationClient Configuration # Default interactive SSLContext We need to ensure they are prioritised as above. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-2024) Optional JACC dependency to org.wildfly.security.elytron

by Pedro Igor (JIRA)

Pedro Igor created WFCORE-2024: ---------------------------------- Summary: Optional JACC dependency to org.wildfly.security.elytron Key: WFCORE-2024 URL: https://issues.jboss.org/browse/WFCORE-2024 Project: WildFly Core Issue Type: Enhancement Components: Security Affects Versions: 3.0.0.Alpha12 Reporter: Pedro Igor Assignee: Pedro Igor -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7635) Implement graceful shutdown support for XTS endpoints

by Gytis Trikleris (JIRA)

Gytis Trikleris created WFLY-7635: ------------------------------------- Summary: Implement graceful shutdown support for XTS endpoints Key: WFLY-7635 URL: https://issues.jboss.org/browse/WFLY-7635 Project: WildFly Issue Type: Feature Request Components: XTS Reporter: Gytis Trikleris Assignee: Gytis Trikleris Priority: Critical Fix For: 11.0.0.Alpha1 -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7634) Implement suspend and resume support for transaction recovery service

by Gytis Trikleris (JIRA)

Gytis Trikleris created WFLY-7634: ------------------------------------- Summary: Implement suspend and resume support for transaction recovery service Key: WFLY-7634 URL: https://issues.jboss.org/browse/WFLY-7634 Project: WildFly Issue Type: Feature Request Components: Transactions Reporter: Gytis Trikleris Assignee: Gytis Trikleris Priority: Critical Fix For: 11.0.0.Alpha1 As part of the https://issues.jboss.org/browse/WFLY-4937 feature transaction recovery service needs to support suspend and resume requests. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (REMJMX-129) Update build to allow system property overrides of components.

by Darran Lofthouse (JIRA)

Darran Lofthouse created REMJMX-129: --------------------------------------- Summary: Update build to allow system property overrides of components. Key: REMJMX-129 URL: https://issues.jboss.org/browse/REMJMX-129 Project: Remoting JMX Issue Type: Task Components: Build Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: 3.0.0.Alpha5 -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 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 November 2016