Never Used To Be This Bad.
 

If I get.....


... or ...


.....one more time, I'm going to scream.

It's complete crapp

Quite agree guys that its not as we hoped it would be but, all that can be done within the restraints that are in place - IS being done.

Don't think it isn't happening to anyone else, either - not an excuse but, I get this 30/40 times a day and factor in having to trawl through posts I don't find particularly interesting - it does not make for a fun time!

Please hang in there, hopefully a resolution is close.

Regards - Frank
DSC Webteam

So, what if it is NOT resolved?

I have to be honnest innthe fact it has done my head in so much that when I get the error I don't bother with DSC !

I only get online at night so if it don't work I go else where and not come back !

I do hope it's sorted soon as I can't be the only one like this.

Age

PHP Resource Leak ?
 

Sounds like a PHP resource leak.
A temporary fix would be sessions configured to time-out sooner rather than trying to recycle existing sessions open that aren't in use. We've seen a lot of code using JRUN on Win32 and Python (PHP) - on Freebsd and Redhat that have been waiting too long for the Ack back from a client (that never turns up) - resulting in time-out ..... waiting and ... waiting until ... bam ! No more resources availbable for more sessions available.

Tongue in cheek
 

I reckon that those who've got time to moan should offer to put it right.

B****r ....the server won't let me post a a reply.......

As has been said before in other posts, the problem lies in the amount of memory available.

The new server has been commissioned and the transfer of programs and data will commence within the next day or two.

I hope to be able to have the new system working before the end of this month.

I know that people are working to resolve the problems, But i never had these continual problems on the old set-up! Did we really go backwards on the memory available, when the old system was already struggling?

Doog, No, there was no drop in the RAM available from what i've read, just that this new software deals with it differenlty and causes the issues we're all now having. Read the post in DSC topics, it's quite concise.