[JBoss JIRA] (WFLY-4288) error when trying to execute commands using jboss-cli.sh
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/WFLY-4288?page=com.atlassian.jira.plugin.... ]
Brian Stansberry reassigned WFLY-4288:
--------------------------------------
Assignee: Alexey Loubyansky (was: Jason Greene)
> error when trying to execute commands using jboss-cli.sh
> --------------------------------------------------------
>
> Key: WFLY-4288
> URL: https://issues.jboss.org/browse/WFLY-4288
> Project: WildFly
> Issue Type: Bug
> Components: CLI
> Affects Versions: JBoss AS7 7.2.0.Final
> Reporter: André Caldeira
> Assignee: Alexey Loubyansky
>
> Hi,
> I've configured jboss to use ssl, and after this change, sometimes, the command cannot be executed:
> [root@<node> ~]# /opt/oss/NSN-SQM-sqm_jboss/install/jboss-eap-6.2/bin/jboss-cli.sh --connect
> org.jboss.as.cli.CliInitializationException: Failed to connect to the controller
> at org.jboss.as.cli.impl.CliLauncher.initCommandContext(CliLauncher.java:284)
> at org.jboss.as.cli.impl.CliLauncher.main(CliLauncher.java:262)
> at org.jboss.as.cli.CommandLineMain.main(CommandLineMain.java:34)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at org.jboss.modules.Module.run(Module.java:292)
> at org.jboss.modules.Main.main(Main.java:455)
> Caused by: org.jboss.as.cli.CommandLineException: The controller is not available at localhost:9990
> at org.jboss.as.cli.impl.CommandContextImpl.tryConnection(CommandContextImpl.java:969)
> at org.jboss.as.cli.impl.CommandContextImpl.connectController(CommandContextImpl.java:808)
> at org.jboss.as.cli.impl.CommandContextImpl.connectController(CommandContextImpl.java:784)
> at org.jboss.as.cli.impl.CliLauncher.initCommandContext(CliLauncher.java:282)
> ... 8 more
> Caused by: java.io.IOException: java.net.ConnectException: JBAS012174: Could not connect to remote://localhost:9990. The connection failed
> at org.jboss.as.controller.client.impl.AbstractModelControllerClient.executeForResult(AbstractModelControllerClient.java:129)
> at org.jboss.as.controller.client.impl.AbstractModelControllerClient.execute(AbstractModelControllerClient.java:71)
> at org.jboss.as.cli.impl.CommandContextImpl.tryConnection(CommandContextImpl.java:947)
> ... 11 more
> Caused by: java.net.ConnectException: JBAS012174: Could not connect to remote://localhost:9990. The connection failed
> at org.jboss.as.protocol.ProtocolConnectionUtils.connectSync(ProtocolConnectionUtils.java:129)
> at org.jboss.as.protocol.ProtocolConnectionManager$EstablishingConnection.connect(ProtocolConnectionManager.java:256)
> at org.jboss.as.protocol.ProtocolConnectionManager.connect(ProtocolConnectionManager.java:70)
> at org.jboss.as.protocol.mgmt.FutureManagementChannel$Establishing.getChannel(FutureManagementChannel.java:204)
> at org.jboss.as.cli.impl.CLIModelControllerClient.getOrCreateChannel(CLIModelControllerClient.java:160)
> at org.jboss.as.cli.impl.CLIModelControllerClient$2.getChannel(CLIModelControllerClient.java:120)
> at org.jboss.as.protocol.mgmt.ManagementChannelHandler.executeRequest(ManagementChannelHandler.java:117)
> at org.jboss.as.protocol.mgmt.ManagementChannelHandler.executeRequest(ManagementChannelHandler.java:92)
> at org.jboss.as.controller.client.impl.AbstractModelControllerClient.executeRequest(AbstractModelControllerClient.java:236)
> at org.jboss.as.controller.client.impl.AbstractModelControllerClient.execute(AbstractModelControllerClient.java:141)
> at org.jboss.as.controller.client.impl.AbstractModelControllerClient.executeForResult(AbstractModelControllerClient.java:127)
> ... 13 more
> Caused by: java.net.ConnectException: Connection refused
> at sun.nio.ch.SocketChannelImpl.checkConnect(Native Method)
> at sun.nio.ch.SocketChannelImpl.finishConnect(SocketChannelImpl.java:739)
> at org.xnio.nio.NioXnioWorker$1.handleEvent(NioXnioWorker.java:322)
> at org.xnio.nio.NioXnioWorker$1.handleEvent(NioXnioWorker.java:318)
> at org.xnio.ChannelListeners.invokeChannelListener(ChannelListeners.java:72)
> at org.xnio.nio.NioHandle.run(NioHandle.java:90)
> at org.xnio.nio.WorkerThread.run(WorkerThread.java:187)
> at ...asynchronous invocation...(Unknown Source)
> at org.jboss.remoting3.EndpointImpl.doConnect(EndpointImpl.java:270)
> at org.jboss.remoting3.EndpointImpl.doConnect(EndpointImpl.java:251)
> at org.jboss.remoting3.EndpointImpl.connect(EndpointImpl.java:349)
> at org.jboss.remoting3.EndpointImpl.connect(EndpointImpl.java:337)
> at org.jboss.as.protocol.ProtocolConnectionUtils.connect(ProtocolConnectionUtils.java:80)
> at org.jboss.as.protocol.ProtocolConnectionUtils.connectSync(ProtocolConnectionUtils.java:99)
> ... 23 more
> In server.log what I can see when it happens is:
> 17:08:30,279 ERROR [org.jboss.remoting.remote.connection] (Remoting "<node>:MANAGEMENT" read-1) JBREM000200: Remote connection failed: java.io.IOException: Broken pipe
> 17:08:42,071 ERROR [org.jboss.remoting.remote.connection] (Remoting "<node>:MANAGEMENT" read-1) JBREM000200: Remote connection failed: java.io.IOException: Broken pipe
> 17:11:47,100 ERROR [org.jboss.remoting.remote.connection] (Remoting "<node>:MANAGEMENT" read-1) JBREM000200: Remote connection failed: java.io.IOException: Broken pipe
> this problem only happens sometimes...
> Thanks in advance,
> Br,
> André
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 8 months
[JBoss JIRA] (WFLY-5633) Cannot load root node after domain start
by Thomas Diesler (JIRA)
Thomas Diesler created WFLY-5633:
------------------------------------
Summary: Cannot load root node after domain start
Key: WFLY-5633
URL: https://issues.jboss.org/browse/WFLY-5633
Project: WildFly
Issue Type: Bug
Components: Test Suite
Reporter: Thomas Diesler
Assignee: Thomas Diesler
{code}
Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 6.008 sec <<< FAILURE! - in org.jboss.as.arquillian.container.domain.managed.test.ManagedDomainTestCase
org.jboss.as.arquillian.container.domain.managed.test.ManagedDomainTestCase Time elapsed: 6.006 sec <<< ERROR!
java.lang.RuntimeException: org.jboss.as.arquillian.container.domain.ManagementClient$UnSuccessfulOperationException: undefined
at org.jboss.as.arquillian.container.domain.ManagementClient.lazyLoadRootNode(ManagementClient.java:390)
at org.jboss.as.arquillian.container.domain.ManagementClient.createDomain(ManagementClient.java:115)
at org.jboss.as.arquillian.container.domain.CommonDomainDeployableContainer.start(CommonDomainDeployableContainer.java:126)
at org.jboss.arquillian.container.impl.ContainerImpl.start(ContainerImpl.java:199)
at org.jboss.arquillian.container.impl.client.container.ContainerLifecycleController$8.perform(ContainerLifecycleController.java:163)
at org.jboss.arquillian.container.impl.client.container.ContainerLifecycleController$8.perform(ContainerLifecycleController.java:157)
at org.jboss.arquillian.container.impl.client.container.ContainerLifecycleController.forContainer(ContainerLifecycleController.java:255)
at org.jboss.arquillian.container.impl.client.container.ContainerLifecycleController.startContainer(ContainerLifecycleController.java:156)
{code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 8 months
[JBoss JIRA] (WFLY-4288) error when trying to execute commands using jboss-cli.sh
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/WFLY-4288?page=com.atlassian.jira.plugin.... ]
Brian Stansberry commented on WFLY-4288:
----------------------------------------
Do you experience this with WildFly 9.0.2 or WildFly 10.0.0.CR4? We can't really investigate issues with a community release as old as AS 7.2.
If you are experiencing this with EAP 6 I recommend that you open a support case through your EAP subscription.
> error when trying to execute commands using jboss-cli.sh
> --------------------------------------------------------
>
> Key: WFLY-4288
> URL: https://issues.jboss.org/browse/WFLY-4288
> Project: WildFly
> Issue Type: Bug
> Affects Versions: JBoss AS7 7.2.0.Final
> Reporter: André Caldeira
> Assignee: Jason Greene
>
> Hi,
> I've configured jboss to use ssl, and after this change, sometimes, the command cannot be executed:
> [root@<node> ~]# /opt/oss/NSN-SQM-sqm_jboss/install/jboss-eap-6.2/bin/jboss-cli.sh --connect
> org.jboss.as.cli.CliInitializationException: Failed to connect to the controller
> at org.jboss.as.cli.impl.CliLauncher.initCommandContext(CliLauncher.java:284)
> at org.jboss.as.cli.impl.CliLauncher.main(CliLauncher.java:262)
> at org.jboss.as.cli.CommandLineMain.main(CommandLineMain.java:34)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at org.jboss.modules.Module.run(Module.java:292)
> at org.jboss.modules.Main.main(Main.java:455)
> Caused by: org.jboss.as.cli.CommandLineException: The controller is not available at localhost:9990
> at org.jboss.as.cli.impl.CommandContextImpl.tryConnection(CommandContextImpl.java:969)
> at org.jboss.as.cli.impl.CommandContextImpl.connectController(CommandContextImpl.java:808)
> at org.jboss.as.cli.impl.CommandContextImpl.connectController(CommandContextImpl.java:784)
> at org.jboss.as.cli.impl.CliLauncher.initCommandContext(CliLauncher.java:282)
> ... 8 more
> Caused by: java.io.IOException: java.net.ConnectException: JBAS012174: Could not connect to remote://localhost:9990. The connection failed
> at org.jboss.as.controller.client.impl.AbstractModelControllerClient.executeForResult(AbstractModelControllerClient.java:129)
> at org.jboss.as.controller.client.impl.AbstractModelControllerClient.execute(AbstractModelControllerClient.java:71)
> at org.jboss.as.cli.impl.CommandContextImpl.tryConnection(CommandContextImpl.java:947)
> ... 11 more
> Caused by: java.net.ConnectException: JBAS012174: Could not connect to remote://localhost:9990. The connection failed
> at org.jboss.as.protocol.ProtocolConnectionUtils.connectSync(ProtocolConnectionUtils.java:129)
> at org.jboss.as.protocol.ProtocolConnectionManager$EstablishingConnection.connect(ProtocolConnectionManager.java:256)
> at org.jboss.as.protocol.ProtocolConnectionManager.connect(ProtocolConnectionManager.java:70)
> at org.jboss.as.protocol.mgmt.FutureManagementChannel$Establishing.getChannel(FutureManagementChannel.java:204)
> at org.jboss.as.cli.impl.CLIModelControllerClient.getOrCreateChannel(CLIModelControllerClient.java:160)
> at org.jboss.as.cli.impl.CLIModelControllerClient$2.getChannel(CLIModelControllerClient.java:120)
> at org.jboss.as.protocol.mgmt.ManagementChannelHandler.executeRequest(ManagementChannelHandler.java:117)
> at org.jboss.as.protocol.mgmt.ManagementChannelHandler.executeRequest(ManagementChannelHandler.java:92)
> at org.jboss.as.controller.client.impl.AbstractModelControllerClient.executeRequest(AbstractModelControllerClient.java:236)
> at org.jboss.as.controller.client.impl.AbstractModelControllerClient.execute(AbstractModelControllerClient.java:141)
> at org.jboss.as.controller.client.impl.AbstractModelControllerClient.executeForResult(AbstractModelControllerClient.java:127)
> ... 13 more
> Caused by: java.net.ConnectException: Connection refused
> at sun.nio.ch.SocketChannelImpl.checkConnect(Native Method)
> at sun.nio.ch.SocketChannelImpl.finishConnect(SocketChannelImpl.java:739)
> at org.xnio.nio.NioXnioWorker$1.handleEvent(NioXnioWorker.java:322)
> at org.xnio.nio.NioXnioWorker$1.handleEvent(NioXnioWorker.java:318)
> at org.xnio.ChannelListeners.invokeChannelListener(ChannelListeners.java:72)
> at org.xnio.nio.NioHandle.run(NioHandle.java:90)
> at org.xnio.nio.WorkerThread.run(WorkerThread.java:187)
> at ...asynchronous invocation...(Unknown Source)
> at org.jboss.remoting3.EndpointImpl.doConnect(EndpointImpl.java:270)
> at org.jboss.remoting3.EndpointImpl.doConnect(EndpointImpl.java:251)
> at org.jboss.remoting3.EndpointImpl.connect(EndpointImpl.java:349)
> at org.jboss.remoting3.EndpointImpl.connect(EndpointImpl.java:337)
> at org.jboss.as.protocol.ProtocolConnectionUtils.connect(ProtocolConnectionUtils.java:80)
> at org.jboss.as.protocol.ProtocolConnectionUtils.connectSync(ProtocolConnectionUtils.java:99)
> ... 23 more
> In server.log what I can see when it happens is:
> 17:08:30,279 ERROR [org.jboss.remoting.remote.connection] (Remoting "<node>:MANAGEMENT" read-1) JBREM000200: Remote connection failed: java.io.IOException: Broken pipe
> 17:08:42,071 ERROR [org.jboss.remoting.remote.connection] (Remoting "<node>:MANAGEMENT" read-1) JBREM000200: Remote connection failed: java.io.IOException: Broken pipe
> 17:11:47,100 ERROR [org.jboss.remoting.remote.connection] (Remoting "<node>:MANAGEMENT" read-1) JBREM000200: Remote connection failed: java.io.IOException: Broken pipe
> this problem only happens sometimes...
> Thanks in advance,
> Br,
> André
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 8 months
[JBoss JIRA] (WFLY-4288) error when trying to execute commands using jboss-cli.sh
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/WFLY-4288?page=com.atlassian.jira.plugin.... ]
Brian Stansberry updated WFLY-4288:
-----------------------------------
Component/s: CLI
> error when trying to execute commands using jboss-cli.sh
> --------------------------------------------------------
>
> Key: WFLY-4288
> URL: https://issues.jboss.org/browse/WFLY-4288
> Project: WildFly
> Issue Type: Bug
> Components: CLI
> Affects Versions: JBoss AS7 7.2.0.Final
> Reporter: André Caldeira
> Assignee: Jason Greene
>
> Hi,
> I've configured jboss to use ssl, and after this change, sometimes, the command cannot be executed:
> [root@<node> ~]# /opt/oss/NSN-SQM-sqm_jboss/install/jboss-eap-6.2/bin/jboss-cli.sh --connect
> org.jboss.as.cli.CliInitializationException: Failed to connect to the controller
> at org.jboss.as.cli.impl.CliLauncher.initCommandContext(CliLauncher.java:284)
> at org.jboss.as.cli.impl.CliLauncher.main(CliLauncher.java:262)
> at org.jboss.as.cli.CommandLineMain.main(CommandLineMain.java:34)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at org.jboss.modules.Module.run(Module.java:292)
> at org.jboss.modules.Main.main(Main.java:455)
> Caused by: org.jboss.as.cli.CommandLineException: The controller is not available at localhost:9990
> at org.jboss.as.cli.impl.CommandContextImpl.tryConnection(CommandContextImpl.java:969)
> at org.jboss.as.cli.impl.CommandContextImpl.connectController(CommandContextImpl.java:808)
> at org.jboss.as.cli.impl.CommandContextImpl.connectController(CommandContextImpl.java:784)
> at org.jboss.as.cli.impl.CliLauncher.initCommandContext(CliLauncher.java:282)
> ... 8 more
> Caused by: java.io.IOException: java.net.ConnectException: JBAS012174: Could not connect to remote://localhost:9990. The connection failed
> at org.jboss.as.controller.client.impl.AbstractModelControllerClient.executeForResult(AbstractModelControllerClient.java:129)
> at org.jboss.as.controller.client.impl.AbstractModelControllerClient.execute(AbstractModelControllerClient.java:71)
> at org.jboss.as.cli.impl.CommandContextImpl.tryConnection(CommandContextImpl.java:947)
> ... 11 more
> Caused by: java.net.ConnectException: JBAS012174: Could not connect to remote://localhost:9990. The connection failed
> at org.jboss.as.protocol.ProtocolConnectionUtils.connectSync(ProtocolConnectionUtils.java:129)
> at org.jboss.as.protocol.ProtocolConnectionManager$EstablishingConnection.connect(ProtocolConnectionManager.java:256)
> at org.jboss.as.protocol.ProtocolConnectionManager.connect(ProtocolConnectionManager.java:70)
> at org.jboss.as.protocol.mgmt.FutureManagementChannel$Establishing.getChannel(FutureManagementChannel.java:204)
> at org.jboss.as.cli.impl.CLIModelControllerClient.getOrCreateChannel(CLIModelControllerClient.java:160)
> at org.jboss.as.cli.impl.CLIModelControllerClient$2.getChannel(CLIModelControllerClient.java:120)
> at org.jboss.as.protocol.mgmt.ManagementChannelHandler.executeRequest(ManagementChannelHandler.java:117)
> at org.jboss.as.protocol.mgmt.ManagementChannelHandler.executeRequest(ManagementChannelHandler.java:92)
> at org.jboss.as.controller.client.impl.AbstractModelControllerClient.executeRequest(AbstractModelControllerClient.java:236)
> at org.jboss.as.controller.client.impl.AbstractModelControllerClient.execute(AbstractModelControllerClient.java:141)
> at org.jboss.as.controller.client.impl.AbstractModelControllerClient.executeForResult(AbstractModelControllerClient.java:127)
> ... 13 more
> Caused by: java.net.ConnectException: Connection refused
> at sun.nio.ch.SocketChannelImpl.checkConnect(Native Method)
> at sun.nio.ch.SocketChannelImpl.finishConnect(SocketChannelImpl.java:739)
> at org.xnio.nio.NioXnioWorker$1.handleEvent(NioXnioWorker.java:322)
> at org.xnio.nio.NioXnioWorker$1.handleEvent(NioXnioWorker.java:318)
> at org.xnio.ChannelListeners.invokeChannelListener(ChannelListeners.java:72)
> at org.xnio.nio.NioHandle.run(NioHandle.java:90)
> at org.xnio.nio.WorkerThread.run(WorkerThread.java:187)
> at ...asynchronous invocation...(Unknown Source)
> at org.jboss.remoting3.EndpointImpl.doConnect(EndpointImpl.java:270)
> at org.jboss.remoting3.EndpointImpl.doConnect(EndpointImpl.java:251)
> at org.jboss.remoting3.EndpointImpl.connect(EndpointImpl.java:349)
> at org.jboss.remoting3.EndpointImpl.connect(EndpointImpl.java:337)
> at org.jboss.as.protocol.ProtocolConnectionUtils.connect(ProtocolConnectionUtils.java:80)
> at org.jboss.as.protocol.ProtocolConnectionUtils.connectSync(ProtocolConnectionUtils.java:99)
> ... 23 more
> In server.log what I can see when it happens is:
> 17:08:30,279 ERROR [org.jboss.remoting.remote.connection] (Remoting "<node>:MANAGEMENT" read-1) JBREM000200: Remote connection failed: java.io.IOException: Broken pipe
> 17:08:42,071 ERROR [org.jboss.remoting.remote.connection] (Remoting "<node>:MANAGEMENT" read-1) JBREM000200: Remote connection failed: java.io.IOException: Broken pipe
> 17:11:47,100 ERROR [org.jboss.remoting.remote.connection] (Remoting "<node>:MANAGEMENT" read-1) JBREM000200: Remote connection failed: java.io.IOException: Broken pipe
> this problem only happens sometimes...
> Thanks in advance,
> Br,
> André
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 8 months
[JBoss JIRA] (WFLY-4304) Servlet authentication kicked off when *not* a part of any security-constraint
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/WFLY-4304?page=com.atlassian.jira.plugin.... ]
Brian Stansberry updated WFLY-4304:
-----------------------------------
Component/s: Web (Undertow)
> Servlet authentication kicked off when *not* a part of any security-constraint
> ------------------------------------------------------------------------------
>
> Key: WFLY-4304
> URL: https://issues.jboss.org/browse/WFLY-4304
> Project: WildFly
> Issue Type: Bug
> Components: Web (Undertow)
> Affects Versions: 8.2.0.Final
> Reporter: Brett Meyer
> Assignee: Darran Lofthouse
> Fix For: 11.0.0.Alpha1
>
>
> Artificer runs on Wildfly 8.2 and uses Keycloak for auth. If our WAR contains a servlet that is *not* protected by a security-constraint in web.xml, Wildfly still attempts to authenticate the call (using Wireshark, I see the GET/POST get funneled through the Keycloak realm redirection) if basic auth credentials are in the header. In a keycloak-dev thread this past Dec., [~bill.burke] suggested this was most likely an issue within Wildfly auth itself.
> A credentialed call on an un-protected servlet does sound like an edge case. However, this came up possibly due to a secondary symptom:
> If I protect the servlet in web.xml, the call's Authorization header is stripped. I'm not currently able to figure out exactly where that's occurring...
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 8 months
[JBoss JIRA] (WFLY-4376) Incorrect callback handler used during authentication (SASL)
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/WFLY-4376?page=com.atlassian.jira.plugin.... ]
Brian Stansberry updated WFLY-4376:
-----------------------------------
Component/s: Clustering
EJB
> Incorrect callback handler used during authentication (SASL)
> -------------------------------------------------------------
>
> Key: WFLY-4376
> URL: https://issues.jboss.org/browse/WFLY-4376
> Project: WildFly
> Issue Type: Bug
> Components: Clustering, EJB
> Reporter: Enrique González Martínez
> Assignee: Enrique González Martínez
>
> Cluster topology messages are not using the proper callbackhandler when the connection is being established.
> {code}
> 06:59:44,609 ERROR [org.jboss.remoting.remote.connection] (Remoting "config-based-ejb-client-endpoint" read-1) JBREM000200: Remote connection failed: javax.security.sasl.SaslException: Authentication failed: all available authentication mechanisms failed
> 06:59:44,611 INFO [org.jboss.ejb.client.remoting.RemotingConnectionClusterNodeManager] (ejb-client-cluster-node-connection-creation-2-thread-2) Could not create a connection for cluster node ClusterNode{clusterName='ejb', nodeName='perf18', clientMappings=[ClientMapping{sourceNetworkAddress=/0:0:0:0:0:0:0:0, sourceNetworkMaskBits=0, destinationAddress='10.16.90.54', destinationPort=4447}], resolvedDestination=[Destination address=10.16.90.54, destination port=4447]} in cluster ejb
> java.lang.RuntimeException: javax.security.sasl.SaslException: Authentication failed: all available authentication mechanisms failed
> at org.jboss.ejb.client.remoting.IoFutureHelper.get(IoFutureHelper.java:91)
> at org.jboss.ejb.client.remoting.RemotingConnectionClusterNodeManager.getEJBReceiver(RemotingConnectionClusterNodeManager.java:89)
> at org.jboss.ejb.client.ClusterContext$EJBReceiverAssociationTask.call(ClusterContext.java:406)
> at org.jboss.ejb.client.ClusterContext$EJBReceiverAssociationTask.call(ClusterContext.java:380)
> at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
> at java.util.concurrent.FutureTask.run(FutureTask.java:138)
> at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
> at java.lang.Thread.run(Thread.java:662)
> Caused by: javax.security.sasl.SaslException: Authentication failed: all available authentication mechanisms failed
> at org.jboss.remoting3.remote.ClientConnectionOpenListener$Capabilities.handleEvent(ClientConnectionOpenListener.java:382)
> at org.jboss.remoting3.remote.ClientConnectionOpenListener$Capabilities.handleEvent(ClientConnectionOpenListener.java:225)
> at org.xnio.ChannelListeners.invokeChannelListener(ChannelListeners.java:72)
> at org.xnio.channels.TranslatingSuspendableChannel.handleReadable(TranslatingSuspendableChannel.java:189)
> at org.xnio.channels.TranslatingSuspendableChannel$1.handleEvent(TranslatingSuspendableChannel.java:103)
> at org.xnio.ChannelListeners.invokeChannelListener(ChannelListeners.java:72)
> at org.xnio.nio.NioHandle.run(NioHandle.java:90)
> at org.xnio.nio.WorkerThread.run(WorkerThread.java:187)
> at ...asynchronous invocation...(Unknown Source)
> at org.jboss.remoting3.EndpointImpl.doConnect(EndpointImpl.java:270)
> at org.jboss.remoting3.EndpointImpl.connect(EndpointImpl.java:386)
> at org.jboss.ejb.client.remoting.NetworkUtil.connect(NetworkUtil.java:151)
> at org.jboss.ejb.client.remoting.NetworkUtil.connect(NetworkUtil.java:132)
> at org.jboss.ejb.client.remoting.RemotingConnectionClusterNodeManager.getEJBReceiver(RemotingConnectionClusterNodeManager.java:87)
> ... 7 more
> {code}
> Before that, this log is produced:
> {code}
> DEBUG: Client authentication failed for mechanism DIGEST-MD5: javax.security.sasl.SaslException: DIGEST-MD5: Cannot perform callback to acquire realm, authentication ID or password [Caused by javax.security.auth.callback.UnsupportedCallbackException]
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 8 months
[JBoss JIRA] (WFLY-4414) Non Standard SESSIONID not clustered
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/WFLY-4414?page=com.atlassian.jira.plugin.... ]
Brian Stansberry updated WFLY-4414:
-----------------------------------
Component/s: Clustering
> Non Standard SESSIONID not clustered
> ------------------------------------
>
> Key: WFLY-4414
> URL: https://issues.jboss.org/browse/WFLY-4414
> Project: WildFly
> Issue Type: Feature Request
> Components: Clustering
> Reporter: Robert Smith
> Assignee: Jason Greene
>
> We are using Wildfly 8.1.0-Final in domain mode with mod-cluster.
> We use a non-standard session id in a web application as follows:
> ...
> <distributable />
> <session-config>
> <cookie-config>
> <name>VSOPSESSIONID</name>
> </cookie-config>
> </session-config>
> ...
> During testing of this we had our sticky set to JSESSIONID which caused requests to be forwarded to our 2 nodes alternatively.
> In our 1st request we do:
> request.getSession().setAttribute(KEY, value)
> In our 2nd request we do:
> request.getSession.getAttribute(KEY)
> The second request always returns null.
> When we remove the custom session id, the session data is avaliable.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 8 months
[JBoss JIRA] (WFLY-4414) Non Standard SESSIONID not clustered
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/WFLY-4414?page=com.atlassian.jira.plugin.... ]
Brian Stansberry reassigned WFLY-4414:
--------------------------------------
Assignee: Paul Ferraro (was: Jason Greene)
> Non Standard SESSIONID not clustered
> ------------------------------------
>
> Key: WFLY-4414
> URL: https://issues.jboss.org/browse/WFLY-4414
> Project: WildFly
> Issue Type: Feature Request
> Components: Clustering
> Reporter: Robert Smith
> Assignee: Paul Ferraro
>
> We are using Wildfly 8.1.0-Final in domain mode with mod-cluster.
> We use a non-standard session id in a web application as follows:
> ...
> <distributable />
> <session-config>
> <cookie-config>
> <name>VSOPSESSIONID</name>
> </cookie-config>
> </session-config>
> ...
> During testing of this we had our sticky set to JSESSIONID which caused requests to be forwarded to our 2 nodes alternatively.
> In our 1st request we do:
> request.getSession().setAttribute(KEY, value)
> In our 2nd request we do:
> request.getSession.getAttribute(KEY)
> The second request always returns null.
> When we remove the custom session id, the session data is avaliable.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 8 months
[JBoss JIRA] (WFLY-4555) Faces converter is not properly assigned if it is a CDI @Named bean
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/WFLY-4555?page=com.atlassian.jira.plugin.... ]
Brian Stansberry reassigned WFLY-4555:
--------------------------------------
Assignee: Farah Juma (was: Jason Greene)
> Faces converter is not properly assigned if it is a CDI @Named bean
> -------------------------------------------------------------------
>
> Key: WFLY-4555
> URL: https://issues.jboss.org/browse/WFLY-4555
> Project: WildFly
> Issue Type: Bug
> Components: JSF
> Affects Versions: 8.2.0.Final
> Environment: Tested on openjdk version "1.8.0_45"
> OpenJDK Runtime Environment (build 1.8.0_45-b13)
> OpenJDK 64-Bit Server VM (build 25.45-b02, mixed mode)
> Reporter: Michał Piotrowski
> Assignee: Farah Juma
> Attachments: ConverterTest.zip
>
>
> If I try to use converter declaring it with attribute converter (e.g. on selectOneMenu) and use expression which points to a @Named CDI bean it isn't properly registered.
> I will try to attach simple maven test case project.
> The same converter class can be used if it is @Inject (-ed) to a CDI managed bean and provided through some getter method to a converter attribute.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 8 months
[JBoss JIRA] (WFLY-4555) Faces converter is not properly assigned if it is a CDI @Named bean
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/WFLY-4555?page=com.atlassian.jira.plugin.... ]
Brian Stansberry updated WFLY-4555:
-----------------------------------
Component/s: JSF
> Faces converter is not properly assigned if it is a CDI @Named bean
> -------------------------------------------------------------------
>
> Key: WFLY-4555
> URL: https://issues.jboss.org/browse/WFLY-4555
> Project: WildFly
> Issue Type: Bug
> Components: JSF
> Affects Versions: 8.2.0.Final
> Environment: Tested on openjdk version "1.8.0_45"
> OpenJDK Runtime Environment (build 1.8.0_45-b13)
> OpenJDK 64-Bit Server VM (build 25.45-b02, mixed mode)
> Reporter: Michał Piotrowski
> Assignee: Jason Greene
> Attachments: ConverterTest.zip
>
>
> If I try to use converter declaring it with attribute converter (e.g. on selectOneMenu) and use expression which points to a @Named CDI bean it isn't properly registered.
> I will try to attach simple maven test case project.
> The same converter class can be used if it is @Inject (-ed) to a CDI managed bean and provided through some getter method to a converter attribute.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 8 months