Skip to main content

Where to set JDBC Connection Idle timeout?

6 replies [Last post]
Anonymous

My database server cuts down a JDBC connection after it is idle for 240 minutes. As a result, some of my pooled connections throw SQLException ("Connection broken") after beeing unused for this time. How can I tell GlassFish to deal with this? What parameter do I have to change in the JDBC pool?

Thanks!

Markus

QUIPSY QUALITY GmbH & Co. KG

Ein Unternehmen der MES-Gruppe

Stuttgarter Strasse 23

D-75179 Pforzheim

Tel: 07231-9189-52

Fax: 07231-9189-59

www.quipsy.de

karg@quipsy.de

Registergericht Mannheim HRA 701214

Geschäftsführer: Nils Schroeder

Diese E-Mail enthält persönliche, vertrauliche und vor Weitergabe geschützte Informationen und ist ausschließlich für den vorgesehenen o.g. Empfänger (Adressaten) bestimmt. Falls Sie diese E-Mail versehentlich erhalten haben und nicht der vorgesehene Empfänger sind, bitten wir Sie, die E-Mail und deren Anhänge nicht aufzubewahren, nicht zu vervielfältigen, nicht zu nutzen und nicht weiterzugeben. Bitte informieren Sie uns als Absender über diesen Zustellungsfehler und löschen Sie die E-Mail.

[att1.html]
[image001.jpg]
[Markus KARG.vcf]
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@glassfish.dev.java.net
For additional commands, e-mail: users-help@glassfish.dev.java.net

Reply viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.
Shalini Muthukrishnan

You could set the --idletimeout attribute of the pool from the admin
console or use the CLI command :

asadmin set
server.resources.jdbc-connection-pool.DerbyPool.idle-timeout-in-seconds=10

Markus Karg wrote:
>
> My database server cuts down a JDBC connection after it is idle for
> 240 minutes. As a result, some of my pooled connections throw
> SQLException ("Connection broken") after beeing unused for this time.
> How can I tell GlassFish to deal with this? What parameter do I have
> to change in the JDBC pool?
>
>
>
> Thanks!
>
> Markus
>
>
>
> QUIPSY QUALITY GmbH & Co. KG
>
> Ein Unternehmen der MES-Gruppe
>
> Stuttgarter Strasse 23
>
> D-75179 Pforzheim
>
> Tel: 07231-9189-52
>
> Fax: 07231-9189-59
>
> www.quipsy.de
>
> karg@quipsy.de
>
> Registergericht Mannheim HRA 701214
>
> Geschäftsführer: Nils Schroeder
>
>
>
> Diese E-Mail enthält persönliche, vertrauliche und vor Weitergabe
> geschützte Informationen und ist ausschließlich für den vorgesehenen
> o.g. Empfänger (Adressaten) bestimmt. Falls Sie diese E-Mail
> versehentlich erhalten haben und nicht der vorgesehene Empfänger sind,
> bitten wir Sie, die E-Mail und deren Anhänge nicht aufzubewahren,
> nicht zu vervielfältigen, nicht zu nutzen und nicht weiterzugeben.
> Bitte informieren Sie uns als Absender über diesen Zustellungsfehler
> und löschen Sie die E-Mail.
>
>
>
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@glassfish.dev.java.net
> For additional commands, e-mail: users-help@glassfish.dev.java.net
>

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@glassfish.dev.java.net
For additional commands, e-mail: users-help@glassfish.dev.java.net

Markus Karg

Will I have to reboot GlassFish or will it have immediate effect?

