license server,
> you've wasted
> your time. Sorry. :-)
>
> Have you managed to fix your connection pool issues?
>
> Kees Jan
>
> > --- On Sun, 12/7/08, Kees Jan Koster
> <[EMAIL PROTECTED]> wrote:
> >
> >> From: Kees Jan Koster &
a license server, you've wasted
your time. Sorry. :-)
Have you managed to fix your connection pool issues?
Kees Jan
--- On Sun, 12/7/08, Kees Jan Koster <[EMAIL PROTECTED]> wrote:
From: Kees Jan Koster <[EMAIL PROTECTED]>
Subject: Re: configure JNDI to avoid error "Last
a license server, you've wasted
your time. Sorry. :-)
Have you managed to fix your connection pool issues?
Kees Jan
--- On Sun, 12/7/08, Kees Jan Koster <[EMAIL PROTECTED]> wrote:
From: Kees Jan Koster <[EMAIL PROTECTED]>
Subject: Re: configure JNDI to avoid error "Last
ure JNDI to avoid error "Last packet sent to the server
> was x ms ago"
> To: "Tomcat Users List"
> Date: Sunday, December 7, 2008, 12:39 AM
> Hmm. Lots of trouble for a file that you can just chmod 600
> to avoid
> this whole issue. But that's jus
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Bob (why not?),
[EMAIL PROTECTED] wrote:
> The second message -- connection has already been closed -- most likely
> arises from my code structure, which is:
>
> Connection connection = null;
> PreparedStatement prepStmt = null;
> try
> {
>Conne
Dear removeps-groups,
How to configure JNDI in order to avoid the error "Last packet sent
to the server was x ms ago."? I've seen two other errors which
seem to be from the same cause: "Communications link failure" and
"Connection.close90 has already been called".
This is what I've c
error "Last packet sent to the server
> was x ms ago"
> To: "Tomcat Users List"
> Date: Saturday, December 6, 2008, 4:39 PM
> Can't you deal with the connection being closed in your
> finally block
> by using this code:
>
> if (connection != n
Can't you deal with the connection being closed in your finally block
by using this code:
if (connection != null && !connection.isClosed()) connection.close();
On Dec 6, 2008, at 6:50 PM, [EMAIL PROTECTED] wrote:
The second message -- connection has already been closed -- most
likely arise
tion;
}
}
--- On Fri, 12/5/08, Christopher Schultz <[EMAIL PROTECTED]> wrote:
> From: Christopher Schultz <[EMAIL PROTECTED]>
> Subject: Re: configure JNDI to avoid error "Last packet sent to the server
> was x ms ago"
> To: "Tomcat Users List"
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
To whom it may concern,
[EMAIL PROTECTED] wrote:
> How to configure JNDI in order to avoid the error "Last packet sent
> to the server was x ms ago."? I've seen two other errors which
> seem to be from the same cause: "Communications link failure
How to configure JNDI in order to avoid the error "Last packet sent to the
server was x ms ago."? I've seen two other errors which seem to be from
the same cause: "Communications link failure" and "Connection.close90 has
already been called".
This is what I've come up with, but wonder if i
11 matches
Mail list logo
