Hi all, I have been given the task of maintaining an app built on hibernate and jboss and I am having some issues with connection pooling.
There is an existing process which clones sections from the database and recurses down through subsections to create this clone. It works fine when there are small numbers of subsections to clone however I get the above error when it's a more substantial size. Checking the database it looks like for each object update it is triggering a new connection to postgresql even though they are all using the same session object in the code. I am having serious trouble tracking down where I should be looking for these bugs, is it normal behaviour for the same session object in code to trigger new database connections or is something going screwy here? any guidance of things to try to debug this would be greatly appreciated. Thanks -- Matt View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4041747#4041747 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4041747 _______________________________________________ jboss-user mailing list [email protected] https://lists.jboss.org/mailman/listinfo/jboss-user
