Hi Jukka, i was talking about the Webdav one. The scenario is the following:
1) The repository is deployed and running within a JBoss 7 AS 2) There are client sessions operating it through Webdav 3) Suddenly the repository is undeployed (or the server shutdown) 4) The session.isLive() and session.refresh(true) methods return true (and no exception arises) despite the repository being not accessible anymore Anyway, session.save() method does effectively throw an exception and then re-obtaining the repository object and the session can be performed, but under heavy load that leads to lots of TCP connections in TIME_WAIT state... Is there a better way to check the repository to be up and getting a new session if needed? If a better explanation is needed please, do not hesitate asking for it! Thank you very much for your attention! Regards. 2012/4/11 Jukka Zitting <[email protected]> > Hi, > > On Wed, Apr 11, 2012 at 8:47 PM, Francisco Carriedo Scher > <[email protected]> wrote: > > which method is the appropriate one to check that given session is > > healthy? I have been trying with isLive() and refresh(true) standard > JCR > > methods, but none says the session is down when i suddenly shutdown the > > server containing the repository... > > I'm not sure I understand your use case. Are you talking about a local > JCR session or one based on WebDAV remoting? > > In either case if the underlying repository is forcibly closed, the > session you have will start throwing RepositoryExceptions when it no > longer can access the repository. > > BR, > > Jukka Zitting >
