Is it normal for Hibernate to initialize the Websphere TransactionManagerLookup twice? I've been having some weird retrieval results from my mappings and I'm thinking it might have something to do with this.
Code:
[11/24/07 15:54:41:960 PST] 1988643c NamingHelper I org.hibernate.util.NamingHelper JNDI InitialContext properties:{}
[11/24/07 15:54:42:073 PST] 1988643c InternalDB2Un I DSRA7021I: DB2 Universal XA datasource custom property, retrieveMessagesFromServerOnGetMessage value is changed from true to false.
[11/24/07 15:54:42:773 PST] 1988643c DatasourceCon I org.hibernate.connection.DatasourceConnectionProvider Using datasource: jdbc/db2devlaix_EFCS
[11/24/07 15:54:42:778 PST] 1988643c ConnectionMan W J2CA0075W: An active transaction should be present while processing method allocateMCWrapper.
[11/24/07 15:54:43:600 PST] 1988643c InternalGener I DSRA8203I: Database product name : DB2/AIX64
[11/24/07 15:54:43:601 PST] 1988643c InternalGener I DSRA8204I: Database product version : SQL09012
[11/24/07 15:54:43:602 PST] 1988643c InternalGener I DSRA8205I: JDBC driver name : IBM DB2 JDBC Universal Driver Architecture
[11/24/07 15:54:43:602 PST] 1988643c InternalGener I DSRA8206I: JDBC driver version : 3.1.57
[11/24/07 15:54:43:622 PST] 1988643c ConnectionMan W J2CA0075W: An active transaction should be present while processing method initializeForUOW.
[11/24/07 15:54:43:659 PST] 1988643c SettingsFacto I org.hibernate.cfg.SettingsFactory RDBMS: DB2/AIX64, version: SQL09012
[11/24/07 15:54:43:660 PST] 1988643c SettingsFacto I org.hibernate.cfg.SettingsFactory JDBC driver: IBM DB2 JDBC Universal Driver Architecture, version: 3.1.57
[11/24/07 15:54:43:732 PST] 1988643c Dialect I org.hibernate.dialect.Dialect Using dialect: org.hibernate.dialect.DB2Dialect
[11/24/07 15:54:43:761 PST] 1988643c TransactionFa I org.hibernate.transaction.TransactionFactoryFactory Transaction strategy: org.hibernate.transaction.JTATransactionFactory
[11/24/07 15:54:43:771 PST] 1988643c NamingHelper I org.hibernate.util.NamingHelper JNDI InitialContext properties:{}
[b]
[i][11/24/07 15:54:43:776 PST] 1988643c TransactionMa I org.hibernate.transaction.TransactionManagerLookupFactory instantiating TransactionManagerLookup: org.hibernate.transaction.WebSphereTransactionManagerLookup
[11/24/07 15:54:43:783 PST] 1988643c WebSphereTran I org.hibernate.transaction.WebSphereTransactionManagerLookup WebSphere 5.1
[11/24/07 15:54:43:783 PST] 1988643c TransactionMa I org.hibernate.transaction.TransactionManagerLookupFactory instantiated TransactionManagerLookup
[11/24/07 15:54:43:784 PST] 1988643c TransactionMa I org.hibernate.transaction.TransactionManagerLookupFactory instantiating TransactionManagerLookup: org.hibernate.transaction.WebSphereTransactionManagerLookup
[11/24/07 15:54:43:784 PST] 1988643c WebSphereTran I org.hibernate.transaction.WebSphereTransactionManagerLookup WebSphere 5.1
[11/24/07 15:54:43:784 PST] 1988643c TransactionMa I org.hibernate.transaction.TransactionManagerLookupFactory instantiated TransactionManagerLookup[/i][/b]
[11/24/07 15:54:43:785 PST] 1988643c SettingsFacto I org.hibernate.cfg.SettingsFactory Automatic flush during beforeCompletion(): enabled
[11/24/07 15:54:43:786 PST] 1988643c SettingsFacto I org.hibernate.cfg.SettingsFactory Automatic session close at end of transaction: enabled
[11/24/07 15:54:43:794 PST] 1988643c SettingsFacto I org.hibernate.cfg.SettingsFactory Scrollable result sets: enabled
Why would it load that manager lookup twice???