Situation:
We had some network changes and the IP of the Machine has been changed. we have changed the IP in all the required file but still adeptia server is not coming up.
Starting input stream handler
2016-03-06 22:06:08 Starting cluster manager
2016-03-06 22:06:10 Starting cluster manager with Enterprise Business Integration Management Suite 6.0
2016-03-06 22:06:16 java.io.IOException: Cannot bind to URL [rmi://adeptiaserver:21000/adeptiaserver]: javax.naming.CommunicationException [Root exception is java.rmi.ConnectIOException: Exception creating connection to: horizon02; nested exception is:
2016-03-06 22:06:16 Interactive boot failed: Cannot bind to URL [rmi://adeptiaserver:21009/adeptiaserver]: javax.naming.CommunicationException [Root exception is java.rmi.ConnectIOException: Exception creating connection to: horizon02; nested exception is:
2016-03-06 22:06:16 java.net.NoRouteToHostException: No route to host]
2016-03-06 22:06:16 java.net.NoRouteToHostException: No route to host]
2016-03-06 22:06:16 at javax.management.remote.rmi.RMIConnectorServer.new
Cause:
The "No route to host" error message indicates and issue with the "adeptiaserver" domain name.
Solution:
Please verify that machine Adeptia is installed on is able to resolve the domain name adeptiaserver to a correct IP address.
If it is not able to resolve the adeptiaserver domain name, try replacing those entries with the IP of the machine.
Comments
0 comments
Article is closed for comments.