Our LiveCycle installation has been plagued by an unstable network. The database LiveCycle runs off of has been randomly dropping from the network, severing the connection with our application server (JBoss). When this happens LiveCycle enters a dangerous state, where if a user takes action on a task, the process in which that task is involved in goes in a stuck state that cannot be recovered. The process does not stall it just gets stuck, and there is no way to recover from it, except to Terminate and start over. Because the network connectivity will continue to be an issue for us (no one to date has found a reason why servers randomly drop from the network), we have had to come up with some ideas for how to proactively watch for this DB drop happening. We have decided to tackle this issue with a three piece solution:
First we are automatically restarting the application server very early in the morning. This will reestablish the connection with the DB should it have gone down over night.
Second, we have set up a short lived process on the server to catch the exception when it is thrown, and email the sys admin, so that they can restart JBoss (I'm not entirely sure if this will work since the process is on the server that would be having problems connecting to its database to begin with)
Third, we would like to scan the current JBoss server log on the LiveCycle server, at the time a user tries logging into the workspace tool. If we see the exception in the log, then the idea is to display an error message, and keep the user from being able to log in.
The idea here is to cover all our bases until our infastructure team can figure out the network stability problem.
My question is in regards to the third step I have laid out. I realize that this involves building a custom workspace, of which we have already done, but is it possible to check the log file from the workspace tool like I have described? All of the documentation I've been able to dig up to date makes it look like I can only look at files local to the user attempting to log in. If this is true, then this approach may not work for us. Ideally resolving the network stability issue would be the best way to fix this problem, but that issue is outside of my control. Does anyone have any ideas on this, or maybe you have run into a similar problem, and have implimented a different solution. Thank you ahead of time for any assistance you can offer.