> -----Original Message-----
> From: Shalini.Muthukrishnan@Sun.COM
> [mailto:Shalini.Muthukrishnan@Sun.COM]
> Sent: Donnerstag, 9. Oktober 2008 14:24
> To: users@glassfish.dev.java.net
> Subject: Re: Where to set JDBC Connection Idle timeout?
>
> You could set the --idletimeout attribute of the pool from the admin
> console or use the CLI command :
>
> asadmin set
> server.resources.jdbc-connection-pool.DerbyPool.idle-timeout-in-
> seconds=10
>
> Markus Karg wrote:
> >
> > My database server cuts down a JDBC connection after it is idle for
> > 240 minutes. As a result, some of my pooled connections throw
> > SQLException ("Connection broken") after beeing unused for this time.
> > How can I tell GlassFish to deal with this? What parameter do I have
> > to change in the JDBC pool?
> >
> >
> >
> > Thanks!
> >
> > Markus
> >
> >
> >
> > QUIPSY QUALITY GmbH & Co. KG
> >
> > Ein Unternehmen der MES-Gruppe
> >
> > Stuttgarter Strasse 23
> >
> > D-75179 Pforzheim
> >
> > Tel: 07231-9189-52
> >
> > Fax: 07231-9189-59
> >
> > www.quipsy.de
> >
> > karg@quipsy.de
> >
> > Registergericht Mannheim HRA 701214
> >
> > Geschäftsführer: Nils Schroeder
> >
> >
> >
> > Diese E-Mail enthält persönliche, vertrauliche und vor Weitergabe
> > geschützte Informationen und ist ausschließlich für den vorgesehenen
> > o.g. Empfänger (Adressaten) bestimmt. Falls Sie diese E-Mail
> > versehentlich erhalten haben und nicht der vorgesehene Empfänger
> sind,
> > bitten wir Sie, die E-Mail und deren Anhänge nicht aufzubewahren,
> > nicht zu vervielfältigen, nicht zu nutzen und nicht weiterzugeben.
> > Bitte informieren Sie uns als Absender über diesen Zustellungsfehler
> > und löschen Sie die E-Mail.
> >
> >
> >
> >
> >
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscribe@glassfish.dev.java.net
> > For additional commands, e-mail: users-help@glassfish.dev.java.net
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@glassfish.dev.java.net
> For additional commands, e-mail: users-help@glassfish.dev.java.net

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@glassfish.dev.java.net
For additional commands, e-mail: users-help@glassfish.dev.java.net

Shalini Muthukrishnan

It will have immediate effect. The attributes are dynamically
reconfigurable.

Markus Karg wrote:
> Will I have to reboot GlassFish or will it have immediate effect?
>
>
>> -----Original Message-----
>> From: Shalini.Muthukrishnan@Sun.COM
>> [mailto:Shalini.Muthukrishnan@Sun.COM]
>> Sent: Donnerstag, 9. Oktober 2008 14:24
>> To: users@glassfish.dev.java.net
>> Subject: Re: Where to set JDBC Connection Idle timeout?
>>
>> You could set the --idletimeout attribute of the pool from the admin
>> console or use the CLI command :
>>
>> asadmin set
>> server.resources.jdbc-connection-pool.DerbyPool.idle-timeout-in-
>> seconds=10
>>
>> Markus Karg wrote:
>>
>>> My database server cuts down a JDBC connection after it is idle for
>>> 240 minutes. As a result, some of my pooled connections throw
>>> SQLException ("Connection broken") after beeing unused for this time.
>>> How can I tell GlassFish to deal with this? What parameter do I have
>>> to change in the JDBC pool?
>>>
>>>
>>>
>>> Thanks!
>>>
>>> Markus
>>>
>>>
>>>
>>> QUIPSY QUALITY GmbH & Co. KG
>>>
>>> Ein Unternehmen der MES-Gruppe
>>>
>>> Stuttgarter Strasse 23
>>>
>>> D-75179 Pforzheim
>>>
>>> Tel: 07231-9189-52
>>>
>>> Fax: 07231-9189-59
>>>
>>> www.quipsy.de
>>>
>>> karg@quipsy.de
>>>
>>> Registergericht Mannheim HRA 701214
>>>
>>> Geschäftsführer: Nils Schroeder
>>>
>>>
>>>
>>> Diese E-Mail enthält persönliche, vertrauliche und vor Weitergabe
>>> geschützte Informationen und ist ausschließlich für den vorgesehenen
>>> o.g. Empfänger (Adressaten) bestimmt. Falls Sie diese E-Mail
>>> versehentlich erhalten haben und nicht der vorgesehene Empfänger
>>>
>> sind,
>>
>>> bitten wir Sie, die E-Mail und deren Anhänge nicht aufzubewahren,
>>> nicht zu vervielfältigen, nicht zu nutzen und nicht weiterzugeben.
>>> Bitte informieren Sie uns als Absender über diesen Zustellungsfehler
>>> und löschen Sie die E-Mail.
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: users-unsubscribe@glassfish.dev.java.net
>>> For additional commands, e-mail: users-help@glassfish.dev.java.net
>>>
>>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@glassfish.dev.java.net
>> For additional commands, e-mail: users-help@glassfish.dev.java.net
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@glassfish.dev.java.net
> For additional commands, e-mail: users-help@glassfish.dev.java.net
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@glassfish.dev.java.net
For additional commands, e-mail: users-help@glassfish.dev.java.net

