java.net.ConnectException

Connection refused: connect at org.apache.jackrabbit.rmi.client.SafeClientRepository.getRemoteRepository(SafeClientRepository.java:85) at org.apache.jackrabbit.rmi.client.SafeClientRepository.<init>(SafeClientRepository.java:56) at org.apache.jackrabbit.rmi.client.ClientRepositoryFactory$1.<init>(ClientRepositoryFactory.java:90) at org.apache.jackrabbit.rmi.client.ClientRepositoryFactory.getRepository(ClientRepositoryFactory.java:90) at org.hippoecm.repository.RemoteHippoRepository.<init>(RemoteHippoRepository.java:35) at org.hippoecm.repository.RemoteHippoRepository.create(RemoteHippoRepository.java:40) at org.hippoecm.repository.HippoRepositoryFactory.getHippoRepository(HippoRepositoryFactory.java:102) at org.onehippo.forge.jcrrunner.JcrHelper.ensureConnected(JcrHelper.java:125)

Samebug tips0

We couldn't find tips for this exception.

Don't give up yet. Paste your full stack trace to get a solution.

Solutions on the web1

  • via Unknown by Ricardo Tangali,
  • Stack trace

    • java.net.ConnectException: Connection refused: connect at org.apache.jackrabbit.rmi.client.SafeClientRepository.getRemoteRepository(SafeClientRepository.java:85) at org.apache.jackrabbit.rmi.client.SafeClientRepository.<init>(SafeClientRepository.java:56) at org.apache.jackrabbit.rmi.client.ClientRepositoryFactory$1.<init>(ClientRepositoryFactory.java:90) at org.apache.jackrabbit.rmi.client.ClientRepositoryFactory.getRepository(ClientRepositoryFactory.java:90) at org.hippoecm.repository.RemoteHippoRepository.<init>(RemoteHippoRepository.java:35) at org.hippoecm.repository.RemoteHippoRepository.create(RemoteHippoRepository.java:40) at org.hippoecm.repository.HippoRepositoryFactory.getHippoRepository(HippoRepositoryFactory.java:102) at org.onehippo.forge.jcrrunner.JcrHelper.ensureConnected(JcrHelper.java:125) at org.onehippo.forge.jcrrunner.JcrRunner.main(JcrRunner.java:60)

    Write tip

    You have a different solution? A short tip here would help you and many other users who saw this issue last week.

    Users with the same issue

    We couldn't find other users who have seen this exception.