[JBoss JIRA] (WFLY-8314) EAP 7.1.0.DR13 starts with errors and missing services in standalone-xts profile
by Ondra Chaloupka (JIRA)
Ondra Chaloupka created WFLY-8314:
-------------------------------------
Summary: EAP 7.1.0.DR13 starts with errors and missing services in standalone-xts profile
Key: WFLY-8314
URL: https://issues.jboss.org/browse/WFLY-8314
Project: WildFly
Issue Type: Bug
Components: XTS
Reporter: Ondra Chaloupka
Assignee: Gytis Trikleris
Priority: Critical
When starting EAP 7.1.0.DR13 with {{./jboss-eap-7.1/bin/standalone.sh --server-config=../../docs/examples/configs/standalone-xts.xml}}, the following errors are logged:
{code}09:27:48,895 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("add") failed - address: ([
("subsystem" => "undertow"),
("server" => "default-server"),
("host" => "default-host"),
("setting" => "http-invoker")
]) - failure description: {
"WFLYCTL0412: Required services that are not installed:" => ["org.wildfly.security.http-authentication-factory.application-http-authentication"],
"WFLYCTL0180: Services with missing/unavailable dependencies" => ["jboss.undertow.server.default-server.default-host.http-invoker is missing [org.wildfly.security.http-authentication-factory.application-http-authentication]"]
}
09:27:48,912 INFO [org.jboss.as.controller] (Controller Boot Thread) WFLYCTL0183: Service status report
WFLYCTL0184: New missing/unsatisfied dependencies:
service org.wildfly.security.http-authentication-factory.application-http-authentication (missing) dependents: [service jboss.undertow.server.default-server.default-host.http-invoker]
09:27:49,003 INFO [org.jboss.as.server] (ServerService Thread Pool -- 65) WFLYSRV0212: Resuming server
09:27:49,005 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0060: Http management interface listening on http://127.0.0.1:9990/management
09:27:49,005 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0051: Admin console listening on http://127.0.0.1:9990
09:27:49,005 ERROR [org.jboss.as] (Controller Boot Thread) WFLYSRV0026: JBoss EAP 7.1.0.Alpha1 (WildFly Core 3.0.0.Beta6-redhat-1) started (with errors) in 3975ms - Started 435 of 677 services (1 services failed or missing dependencies, 440 services are lazy, passive or on-demand)
{code}
This seems to be the result of adding a {{http-invoker}} into Undertow subsystem that references and Elytron {{http-authentication-factory}}. This configuration file does not have Elytron subsystem added.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 2 months
[JBoss JIRA] (WFLY-8314) WFLY starts with errors and missing services in standalone-xts and standalone-rts profile
by Ondra Chaloupka (JIRA)
[ https://issues.jboss.org/browse/WFLY-8314?page=com.atlassian.jira.plugin.... ]
Ondra Chaloupka updated WFLY-8314:
----------------------------------
Summary: WFLY starts with errors and missing services in standalone-xts and standalone-rts profile (was: EAP 7.1.0.DR13 starts with errors and missing services in standalone-xts profile)
> WFLY starts with errors and missing services in standalone-xts and standalone-rts profile
> -----------------------------------------------------------------------------------------
>
> Key: WFLY-8314
> URL: https://issues.jboss.org/browse/WFLY-8314
> Project: WildFly
> Issue Type: Bug
> Components: XTS
> Reporter: Ondra Chaloupka
> Assignee: Gytis Trikleris
> Priority: Critical
>
> When starting EAP 7.1.0.DR13 with {{./jboss-eap-7.1/bin/standalone.sh --server-config=../../docs/examples/configs/standalone-xts.xml}}, the following errors are logged:
> {code}09:27:48,895 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("add") failed - address: ([
> ("subsystem" => "undertow"),
> ("server" => "default-server"),
> ("host" => "default-host"),
> ("setting" => "http-invoker")
> ]) - failure description: {
> "WFLYCTL0412: Required services that are not installed:" => ["org.wildfly.security.http-authentication-factory.application-http-authentication"],
> "WFLYCTL0180: Services with missing/unavailable dependencies" => ["jboss.undertow.server.default-server.default-host.http-invoker is missing [org.wildfly.security.http-authentication-factory.application-http-authentication]"]
> }
> 09:27:48,912 INFO [org.jboss.as.controller] (Controller Boot Thread) WFLYCTL0183: Service status report
> WFLYCTL0184: New missing/unsatisfied dependencies:
> service org.wildfly.security.http-authentication-factory.application-http-authentication (missing) dependents: [service jboss.undertow.server.default-server.default-host.http-invoker]
> 09:27:49,003 INFO [org.jboss.as.server] (ServerService Thread Pool -- 65) WFLYSRV0212: Resuming server
> 09:27:49,005 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0060: Http management interface listening on http://127.0.0.1:9990/management
> 09:27:49,005 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0051: Admin console listening on http://127.0.0.1:9990
> 09:27:49,005 ERROR [org.jboss.as] (Controller Boot Thread) WFLYSRV0026: JBoss EAP 7.1.0.Alpha1 (WildFly Core 3.0.0.Beta6-redhat-1) started (with errors) in 3975ms - Started 435 of 677 services (1 services failed or missing dependencies, 440 services are lazy, passive or on-demand)
> {code}
> This seems to be the result of adding a {{http-invoker}} into Undertow subsystem that references and Elytron {{http-authentication-factory}}. This configuration file does not have Elytron subsystem added.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 2 months
[JBoss JIRA] (WFLY-8314) WFLY starts with errors and missing services in standalone-xts and standalone-rts profile
by Ondra Chaloupka (JIRA)
[ https://issues.jboss.org/browse/WFLY-8314?page=com.atlassian.jira.plugin.... ]
Ondra Chaloupka reassigned WFLY-8314:
-------------------------------------
Assignee: Ondra Chaloupka (was: Gytis Trikleris)
> WFLY starts with errors and missing services in standalone-xts and standalone-rts profile
> -----------------------------------------------------------------------------------------
>
> Key: WFLY-8314
> URL: https://issues.jboss.org/browse/WFLY-8314
> Project: WildFly
> Issue Type: Bug
> Components: XTS
> Reporter: Ondra Chaloupka
> Assignee: Ondra Chaloupka
> Priority: Critical
>
> When starting EAP 7.1.0.DR13 with {{./jboss-eap-7.1/bin/standalone.sh --server-config=../../docs/examples/configs/standalone-xts.xml}}, the following errors are logged:
> {code}09:27:48,895 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("add") failed - address: ([
> ("subsystem" => "undertow"),
> ("server" => "default-server"),
> ("host" => "default-host"),
> ("setting" => "http-invoker")
> ]) - failure description: {
> "WFLYCTL0412: Required services that are not installed:" => ["org.wildfly.security.http-authentication-factory.application-http-authentication"],
> "WFLYCTL0180: Services with missing/unavailable dependencies" => ["jboss.undertow.server.default-server.default-host.http-invoker is missing [org.wildfly.security.http-authentication-factory.application-http-authentication]"]
> }
> 09:27:48,912 INFO [org.jboss.as.controller] (Controller Boot Thread) WFLYCTL0183: Service status report
> WFLYCTL0184: New missing/unsatisfied dependencies:
> service org.wildfly.security.http-authentication-factory.application-http-authentication (missing) dependents: [service jboss.undertow.server.default-server.default-host.http-invoker]
> 09:27:49,003 INFO [org.jboss.as.server] (ServerService Thread Pool -- 65) WFLYSRV0212: Resuming server
> 09:27:49,005 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0060: Http management interface listening on http://127.0.0.1:9990/management
> 09:27:49,005 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0051: Admin console listening on http://127.0.0.1:9990
> 09:27:49,005 ERROR [org.jboss.as] (Controller Boot Thread) WFLYSRV0026: JBoss EAP 7.1.0.Alpha1 (WildFly Core 3.0.0.Beta6-redhat-1) started (with errors) in 3975ms - Started 435 of 677 services (1 services failed or missing dependencies, 440 services are lazy, passive or on-demand)
> {code}
> This seems to be the result of adding a {{http-invoker}} into Undertow subsystem that references and Elytron {{http-authentication-factory}}. This configuration file does not have Elytron subsystem added.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 2 months
[JBoss JIRA] (WFCORE-2363) Improve capability registration API
by Tomaz Cerar (JIRA)
Tomaz Cerar created WFCORE-2363:
-----------------------------------
Summary: Improve capability registration API
Key: WFCORE-2363
URL: https://issues.jboss.org/browse/WFCORE-2363
Project: WildFly Core
Issue Type: Enhancement
Components: Domain Management
Reporter: Tomaz Cerar
Assignee: Tomaz Cerar
we should be able to do things like
{code:java}
context.getServiceTarget().addCapability(IO_WORKER_RUNTIME_CAPABILITY, workerService)
.setInitialMode(ServiceController.Mode.ON_DEMAND)
.install();
{code}
instead of longer version with figuring out service name etc.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 2 months
[JBoss JIRA] (WFLY-7371) JAXRS endpoint - CDI injection to constructor doesn't work
by Ron Sigal (JIRA)
[ https://issues.jboss.org/browse/WFLY-7371?page=com.atlassian.jira.plugin.... ]
Ron Sigal commented on WFLY-7371:
---------------------------------
RESTEASY-1538 is closed.
> JAXRS endpoint - CDI injection to constructor doesn't work
> ----------------------------------------------------------
>
> Key: WFLY-7371
> URL: https://issues.jboss.org/browse/WFLY-7371
> Project: WildFly
> Issue Type: Bug
> Components: CDI / Weld, REST
> Affects Versions: 10.1.0.Final
> Reporter: Tomas Remes
> Assignee: Ron Sigal
>
> Deploying app with following JAXRS endpoint
> {code}
> @Path("/test")
> public class MyTimeResource {
> private final LocalDateTime dateTime;
> @Inject
> public MyTimeResource(LocalDateTime dateTime){
> this.dateTime = dateTime;
> };
> }
> {code}
> is failing with following stack trace:
> {noformat}
> Caused by: java.lang.RuntimeException: RESTEASY003190: Could not find constructor for class: org.example.microprofile.MyTimeResource
> at org.jboss.resteasy.spi.metadata.ResourceBuilder.constructor(ResourceBuilder.java:692)
> at org.jboss.resteasy.plugins.server.resourcefactory.POJOResourceFactory.registered(POJOResourceFactory.java:42)
> at org.jboss.resteasy.core.ResourceMethodRegistry.addResourceFactory(ResourceMethodRegistry.java:208)
> at org.jboss.resteasy.core.ResourceMethodRegistry.addResourceFactory(ResourceMethodRegistry.java:194)
> at org.jboss.resteasy.core.ResourceMethodRegistry.addResourceFactory(ResourceMethodRegistry.java:180)
> at org.jboss.resteasy.core.ResourceMethodRegistry.addResourceFactory(ResourceMethodRegistry.java:157)
> at org.jboss.resteasy.core.ResourceMethodRegistry.addPerRequestResource(ResourceMethodRegistry.java:76)
> at org.jboss.resteasy.spi.ResteasyDeployment.registration(ResteasyDeployment.java:409)
> at org.jboss.resteasy.spi.ResteasyDeployment.start(ResteasyDeployment.java:250)
> at org.jboss.resteasy.plugins.server.servlet.ServletContainerDispatcher.init(ServletContainerDispatcher.java:113)
> at org.jboss.resteasy.plugins.server.servlet.HttpServletDispatcher.init(HttpServletDispatcher.java:36)
> at io.undertow.servlet.core.LifecyleInterceptorInvocation.proceed(LifecyleInterceptorInvocation.java:117)
> at org.wildfly.extension.undertow.security.RunAsLifecycleInterceptor.init(RunAsLifecycleInterceptor.java:78)
> at io.undertow.servlet.core.LifecyleInterceptorInvocation.proceed(LifecyleInterceptorInvocation.java:103)
> at io.undertow.servlet.core.ManagedServlet$DefaultInstanceStrategy.start(ManagedServlet.java:250)
> at io.undertow.servlet.core.ManagedServlet.createServlet(ManagedServlet.java:133)
> at io.undertow.servlet.core.DeploymentManagerImpl$2.call(DeploymentManagerImpl.java:546)
> at io.undertow.servlet.core.DeploymentManagerImpl$2.call(DeploymentManagerImpl.java:517)
> at io.undertow.servlet.core.ServletRequestContextThreadSetupAction$1.call(ServletRequestContextThreadSetupAction.java:42)
> at io.undertow.servlet.core.ContextClassLoaderSetupAction$1.call(ContextClassLoaderSetupAction.java:43)
> at io.undertow.servlet.api.LegacyThreadSetupActionWrapper$1.call(LegacyThreadSetupActionWrapper.java:44)
> at io.undertow.servlet.api.LegacyThreadSetupActionWrapper$1.call(LegacyThreadSetupActionWrapper.java:44)
> at io.undertow.servlet.api.LegacyThreadSetupActionWrapper$1.call(LegacyThreadSetupActionWrapper.java:44)
> at io.undertow.servlet.api.LegacyThreadSetupActionWrapper$1.call(LegacyThreadSetupActionWrapper.java:44)
> at io.undertow.servlet.api.LegacyThreadSetupActionWrapper$1.call(LegacyThreadSetupActionWrapper.java:44)
> at io.undertow.servlet.core.DeploymentManagerImpl.start(DeploymentManagerImpl.java:559)
> at org.wildfly.extension.undertow.deployment.UndertowDeploymentService.startContext(UndertowDeploymentService.java:101)
> at org.wildfly.extension.undertow.deployment.UndertowDeploymentService$1.run(UndertowDeploymentService.java:82)
> ... 6 more
> {noformat}
> Note that app contains beans.xml so the JAXRS resource should be really managed by CDI.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 2 months
[JBoss JIRA] (ELY-977) PLAIN mechanism does not work with WildFlyElytronProvider for AuthenticationConfiguration
by Jan Kalina (JIRA)
[ https://issues.jboss.org/browse/ELY-977?page=com.atlassian.jira.plugin.sy... ]
Jan Kalina closed ELY-977.
--------------------------
Resolution: Duplicate Issue
> PLAIN mechanism does not work with WildFlyElytronProvider for AuthenticationConfiguration
> -----------------------------------------------------------------------------------------
>
> Key: ELY-977
> URL: https://issues.jboss.org/browse/ELY-977
> Project: WildFly Elytron
> Issue Type: Bug
> Affects Versions: 1.1.0.Beta25
> Reporter: Ondrej Lukas
> Assignee: Jan Kalina
> Priority: Blocker
>
> In case when WildFlyElytronProvider is set as provider for AuthenticationConfiguration then SASL PLAIN mechanism is stopped to work (see exception below). In case when WildFlyElytronProvider is removed then PLAIN mechanism works. It seems that Elytron does not implement SASL PLAIN mechanism correctly.
> Thrown Exception:
> {code}
> java.io.IOException: java.net.ConnectException: WFLYPRT0053: Could not connect to remote+http://127.0.0.1:9990. The connection failed
> at org.jboss.as.controller.client.impl.AbstractModelControllerClient.executeForResult(AbstractModelControllerClient.java:149)
> at org.jboss.as.controller.client.impl.AbstractModelControllerClient.execute(AbstractModelControllerClient.java:75)
> at org.wildfly.security.elytron.SimpleClient$1.run(SimpleClient.java:67)
> at org.wildfly.common.context.Contextual.run(Contextual.java:71)
> at org.wildfly.security.elytron.SimpleClient.main(SimpleClient.java:48)
> 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:497)
> at org.codehaus.mojo.exec.ExecJavaMojo$1.run(ExecJavaMojo.java:297)
> at java.lang.Thread.run(Thread.java:745)
> Caused by: java.net.ConnectException: WFLYPRT0053: Could not connect to remote+http://127.0.0.1:9990. The connection failed
> at org.jboss.as.protocol.ProtocolConnectionUtils.connectSync(ProtocolConnectionUtils.java:119)
> at org.jboss.as.protocol.ProtocolConnectionManager$EstablishingConnection.connect(ProtocolConnectionManager.java:259)
> at org.jboss.as.protocol.ProtocolConnectionManager.connect(ProtocolConnectionManager.java:70)
> at org.jboss.as.protocol.mgmt.ManagementClientChannelStrategy$Establishing.getChannel(ManagementClientChannelStrategy.java:162)
> at org.jboss.as.controller.client.impl.RemotingModelControllerClient.getOrCreateChannel(RemotingModelControllerClient.java:135)
> at org.jboss.as.controller.client.impl.RemotingModelControllerClient$1.getChannel(RemotingModelControllerClient.java:59)
> at org.jboss.as.protocol.mgmt.ManagementChannelHandler.executeRequest(ManagementChannelHandler.java:135)
> at org.jboss.as.protocol.mgmt.ManagementChannelHandler.executeRequest(ManagementChannelHandler.java:110)
> at org.jboss.as.controller.client.impl.AbstractModelControllerClient.executeRequest(AbstractModelControllerClient.java:263)
> at org.jboss.as.controller.client.impl.AbstractModelControllerClient.execute(AbstractModelControllerClient.java:168)
> at org.jboss.as.controller.client.impl.AbstractModelControllerClient.executeForResult(AbstractModelControllerClient.java:147)
> ... 10 more
> Caused by: java.io.IOException: JBREM000202: Abrupt close on Remoting connection 6900a112 to /127.0.0.1:9990 of endpoint "management-client" <7c9695fa>
> at org.jboss.remoting3.remote.ClientConnectionOpenListener$Authentication.handleEvent(ClientConnectionOpenListener.java:578)
> at org.jboss.remoting3.remote.ClientConnectionOpenListener$Authentication.handleEvent(ClientConnectionOpenListener.java:546)
> at org.xnio.ChannelListeners.invokeChannelListener(ChannelListeners.java:92)
> at org.xnio.conduits.ReadReadyHandler$ChannelListenerHandler.readReady(ReadReadyHandler.java:66)
> at org.xnio.nio.NioSocketConduit.handleReady(NioSocketConduit.java:89)
> at org.xnio.nio.WorkerThread.run(WorkerThread.java:567)
> at ...asynchronous invocation...(Unknown Source)
> at org.jboss.remoting3.EndpointImpl.connect(EndpointImpl.java:464)
> at org.jboss.remoting3.EndpointImpl.connect(EndpointImpl.java:426)
> at org.jboss.remoting3.EndpointImpl.connect(EndpointImpl.java:414)
> at org.jboss.as.protocol.ProtocolConnectionUtils.connect(ProtocolConnectionUtils.java:164)
> at org.jboss.as.protocol.ProtocolConnectionUtils.connectSync(ProtocolConnectionUtils.java:111)
> ... 20 more
> {code}
> We request blocker flag because this issue blocks RFE EAP7-530. PLAIN is widely used SASL mechanism.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 2 months
[JBoss JIRA] (ELY-977) PLAIN mechanism does not work with WildFlyElytronProvider for AuthenticationConfiguration
by Jan Kalina (JIRA)
[ https://issues.jboss.org/browse/ELY-977?page=com.atlassian.jira.plugin.sy... ]
Jan Kalina reassigned ELY-977:
------------------------------
Assignee: Jan Kalina (was: Darran Lofthouse)
> PLAIN mechanism does not work with WildFlyElytronProvider for AuthenticationConfiguration
> -----------------------------------------------------------------------------------------
>
> Key: ELY-977
> URL: https://issues.jboss.org/browse/ELY-977
> Project: WildFly Elytron
> Issue Type: Bug
> Affects Versions: 1.1.0.Beta25
> Reporter: Ondrej Lukas
> Assignee: Jan Kalina
> Priority: Blocker
>
> In case when WildFlyElytronProvider is set as provider for AuthenticationConfiguration then SASL PLAIN mechanism is stopped to work (see exception below). In case when WildFlyElytronProvider is removed then PLAIN mechanism works. It seems that Elytron does not implement SASL PLAIN mechanism correctly.
> Thrown Exception:
> {code}
> java.io.IOException: java.net.ConnectException: WFLYPRT0053: Could not connect to remote+http://127.0.0.1:9990. The connection failed
> at org.jboss.as.controller.client.impl.AbstractModelControllerClient.executeForResult(AbstractModelControllerClient.java:149)
> at org.jboss.as.controller.client.impl.AbstractModelControllerClient.execute(AbstractModelControllerClient.java:75)
> at org.wildfly.security.elytron.SimpleClient$1.run(SimpleClient.java:67)
> at org.wildfly.common.context.Contextual.run(Contextual.java:71)
> at org.wildfly.security.elytron.SimpleClient.main(SimpleClient.java:48)
> 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:497)
> at org.codehaus.mojo.exec.ExecJavaMojo$1.run(ExecJavaMojo.java:297)
> at java.lang.Thread.run(Thread.java:745)
> Caused by: java.net.ConnectException: WFLYPRT0053: Could not connect to remote+http://127.0.0.1:9990. The connection failed
> at org.jboss.as.protocol.ProtocolConnectionUtils.connectSync(ProtocolConnectionUtils.java:119)
> at org.jboss.as.protocol.ProtocolConnectionManager$EstablishingConnection.connect(ProtocolConnectionManager.java:259)
> at org.jboss.as.protocol.ProtocolConnectionManager.connect(ProtocolConnectionManager.java:70)
> at org.jboss.as.protocol.mgmt.ManagementClientChannelStrategy$Establishing.getChannel(ManagementClientChannelStrategy.java:162)
> at org.jboss.as.controller.client.impl.RemotingModelControllerClient.getOrCreateChannel(RemotingModelControllerClient.java:135)
> at org.jboss.as.controller.client.impl.RemotingModelControllerClient$1.getChannel(RemotingModelControllerClient.java:59)
> at org.jboss.as.protocol.mgmt.ManagementChannelHandler.executeRequest(ManagementChannelHandler.java:135)
> at org.jboss.as.protocol.mgmt.ManagementChannelHandler.executeRequest(ManagementChannelHandler.java:110)
> at org.jboss.as.controller.client.impl.AbstractModelControllerClient.executeRequest(AbstractModelControllerClient.java:263)
> at org.jboss.as.controller.client.impl.AbstractModelControllerClient.execute(AbstractModelControllerClient.java:168)
> at org.jboss.as.controller.client.impl.AbstractModelControllerClient.executeForResult(AbstractModelControllerClient.java:147)
> ... 10 more
> Caused by: java.io.IOException: JBREM000202: Abrupt close on Remoting connection 6900a112 to /127.0.0.1:9990 of endpoint "management-client" <7c9695fa>
> at org.jboss.remoting3.remote.ClientConnectionOpenListener$Authentication.handleEvent(ClientConnectionOpenListener.java:578)
> at org.jboss.remoting3.remote.ClientConnectionOpenListener$Authentication.handleEvent(ClientConnectionOpenListener.java:546)
> at org.xnio.ChannelListeners.invokeChannelListener(ChannelListeners.java:92)
> at org.xnio.conduits.ReadReadyHandler$ChannelListenerHandler.readReady(ReadReadyHandler.java:66)
> at org.xnio.nio.NioSocketConduit.handleReady(NioSocketConduit.java:89)
> at org.xnio.nio.WorkerThread.run(WorkerThread.java:567)
> at ...asynchronous invocation...(Unknown Source)
> at org.jboss.remoting3.EndpointImpl.connect(EndpointImpl.java:464)
> at org.jboss.remoting3.EndpointImpl.connect(EndpointImpl.java:426)
> at org.jboss.remoting3.EndpointImpl.connect(EndpointImpl.java:414)
> at org.jboss.as.protocol.ProtocolConnectionUtils.connect(ProtocolConnectionUtils.java:164)
> at org.jboss.as.protocol.ProtocolConnectionUtils.connectSync(ProtocolConnectionUtils.java:111)
> ... 20 more
> {code}
> We request blocker flag because this issue blocks RFE EAP7-530. PLAIN is widely used SASL mechanism.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 2 months