Markus Karg

The description of this option says: "The maximum time in seconds that a connection can remain idle in the pool. After this time expires, the connection is removed from the pool.". There is one question left open unanswered: If a RAR asks for a connection from the pool, it can keep that connection for a long time (e. g. think of a very long running background task processed by the RAR). What will happen if the application does not issue SQL commands for a long time? Will this get detected by the idletimeout parameter? Or does this timer only run as long as the connection is in the pool, not currently acquired by an application? (The actual question is: What means IDLE exactly -- REALLY UNUSED or NOT ACQUIRED BY THE APPLICATION?).

Thanks!
Markus

> -----Original Message-----
> From: Shalini.Muthukrishnan@Sun.COM
> [mailto:Shalini.Muthukrishnan@Sun.COM]
> Sent: Donnerstag, 9. Oktober 2008 18:37
> To: users@glassfish.dev.java.net
> Subject: Re: Where to set JDBC Connection Idle timeout?
>
> It will have immediate effect. The attributes are dynamically
> reconfigurable.
>
> Markus Karg wrote:
> > Will I have to reboot GlassFish or will it have immediate effect?
> >
> >
> >> -----Original Message-----
> >> From: Shalini.Muthukrishnan@Sun.COM
> >> [mailto:Shalini.Muthukrishnan@Sun.COM]
> >> Sent: Donnerstag, 9. Oktober 2008 14:24
> >> To: users@glassfish.dev.java.net
> >> Subject: Re: Where to set JDBC Connection Idle timeout?
> >>
> >> You could set the --idletimeout attribute of the pool from the admin
> >> console or use the CLI command :
> >>
> >> asadmin set
> >> server.resources.jdbc-connection-pool.DerbyPool.idle-timeout-in-
> >> seconds=10
> >>
> >> Markus Karg wrote:
> >>
> >>> My database server cuts down a JDBC connection after it is idle for
> >>> 240 minutes. As a result, some of my pooled connections throw
> >>> SQLException ("Connection broken") after beeing unused for this
> time.
> >>> How can I tell GlassFish to deal with this? What parameter do I
> have
> >>> to change in the JDBC pool?
> >>>
> >>>
> >>>
> >>> Thanks!
> >>>
> >>> Markus
> >>>
> >>>
> >>>
> >>> QUIPSY QUALITY GmbH & Co. KG
> >>>
> >>> Ein Unternehmen der MES-Gruppe
> >>>
> >>> Stuttgarter Strasse 23
> >>>
> >>> D-75179 Pforzheim
> >>>
> >>> Tel: 07231-9189-52
> >>>
> >>> Fax: 07231-9189-59
> >>>
> >>> www.quipsy.de
> >>>
> >>> karg@quipsy.de
> >>>
> >>> Registergericht Mannheim HRA 701214
> >>>
> >>> Geschäftsführer: Nils Schroeder
> >>>
> >>>
> >>>
> >>> Diese E-Mail enthält persönliche, vertrauliche und vor Weitergabe
> >>> geschützte Informationen und ist ausschließlich für den
> vorgesehenen
> >>> o.g. Empfänger (Adressaten) bestimmt. Falls Sie diese E-Mail
> >>> versehentlich erhalten haben und nicht der vorgesehene Empfänger
> >>>
> >> sind,
> >>
> >>> bitten wir Sie, die E-Mail und deren Anhänge nicht aufzubewahren,
> >>> nicht zu vervielfältigen, nicht zu nutzen und nicht weiterzugeben.
> >>> Bitte informieren Sie uns als Absender über diesen
> Zustellungsfehler
> >>> und löschen Sie die E-Mail.
> >>>
> >>>
> >>>
> >>>
> >>>
> >>>
> >>>
> >>> -------------------------------------------------------------------
> --
> >>> To unsubscribe, e-mail: users-unsubscribe@glassfish.dev.java.net
> >>> For additional commands, e-mail: users-help@glassfish.dev.java.net
> >>>
> >>>
> >> --------------------------------------------------------------------
> -
> >> To unsubscribe, e-mail: users-unsubscribe@glassfish.dev.java.net
> >> For additional commands, e-mail: users-help@glassfish.dev.java.net
> >>
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscribe@glassfish.dev.java.net
> > For additional commands, e-mail: users-help@glassfish.dev.java.net
> >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@glassfish.dev.java.net
> For additional commands, e-mail: users-help@glassfish.dev.java.net

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@glassfish.dev.java.net
For additional commands, e-mail: users-help@glassfish.dev.java.net

