This could also be due to synchronization somewhere in your code. Something to look for is heavy usage of System.out. Writing using System.out is synchronized and can be really slow if you have the console open.
I've seen this once on a really powerful AIX cluster (Jboss was not part of that setup though) When tracking the problem we added more trace messages to System.out. That did not help :-)

I hope this helped

/Fredrik Lindgren

Alwyn Schoeman wrote:
I get the idea that this is Sparc specific problem, anyone with sparc
success?

On Fri, Oct 11, 2002 at 09:25:24AM +0200, [EMAIL PROTECTED] wrote:

Jboss (3.0.2 at least) is using both of our 2 CPUs on 2.2.* SuSE kernel on intel.

On Fri, Oct 11, 2002 at 12:06:23PM +0800, Alwyn Schoeman wrote:

Hi,

I'm running JBoss 3.0.3 on a Sun Fire 880 with 8 cpu's.  Even though I
have about 450 threads going it uses only 1 cpu and not very well at
that.  I have tried all the JVM options for 1.4.1, but no difference.

Anyone have any ideas?

--
Alwyn Schoeman
SMART Money Inc.

"The clock on the wall keeps moving, time stands still...
No matter how the dice may fall, someone else always gets to call the number..."


--
MVH
Marius Kotsbak
Boost communications AS


-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
JBoss-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-user




-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
JBoss-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-user

Reply via email to