On 3 Apr 2006, at 17:05, Sacha Michel Mallais wrote:
On Apr 2, 2006, at 5:03 PM, Corin Lawson wrote:
I would like to know what kinds of limits there are for load on
WO. How many instances of an application could I run, has anyone
much experience with high loads, say 1000's of requests in t
On Apr 2, 2006, at 5:03 PM, Corin Lawson wrote:
I would like to know what kinds of limits there are for load on WO.
How many instances of an application could I run, has anyone much
experience with high loads, say 1000's of requests in the space of
a few minutes? Java Monitor seems cumberso
Am 03.04.2006 2:03 Uhr schrieb "Corin Lawson" unter
<[EMAIL PROTECTED]>:
> Thanks for the response... What major headache that bug is. I shall
> upgrade rather than coming up with a creative workaround (I'd love
> to, but I need a proper fix).
>
> I would like to know what kinds of limits there a
Thanks for the response... What major headache that bug is. I shall
upgrade rather than coming up with a creative workaround (I'd love
to, but I need a proper fix).
I would like to know what kinds of limits there are for load on WO.
How many instances of an application could I run, has anyo
IIRC, leaving a browser open on one of the JavaMonitor pages that
refreshes periodically aggravated this bug.
Chuck
On Mar 29, 2006, at 10:04 AM, Sacha Michel Mallais wrote:
On Mar 28, 2006, at 7:23 PM, Corin Lawson wrote:
Recently I have found that under a increased load there is a large
On Mar 28, 2006, at 7:23 PM, Corin Lawson wrote:
Recently I have found that under a increased load there is a large
number of tcp connections in CLOSE_WAIT state. When there is enough
of them the adapter to no longer able to find any app (including
the JavaMonitor) and the whole system grin
Hi all,
Recently I have found that under a increased load there is a large
number of tcp connections in CLOSE_WAIT state. When there is enough
of them the adapter to no longer able to find any app (including the
JavaMonitor) and the whole system grinds to a halt...
I have confirmed that W
