Hi there,
I have an application that calls EJBs deployed on a remote Websphere 3.5 server from a
servlet on a client machine also running Websphere 3.5. No probs there.
The client machine also holds a Service Locator class which handles the jndi look-up and caching of
ejb home interfaces and other factory objects.
So far so good.
Now this service Locator class is required to performs checks from time to time on the remote server to see whether or not Websphere has gone down so that it can refresh its cache and do other clean up stuff. Now here's the problem.
Does anyone know of a way of 'touching' websphere just to check if it is still alive or not?
So far the only thing I can think of is calling create on a home interface and seeing if it thows an exception - but thats a bit heavy.
Any suggestions at all would be greatly appreciated.
Thanx,
Andrew.
