users@glassfish.java.net

Re: Using Glassfish 3 in production

From: Barry van Someren <barry_at_bvansomeren.net>
Date: Sun, 28 Mar 2010 12:11:33 +0200

All,

Could it be related to this:
https://grizzly.dev.java.net/issues/show_bug.cgi?id=547
Try setting the linger to -1 and let us know if it helps.

Regards,

Barry

On Sat, Mar 27, 2010 at 11:27 PM, Barry van Someren
<barry_at_bvansomeren.net> wrote:
> Hi,
>
> We run VMWare dev/test environments, but I never loadtest those.
>
> The 64 Bit JVM allows larger heaps and it can improve performance as
> it uses more registers from the CPU (the x86_64 extensions)
> The  -XX:+UseCompressedOops is used to offset the increased pointer
> sizes for 64 bit usage.
> To be honest, I'm unsure about the difference between 32 and 64 bit, I
> believe 64 bit to be faster on paper, but I've not tested it recently.
> Your settings seem good, in fact except for the garbage collector they
> are pretty close to what I use (I use the CMS gc)
>
> As for the stalling, I've seen a few mentions about this on the list;
> And a patch being posted to fix this.
> Not sure, but I'll see if I can dig up the email.
>
> Currently I work mostly with Glassfish 2.1.1 so I've never seen the
> stalling issue :-/
>
> Regards,
>
> Barry
>
>
>
> On Sat, Mar 27, 2010 at 6:15 PM,  <glassfish_at_javadesktop.org> wrote:
>> Barry,
>>
>> No success.   I've started clean.   I installed RHEL 5.4 64 bit, the 64 bit JVM (6U18), and the 64 bit version of MySQL.
>>
>> First I tried using loadimpact.com to test the site.   I went through a full 50 user test without a problem, 12000 page hits and nearly 100m of data transferred.   I ran a second test and got about 75% complete before the site died.
>>
>> I moved to JMeter after this   It seems like I can't get a good estimate of when the site dies.   I've killed it running a test with 150 threads running 5 times, other times I can run a test 200 thread test 20 times before killing the server.   At times the site doesn't die.
>>
>> I've made modifications to the thread pool without any noticeable change.   I've set the min thread count from 5 to 20 and the max from 500 to 2000.   I even tried setting the max queue size to -1.   There seemed to be no pattern between the load required to kill the site and the thread settings.
>>
>> For an odd test I swapped our production site for this server and ran no load tests against it.   In less than 30 minute the site was down.   I'm sure there was traffic hitting the site during this time, but not anywhere near the amount generated by JMeter or loadimpact.
>>
>> Does anyone have any suggestions on how I can troubleshoot this?   Nothing regarding the server hangs appears in the logs.
>>
>> BTW, on this rebuild of the server I'm using the following JVM options:
>> -server
>> -Xmx3500m
>> -XX:+AggressiveHeap
>> -Xms3500m
>> -Xss128k
>> -XX:+DisableExplicitGC
>> -XX:ParallelGCThreads=2
>> -XX:+UseParallelOldGC
>> -XX:+UseCompressedOops
>> -XX:+UseTLAB
>>
>> Thanks,
>> Bob
>> [Message sent by forum member 'bdushok']
>>
>> http://forums.java.net/jive/thread.jspa?messageID=394034
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe_at_glassfish.dev.java.net
>> For additional commands, e-mail: users-help_at_glassfish.dev.java.net
>>
>>
>
>
>
> --
> Barry van Someren
> ---------------------------------------
> LinkedIn: http://www.linkedin.com/in/barryvansomeren
> Skype: BvsomerenSprout
> Blog: http://blog.bvansomeren.com
> KvK: 27317624
> M: +31 (0)6-81464338
> T: +31 (0)70-2500450
>



-- 
Barry van Someren
---------------------------------------
LinkedIn: http://www.linkedin.com/in/barryvansomeren
Skype: BvsomerenSprout
Blog: http://blog.bvansomeren.com
KvK: 27317624
M: +31 (0)6-81464338
T: +31 (0)70-2500450