I asked my provider and they didn't change anything. They pointed out the
possible absence of autoReconnect=true in my JDBC url. Does anybody knows if
that might help. I'd rather have that than a ping query for every call.
Thanks,
Dennis
2006/1/4, Dennis Bekkering [EMAIL PROTECTED]:
Thomas,
On 1/5/06, Dennis Bekkering [EMAIL PROTECTED] wrote:
I asked my provider and they didn't change anything. They pointed out the
possible absence of autoReconnect=true in my JDBC url. Does anybody knows if
that might help. I'd rather have that than a ping query for every call.
Hmm,
Sorry for multi posting,
Otherwise, the version we use is 1.03
Jakob Braeuchi wrote:
hi nicolas,
i recommend not to cross-post, and to post the same message only once ;)
further i recommend to tell us the version of ojb you're using.
thank
jakob
--
Nicolas DELAHAYE
hi nicolas,
i recommend not to cross-post, and to post the same message only once ;)
further i recommend to tell us the version of ojb you're using.
thank
jakob
[EMAIL PROTECTED] schrieb:
Hi,
It seems when i use a n-m relation to a subclassed object, the sql produced
by ojb is not good.
hi nicolas,
ojb just release 1.0.4. could you please try this as well ?
jakob
DELAHAYE Nicolas schrieb:
Sorry for multi posting,
Otherwise, the version we use is 1.03
Jakob Braeuchi wrote:
hi nicolas,
i recommend not to cross-post, and to post the same message only once ;)
further i
i added
testOnBorrow=true
validationQuery=SELECT 1
to the descriptor, I'l wait and see what happens.
Dennis
2006/1/5, Thomas Dudziak [EMAIL PROTECTED]:
On 1/5/06, Dennis Bekkering [EMAIL PROTECTED] wrote:
I asked my provider and they didn't change anything. They