Another Glassfish Gotcha!

Logs again folks.

We had a big system we deployed, got 23 users in it ran like a DOG, updated Glassfish 2.1.1 still ran like a dog (but didn’t crash with permgen problems).

What was happening was simple the web stack was writing hundreds of INFO statements about combos and drop downs. I set all the logs to only report SEVERE errors and it all sped up!

Advertisements

About Paul C

I am a Senior Java programmer/Web Technologies, Play in a band called Mandolin Monday, I have a cat and I live on a boat.

Posted on February 25, 2010, in glassfish. Bookmark the permalink. 2 Comments.

  1. That’s probably a very common gotcha that isn’t all that related to GlassFish (other than it’s pretty easy to dynamically change log levels 😉

    • Hi Alexis,

      Yes it’s true when you think about it in the context of other servers, but glassfish especially when working with Visual Web (some of us have to create 300 field forms!). Because visual web creates hundreds of messages when drop down boxes are not populated on load of the page, which is what we do when using DHTMLX components. 🙂 Thanks for the comment.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: