On Dec 14, 11:02 am, ap...@[EMAIL PROTECTED]
wrote:
> Occasionally (3 or 4 times times now in the last 3 months) orbixd
> appears to go into CPU meltdown on our UAT machine. No-one can fathom
> why. All we can do is restart our processes until the problem goes
> away, as mysteriously as it arose. I wonder if anyone else has seen
> anything like this. We are using an ancient, unsup****ted version of
> OrbixWeb (3.0.x).
>
> -Andrew Marlow
I guess I'm beating a dead horse here, but I have to question the
sanity of an organization that continues to suffer with an ancient,
buggy piece of software, rather than upgrade to something current. The
number of issues you've encountered are roughly the same number I
experienced nearly a decade ago. It's time to move on.
How is wasting your time saving your organization any money,
especially when there are plenty of free orbs out there? As a general
rule of thumb, many organizations take the 'if it isn't broke, don't
fix it' route. They're not going to throw out working software just
for the sake of running the latest and greatest. However, it's quite
clear here that it *is* broken, and it can't be fixed.
I know it's not your choice. I hope you're learning something valuable
as you struggle through this. I wouldn't be that patient. If my
organization saddled me with a crappy piece of code like OW, I'd have
resigned ages ago.
Mark
|
