The jre (- server) option was the culprit!!
shyte! i tell you...
d.
-----Original Message-----
From: Peter Wone [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, September 19, 2001 10:02 PM
To: [EMAIL PROTECTED]
Subject: Re: [JBoss-user] Performance on RedHat 7.0 & JBoss 2.4.1
Unix (and therefore Linux) doesn't traditionally use a "keep-alive"
architecture. Rather, processes are spawned on demand, do their thing and
then die. Unix is designed for this approach; it masks a multitude of sins,
in particular memory and thread leakage.
Keep-alive is more of a Windows NT thing, and for this reason, thread
management under NT is rather more evolved than it is under Unix. So is
virtual memory management, due to high memory demands arising from a
keep-alive design philosophy. (I'm not really a fan of Windows...those are
the only nice things I'll ever say about it.)
At any rate, I wouldn't be surprised if immature and rapidly changing Linux
thread management were the fundament of the problem.
----- Original Message -----
From: "Ferguson, Doug" <[EMAIL PROTECTED]>
To: "JBoss User (E-mail)" <[EMAIL PROTECTED]>
Sent: Thursday, September 20, 2001 12:17 PM
Subject: [JBoss-user] Performance on RedHat 7.0 & JBoss 2.4.1
> I upgraded to 2.4.1 and I am seeing my xalan transformations are taking 5x
> as long.
>
> Any ideas what could be going on here?
>
> Thanks,
> d.
>
> _______________________________________________
> JBoss-user mailing list
> [EMAIL PROTECTED]
> https://lists.sourceforge.net/lists/listinfo/jboss-user
_______________________________________________
JBoss-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-user
_______________________________________________
JBoss-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-user
