We are using JBoss Portal version 2.6.5SP1 in our comopany. We didn't change the configuration of JBoss Portal that come with a default option of EHCache for the portal DB. I also checked the configuration of the hibernate and it seems correct which mean that the first\second levels are true and everything there seems fine.
The issue is that we have some gaps in our log files and we found out that the times spent on the Jboss Portal DB. The issue is that in every login we spend at least 300ms for it and also there are some places during the login that we spend the same amount of time on them (another 2-3 times).
When I checked the Hibernate logs I found out those line (this is from the first login, and those are just samples from 2000 lines):
[org.hibernate.jdbc.AbstractBatcher] about to open PreparedStatement (open PreparedStatements: 0, globally: 0)
[org.hibernate.SQL] select displaynam0_.INSTANCE_PK as INSTANCE1_0_, displaynam0_.TEXT as TEXT0_, displaynam0_.LOCALE as LOCALE0_ from JBP_PORTAL_OBJECT_DNAMES displaynam0_ where displaynam0_.INSTANCE_PK=?
[org.hibernate.cache.EhCache]: key: org.jboss.portal.core.impl.model.portal.PortalImpl.windowStates#119 \\this line showen many times with diff keys
[org.hibernate.loader.Loader]: [user:] [context:] result row: EntityKey[org.jboss.portal.core.impl.model.portal.PortalObjectImpl#95] \\this line showen many times with diff rows
and finally I see those 2 lines at the end:
[org.hibernate.engine.StatefulPersistenceContext]: initializing non-lazy collections
[org.hibernate.loader.Loader]: done loading collection
I understand that at those times we are loading things from the DB but: a. Why this is happenned every time instead of using EHCache. b. how I can avoid it or minimize the times that spend.
* I uploaded the full log file in case that you want to see everything
Thanks for any response!