Another QTAC innovation
It was simple, really. A minor path to the behind the scenes batch processes. A new library file for the batch process to run. A small change, a bug fix really.
So I rsync the distribution directory (which is rsync'd from QTAC) with the working directory. Systems fail all over the place. JCBridge breaks completely and needs a restart, users can no longer log in. The log in process goes through the JCBridge to make it faster because:
Connection con = DriverManager.getConnection(url, userID, password); takes too long to execute!
It takes only a few seconds to shutdown the server and restart, particularly as we have written a script to do it for us, in the correct order, to keep the cache being executed in the correct way, but still! A new patch to a library batch process kills the users connections! Question still on the cards: Why are we using this software?
So I rsync the distribution directory (which is rsync'd from QTAC) with the working directory. Systems fail all over the place. JCBridge breaks completely and needs a restart, users can no longer log in. The log in process goes through the JCBridge to make it faster because:
Connection con = DriverManager.getConnection(url, userID, password); takes too long to execute!
It takes only a few seconds to shutdown the server and restart, particularly as we have written a script to do it for us, in the correct order, to keep the cache being executed in the correct way, but still! A new patch to a library batch process kills the users connections! Question still on the cards: Why are we using this software?
0 Comments:
Post a Comment
<< Home