Jagadish Prasath Ramu

idle-timeout feature will act on connections in the pool (not on the
connections currently acquired by applications). So, if RA is holding
the connection (which means, its not in the pool), idle-timeout feature
will not act on it.

HTH,
-Jagadish

On Sat, 2008-10-11 at 20:14 +0200, Markus Karg wrote:
> The description of this option says: "The maximum time in seconds that a connection can remain idle in the pool. After this time expires, the connection is removed from the pool.". There is one question left open unanswered: If a RAR asks for a connection from the pool, it can keep that connection for a long time (e. g. think of a very long running background task processed by the RAR). What will happen if the application does not issue SQL commands for a long time? Will this get detected by the idletimeout parameter? Or does this timer only run as long as the connection is in the pool, not currently acquired by an application? (The actual question is: What means IDLE exactly -- REALLY UNUSED or NOT ACQUIRED BY THE APPLICATION?).
>
> Thanks!
> Markus
>
> > -----Original Message-----
> > From: Shalini.Muthukrishnan@Sun.COM
> > [mailto:Shalini.Muthukrishnan@Sun.COM]
> > Sent: Donnerstag, 9. Oktober 2008 18:37
> > To: users@glassfish.dev.java.net
> > Subject: Re: Where to set JDBC Connection Idle timeout?
> >
> > It will have immediate effect. The attributes are dynamically
> > reconfigurable.
> >
> > Markus Karg wrote:
> > > Will I have to reboot GlassFish or will it have immediate effect?
> > >
> > >
> > >> -----Original Message-----
> > >> From: Shalini.Muthukrishnan@Sun.COM
> > >> [mailto:Shalini.Muthukrishnan@Sun.COM]
> > >> Sent: Donnerstag, 9. Oktober 2008 14:24
> > >> To: users@glassfish.dev.java.net
> > >> Subject: Re: Where to set JDBC Connection Idle timeout?
> > >>
> > >> You could set the --idletimeout attribute of the pool from the admin
> > >> console or use the CLI command :
> > >>
> > >> asadmin set
> > >> server.resources.jdbc-connection-pool.DerbyPool.idle-timeout-in-
> > >> seconds=10
> > >>
> > >> Markus Karg wrote:
> > >>
> > >>> My database server cuts down a JDBC connection after it is idle for
> > >>> 240 minutes. As a result, some of my pooled connections throw
> > >>> SQLException ("Connection broken") after beeing unused for this
> > time.
> > >>> How can I tell GlassFish to deal with this? What parameter do I
> > have
> > >>> to change in the JDBC pool?
> > >>>
> > >>>
> > >>>
> > >>> Thanks!
> > >>>
> > >>> Markus
> > >>>
> > >>>
> > >>>
> > >>> QUIPSY QUALITY GmbH & Co. KG
> > >>>
> > >>> Ein Unternehmen der MES-Gruppe
> > >>>
> > >>> Stuttgarter Strasse 23
> > >>>
> > >>> D-75179 Pforzheim
> > >>>
> > >>> Tel: 07231-9189-52
> > >>>
> > >>> Fax: 07231-9189-59
> > >>>
> > >>> www.quipsy.de
> > >>>
> > >>> karg@quipsy.de
> > >>>
> > >>> Registergericht Mannheim HRA 701214
> > >>>
> > >>> Geschäftsführer: Nils Schroeder
> > >>>
> > >>>
> > >>>
> > >>> Diese E-Mail enthält persönliche, vertrauliche und vor Weitergabe
> > >>> geschützte Informationen und ist ausschließlich für den
> > vorgesehenen
> > >>> o.g. Empfänger (Adressaten) bestimmt. Falls Sie diese E-Mail
> > >>> versehentlich erhalten haben und nicht der vorgesehene Empfänger
> > >>>
> > >> sind,
> > >>
> > >>> bitten wir Sie, die E-Mail und deren Anhänge nicht aufzubewahren,
> > >>> nicht zu vervielfältigen, nicht zu nutzen und nicht weiterzugeben.
> > >>> Bitte informieren Sie uns als Absender über diesen
> > Zustellungsfehler
> > >>> und löschen Sie die E-Mail.
> > >>>
> > >>>
> > >>>
> > >>>
> > >>>
> > >>>
> > >>>
> > >>> -------------------------------------------------------------------
> > --
> > >>> To unsubscribe, e-mail: users-unsubscribe@glassfish.dev.java.net
> > >>> For additional commands, e-mail: users-help@glassfish.dev.java.net
> > >>>
> > >>>
> > >> --------------------------------------------------------------------
> > -
> > >> To unsubscribe, e-mail: users-unsubscribe@glassfish.dev.java.net
> > >> For additional commands, e-mail: users-help@glassfish.dev.java.net
> > >>
> > >
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: users-unsubscribe@glassfish.dev.java.net
> > > For additional commands, e-mail: users-help@glassfish.dev.java.net
> > >
> > >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscribe@glassfish.dev.java.net
> > For additional commands, e-mail: users-help@glassfish.dev.java.net
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@glassfish.dev.java.net
> For additional commands, e-mail: users-help@glassfish.dev.java.net
>

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@glassfish.dev.java.net
For additional commands, e-mail: users-help@glassfish.dev.java.net

