[ https://issues.redhat.com/browse/WFLY-14284?page=com.atlassian.jira.plugi... ] Adriano Teixeira de Souza edited comment on WFLY-14284 at 1/22/21 12:47 PM: ---------------------------------------------------------------------------- Hi [~ochaloup] I can't find any documentation that show how to use remote+http instead of http-remoting and how is correct way to replace this commands   {code:java} /profile=$PROFILE_NAME/subsystem=remoting/remote-outbound-connection=remote-workflow-connection:add(outbound-socket-binding-ref=remote-workflow, protocol=http-remoting, security-realm=remote-ejb-security-realm, username=ejbserver) /profile=$PROFILE_NAME/subsystem=remoting/remote-outbound-connection=remote-workflow-connection/property=SASL_POLICY_NOANONYMOUS:add(value=false) /profile=$PROFILE_NAME/subsystem=remoting/remote-outbound-connection=remote-workflow-connection/property=SSL_ENABLED:add(value=false) {code}   And how to use {{-Dwildfly.config.url}} with {{wildfly-config.xml on a domain mode with multiples instances on different port with offset}} Can you put here some links to get the right way to use both?   I tried it and received this exception {code:java} 12:12:57,714 ERROR [org.jboss.msc.service.fail] (ServerService Thread Pool -- 2) MSC000001: Failed to start service jboss.server-boot-operations: org.jboss.msc.service$ at org.jboss.as.server@10.0.3.Final//org.jboss.as.server.mgmt.domain.ServerBootOperationsService$1.run(ServerBootOperationsService.java:72) at org.jboss.threads@2.3.3.Final//org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35) at org.jboss.threads@2.3.3.Final//org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1982) at org.jboss.threads@2.3.3.Final//org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1486) at org.jboss.threads@2.3.3.Final//org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1348) at java.base/java.lang.Thread.run(Thread.java:834) at org.jboss.threads@2.3.3.Final//org.jboss.threads.JBossThread.run(JBossThread.java:485) Caused by: java.net.ConnectException: WFLYPRT0053: Could not connect to remote+http://172.16.1.149:9990. The connection failed at org.jboss.as.protocol@10.0.3.Final//org.jboss.as.protocol.ProtocolConnectionUtils.connectSync(ProtocolConnectionUtils.java:128) at org.jboss.as.protocol@10.0.3.Final//org.jboss.as.protocol.ProtocolConnectionManager$EstablishingConnection.connect(ProtocolConnectionManager.java:259) at org.jboss.as.protocol@10.0.3.Final//org.jboss.as.protocol.ProtocolConnectionManager.connect(ProtocolConnectionManager.java:70) at org.jboss.as.server@10.0.3.Final//org.jboss.as.server.mgmt.domain.HostControllerConnection.openConnection(HostControllerConnection.java:128) at org.jboss.as.server@10.0.3.Final//org.jboss.as.server.mgmt.domain.HostControllerClient.resolveBootUpdates(HostControllerClient.java:112) at org.jboss.as.server@10.0.3.Final//org.jboss.as.server.mgmt.domain.ServerBootOperationsService$1.run(ServerBootOperationsService.java:68) ... 6 more Caused by: javax.security.sasl.SaslException: Authentication failed: all available authentication mechanisms failed: DIGEST-MD5: javax.security.sasl.SaslException: DIGEST-MD5: Server rejected authentication at org.jboss.remoting@5.0.15.Final//org.jboss.remoting3.remote.ClientConnectionOpenListener.allMechanismsFailed(ClientConnectionOpenListener.java:109) at org.jboss.remoting@5.0.15.Final//org.jboss.remoting3.remote.ClientConnectionOpenListener$Capabilities.handleEvent(ClientConnectionOpenListener.java:446) at org.jboss.remoting@5.0.15.Final//org.jboss.remoting3.remote.ClientConnectionOpenListener$Capabilities.handleEvent(ClientConnectionOpenListener.java:242) at org.jboss.xnio@3.7.3.Final//org.xnio.ChannelListeners.invokeChannelListener(ChannelListeners.java:92) at org.jboss.xnio@3.7.3.Final//org.xnio.conduits.ReadReadyHandler$ChannelListenerHandler.readReady(ReadReadyHandler.java:66) at org.jboss.xnio.nio@3.7.3.Final//org.xnio.nio.NioSocketConduit.handleReady(NioSocketConduit.java:89) at org.jboss.xnio.nio@3.7.3.Final//org.xnio.nio.WorkerThread.run(WorkerThread.java:591) {code}   I used this content file and pass {{-Dwildfly.config.url on JBOSS_OPTS /etc/default/wildfly.conf}} {{ }} {{-Dwildfly.config.url=/app/wildfly/domain/configuration/wildfly-config.xml}} {code:java} <?xml version="1.0" encoding="UTF-8"?> <configuration> <authentication-client xmlns="urn:elytron:1.0"> <authentication-rules> <rule use-configuration="default" /> </authentication-rules> <authentication-configurations> <configuration name="default"> <set-user-name name="ejbserver" /> <credentials> <clear-password password="ejb" /> </credentials> </configuration> </authentication-configurations> </authentication-client> </configuration> {code}   was (Author: JIRAUSER147207): Hi [~ochaloup] I can't find any documentation that show how to use remote+http instead of http-remoting and how is correct way to replace this commands   {code:java} /profile=$PROFILE_NAME/subsystem=remoting/remote-outbound-connection=remote-workflow-connection:add(outbound-socket-binding-ref=remote-workflow, protocol=http-remoting, security-realm=remote-ejb-security-realm, username=ejbserver) /profile=$PROFILE_NAME/subsystem=remoting/remote-outbound-connection=remote-workflow-connection/property=SASL_POLICY_NOANONYMOUS:add(value=false) /profile=$PROFILE_NAME/subsystem=remoting/remote-outbound-connection=remote-workflow-connection/property=SSL_ENABLED:add(value=false) {code}   And how to use {{-Dwildfly.config.url}} with {{wildfly-config.xml on a domain mode with multiples instances on different port with offset}} Can you put here some links to get the right way to use both?   I tried it and received this exception {code:java} 12:12:57,714 ERROR [org.jboss.msc.service.fail] (ServerService Thread Pool -- 2) MSC000001: Failed to start service jboss.server-boot-operations: org.jboss.msc.service$ at org.jboss.as.server@10.0.3.Final//org.jboss.as.server.mgmt.domain.ServerBootOperationsService$1.run(ServerBootOperationsService.java:72) at org.jboss.threads@2.3.3.Final//org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35) at org.jboss.threads@2.3.3.Final//org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1982) at org.jboss.threads@2.3.3.Final//org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1486) at org.jboss.threads@2.3.3.Final//org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1348) at java.base/java.lang.Thread.run(Thread.java:834) at org.jboss.threads@2.3.3.Final//org.jboss.threads.JBossThread.run(JBossThread.java:485) Caused by: java.net.ConnectException: WFLYPRT0053: Could not connect to remote+http://172.16.1.149:9990. The connection failed at org.jboss.as.protocol@10.0.3.Final//org.jboss.as.protocol.ProtocolConnectionUtils.connectSync(ProtocolConnectionUtils.java:128) at org.jboss.as.protocol@10.0.3.Final//org.jboss.as.protocol.ProtocolConnectionManager$EstablishingConnection.connect(ProtocolConnectionManager.java:259) at org.jboss.as.protocol@10.0.3.Final//org.jboss.as.protocol.ProtocolConnectionManager.connect(ProtocolConnectionManager.java:70) at org.jboss.as.server@10.0.3.Final//org.jboss.as.server.mgmt.domain.HostControllerConnection.openConnection(HostControllerConnection.java:128) at org.jboss.as.server@10.0.3.Final//org.jboss.as.server.mgmt.domain.HostControllerClient.resolveBootUpdates(HostControllerClient.java:112) at org.jboss.as.server@10.0.3.Final//org.jboss.as.server.mgmt.domain.ServerBootOperationsService$1.run(ServerBootOperationsService.java:68) ... 6 more Caused by: javax.security.sasl.SaslException: Authentication failed: all available authentication mechanisms failed: DIGEST-MD5: javax.security.sasl.SaslException: DIGEST-MD5: Server rejected authentication at org.jboss.remoting@5.0.15.Final//org.jboss.remoting3.remote.ClientConnectionOpenListener.allMechanismsFailed(ClientConnectionOpenListener.java:109) at org.jboss.remoting@5.0.15.Final//org.jboss.remoting3.remote.ClientConnectionOpenListener$Capabilities.handleEvent(ClientConnectionOpenListener.java:446) at org.jboss.remoting@5.0.15.Final//org.jboss.remoting3.remote.ClientConnectionOpenListener$Capabilities.handleEvent(ClientConnectionOpenListener.java:242) at org.jboss.xnio@3.7.3.Final//org.xnio.ChannelListeners.invokeChannelListener(ChannelListeners.java:92) at org.jboss.xnio@3.7.3.Final//org.xnio.conduits.ReadReadyHandler$ChannelListenerHandler.readReady(ReadReadyHandler.java:66) at org.jboss.xnio.nio@3.7.3.Final//org.xnio.nio.NioSocketConduit.handleReady(NioSocketConduit.java:89) at org.jboss.xnio.nio@3.7.3.Final//org.xnio.nio.WorkerThread.run(WorkerThread.java:591) {code}   I used this content file and pass {{-Dwildfly.config.url on JBOSS_OPTS /etc/default/wildfly.conf }} {code:java} <?xml version="1.0" encoding="UTF-8"?> <configuration> <authentication-client xmlns="urn:elytron:1.0"> <authentication-rules> <rule use-configuration="default" /> </authentication-rules> <authentication-configurations> <configuration name="default"> <set-user-name name="ejbserver" /> <credentials> <clear-password password="ejb" /> </credentials> </configuration> </authentication-configurations> </authentication-client> </configuration> {code}   -- This message was sent by Atlassian Jira (v8.13.1#813001)