On Mon, 16 Sep 2013 13:03:03 -0300, Will N. wrote:
Hi,
Hi!
This is a question completely unrelated to Tapestry, so it shouldn't be
posted. In addition, the error is very easy to spot from reading the end
of the stack trace:
Caused by: org.dom4j.DocumentException: Error on line 98 of d
bernate.c3p0.validate=true to force
>> checking of every connection on checkout from the pool.
>>
>>
>>
>>> -Original Message-
>>> From: Angelo Chen [mailto:angelochen...@yahoo.com.hk]
>>> Sent: Sunday, January 11, 2009 22:10
>>> To
;> Sent: Sunday, January 11, 2009 22:10
>> To: users@tapestry.apache.org
>> Subject: Re: Connection Problem
>>
>>
>> Hi,
>>
>> there was a post before in this forum that solves this problem for me, but
>> I
>> can't reme
m the pool.
> -Original Message-
> From: Angelo Chen [mailto:angelochen...@yahoo.com.hk]
> Sent: Sunday, January 11, 2009 22:10
> To: users@tapestry.apache.org
> Subject: Re: Connection Problem
>
>
> Hi,
>
> there was a post before in this forum that
Hi,
there was a post before in this forum that solves this problem for me, but I
can't remember the link, basically, here are the things I added and it's
running with any problem:
org.hibernate.connection.C3P0ConnectionProvider
3
100
20
0
1
1000
I put this in
Hi jonathan,
in the link that I've given. I tried setting up c3po (hibernate
connection pool) idle_test_period and timeout. But it didn't seem to
take an effect. I was following one of the tutorial, and i notice my
META-INF doesn't contain persistence.xml could this have an effect ?
The connection
It sounds like you need to configure your connection pool to issue check
statements before returning a connection (new or existing).
> -Original Message-
> From: abangkis [mailto:abang...@gmail.com]
> Sent: Saturday, January 10, 2009 17:42
> To: Tapestry users
> Subject: Connection Probl
