| > What on earth is happening to CURRNT at the moment ?
>
> One minute the queue manager isn't running, the next all (well most)
> of the logical name tables disappear (including mine), then the queue's
> are running so slowly that you're forced to go and get a coffee,
> before you're even notified that the job is 'pending'
At the moment? This problem has been occuring for six months, or more.
I regularly log hot-lines about it.
> Is there any reason for the machines behaving like this, or am I
> naive to think that anything is wrong at all.
After this length of time, I am extremely suprised that the problem still
exists. Isn't it about time that it was escalated?
Terry
|
| There has been a specific problem with the queue manager on CURRNT,
caused mainly by what seems to have been a "run away' program,
putting literally thousands of requests into a queue.
As you can imagine, the poor old queue manager got a severe attack
of migraine.....
It's in the process of being cleaned up now; the errant user has
been politely informed of the error of their ways; hopefully the
queue manager can now get on with managing it's queues!
Peter (and no, it wasn't me!)
|