-
1. Re: why jboss 7.2 gives JBREM000200: Remote connection failed error in host.xml
shailendra.soni Feb 18, 2014 2:36 AM (in response to shailendra.soni)@@@My host.xml interface configuration file look like below,
<domain-controller>
<local/>
<!-- Alternative remote domain controller configuration with a host and port -->
<!-- <remote host="${jboss.domain.master.address}" port="${jboss.domain.master.port:9999}" security-realm="ManagementRealm"/> -->
</domain-controller>
<interfaces>
<interface name="management">
<inet-address value="${jboss.bind.address.management:10.0.76.12}"/>
</interface>
<interface name="public">
<inet-address value="${jboss.bind.address:10.0.76.12}"/>
</interface>
<interface name="unsecure">
<!-- Used for IIOP sockets in the standard configuration.
To secure JacORB you need to setup SSL -->
<inet-address value="${jboss.bind.address.unsecure:127.0.0.1}"/>
</interface>
</interfaces>
In recent, one of the my instance just crashed with following error
09:58:10,407 ERROR [org.jboss.remoting.remote.connection] (Remoting "master:ims5:MANAGEMENT" read-1) JBREM000200: Remote connection failed: java.io.IOException: Connection reset by peer
-
2. Re: why jboss 7.2 gives JBREM000200: Remote connection failed error in host.xml
wdfink Feb 19, 2014 3:18 PM (in response to shailendra.soni)that looks like a network issue.
Could you elaborate where the different instances installed and when you get the error.
A stacktrace with the full error might be helpful as well.
-
3. Re: why jboss 7.2 gives JBREM000200: Remote connection failed error in host.xml
shailendra.soni Feb 20, 2014 5:17 AM (in response to wdfink)Thanks for your reply.
Jboss 7.2 is on single server and there is not stack trace. I have only got mentioned error log.
Please let me know if you need any other information.
-
4. Re: why jboss 7.2 gives JBREM000200: Remote connection failed error in host.xml
wdfink Feb 20, 2014 7:48 AM (in response to shailendra.soni)As you show 10.0.76.12 in your configuration and 10.0.76.13 is a IP from the error message there should be a remote instance to connect to.
As you say setup a "domain" what does that mean, do you use the domain-mode or simple start 5 standalone server?
Did you have a firewall in between?
-
5. Re: why jboss 7.2 gives JBREM000200: Remote connection failed error in host.xml
shailendra.soni Feb 21, 2014 12:01 AM (in response to wdfink)We have two physical servers and both have same issues. So Logger was posted different server. Sorry for that. Actual logger you can see below for 10.0.76.12. Two physical Servers but having different applications. So there is no master - slave implementation. Both servers consider as Master.
11:07:14,667 ERROR [org.jboss.remoting.remote.connection] (Remoting "plpccd150:MANAGEMENT" read-1) JBREM000200: Remote connection failed: org.xnio.channels.ReadTimeoutException: Read timed out
11:07:33,143 INFO [org.jboss.as.domain.controller.mgmt] (Remoting "plpccd150:MANAGEMENT" task-1) JBAS010920: Server [Server:ims1] registered using connection [Channel ID 48cb5d68 (inbound) of Remoting connection 00e52a91 to /10.0.76.12:55247]
Yes we are running domain mode with using "Full" as profile and having 5 instances.
No, We do not have firewall.
Please let me know if you would require any other information.
-
6. Re: why jboss 7.2 gives JBREM000200: Remote connection failed error in host.xml
wdfink Feb 21, 2014 3:43 AM (in response to shailendra.soni)It is still not clear to me when that issue happen and how the configuration look like.
As I understand you run two DC instances on different machines (BTW what OS). As you said "Both servers consider as Master." you mean both are independent domain controllers. right?
Is that issue if you start the domain without applications? Or did that happen together with your application?
Did you have the issue if you only run one of the domains?
Again, for me it looks like a network issue, there might be network problems, i.e. Windows VirusScanner might cause such problems.
-
7. Re: why jboss 7.2 gives JBREM000200: Remote connection failed error in host.xml
shailendra.soni Feb 21, 2014 6:52 AM (in response to wdfink)Your understand is right. This issue comes after application deployed and also this error is not coming instantly, it is coming after few hours. And then it is keep coming and at last all instances automatically crash.
We have using Sun Solaris Sparc as operating system and it is old system.
Please let me know if you would require more information.