Hi Jukka,
removing the connection cache from the ClientRepositoryFactory doesn't
seem to help. After building the jcr-rmi.jar form the latest sources
i'am getting again the following exception (after restarting the jcr-rmi
server):
Stack Trace follows:
org.apache.jackrabbit.rmi.client.RemoteRepositoryException: Connection
refused to host: 192.168.1.61; nested exception is:
java.net.ConnectException: Connection refused: connect: Connection
refused to host: 192.168.1.61; nested exception is:
java.net.ConnectException: Connection refused: connect at
org.apache.jackrabbit.rmi.client.ClientRepository.login(ClientRepository.java:80)
at
com.contens.jcr.portal.ContentRepositoryAccessPortletPortlet.doView(ContentRepositoryAccessPortletPortlet.java:126)...
-Flo
Jukka Zitting wrote:
Hi,
Florian Ried wrote:
I also think, that for now connection managment should be layered out
to a higher level. Removing the cache in the ClientRepositoryFactory
makes the RMI Server JNDI registration working as I expected it.
Agreed. I have now (r233448) removed the connection cache from
ClientRepositoryFactory.
BR,
Jukka Zitting
