We have an application which has an Authentication service running on a windows server and this service is connecting to the iSeries. In an unlikely event of iSeries not being available (eg if the backups are running longer than expected), the service tries to connect to iSeries and fails. This causes the windows service to go in a loop of something and the CPU usage on the windows server goes very high. Once the CPU usage has shot pass the ceiling, we have to re start the server itself as the services become non-responsive. Is there any way to stop this? Also is it possible to somehow find out if iSeries is available for connection or not?
July 20, 2009 12:52 PM
July 29, 2009 11:14 AM