Hi ,

We have an application hosted in weblogic 8.1 . Transactions are managed by the container and the driver is XA. Recently we enabled no-proxy lazy loading for association mappings (many-to-one) . But we are getting an exception while accessing the associations. This exception doesn't occur for all associations. Also, this doesnt occur when the same piece of code is run stand alone. Exception comes only in weblogic. Anybody has any clues? Kindly help.

Exception:
org.hibernate.exception.GenericJDBCException: could not initialize lazy properties: [XXXXXXXXXXXXXX]
at org.hibernate.exception.SQLStateConverter.handledNonSpecificException(SQLStateConverter.java:126)
at org.hibernate.exception.SQLStateConverter.convert(SQLStateConverter.java:114)
at org.hibernate.exception.JDBCExceptionHelper.convert(JDBCExceptionHelper.java:66)
at org.hibernate.persister.entity.AbstractEntityPersister.initializeLazyPropertiesFromDatastore(AbstractEntityPersister.java:831)
at org.hibernate.persister.entity.AbstractEntityPersister.initializeLazyProperty(AbstractEntityPersister.java:771)
at org.hibernate.intercept.AbstractFieldInterceptor.intercept(AbstractFieldInterceptor.java:97)
at org.hibernate.intercept.javassist.FieldInterceptorImpl.readObject(FieldInterceptorImpl.java:105)
at com.db.prisma.business.physicalUnitDomain.bo.SubUnit.$javassist_read_lnkPhysicalUnit(SubUnit.java)
at com.db.prisma.business.physicalUnitDomain.bo.SubUnit.getPhysicalUnit(SubUnit.java:674)
at com.db.prisma.business.instructionDomain.proxy.InstructionProxy.getInboundContract(InstructionProxy.java:1224)
...
....
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:224)
at weblogic.kernel.Exe cuteThread.run(ExecuteThread.java:183)
Caused by: java.sql.SQLException: Result set already closed
at weblogic.jdbc.wrapper.ResultSet.getLong(ResultSet.java:516)
at org.hibernate.type.LongType.get(LongType.java:51)
at org.hibernate.type.NullableType.nullSafeGet(NullableType.java:184)
at org.hibernate.type.NullableType.nullSafeGet(NullableType.java:173)
at org.hibernate.type.ManyToOneType.hydrate(ManyToOneType.java:126)

Thanks and Regards,
jivi

Looks like the issue was with connection release. In, JTASessionContext, connection release mode is AFTER_STATEMENT and it didnt go well with lazy loading.

Here is a solution i tried:

Created a new session context class extending JTASessionContext and overrode the method getConnectionReleaseMode() which returns the release mode AFTER_TRANSACTION.

It worked without any issues so far. But the doc says this should not be used in a JTA environment. Can someone please clarify why it should not be used in JTA?

Regards,
Jivi