On 10/15/2015 07:44 PM, Stefan Seelmann wrote: > On 10/15/2015 07:26 PM, Lucas Theisen wrote: >> >> I tried both Oracle jdk1.8.0_60 and openjdk-1.7.0.71, so i don't think it >> has to do with java version. I tried turning off firewalld, but no dice. >> Could be SELinux, i could try booting without... >> > > Lucas, > > What is the output of `nslookup localhost`? > And is locahost in your /etc/hosts? >
So in [1] we see the code that starts the forked JVM. It also starts a RMI LocateRegistry, I think on localhost. Then the forked process should also try to connect to that registry, Here [2] [3] are some other examples where connection to RMI registry failed. HTH, Stefan [1] https://github.com/ops4j/org.ops4j.pax.exam2/blob/25d5181a00b2e433537e4b53dce50b8925236bc3/containers/pax-exam-container-forked/src/main/java/org/ops4j/pax/exam/forked/ForkedFrameworkFactory.java#L103 [2]https://stackoverflow.com/questions/6180383/rmi-registry-connecting-to-wrong-adress [3]http://knowledgebase.progress.com/articles/Article/AdminServerattemptstobindtothewrongIPAddress
