For quite some time (perhaps 18 months or so), we were experiencing a
problem where users were encountering "monitor debugger" errors, which
resulted in entries into the ERRORS file called "PX_ILOAD". We were
running on D3/NT 7.4.1. These errors would then propagate, causing
other users to experience the same problem. The resolution was to
shutdown D3 and restart. With 130+ users, especially during peak-
periods of business, this situation wreaked havoc. RD's answer was
that we had flashed programs that were not fully-pathed, and were
corrupting "Flashed Shared Code Memory" (viewable from "tools", within
D3 File Manager). We recompiled-cataloged, with full path, every
program that was found to be in error, but still could not remedy the
situation. Attempts were made to reboot the server every 3 days, or
so. Due to other schedules, we were not always able to get the
reboot accomplished in due time.
Upgrades to 7.4.7a proved no help, either. A temporary server was set
up with 7.5.3, temporary 130 user D3 licenses, and within 2 hours the
volume of PX_ILOAD errors accumulated at an even faster rate than on
7.4.1. We were on the verge of migrating to Linux, which was RD's
recommended solution.
As a last resort, preparatory to changing over to D3/Linux, RD
delivered to me version 7.4.7c. We have now been on this version for
about one month and have not had one PX_ILOAD error. Interestingly
enough, we had noticed that on prior versions of D3, the Available
Virtual Memory (AVM) from "nt_pinfo" command was down around 1.2 GB,
which is about 38% of our total 3.2 GB physical memory.
Now, on 7.4.7c, I am gathering stats every 15 minutes with a phantom
process, using "nt_pinfo m" , "maxusers", and "free" commands,
"capturing" the respective outputs, then filtering out the information
I need to review. Our AVM now stays in the vicinity of 2.0, or about
62%. Following the end-of-day procedures, which are completed at
about 23:00, and with no end-users on the system, AVM increases to
about 2.1-2.2 GB.
Although RD cannot confirm the resolution, I truly believe that we
were experiencing extensive D3 memory-leaks, which have been
"repaired", apparently, with the 7.4.7c version.
Has anyone else seen the "PX_ILOAD" errors as I have defined? I'd be
curious to know.
|
