D
dbeavon
Guest
I noticed a change in PASOE, but I don't believe that I had seen any announcements or KB's about it. In the past when a remote database connection was lost, PASOE didn't seem to know or care about that insignificant detail. This was the case even when the database connection was started based on client session startup parameters. Until manual maintenance was performed on the PASOE instance, all clients that tried to use it would experience STOP conditions. Now, in version 11.7.4, I'm seeing messages like this in the logs: [18/11/25@02:30:36.041-0500] P-002304 T-002800 1 AS-4 MSAS Connection to networked db lumbertrack lost for AS-4. [18/11/25@02:30:36.041-0500] P-002304 T-002800 1 AS-4 -- Disconnect from server; database is being shutdown. (2659) [18/11/25@02:30:36.047-0500] P-002304 T-002800 1 AS-4 MSAS Destroying Session AS-4 due to externally instigated db disconnect. Notice the message, MSAS Destroying Session AS-### due to externally instigated db disconnect This seems to indicate that PASOE is able to detect and resolve database disconnections. I think this is a step in the right direction. The only complaint I have is that PASOE doesn't proactively trim these bad sessions. It seems to wait until the first use of them, after the database was shut down and restarted. That usually means that the PASOE client will get an error message, even if the database had been stopped and restarted over an hour ago (ie. there is a residual problem with the session that needs to be flushed out and it won't be flushed out until the arrival of the first unfortunate client that attempts to use the session). After that, the problems seem to resolve on their own. After ALL ABL sessions that had lost their connections have been individually repaired, one at a time.
Continue reading...
Continue reading...