Hi,
Sebastien Alborini wrote:
>
> Hi,
>
> I've checked in the changes in the synchronization, jboss seems to
> perform good: if the tx timeout is big enough, it stands 300 clients
> without a problem, except the fact that my machine displays a load of
> 29.74 (btw, completely offtopic, but anybody knows what this means?)
This is "load average". The load can only be a whole number,
as it is defined as "number of processes ready to be serviced
by a processor". The raw load is generally of little use as it
can change very rapidly. Instead one (or more) running average(s)
of the load are calculated.
So 29.74 means that recently an average of 29.74 processes were
ready to run.
>
> Sebastien, happy
>
> PS: I've tried with more clients, but then the client says
>
> Exception in thread "main" java.lang.OutOfMemoryError: unable to create
> new native thread
> or
> java.net.SocketException: No buffer space available
>
> Pushing the limits...
Bad, only excuse is overload, but even in that case we
should not get such errors.
Which OS do you get this on?
Best Regards,
Ole Husgaard.
