Did you make sure that when using c3p0 it actually was enabled and that you
used the validation query? and set this property:
http://stackoverflow.com/questions/1652676/hibernate-c3p0-broken-pipe
property
Hi Martin,
thanks for you suggestion. I'll make more test in this direction. Right know
I temporaly solved the problem avoiding the use of the c3p0 library and
having a thread that every hour keep the connection awake. Of course I'll do
test to optimize the app based on your suggestion.
Thanks a
c3p0 and other connection pools are pretty much deprecated with
hibernate 3.6 (as we discovered). com.jolbox.bonecp is a competent
replacement.
Martijn
On Fri, Jan 7, 2011 at 11:42 AM, LucHub luca.abb...@luchub.com wrote:
Hi Martin,
thanks for you suggestion. I'll make more test in this
Hi, I tried to kill the process but I found nothing of strange. Right now I
think that the problem is probably solved. I throw away a library that I
used together with Hibernate (the c3p0 library) that I put ther essentially
for autoReconnection problems of the JDBC mysql driver. Avoiding this
it sounds like you were leaking DB connections
Thread dump easily will show you this problem. You'll see threads trying to
acquire a DB connection and will wait until some of the previous acquired
connections is returned to the pool.
On Thu, Jan 6, 2011 at 12:27 PM, LucHub luca.abb...@luchub.com
Hi Martin,
What do you exactly mean for dump the threads? I am almost a newbie, I
cannot find any document that examplin this.
I made a few more test logging Wicket. To have the web site going down I
need a few hits (close each other) on a bookmarkablepagelink.
Here (
Hi, thanks for the reply.
Honestly I read a little bit around and using WicketServlet instead of
wicketFilter is a kind of not reccomended. I would like to go for teh filter
way, but thanks a lot for teh reply.
Part of the reason is that I think that is impossible that a wicket app goes
down
If you use some kind of Unix then run: kill -3 process id of
tomcat/jetty/...)
This will dump the threads' stack traces in the process standard out
(somewhere in the log files).
This way you can see whether there are threads waiting for something.
Making 20 requests and stopping responding could
Any indications what exactly is the problem ?
Anything in the logs? Any jvm crashes?
On Tue, Jan 4, 2011 at 7:38 PM, LucHub luca.abb...@luchub.com wrote:
Hi all,
I recently created a wicket 1.4.12 web site and I deployed it on Apache
Tomcat 7 on Ubuntu Server. What happen is that if I hit
Hi, thank you for the fast reply,
Nothing strange from tomcat logs, also the server is not out of CPU or
memory.
I still have to enable wicket logs and check with a non Hibernate app (i
omitted I'm using Hibernate)
I'll post. Thanks again
--
View this message in context:
dump the threads
maybe there is a deadlock
On Tue, Jan 4, 2011 at 9:25 PM, LucHub luca.abb...@luchub.com wrote:
Hi, thank you for the fast reply,
Nothing strange from tomcat logs, also the server is not out of CPU or
memory.
I still have to enable wicket logs and check with a non
Just a hunchtry WicketServlet instead of WicketFilter (in web.xml)...
From: LucHub luca.abb...@luchub.com
To: users@wicket.apache.org
Date: 01/04/2011 03:26 PM
Subject:Re: Wicket web site down with a few hits
Hi, thank you for the fast reply,
Nothing strange from tomcat
12 matches
Mail list logo
