Skip to main content

1.5Gb in Memory : Constant Restarting of Services

2 replies [Last post]
justind
Offline
Joined: 2011-07-26
Points: 0

Hi All

I work in our Operations department, and recently we were asked to baby sit our Glassfish environment.

Currently we have 2 webservers, both MS server 2003 R2 enterprise edition with service pack2.

What we have been requested to do is monitor the NumConnFree (not sure if this is standard naming convention for the Admin Console).

When this count (default to 150) gets to 20 or less, we need to log on to either of the affected server and stop the services (in our case its GlassFishAppServer), then stop Apache2.2, then start the glassfish service and start Apache. Its either that, or we need to monitor the memory usage of "Java" on both boxes and when it gets above 1.5Gb in memory(theses boxes only have 2Gb) then we do the same stop and start process.

Since we have two webservers, we have to alternate the stop/restart process to ensure we always have connections open for our clients to connect.

Now Im not a developer, but i know this is wrong. And when I ask them why this works like this they say this is just the way it works..

Is there anything else I can provide this community to paint this picture any clearer, and then request the assistance to help overcome this repetitive and (Im fairly certain) unnecessary process?

Eagerly awaiting your responses, questions, sympathy etc..

JDee

Reply viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.
mgainty
Offline
Joined: 2004-05-21
Points: 0

there are a number of strategies you can use to ensure number of available pre-alloced connections stay above the configured threshold
the first is to implement Apache-DBCP connection pooling and pull the next available connection from the pre-allocated connection pool.
http://commons.apache.org/dbcp/

and remember
if you dont need the connection close it!

Martin
______________________________________________
Verzicht und Vertraulichkeitanmerkung/Note de déni et de confidentialité

Diese Nachricht ist vertraulich. Sollten Sie nicht der vorgesehene Empfaenger sein, so bitten wir hoeflich um eine Mitteilung. Jede unbefugte Weiterleitung oder Fertigung einer Kopie ist unzulaessig. Diese Nachricht dient lediglich dem Austausch von Informationen und entfaltet keine rechtliche Bindungswirkung. Aufgrund der leichten Manipulierbarkeit von E-Mails koennen wir keine Haftung fuer den Inhalt uebernehmen.
Ce message est confidentiel et peut être privilégié. Si vous n'êtes pas le destinataire prévu, nous te demandons avec bonté que pour satisfaire informez l'expéditeur. N'importe quelle diffusion non autorisée ou la copie de ceci est interdite. Ce message sert à l'information seulement et n'aura pas n'importe quel effet légalement obligatoire. Étant donné que les email peuvent facilement être sujets à la manipulation, nous ne pouvons accepter aucune responsabilité pour le contenu fourni.

> To: users@glassfish.dev.java.net
> Subject: 1.5Gb in Memory : Constant Restarting of Services
> From: forums@java.net
> Date: Tue, 26 Jul 2011 08:25:01 -0500
>
> Hi All
>
> I work in our Operations department, and recently we were asked to baby sit
> our Glassfish environment.
>
> Currently we have 2 webservers, both MS server 2003 R2 enterprise edition
> with service pack2.
>
> What we have been requested to do is monitor the NumConnFree (not sure if
> this is standard naming convention for the Admin Console).
>
> When this count (default to 150) gets to 20 or less, we need to log on to
> either of the affected server and stop the services (in our case its
> GlassFishAppServer), then stop Apache2.2, then start the glassfish service
> and start Apache. Its either that, or we need to monitor the memory usage of
> "Java" on both boxes and when it gets above 1.5Gb in memory(theses boxes only
> have 2Gb) then we do the same stop and start process.
>
> Since we have two webservers, we have to alternate the stop/restart process
> to ensure we always have connections open for our clients to connect.
>
> Now Im not a developer, but i know this is wrong. And when I ask them why
> this works like this they say this is just the way it works..
>
>
>
> Is there anything else I can provide this community to paint this picture any
> clearer, and then request the assistance to help overcome this repetitive and
> (Im fairly certain) unnecessary process?
>
> Eagerly awaiting your responses, questions, sympathy etc..
>
> JDee
>
>
> --
>
> [Message sent by forum member 'justind']
>
> View Post: http://forums.java.net/node/826160
>
>

justind
Offline
Joined: 2011-07-26
Points: 0

thank you for your reply mgainty!
do you know how I would be able to check whether there are lingering connections that could be closed?

the developers seem fairly certain there is nothing they can do to resolve this. so if I could show them that their code does have 'holes' in it, I might be able to get management to push that this project gets re-visited and hopefully this will end the need to continously reset the services.

once again, thank you for taking the time to help me with this mgainty!