Yes. Please follow
I think it is a feature request as we know we never added support
for
http-remoting in domain mode ;-) An issue may already exist.
On 28/05/14 00:13, Kabir Khan wrote:
>
> On 27 May 2014, at 23:39, Arun Gupta <arun.gupta(a)gmail.com> wrote:
>
>> Trying to following the instructions at:
>>
>>
https://docs.jboss.org/author/display/WFLY8/WildFly+8+Cluster+Howto
>>
>> This shows how to setup a 2-instance cluster in master/slave where
>> master is on my laptop and slave is on a Raspi. Couple of questions
>> ...
>>
>> 1). Why the following entry is still referring to 9999 ? Shouldn't it be 9990
?
>>
>> <domain-controller>
>> <remote host="10.211.55.7" port="9999"/>
>> </domain-controller>
>>
>> FTR it only works with 9999, not with 9990.
>>
>> Domain Controller shows the message:
>>
>> [Host Controller] 15:36:22,811 INFO [org.jboss.as.domain] (Host
>> Controller Service Threads - 28) JBAS010918: Registered remote slave
>> host "slave", WildFly 8.1.0.CR2 “Kenny”
> It looks like we hardcode the old “remote://“ protocol in
RemoteDomainConnectionService rather than the new http-remoting protocol, so it is a bug.
I am not sure if that is something we should attempt to negotiate explicitly, or to make
the <remote> element take a ‘protocol’ attribute?
>>
>>
>> 2). Master is throwing the following exception:
>>
>> 22:15:25,094 INFO [org.jboss.as.process.Server:server-one.status]
>> (ProcessController-threads - 3) JBAS012017: Starting process
>> 'Server:server-one'
>> [Server:server-one] Error occurred during initialization of VM
>> [Server:server-one] Server VM is only supported on ARMv7+ VFP
> This ^^ seems to be the real error. Try removing “-server” in the jvm-options.
>
>> 22:15:25,557 INFO [org.jboss.as.process.Server:server-one.status]
>> (reaper for Server:server-one) JBAS012010: Process 'Server:server-one'
>> finished with an exit status of 1
>> [Host Controller] 22:15:26,408 INFO [org.jboss.as.host.controller]
>> (ProcessControllerConnection-thread - 2) JBAS010926: Unregistering
>> server server-one
>> [Host Controller] 22:15:26,495 INFO [org.jboss.as.host.controller]
>> (Controller Boot Thread) JBAS010922: Starting server server-two
>> 22:15:26,417 ERROR [org.jboss.as.process.Server:server-one.status]
>> (ProcessController-threads - 3) JBAS012006: Failed to send data bytes
>> to process 'Server:server-one' input stream: java.io.IOException:
>> Stream closed
>> at java.lang.ProcessBuilder$NullOutputStream.write(ProcessBuilder.java:434)
>> [rt.jar:1.7.0_40]
>> at java.io.OutputStream.write(OutputStream.java:116) [rt.jar:1.7.0_40]
>> at java.io.BufferedOutputStream.flushBuffer(BufferedOutputStream.java:82)
>> [rt.jar:1.7.0_40]
>> at java.io.BufferedOutputStream.flush(BufferedOutputStream.java:140)
>> [rt.jar:1.7.0_40]
>> at java.io.FilterOutputStream.flush(FilterOutputStream.java:140)
>> [rt.jar:1.7.0_40]
>> at
org.jboss.as.process.stdin.BaseNCodecOutputStream.flush(BaseNCodecOutputStream.java:125)
>> [wildfly-process-controller-8.1.0.CR2.jar:8.1.0.CR2]
>> at
org.jboss.as.process.stdin.BaseNCodecOutputStream.flush(BaseNCodecOutputStream.java:137)
>> [wildfly-process-controller-8.1.0.CR2.jar:8.1.0.CR2]
>> at
org.jboss.as.process.stdin.Base64OutputStream.flush(Base64OutputStream.java:44)
>> [wildfly-process-controller-8.1.0.CR2.jar:8.1.0.CR2]
>> at
org.jboss.as.process.stdin.BaseNCodecOutputStream.close(BaseNCodecOutputStream.java:154)
>> [wildfly-process-controller-8.1.0.CR2.jar:8.1.0.CR2]
>> at
org.jboss.as.process.stdin.Base64OutputStream.close(Base64OutputStream.java:44)
>> [wildfly-process-controller-8.1.0.CR2.jar:8.1.0.CR2]
>> at org.jboss.as.process.ManagedProcess.sendStdin(ManagedProcess.java:164)
>> [wildfly-process-controller-8.1.0.CR2.jar:8.1.0.CR2]
>> at org.jboss.as.process.ProcessController.sendStdin(ProcessController.java:207)
>> [wildfly-process-controller-8.1.0.CR2.jar:8.1.0.CR2]
>> at
org.jboss.as.process.ProcessControllerServerHandler$InitMessageHandler$ConnectedMessageHandler.handleMessage(ProcessControllerServerHandler.java:140)
>> [wildfly-process-controller-8.1.0.CR2.jar:8.1.0.CR2]
>> at
org.jboss.as.process.protocol.ConnectionImpl.safeHandleMessage(ConnectionImpl.java:269)
>> [wildfly-process-controller-8.1.0.CR2.jar:8.1.0.CR2]
>> at org.jboss.as.process.protocol.ConnectionImpl$1$1.run(ConnectionImpl.java:223)
>> [wildfly-process-controller-8.1.0.CR2.jar:8.1.0.CR2]
>> at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
>> [rt.jar:1.7.0_40]
>> at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
>> [rt.jar:1.7.0_40]
>> at java.lang.Thread.run(Thread.java:724) [rt.jar:1.7.0_40]
>> at org.jboss.threads.JBossThread.run(JBossThread.java:122)
>> [jboss-threads-2.1.1.Final.jar:2.1.1.Final]
>> 22:15:26,573 ERROR [org.jboss.as.protocol.connection]
>> (ProcessController-threads - 3) JBAS016610: Failed to read a message:
>> java.io.IOException: Stream closed
>> at java.lang.ProcessBuilder$NullOutputStream.write(ProcessBuilder.java:434)
>> [rt.jar:1.7.0_40]
>> at java.io.OutputStream.write(OutputStream.java:116) [rt.jar:1.7.0_40]
>> at java.io.BufferedOutputStream.flushBuffer(BufferedOutputStream.java:82)
>> [rt.jar:1.7.0_40]
>> at java.io.BufferedOutputStream.flush(BufferedOutputStream.java:140)
>> [rt.jar:1.7.0_40]
>> at java.io.FilterOutputStream.flush(FilterOutputStream.java:140)
>> [rt.jar:1.7.0_40]
>> at
org.jboss.as.process.stdin.BaseNCodecOutputStream.flush(BaseNCodecOutputStream.java:125)
>> [wildfly-process-controller-8.1.0.CR2.jar:8.1.0.CR2]
>> at
org.jboss.as.process.stdin.BaseNCodecOutputStream.flush(BaseNCodecOutputStream.java:137)
>> [wildfly-process-controller-8.1.0.CR2.jar:8.1.0.CR2]
>> at
org.jboss.as.process.stdin.Base64OutputStream.flush(Base64OutputStream.java:44)
>> [wildfly-process-controller-8.1.0.CR2.jar:8.1.0.CR2]
>> at
org.jboss.as.process.stdin.BaseNCodecOutputStream.close(BaseNCodecOutputStream.java:154)
>> [wildfly-process-controller-8.1.0.CR2.jar:8.1.0.CR2]
>> at
org.jboss.as.process.stdin.Base64OutputStream.close(Base64OutputStream.java:44)
>> [wildfly-process-controller-8.1.0.CR2.jar:8.1.0.CR2]
>> at org.jboss.as.process.ManagedProcess.sendStdin(ManagedProcess.java:164)
>> [wildfly-process-controller-8.1.0.CR2.jar:8.1.0.CR2]
>> at org.jboss.as.process.ProcessController.sendStdin(ProcessController.java:207)
>> [wildfly-process-controller-8.1.0.CR2.jar:8.1.0.CR2]
>> at
org.jboss.as.process.ProcessControllerServerHandler$InitMessageHandler$ConnectedMessageHandler.handleMessage(ProcessControllerServerHandler.java:140)
>> [wildfly-process-controller-8.1.0.CR2.jar:8.1.0.CR2]
>> at
org.jboss.as.process.protocol.ConnectionImpl.safeHandleMessage(ConnectionImpl.java:269)
>> [wildfly-process-controller-8.1.0.CR2.jar:8.1.0.CR2]
>> at org.jboss.as.process.protocol.ConnectionImpl$1$1.run(ConnectionImpl.java:223)
>> [wildfly-process-controller-8.1.0.CR2.jar:8.1.0.CR2]
>> at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
>> [rt.jar:1.7.0_40]
>> at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
>> [rt.jar:1.7.0_40]
>> at java.lang.Thread.run(Thread.java:724) [rt.jar:1.7.0_40]
>> at org.jboss.threads.JBossThread.run(JBossThread.java:122)
>> [jboss-threads-2.1.1.Final.jar:2.1.1.Final]
>>
>> Same error for server-two as well.
>>
>> Trying to explicitly start server-three on slave gives the same error.
>>
>> This is all using 8.1 CR2.
>>
>> Any idea what might be wrong ?
>>
>> Thanks
>> Aru
>>
>> --
>>
http://blog.arungupta.me
>>
http://twitter.com/arungupta
>> _______________________________________________
>> wildfly-dev mailing list
>> wildfly-dev(a)lists.jboss.org
>>
https://lists.jboss.org/mailman/listinfo/wildfly-dev
>
>
> _______________________________________________
> wildfly-dev mailing list
> wildfly-dev(a)lists.jboss.org
>
https://lists.jboss.org/mailman/listinfo/wildfly-dev
>
_______________________________________________
wildfly-dev mailing list
wildfly-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/wildfly-dev