Markus Karg

I see. Anyways, thanks for the answer, but it seems as if the default of 300 seconds is good enough already. :-)

Regards
Markus

> -----Original Message-----
> From: Jagadish.Ramu@Sun.COM [mailto:Jagadish.Ramu@Sun.COM]
> Sent: Montag, 13. Oktober 2008 06:04
> To: users@glassfish.dev.java.net
> Subject: RE: Re: Where to set JDBC Connection Idle timeout?
>
> idle-timeout feature will act on connections in the pool (not on the
> connections currently acquired by applications). So, if RA is holding
> the connection (which means, its not in the pool), idle-timeout feature
> will not act on it.
>
> HTH,
> -Jagadish
>
>
> On Sat, 2008-10-11 at 20:14 +0200, Markus Karg wrote:
> > The description of this option says: "The maximum time in seconds
> that a connection can remain idle in the pool. After this time expires,
> the connection is removed from the pool.". There is one question left
> open unanswered: If a RAR asks for a connection from the pool, it can
> keep that connection for a long time (e. g. think of a very long
> running background task processed by the RAR). What will happen if the
> application does not issue SQL commands for a long time? Will this get
> detected by the idletimeout parameter? Or does this timer only run as
> long as the connection is in the pool, not currently acquired by an
> application? (The actual question is: What means IDLE exactly -- REALLY
> UNUSED or NOT ACQUIRED BY THE APPLICATION?).
> >
> > Thanks!
> > Markus
> >
> > > -----Original Message-----
> > > From: Shalini.Muthukrishnan@Sun.COM
> > > [mailto:Shalini.Muthukrishnan@Sun.COM]
> > > Sent: Donnerstag, 9. Oktober 2008 18:37
> > > To: users@glassfish.dev.java.net
> > > Subject: Re: Where to set JDBC Connection Idle timeout?
> > >
> > > It will have immediate effect. The attributes are dynamically
> > > reconfigurable.
> > >
> > > Markus Karg wrote:
> > > > Will I have to reboot GlassFish or will it have immediate effect?
> > > >
> > > >
> > > >> -----Original Message-----
> > > >> From: Shalini.Muthukrishnan@Sun.COM
> > > >> [mailto:Shalini.Muthukrishnan@Sun.COM]
> > > >> Sent: Donnerstag, 9. Oktober 2008 14:24
> > > >> To: users@glassfish.dev.java.net
> > > >> Subject: Re: Where to set JDBC Connection Idle timeout?
> > > >>
> > > >> You could set the --idletimeout attribute of the pool from the
> admin
> > > >> console or use the CLI command :
> > > >>
> > > >> asadmin set
> > > >> server.resources.jdbc-connection-pool.DerbyPool.idle-timeout-in-
> > > >> seconds=10
> > > >>
> > > >> Markus Karg wrote:
> > > >>
> > > >>> My database server cuts down a JDBC connection after it is idle
> for
> > > >>> 240 minutes. As a result, some of my pooled connections throw
> > > >>> SQLException ("Connection broken") after beeing unused for this
> > > time.
> > > >>> How can I tell GlassFish to deal with this? What parameter do I
> > > have
> > > >>> to change in the JDBC pool?
> > > >>>
> > > >>>
> > > >>>
> > > >>> Thanks!
> > > >>>
> > > >>> Markus
> > > >>>
> > > >>>
> > > >>>
> > > >>> QUIPSY QUALITY GmbH & Co. KG
> > > >>>
> > > >>> Ein Unternehmen der MES-Gruppe
> > > >>>
> > > >>> Stuttgarter Strasse 23
> > > >>>
> > > >>> D-75179 Pforzheim
> > > >>>
> > > >>> Tel: 07231-9189-52
> > > >>>
> > > >>> Fax: 07231-9189-59
> > > >>>
> > > >>> www.quipsy.de
> > > >>>
> > > >>> karg@quipsy.de
> > > >>>
> > > >>> Registergericht Mannheim HRA 701214
> > > >>>
> > > >>> Geschäftsführer: Nils Schroeder
> > > >>>
> > > >>>
> > > >>>
> > > >>> Diese E-Mail enthält persönliche, vertrauliche und vor
> Weitergabe
> > > >>> geschützte Informationen und ist ausschließlich für den
> > > vorgesehenen
> > > >>> o.g. Empfänger (Adressaten) bestimmt. Falls Sie diese E-Mail
> > > >>> versehentlich erhalten haben und nicht der vorgesehene
> Empfänger
> > > >>>
> > > >> sind,
> > > >>
> > > >>> bitten wir Sie, die E-Mail und deren Anhänge nicht
> aufzubewahren,
> > > >>> nicht zu vervielfältigen, nicht zu nutzen und nicht
> weiterzugeben.
> > > >>> Bitte informieren Sie uns als Absender über diesen
> > > Zustellungsfehler
> > > >>> und löschen Sie die E-Mail.
> > > >>>
> > > >>>
> > > >>>
> > > >>>
> > > >>>
> > > >>>
> > > >>>
> > > >>> ---------------------------------------------------------------
> ----
> > > --
> > > >>> To unsubscribe, e-mail: users-
> unsubscribe@glassfish.dev.java.net
> > > >>> For additional commands, e-mail: users-
> help@glassfish.dev.java.net
> > > >>>
> > > >>>
> > > >> ----------------------------------------------------------------
> ----
> > > -
> > > >> To unsubscribe, e-mail: users-unsubscribe@glassfish.dev.java.net
> > > >> For additional commands, e-mail: users-
> help@glassfish.dev.java.net
> > > >>
> > > >
> > > >
> > > > -----------------------------------------------------------------
> ----
> > > > To unsubscribe, e-mail: users-unsubscribe@glassfish.dev.java.net
> > > > For additional commands, e-mail: users-
> help@glassfish.dev.java.net
> > > >
> > > >
> > >
> > > -------------------------------------------------------------------
> --
> > > To unsubscribe, e-mail: users-unsubscribe@glassfish.dev.java.net
> > > For additional commands, e-mail: users-help@glassfish.dev.java.net
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscribe@glassfish.dev.java.net
> > For additional commands, e-mail: users-help@glassfish.dev.java.net
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@glassfish.dev.java.net
> For additional commands, e-mail: users-help@glassfish.dev.java.net