Dear removeps-groups,
Thanks for the links. But in answer to the issues below:
chmod 600 is not sufficient because the admin of my website should
not be able to see the passwords either. And if you're using a web
hosting service, all the more reason.
The decryption algorithm may need a
Dear removeps-groups,
Thanks for the links. But in answer to the issues below:
chmod 600 is not sufficient because the admin of my website should
not be able to see the passwords either. And if you're using a web
hosting service, all the more reason.
The decryption algorithm may need a
Yeah, the validationQuery seems to have fixed the problem. I guess a full week
of non-use of the website should tell for sure.
--- On Tue, 12/9/08, Kees Jan Koster [EMAIL PROTECTED] wrote:
From: Kees Jan Koster [EMAIL PROTECTED]
Subject: Re: configure JNDI to avoid error Last packet sent to
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 come
-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
{
Connection
Thanks for the links. But in answer to the issues below:
chmod 600 is not sufficient because the admin of my website should not be able
to see the passwords either. And if you're using a web hosting service, all
the more reason.
The decryption algorithm may need a license key which is
But I need to re-trigger the operation (such as an INSERT statement), and also
to remove the dead connection from the pool or reconnect it.
--- On Sat, 12/6/08, Ken Bowen [EMAIL PROTECTED] wrote:
From: Ken Bowen [EMAIL PROTECTED]
Subject: Re: configure JNDI to avoid error Last packet sent to
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 it is
-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 and
