Hello

I have a grid in my web application and after viewing a few pages correctly everything freezes. This is the only place in my application this happens.
I use Spring, so I don't create manualy my sessions.
I use something like this:
query = getSession().createQuery(sqlQuery).setFirstResult(startWith).
setMaxResults(maxResults);
I use MySql and the grid displays only 10 rows at a time of a total of just 500.
If I stop right befot the "blocking" page and do something else, also the application freezes.

Here is the log:
[DEBUG] (SessionImpl.java:555) opened session
[DEBUG] (SessionImpl.java:1526) find: select ...
[DEBUG] (QueryParameters.java:109) named parameters: {}
[DEBUG] (SessionImpl.java:2242) flushing session
[DEBUG] (SessionImpl.java:2435) Flushing entities and processing referenced coll
ections
[DEBUG] (SessionImpl.java:2776) Processing unreferenced collections
[DEBUG] (SessionImpl.java:2790) Scheduling collection removes/(re)creates/update
s
[DEBUG] (SessionImpl.java:2266) Flushed: 0 insertions, 0 updates, 0 deletions to
0 objects
[DEBUG] (SessionImpl.java:2271) Flushed: 0 (re)creations, 0 updates, 0 removals
to 0 collections
[DEBUG] (SessionImpl.java:1814) Dont need to execute flush
[DEBUG] (QueryTranslator.java:199) HQL: select ...
[DEBUG] (QueryTranslator.java:200) SQL: select ...
[DEBUG] (BatcherImpl.java:196) about to open: 0 open PreparedStatements, 0 open
ResultSets

Please, at least tell me where should I start looking for the solution of this problem.
What parameters should I watch.

Nobody knows.

:)
Maybe I just run out of resources beacause of my incorrect use of Hibernate.
Is there a way to monitor that?

Use your profiler.

Hm... Found the problem.
Indeed very incorrect use of hibernate.
I don't know where was I thinking when I wrote that strange (understatement) code...

Anyway, thanks for beening here. I have to admit it's one of promptest support system I've seen