Our application is using JavaBean Seam components which talk to a Spring service layer. The spring components utilize a Seam-managed Hibernate Session and everything is working just fine. However, we just did some profiling using OptimizeIT Server Trace and two components cited as having open resources when a connection was closed.
The two actions in question are Seam components which are Session-scoped JavaBeans (not EJBs) which perform a data look up and hold on to the search results for the duration of the session. I assume that this is most likely due to the fact that since session scope does not not demarcate a begin or end state, there is a possibility that resources could be left open? But should this be the case?