[JBoss JIRA] (HIBERNATE-131) connection pool not getting released for hibernate 3
by Steve Ebersole (JIRA)
[ https://issues.jboss.org/browse/HIBERNATE-131?page=com.atlassian.jira.plu... ]
Steve Ebersole closed HIBERNATE-131.
------------------------------------
Resolution: Rejected
> connection pool not getting released for hibernate 3
> ----------------------------------------------------
>
> Key: HIBERNATE-131
> URL: https://issues.jboss.org/browse/HIBERNATE-131
> Project: Hibernate Integration
> Issue Type: Bug
> Environment: test
> Reporter: shirish maurya
> Assignee: Steve Ebersole
> Labels: hibernate
>
> Hi , i have a issue reported with jboss 5.1, linux and java based hibernate ,oracle 11.2.3.0 DB,Hibernate 3.3.2.GA
> while load testing for application for jboss on one JVM load balanced on each server ( i.e 2 JVM) heap 1.5 GB
> while running test for 200 users i was able to perform the test successfully .
> as i increase the amount of users to 400 after exact 20 mins of test i start getting errors as unable to get managed connection
> following is the ds.xml file into
> min-pool-size>1</min-pool-size>
> <max-pool-size>64</max-pool-size>
> <query-timeout>300</query-timeout>
> <idle-timeout-minutes>0</idle-timeout-minutes>
> <blocking-timeout-millis>50000</blocking-timeout-millis>
> <use-strict-min>true</use-strict-min>
> <track-statements>true</track-statements>
> <exception-sorter-class-name>org.jboss.resource.adapter.jdbc.vendor.OracleExceptionSorter</exception-sorter-class-name>
> <metadata>
> <type-mapping>Oracle11g</type-mapping>
> </metadata>
> </local-tx-datasource>
> </datasources>
> 2012-05-19 02:54:01,406 INFO [org.hibernate.cfg.SettingsFactory] (main) Automatic flush during beforeCompletion(): disabled
> 2012-05-19 02:54:01,406 INFO [org.hibernate.cfg.SettingsFactory] (main) Automatic session close at end of transaction: disabled
> 2012-05-19 02:54:01,407 INFO [org.hibernate.cfg.SettingsFactory] (main) Scrollable result sets: enabled
> 2012-05-19 02:54:01,407 INFO [org.hibernate.cfg.SettingsFactory] (main) JDBC3 getGeneratedKeys(): disabled
> 2012-05-19 02:54:01,407 INFO [org.hibernate.cfg.SettingsFactory] (main) Connection release mode: auto
> 2012-05-19 02:54:01,408 INFO [org.hibernate.cfg.SettingsFactory] (main) Default batch fetch size: 4
> 2012-05-19 02:54:01,409 INFO [org.hibernate.cfg.SettingsFactory] (main) Generate SQL with comments: disabled
> 2012-05-19 02:54:01,409 INFO [org.hibernate.cfg.SettingsFactory] (main) Order SQL updates by primary key: disabled
> 2012-05-19 02:54:01,409 INFO [org.hibernate.cfg.SettingsFactory] (main) Order SQL inserts for batching: disabled
> 2012-05-19 02:54:01,409 INFO [org.hibernate.cfg.SettingsFactory] (main) Query translator: org.hibernate.hql.ast.ASTQueryTranslatorF
> actory
> 2012-05-19 02:54:01,413 INFO [org.hibernate.hql.ast.ASTQueryTranslatorFactory] (main) Using ASTQueryTranslatorFactory
> 2012-05-19 02:54:01,413 INFO [org.hibernate.cfg.SettingsFactory] (main) Query language substitutions: {}
> 2012-05-19 02:54:01,413 INFO [org.hibernate.cfg.SettingsFactory] (main) JPA-QL strict compliance: disabled
> 2012-05-19 02:54:01,413 INFO [org.hibernate.cfg.SettingsFactory] (main) Second-level cache: disabled
> 2012-05-19 02:54:01,413 INFO [org.hibernate.cfg.SettingsFactory] (main) Query cache: disabled
> 2012-05-19 02:54:01,413 INFO [org.hibernate.cfg.SettingsFactory] (main) Cache region factory : org.hibernate.cache.impl.NoCachingRe
> gionFactory
> 2012-05-19 02:54:01,413 INFO [org.hibernate.cfg.SettingsFactory] (main) Optimize cache for minimal puts: disabled
> 2012-05-19 02:54:01,413 INFO [org.hibernate.cfg.SettingsFactory] (main) Structured second-level cache entries: disabled
> 2012-05-19 02:54:01,422 INFO [org.hibernate.cfg.SettingsFactory] (main) Statistics: disabled
> 2012-05-19 02:54:01,423 INFO [org.hibernate.cfg.SettingsFactory] (main) Deleted entity synthetic identifier rollback: disabled
> 2012-05-19 02:54:01,423 INFO [org.hibernate.cfg.SettingsFactory] (main) Default entity-mode: pojo
> 2012-05-19 02:54:01,423 INFO [org.hibernate.cfg.SettingsFactory] (main) Named query checking : enabled
> error msg
> org.hibernate.exception.GenericJDBCException: Cannot open connection
> 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.exception.JDBCExceptionHelper.convert(JDBCExceptionHelper.java:52)
> at org.hibernate.jdbc.ConnectionManager.openConnection(ConnectionManager.java:449)
> at org.hibernate.jdbc.ConnectionManager.getConnection(ConnectionManager.java:167)
> at org.hibernate.jdbc.AbstractBatcher.prepareQueryStatement(AbstractBatcher.java:161)
> at org.hibernate.loader.Loader.prepareQueryStatement(Loader.java:1577)
> at org.hibernate.loader.Loader.doQuery(Loader.java:696)
> at org.hibernate.loader.Loader.doQueryAndInitializeNonLazyCollections(Loader.java:259)
> at org.hibernate.loader.Loader.loadCollectionBatch(Loader.java:2057)
> at org.hibernate.loader.collection.BatchingCollectionInitializer.initialize(BatchingCollectionInitializer.java:70)
> at org.hibernate.persister.collection.AbstractCollectionPersister.initialize(AbstractCollectionPersister.java:587)
> at org.hibernate.event.def.DefaultInitializeCollectionEventListener.onInitializeCollection(DefaultInitializeCollectionEventL
> istener.java:83)
> at org.hibernate.impl.SessionImpl.initializeCollection(SessionImpl.java:1744)
> at org.hibernate.collection.AbstractPersistentCollection.initialize(AbstractPersistentCollection.java:366)
> at org.hibernate.collection.AbstractPersistentCollection.read(AbstractPersistentCollection.java:108)
> at org.hibernate.collection.PersistentBag.iterator(PersistentBag.java:272)
> at com.pepsico.mya.bonus.domain.verification.VerificationRecordCalcSheet.populateBonusRecordDetails(VerificationRecordCalcSh
> eet.java:153)
> at com.pepsico.mya.bonus.domain.verification.VerificationRecordCalcSheet.getEmployeeRecordsFromForecast(VerificationRecordCa
> lcSheet.java:60)
> at com.pepsico.mya.bonus.domain.verification.VerificationRecordCalcSheet.getCurrentVerificationRecord(VerificationRecordCalc
> Sheet.java:34)
> at com.pepsico.mya.bonus.struts.verification.ViewVerificationSheetAction.execute(ViewVerificationSheetAction.java:168)
> at org.apache.struts.action.RequestProcessor.processActionPerform(RequestProcessor.java:425)
> at org.apache.struts.action.RequestProcessor.process(RequestProcessor.java:228)
> at org.apache.struts.action.ActionServlet.process(ActionServlet.java:1913)
> at org.apache.struts.action.ActionServlet.doGet(ActionServlet.java:449)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:617)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
> at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
> at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
> at com.pepsico.mya.bonus.webapp.RoleModeFilter.doFilter(RoleModeFilter.java:44)
> at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
> at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
> at com.pepsico.mya.bonus.webapp.security.SecurityContextFilter.doFilter(SecurityContextFilter.java:138)
> at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
> at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
> at com.pepsico.mya.bonus.webapp.LocaleFilter.doFilter(LocaleFilter.java:59)
> at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
> at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
> at com.pepsico.mya.bonus.webapp.ApplicationContextFilter.doFilter(ApplicationContextFilter.java:86)
> at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
> at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
> at com.pepsico.mya.bonus.webapp.SessionSettingsFilter.doFilter(SessionSettingsFilter.java:187)
> at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
> at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
> at org.acegisecurity.util.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:265)
> at org.acegisecurity.intercept.web.FilterSecurityInterceptor.invoke(FilterSecurityInterceptor.java:107)
> at org.acegisecurity.intercept.web.FilterSecurityInterceptor.doFilter(FilterSecurityInterceptor.java:72)
> at org.acegisecurity.util.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:275)
> at org.acegisecurity.ui.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:124)
> at org.acegisecurity.util.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:275)
> at org.acegisecurity.providers.anonymous.AnonymousProcessingFilter.doFilter(AnonymousProcessingFilter.java:125)
> at org.acegisecurity.util.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:275)
> at org.acegisecurity.ui.rememberme.RememberMeProcessingFilter.doFilter(RememberMeProcessingFilter.java:142)
> at org.acegisecurity.util.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:275)
> at org.acegisecurity.wrapper.SecurityContextHolderAwareRequestFilter.doFilter(SecurityContextHolderAwareRequestFilter.java:8
> 1)
> at org.acegisecurity.util.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:275)
> at org.acegisecurity.ui.AbstractProcessingFilter.doFilter(AbstractProcessingFilter.java:271)
> at org.acegisecurity.util.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:275)
> at org.acegisecurity.ui.logout.LogoutFilter.doFilter(LogoutFilter.java:110)
> at org.acegisecurity.util.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:275)
> at org.acegisecurity.context.HttpSessionContextIntegrationFilter.doFilter(HttpSessionContextIntegrationFilter.java:249)
> at org.acegisecurity.util.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:275)
> at org.acegisecurity.util.FilterChainProxy.doFilter(FilterChainProxy.java:149)
> at org.acegisecurity.util.FilterToBeanProxy.doFilter(FilterToBeanProxy.java:98)
> at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
> at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
> at org.springframework.orm.hibernate3.support.OpenSessionInViewFilter.doFilterInternal(OpenSessionInViewFilter.java:198)
> at org.springframework.web.filter.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:76)
> at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
> at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
> at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)
> at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
> at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
> at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:235)
> at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
> at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:183)
> at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:95)
> at org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.process(SecurityContextEstablishmentValve.java:126)
> at org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.invoke(SecurityContextEstablishmentValve.java:70)
> at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
> at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
> at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:158)
> at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
> at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:330)
> at org.apache.coyote.ajp.AjpProcessor.process(AjpProcessor.java:436)
> at org.apache.coyote.ajp.AjpProtocol$AjpConnectionHandler.process(AjpProtocol.java:384)
> at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:451)
> at java.lang.Thread.run(Thread.java:662)
> Caused by: org.jboss.util.NestedSQLException: Unable to get managed connection for jdbc/mya/bonusPool; - nested throwable: (javax.re
> source.ResourceException: Unable to get managed connection for jdbc/mya/bonusPool)
> at org.jboss.resource.adapter.jdbc.WrapperDataSource.getConnection(WrapperDataSource.java:95)
> at org.springframework.orm.hibernate3.LocalDataSourceConnectionProvider.getConnection(LocalDataSourceConnectionProvider.java
> :82)
> at org.hibernate.jdbc.ConnectionManager.openConnection(ConnectionManager.java:446)
> ... 84 more
> Caused by: javax.resource.ResourceException: Unable to get managed connection for jdbc/mya/bonusPool
> at org.jboss.resource.connectionmanager.BaseConnectionManager2.getManagedConnection(BaseConnectionManager2.java:441)
> at org.jboss.resource.connectionmanager.TxConnectionManager.getManagedConnection(TxConnectionManager.java:424)
> at org.jboss.resource.connectionmanager.BaseConnectionManager2.allocateConnection(BaseConnectionManager2.java:496)
> at org.jboss.resource.connectionmanager.BaseConnectionManager2$ConnectionManagerProxy.allocateConnection(BaseConnectionManag
> er2.java:941)
> at org.jboss.resource.adapter.jdbc.WrapperDataSource.getConnection(WrapperDataSource.java:89)
> ... 86 more
> Caused by: javax.resource.ResourceException: No ManagedConnections available within configured blocking timeout ( 50000 [ms] )
> at org.jboss.resource.connectionmanager.InternalManagedConnectionPool.getConnection(InternalManagedConnectionPool.java:311)
> at org.jboss.resource.connectionmanager.JBossManagedConnectionPool$BasePool.getConnection(JBossManagedConnectionPool.java:69
> 0)
> at org.jboss.resource.connectionmanager.BaseConnectionManager2.getManagedConnection(BaseConnectionManager2.java:404)
> ... 90 more
> 2012-05-19 03:36:46,258 ERROR [com.pepsico.mya.bonus.exception.ApplicationException] (ajp-lrhisa02.hewitt.com%2F10.20.95.36-12002-17
> 6) Entity is still being used in the application.
> 2012-05-19 03:36:46,262 ERROR [com.pepsico.mya.bonus.exception.BusinessException] (ajp-lrhisa02.hewitt.com%2F10.20.95.36-12002-176)
> Entity is still being used in the application.
> 2012-05-19 03:36:40,158 ERROR [com.pepsico.mya.bonus.struts.calcsheet.CalculationSheetLoadAction] (ajp-lrhisa02.hewitt.com%2F10.20.9
> 5.36-12002-156) Unable to create verification record sheet
> org.hibernate.exception.GenericJDBCException: Cannot open connection
> 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.exception.JDBCExceptionHelper.convert(JDBCExceptionHelper.java:52)
> at org.hibernate.jdbc.ConnectionManager.openConnection(ConnectionManager.java:449)
> at org.hibernate.jdbc.ConnectionManager.getConnection(ConnectionManager.java:167)
> at org.hibernate.jdbc.AbstractBatcher.prepareQueryStatement(AbstractBatcher.java:161)
> at org.hibernate.loader.Loader.prepareQueryStatement(Loader.java:1577)
> at org.hibernate.loader.Loader.doQuery(Loader.java:696)
> at org.hibernate.loader.Loader.doQueryAndInitializeNonLazyCollections(Loader.java:259)
> at org.hibernate.loader.Loader.loadCollectionBatch(Loader.java:2057)
> at org.hibernate.loader.collection.BatchingCollectionInitializer.initialize(BatchingCollectionInitializer.java:70)
> at org.hibernate.persister.collection.AbstractCollectionPersister.initialize(AbstractCollectionPersister.java:587)
> at org.hibernate.event.def.DefaultInitializeCollectionEventListener.onInitializeCollection(DefaultInitializeCollectionEventL
> istener.java:83)
> at org.hibernate.impl.SessionImpl.initializeCollection(SessionImpl.java:1744)
> at org.hibernate.collection.AbstractPersistentCollection.initialize(AbstractPersistentCollection.java:366)
> at org.hibernate.collection.AbstractPersistentCollection.read(AbstractPersistentCollection.java:108)
> at org.hibernate.collection.PersistentBag.iterator(PersistentBag.java:272)
> at com.pepsico.mya.bonus.domain.verification.VerificationRecordCalcSheet.populateBonusRecordDetails(VerificationRecordCalcSh
> eet.java:153)
> at com.pepsico.mya.bonus.domain.verification.VerificationRecordCalcSheet.getEmployeeRecordsFromForecast(VerificationRecordCa
> lcSheet.java:60)
> at com.pepsico.mya.bonus.domain.verification.VerificationRecordCalcSheet.getCurrentVerificationRecord(VerificationRecordCalc
> Sheet.java:34)
> at com.pepsico.mya.bonus.struts.verification.ViewVerificationSheetAction.execute(ViewVerificationSheetAction.java:168)
> at org.apache.struts.action.RequestProcessor.processActionPerform(RequestProcessor.java:425)
> at org.apache.struts.action.RequestProcessor.process(RequestProcessor.java:228)
> at org.apache.struts.action.ActionServlet.process(ActionServlet.java:1913)
> at org.apache.struts.action.ActionServlet.doPost(ActionServlet.java:462)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:637)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
> at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
> at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
> at org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:638)
> at org.apache.catalina.core.ApplicationDispatcher.processRequest(ApplicationDispatcher.java:444)
> at org.apache.catalina.core.ApplicationDispatcher.doForward(ApplicationDispatcher.java:382)
> at org.apache.catalina.core.ApplicationDispatcher.forward(ApplicationDispatcher.java:310)
> at org.apache.struts.action.RequestProcessor.doForward(RequestProcessor.java:1078)
> at org.apache.struts.tiles.TilesRequestProcessor.doForward(TilesRequestProcessor.java:295)
> at org.apache.struts.action.RequestProcessor.processForwardConfig(RequestProcessor.java:396)
> at org.apache.struts.tiles.TilesRequestProcessor.processForwardConfig(TilesRequestProcessor.java:347)
> at org.apache.struts.action.RequestProcessor.process(RequestProcessor.java:232)
> at org.apache.struts.action.ActionServlet.process(ActionServlet.java:1913)
> at org.apache.struts.action.ActionServlet.doPost(ActionServlet.java:462)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:637)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
> at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
> at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
> at com.pepsico.mya.bonus.webapp.RoleModeFilter.doFilter(RoleModeFilter.java:44)
> at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
> at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
> at com.pepsico.mya.bonus.webapp.security.SecurityContextFilter.doFilter(SecurityContextFilter.java:138)
> at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
> at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
> at com.pepsico.mya.bonus.webapp.LocaleFilter.doFilter(LocaleFilter.java:59)
> at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
> at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
> at com.pepsico.mya.bonus.webapp.ApplicationContextFilter.doFilter(ApplicationContextFilter.java:86)
> at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
> at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
> at com.pepsico.mya.bonus.webapp.SessionSettingsFilter.doFilter(SessionSettingsFilter.java:187)
> at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
> at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
> at org.acegisecurity.util.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:265)
> at org.acegisecurity.intercept.web.FilterSecurityInterceptor.invoke(FilterSecurityInterceptor.java:107)
> at org.acegisecurity.intercept.web.FilterSecurityInterceptor.doFilter(FilterSecurityInterceptor.java:72)
> at org.acegisecurity.util.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:275)
> Caused by: org.jboss.util.NestedSQLException: Unable to get managed connection for jdbc/mya/bonusPool; - nested throwable: (javax.re
> source.ResourceException: Unable to get managed connection for jdbc/mya/bonusPool)
> at org.jboss.resource.adapter.jdbc.WrapperDataSource.getConnection(WrapperDataSource.java:95)
> at org.springframework.orm.hibernate3.LocalDataSourceConnectionProvider.getConnection(LocalDataSourceConnectionProvider.java
> :82)
> at org.hibernate.jdbc.ConnectionManager.openConnection(ConnectionManager.java:446)
> ... 99 more
> Caused by: javax.resource.ResourceException: Unable to get managed connection for jdbc/mya/bonusPool
> at org.jboss.resource.connectionmanager.BaseConnectionManager2.getManagedConnection(BaseConnectionManager2.java:441)
> at org.jboss.resource.connectionmanager.TxConnectionManager.getManagedConnection(TxConnectionManager.java:424)
> at org.jboss.resource.connectionmanager.BaseConnectionManager2.allocateConnection(BaseConnectionManager2.java:496)
> at org.jboss.resource.connectionmanager.BaseConnectionManager2$ConnectionManagerProxy.allocateConnection(BaseConnectionManag
> er2.java:941)
> at org.jboss.resource.adapter.jdbc.WrapperDataSource.getConnection(WrapperDataSource.java:89)
> ... 101 more
> Caused by: javax.resource.ResourceException: No ManagedConnections available within configured blocking timeout ( 50000 [ms] )
> at org.jboss.resource.connectionmanager.InternalManagedConnectionPool.getConnection(InternalManagedConnectionPool.java:311)
> at org.jboss.resource.connectionmanager.JBossManagedConnectionPool$BasePool.getConnection(JBossManagedConnectionPool.java:69
> 0)
> at org.jboss.resource.connectionmanager.BaseConnectionManager2.getManagedConnection(BaseConnectionManager2.java:404)
> ... 105 more
> 2012-05-19 03:36:40,198 ERROR [com.pepsico.mya.bonus.struts.calcsheet.CalculationSheetLoadAction] (ajp-lrhisa02.hewitt.com%2F10.20.9
> 5.36-12002-140) Unable to create verification record sheet
> org.hibernate.exception.GenericJDBCException: Cannot open connection
> 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.exception.JDBCExceptionHelper.convert(JDBCExceptionHelper.java:52)
> at org.hibernate.jdbc.ConnectionManager.openConnection(ConnectionManager.java:449)
> at org.hibernate.jdbc.ConnectionManager.getConnection(ConnectionManager.java:167)
> at org.hibernate.jdbc.AbstractBatcher.prepareQueryStatement(AbstractBatcher.java:161)
> at org.hibernate.loader.Loader.prepareQueryStatement(Loader.java:1577)
> at org.hibernate.loader.Loader.doQuery(Loader.java:696)
> at org.hibernate.loader.Loader.doQueryAndInitializeNonLazyCollections(Loader.java:259)
> at org.hibernate.loader.Loader.loadCollectionBatch(Loader.java:2057)
> at org.hibernate.loader.collection.BatchingCollectionInitializer.initialize(BatchingCollectionInitializer.java:70)
> at org.hibernate.persister.collection.AbstractCollectionPersister.initialize(AbstractCollectionPersister.java:587)
> at org.hibernate.event.def.DefaultInitializeCollectionEventListener.onInitializeCollection(DefaultInitializeCollectionEventL
> istener.java:83)
> at org.hibernate.impl.SessionImpl.initializeCollection(SessionImpl.java:1744)
> at org.hibernate.collection.AbstractPersistentCollection.initialize(AbstractPersistentCollection.java:366)
> at org.hibernate.collection.AbstractPersistentCollection.read(AbstractPersistentCollection.java:108)
> at org.hibernate.collection.PersistentBag.iterator(PersistentBag.java:272)
> Please provide some resolution for troubleshooting.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 8 months
[JBoss JIRA] (HIBERNATE-100) All versions of hibernate-tools packages are broken on eclipse-3.4
by Steve Ebersole (JIRA)
[ https://issues.jboss.org/browse/HIBERNATE-100?page=com.atlassian.jira.plu... ]
Steve Ebersole commented on HIBERNATE-100:
------------------------------------------
This is not the correct project to report Hibernate issues under. This Jira project is for reporting issues in the integration between Hibernate and WildFly. To report issues in Hibernate, please use https://hibernate.atlassian.net. Thanks.
This appears to be an issue with Hibernate support inside JBoss Tools (or whatever it is called nowadays). I do not know the proper Jira project for that, [~maxandersen]?
> All versions of hibernate-tools packages are broken on eclipse-3.4
> ------------------------------------------------------------------
>
> Key: HIBERNATE-100
> URL: https://issues.jboss.org/browse/HIBERNATE-100
> Project: Hibernate Integration
> Issue Type: Bug
> Environment: Reproducable on Linux, Windows and Mac OSX
> Reporter: solid Iduncare
> Assignee: Steve Ebersole
>
> All versions of the Jboss hibernate-tools eclipse plugin fail in various ways on eclipse-3.4 (Ganymede). I have obtained various versions of the plugin via the eclipse update sites (both stable and dev) and all have various problems. I first attempted to download the latest from the stable update link (http://download.jboss.org/jbosstools/updates/stable/) . I selected the hibernate tools package for install only. It installs but is unusable. It seems to have no ill effects otherwise. When you attempt to add a hibernate configuration in the hibernate console, you get an exception similar to the followng:
> java.lang.NoClassDefFoundError: org/eclipse/ui/internal/util/SWTResourceUtil
> at org.hibernate.eclipse.console.workbench.xpl.AnyAdaptableLabelProvider.getImage(AnyAdaptableLabelProvider.java:166)
> at org.eclipse.jface.viewers.WrappedViewerLabelProvider.getImage(WrappedViewerLabelProvider.java:117)
> at org.eclipse.jface.viewers.WrappedViewerLabelProvider.update(WrappedViewerLabelProvider.java:165)
> at org.eclipse.jface.viewers.ViewerColumn.refresh(ViewerColumn.java:145)
> at org.eclipse.jface.viewers.AbstractTreeViewer.doUpdateItem(AbstractTreeViewer.java:932)
> at org.eclipse.jface.viewers.AbstractTreeViewer$UpdateItemSafeRunnable.run(AbstractTreeViewer.java:102)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:37)
> at org.eclipse.core.runtime.Platform.run(Platform.java:880)
> at org.eclipse.ui.internal.JFaceUtil$1.run(JFaceUtil.java:48)
> at org.eclipse.jface.util.SafeRunnable.run(SafeRunnable.java:175)
> at org.eclipse.jface.viewers.AbstractTreeViewer.doUpdateItem(AbstractTreeViewer.java:1012)
> at org.eclipse.jface.viewers.StructuredViewer$UpdateItemSafeRunnable.run(StructuredViewer.java:466)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:37)
> at org.eclipse.core.runtime.Platform.run(Platform.java:880)
> at org.eclipse.ui.internal.JFaceUtil$1.run(JFaceUtil.java:48)
> at org.eclipse.jface.util.SafeRunnable.run(SafeRunnable.java:175)
> at org.eclipse.jface.viewers.StructuredViewer.updateItem(StructuredViewer.java:2041)
> at org.eclipse.jface.viewers.AbstractTreeViewer.createTreeItem(AbstractTreeViewer.java:827)
> at org.eclipse.jface.viewers.AbstractTreeViewer.createAddedElements(AbstractTreeViewer.java:340)
> at org.eclipse.jface.viewers.AbstractTreeViewer.internalAdd(AbstractTreeViewer.java:270)
> at org.eclipse.jface.viewers.TreeViewer.internalAdd(TreeViewer.java:652)
> at org.hibernate.eclipse.console.viewers.xpl.MTreeViewer.add(MTreeViewer.java:106)
> at org.eclipse.ui.progress.DeferredTreeContentManager$3.runInUIThread(DeferredTreeContentManager.java:353)
> at org.eclipse.ui.progress.UIJob$1.run(UIJob.java:94)
> at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35)
> at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:133)
> at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3800)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3425)
> at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2382)
> at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2346)
> at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2198)
> at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:493)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:288)
> at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:488)
> at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)
> at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:113)
> at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:193)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:382)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
> at java.lang.reflect.Method.invoke(Unknown Source)
> at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:549)
> at org.eclipse.equinox.launcher.Main.basicRun(Main.java:504)
> at org.eclipse.equinox.launcher.Main.run(Main.java:1236)
> I googled this error and it brought me to a hibernate jira page hosted by atlasian. That Jira page recommended using the latest hibernate tools plugin from the dev update site(http://download.jboss.org/jbosside/hibernatetools/updates/development/) so I did. Now this is where all hell brakes loose. After installing the latest version from this site and restarting eclipse, the JEE perspective is completely disabled. JSP files open in a regular text editor and all attempts to update eclipse fail with this exception:
> Cannot complete the request. See the details.
> Cannot find a solution where both Match[requiredCompatibility:
> org.eclipse.equinox.p2.iu/org.eclipse.emf.ecore.xml/[2.1.0,2.1.0]] and Match[requiredCompatability:
> ....
> In short there is no usable version of hibernate tools for eclipse-3.4.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 8 months
[JBoss JIRA] (HIBERNATE-135) Hibernate 2LC - Infinispan: Query-cache expiration depends on namedCache name
by Steve Ebersole (JIRA)
[ https://issues.jboss.org/browse/HIBERNATE-135?page=com.atlassian.jira.plu... ]
Steve Ebersole commented on HIBERNATE-135:
------------------------------------------
This is not the correct project to report Hibernate issues under. This Jira project is for reporting issues in the integration between Hibernate and WildFly. To report issues in Hibernate, please use https://hibernate.atlassian.net. Thanks.
> Hibernate 2LC - Infinispan: Query-cache expiration depends on namedCache name
> -----------------------------------------------------------------------------
>
> Key: HIBERNATE-135
> URL: https://issues.jboss.org/browse/HIBERNATE-135
> Project: Hibernate Integration
> Issue Type: Bug
> Reporter: Anna Manukyan
> Assignee: Steve Ebersole
>
> Hi,
> I'm writing arquillian tests for Infinispan as a Hibernate 2LC and during writing tests for cache expiration case, I've found out an issue which I cannot explain.
> I'm running tests under Arquillian AS7 managed container. The tests are using external infinispan configuration (not AS7 subsystem). Here I'm defining 2 named caches, one for Hibernate entities another for query cache.
> <namedCache name="local-query">
> <locking isolationLevel="READ_COMMITTED" concurrencyLevel="1000"
> lockAcquisitionTimeout="15000" useLockStriping="false"/>
> <eviction maxEntries="10000" strategy="LRU"/>
> <expiration lifespan="5000" maxIdle="5000" wakeUpInterval="2000" />
> </namedCache>
> <namedCache name="local-entity">
> <locking isolationLevel="READ_COMMITTED" concurrencyLevel="1000"
> lockAcquisitionTimeout="15000" useLockStriping="false"/>
> <eviction maxEntries="10000" strategy="LRU"/>
> <expiration maxIdle="5000" wakeUpInterval="2000" lifespan="5000"/>
> </namedCache>
> In the tests I'm accessing the InfinispanRegionFactory using EntityManager's SessionFactory. From here I am able to access my cache regions. When I'm looking through all available regions I can see that the data is stored in the prefixed regions, so e.g. for my app the queries and entities are stored in testable.war#hib2Lc.local-query and testable.war#hib2Lc.local-entity caches.
> When I'm testing the expiration for "local-query" cache, i.e. I'm performing a query, I'm checking that the query is placed tothe cache. Then I'm waiting for 5 seconds (as it is set in configuration), then I'm checking the cache again and the query is still there. It is not removed from the cache, although it should be expired already.
> When I'm changing the namedCache name from "local-query" to "testable.war#hib2Lc.local-query", this time the expiration works properly so the second time check succeeds.
> The same case works without namedCache name change for entity cache.
> You can find the tests located here: https://github.com/andyuk1986/ispn-hibernate2lc-tests/tree/master/hiberna... - the test is located here: https://github.com/andyuk1986/ispn-hibernate2lc-tests/blob/master/hiberna...
> I'm using infinispan-core-5.1.2.FINAL, hibernate-core-4.1.3.Final, hibernate-infinispan-4.1.3.Final.
> Thanks in advance.
> Best regards,
> Anna.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 8 months
[JBoss JIRA] (HIBERNATE-135) Hibernate 2LC - Infinispan: Query-cache expiration depends on namedCache name
by Steve Ebersole (JIRA)
[ https://issues.jboss.org/browse/HIBERNATE-135?page=com.atlassian.jira.plu... ]
Steve Ebersole closed HIBERNATE-135.
------------------------------------
Resolution: Rejected
> Hibernate 2LC - Infinispan: Query-cache expiration depends on namedCache name
> -----------------------------------------------------------------------------
>
> Key: HIBERNATE-135
> URL: https://issues.jboss.org/browse/HIBERNATE-135
> Project: Hibernate Integration
> Issue Type: Bug
> Reporter: Anna Manukyan
> Assignee: Steve Ebersole
>
> Hi,
> I'm writing arquillian tests for Infinispan as a Hibernate 2LC and during writing tests for cache expiration case, I've found out an issue which I cannot explain.
> I'm running tests under Arquillian AS7 managed container. The tests are using external infinispan configuration (not AS7 subsystem). Here I'm defining 2 named caches, one for Hibernate entities another for query cache.
> <namedCache name="local-query">
> <locking isolationLevel="READ_COMMITTED" concurrencyLevel="1000"
> lockAcquisitionTimeout="15000" useLockStriping="false"/>
> <eviction maxEntries="10000" strategy="LRU"/>
> <expiration lifespan="5000" maxIdle="5000" wakeUpInterval="2000" />
> </namedCache>
> <namedCache name="local-entity">
> <locking isolationLevel="READ_COMMITTED" concurrencyLevel="1000"
> lockAcquisitionTimeout="15000" useLockStriping="false"/>
> <eviction maxEntries="10000" strategy="LRU"/>
> <expiration maxIdle="5000" wakeUpInterval="2000" lifespan="5000"/>
> </namedCache>
> In the tests I'm accessing the InfinispanRegionFactory using EntityManager's SessionFactory. From here I am able to access my cache regions. When I'm looking through all available regions I can see that the data is stored in the prefixed regions, so e.g. for my app the queries and entities are stored in testable.war#hib2Lc.local-query and testable.war#hib2Lc.local-entity caches.
> When I'm testing the expiration for "local-query" cache, i.e. I'm performing a query, I'm checking that the query is placed tothe cache. Then I'm waiting for 5 seconds (as it is set in configuration), then I'm checking the cache again and the query is still there. It is not removed from the cache, although it should be expired already.
> When I'm changing the namedCache name from "local-query" to "testable.war#hib2Lc.local-query", this time the expiration works properly so the second time check succeeds.
> The same case works without namedCache name change for entity cache.
> You can find the tests located here: https://github.com/andyuk1986/ispn-hibernate2lc-tests/tree/master/hiberna... - the test is located here: https://github.com/andyuk1986/ispn-hibernate2lc-tests/blob/master/hiberna...
> I'm using infinispan-core-5.1.2.FINAL, hibernate-core-4.1.3.Final, hibernate-infinispan-4.1.3.Final.
> Thanks in advance.
> Best regards,
> Anna.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 8 months
[JBoss JIRA] (HIBERNATE-18) Problem when path containing the project is too long
by Steve Ebersole (JIRA)
[ https://issues.jboss.org/browse/HIBERNATE-18?page=com.atlassian.jira.plug... ]
Steve Ebersole commented on HIBERNATE-18:
-----------------------------------------
This is not the correct project to report Hibernate issues under. This Jira project is for reporting issues in the integration between Hibernate and WildFly. To report issues in Hibernate, please use https://hibernate.atlassian.net.
I guess maybe you are saying there is an issue here with JBoss Tooling, or whatever it is called nowadays... Not sure the correct project for that. [~maxandersen]?
> Problem when path containing the project is too long
> ----------------------------------------------------
>
> Key: HIBERNATE-18
> URL: https://issues.jboss.org/browse/HIBERNATE-18
> Project: Hibernate Integration
> Issue Type: Bug
> Environment: Eclipse 3.1
> Embeddable EJB 3.0
> Example: microcontainer-deployment
> Reporter: Doink06 Doink06
> Assignee: Gavin King
>
> Hello,
> I have the following configuration:
> - an eclipse workspace, which contains all the examples extrated from "Embeddable EJB 3.0"
> - Each example is transformed into a java project
> - a special project named Jboss is containing Embeddable EJB 3.0 with subdirectories lib/ and conf/
> Case #1
> The workspace is located on my disk at the following place : "D:/EJB3Examples"
> The example microcontainer-deployment is working perfectly
> Case #2
> I moved the workspace to the following place : "D:/Projects/Java/Eclipse3/EJB3Examples"
> The example microcontainer-deployment is crashing.
> WARN 30-08 01:02:38,906 (JBossEntityResolver.java:getLocalEntityName:201) -Entity is not registered, publicId=null systemId=file:/D:/Projects/Java/Eclipse3/EJB3Examples/jboss/conf/bean-deployer_1_0.xsd
> WARN 30-08 01:02:38,953 (SaxJBossXBParser.java:warning:226) -schema_reference.4: Failed to read schema document 'bean-deployer_1_0.xsd', because 1) could not find the document; 2) the document could not be read; 3) the root element of the document is not <xsd:schema>. @ file:/D:/Projects/Java/Eclipse3/EJB3Examples/jboss/conf/embedded-jboss-beans.xml[5,45]
> WARN 30-08 01:02:41,062 (JBossEntityResolver.java:getLocalEntityName:201) -Entity is not registered, publicId=null systemId=file:/D:/Projects/Java/Eclipse3/EJB3Examples/microcontainer-deployment/conf/bean-deployer_1_0.xsd
> WARN 30-08 01:02:41,062 (SaxJBossXBParser.java:warning:226) -schema_reference.4: Failed to read schema document 'bean-deployer_1_0.xsd', because 1) could not find the document; 2) the document could not be read; 3) the root element of the document is not <xsd:schema>. @ file:/D:/Projects/Java/Eclipse3/EJB3Examples/microcontainer-deployment/conf/ejb3-deployment.xml[5,45]
> ERROR 30-08 01:02:45,609 (EjbTimerUtil.java:getTimerService:43) -Unable to initialize timer service
> ----------------------------------------------------------
> Exception in thread "main" javax.ejb.EJBException: null; CausedByException is:
> Unknown entity: org.jboss.tutorial.mcdeploy.Customer
> at org.jboss.ejb3.tx.Ejb3TxPolicy.handleExceptionInOurTx(Ejb3TxPolicy.java:46)
> at org.jboss.aspects.tx.TxPolicy.invokeInOurTx(TxPolicy.java:70)
> at org.jboss.aspects.tx.TxInterceptor$Required.invoke(TxInterceptor.java:134)
> at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:91)
> at org.jboss.aspects.tx.TxPropagationInterceptor.invoke(TxPropagationInterceptor.java:61)
> at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:91)
> at org.jboss.ejb3.stateless.StatelessInstanceInterceptor.invoke(StatelessInstanceInterceptor.java:39)
> at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:91)
> at org.jboss.aspects.security.AuthenticationInterceptor.invoke(AuthenticationInterceptor.java:63)
> at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:91)
> at org.jboss.ejb3.asynchronous.AsynchronousInterceptor.invoke(AsynchronousInterceptor.java:91)
> at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:91)
> at org.jboss.ejb3.stateless.StatelessContainer.localInvoke(StatelessContainer.java:152)
> at org.jboss.ejb3.stateless.StatelessLocalProxy.invoke(StatelessLocalProxy.java:60)
> at $Proxy11.createCustomer(Unknown Source)
> at org.jboss.tutorial.mcdeploy.Main.main(Main.java:32)
> java.lang.IllegalArgumentException: Unknown entity: org.jboss.tutorial.mcdeploy.Customer
> at org.hibernate.ejb.AbstractEntityManagerImpl.persist(AbstractEntityManagerImpl.java:133)
> at org.jboss.ejb3.entity.InjectedEntityManager.persist(InjectedEntityManager.java:97)
> at org.jboss.tutorial.mcdeploy.CustomerDAOBean.createCustomer(CustomerDAOBean.java:28)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:585)
> at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
> at org.jboss.ejb3.AllowedOperationsInterceptor.invoke(AllowedOperationsInterceptor.java:32)
> at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:91)
> at org.jboss.aspects.tx.TxPolicy.invokeInOurTx(TxPolicy.java:66)
> at org.jboss.aspects.tx.TxInterceptor$Required.invoke(TxInterceptor.java:134)
> at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:91)
> at org.jboss.aspects.tx.TxPropagationInterceptor.invoke(TxPropagationInterceptor.java:61)
> at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:91)
> at org.jboss.ejb3.stateless.StatelessInstanceInterceptor.invoke(StatelessInstanceInterceptor.java:39)
> at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:91)
> at org.jboss.aspects.security.AuthenticationInterceptor.invoke(AuthenticationInterceptor.java:63)
> at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:91)
> at org.jboss.ejb3.asynchronous.AsynchronousInterceptor.invoke(AsynchronousInterceptor.java:91)
> at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:91)
> at org.jboss.ejb3.stateless.StatelessContainer.localInvoke(StatelessContainer.java:152)
> at org.jboss.ejb3.stateless.StatelessLocalProxy.invoke(StatelessLocalProxy.java:60)
> at $Proxy11.createCustomer(Unknown Source)
> at org.jboss.tutorial.mcdeploy.Main.main(Main.java:32)
> Case #3
> I have copied the workspace to the following directory "D:\Projects\EJB3Examples"
> It works fine
> Case #4
> I have copied the workspace to the following directory "D:\Projects\Java\EJB3Examples"
> It works fine
> Case #5
> I have copied the workspace to the following directory "D:\Projects\Java\Eclips3\EJB3Examples"
> Without the "e" for eclips3. It works fine
> Case #5
> As soon as I rename the directory Eclips3 into Eclipse3, it crashes ... ?!?
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 8 months
[JBoss JIRA] (HIBERNATE-134) Infinispan custom cache command factory not installed error during app deployment
by Steve Ebersole (JIRA)
[ https://issues.jboss.org/browse/HIBERNATE-134?page=com.atlassian.jira.plu... ]
Steve Ebersole commented on HIBERNATE-134:
------------------------------------------
This is not the correct project to report Hibernate issues under. This Jira project is for reporting issues in the integration between Hibernate and WildFly. To report issues in Hibernate, please use https://hibernate.atlassian.net. Thanks.
IMO this is either a problem with hibernate-infinispan or the WF jipijapa module. [~smarlow] What are your thoughts?
> Infinispan custom cache command factory not installed error during app deployment
> ---------------------------------------------------------------------------------
>
> Key: HIBERNATE-134
> URL: https://issues.jboss.org/browse/HIBERNATE-134
> Project: Hibernate Integration
> Issue Type: Bug
> Environment: Ubuntu 12.04, JBoss AS 7.1.2, Hibernate 4.1.2, Infinispan 5.1.4
> Reporter: Dmitry Chuiko
> Assignee: Steve Ebersole
>
> We use Infinispan as 2LC for Hibernate in a clustered configuration under JBoss 7. So {{persistence.xml}} contains the following line: {code:xml}<property name="hibernate.cache.region.factory_class" value="org.hibernate.cache.infinispan.InfinispanRegionFactory"/>{code}. The following error occurs during app deployment:
> {noformat}12:04:52,859 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-14) MSC00001: Failed to start service jboss.persistenceunit."MOYsklad.ear/sklad-base.jar#MOYsklad": org.jboss.msc.service.StartException in service jboss.persistenceunit."MOYsklad.ear/sklad-base.jar#MOYsklad": Failed to start service
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1767) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) [rt.jar:1.7.0_05]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) [rt.jar:1.7.0_05]
> at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_05]
> Caused by: javax.persistence.PersistenceException: [PersistenceUnit: MOYsklad] Unable to build EntityManagerFactory
> at org.hibernate.ejb.Ejb3Configuration.buildEntityManagerFactory(Ejb3Configuration.java:915)
> at org.hibernate.ejb.Ejb3Configuration.buildEntityManagerFactory(Ejb3Configuration.java:890)
> at org.hibernate.ejb.HibernatePersistence.createContainerEntityManagerFactory(HibernatePersistence.java:74)
> at org.hibernate.ejb.HibernatePersistenceLognex.createContainerEntityManagerFactory(HibernatePersistenceLognex.java:16)
> at org.jboss.as.jpa.service.PersistenceUnitServiceImpl.createContainerEntityManagerFactory(PersistenceUnitServiceImpl.java:162)
> at org.jboss.as.jpa.service.PersistenceUnitServiceImpl.start(PersistenceUnitServiceImpl.java:85)
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]
> ... 3 more
> Caused by: org.hibernate.cache.CacheException: Infinispan custom cache command factory not installed (possibly because the classloader where Infinispan lives couldn't find the Hibernate Infinispan cache provider)
> at org.hibernate.cache.infinispan.InfinispanRegionFactory.getCacheCommandFactory(InfinispanRegionFactory.java:500)
> at org.hibernate.cache.infinispan.InfinispanRegionFactory.startRegion(InfinispanRegionFactory.java:379)
> at org.hibernate.cache.infinispan.InfinispanRegionFactory.buildEntityRegion(InfinispanRegionFactory.java:212)
> at org.hibernate.internal.SessionFactoryImpl.<init>(SessionFactoryImpl.java:347)
> at org.hibernate.cfg.Configuration.buildSessionFactory(Configuration.java:1741)
> at org.hibernate.ejb.EntityManagerFactoryImpl.<init>(EntityManagerFactoryImpl.java:93)
> at org.hibernate.ejb.Ejb3Configuration.buildEntityManagerFactory(Ejb3Configuration.java:905)
> ... 10 more
> {noformat}
> This issue takes place because context {{ClassLoader}} is substituted in {{org.hibernate.ejb.Ejb3Configuration#configure}}. So Infinispan can not find {{org.infinispan.commands.module.ModuleCommandExtensions}} realization from {{hibernate-infinispan}} module in {{org.infinispan.util.ModuleProperties#loadModuleCommandHandlers}} method.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 8 months
[JBoss JIRA] (HIBERNATE-112) Schema auto generation creates columns in alphabetical order for compound primary keys
by Steve Ebersole (JIRA)
[ https://issues.jboss.org/browse/HIBERNATE-112?page=com.atlassian.jira.plu... ]
Steve Ebersole commented on HIBERNATE-112:
------------------------------------------
This is not the correct project to report Hibernate issues under. This Jira project is for reporting issues in the integration between Hibernate and WildFly. To report issues in Hibernate, please use https://hibernate.atlassian.net. Thanks.
Also the referenced issue in the proper Jira system indicates that the issue was resolved.
> Schema auto generation creates columns in alphabetical order for compound primary keys
> --------------------------------------------------------------------------------------
>
> Key: HIBERNATE-112
> URL: https://issues.jboss.org/browse/HIBERNATE-112
> Project: Hibernate Integration
> Issue Type: Bug
> Environment: JBoss AS 5.0.1 with EJB3 entities / Hibernate with MySQL Server 5.1
> Reporter: Jochen Reinhardt
> Assignee: Steve Ebersole
>
> Schema auto generation creates columns in alphabetical order.
> I would not mind that, but it also affects the creation of primary key indexes. These are rather useless from a database point of view, as the database will only be able to use an index for searching if the columns that are searched for are a prefix of the key. Alphabetical column order is not what one expects. Instead, I would want that my columns are sorted in the same way they appear in my annotated POJO class. I hope I am not missing some simple configuration issue...
> I have a rather complex setup with my entities and relations, using compound primary keys and references. In an entity that maps a complex m:n relationship between two entities with additional properties... Please let me know if you need more details.
> I'm using @Embedded on a primary key class and @EmbeddedId in all my entities.
> I already posted in the Hibernate forums, but I did not get an answer yet, nor did I find any information about my specific problem. The only peace of information I found so far is, that the alphabetical column sort order was introduced because of some issues related to foreign key constraints in clustered environments. As it is already somewhat urgent, I decided to submit a bug report.
> A colleague of mine found the following in some other forum and I looked up in the source code, too - it's still there. But I do not know if it is correct in general and it only does not work for my setup.
> Cite:
> Hi all,
> I am using EJB3 with hibernate.hbm2ddl.auto=update. I notice the primary keys is been created in database in alphabetic order and not like the order defined at the embedded class. I look at the source code of Hibernate Annotations and found in AnnotationBinder class a Collections.sort at line 1024 with this comment:
> //order so that property are used in the same order when binding native query
> In my project I have primary keys with 4 or 5 fields, and many queries use only 2 ou 3 of them and are running very slow, and the cause was the wrong order of the primary keys in the database.
> I guest that sort is for fixing another bug, but is really annoying, because I need to look each primary key and adjust its order by hand.
> Is there another solution?
> Thanks in advance.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 8 months
[JBoss JIRA] (HIBERNATE-112) Schema auto generation creates columns in alphabetical order for compound primary keys
by Steve Ebersole (JIRA)
[ https://issues.jboss.org/browse/HIBERNATE-112?page=com.atlassian.jira.plu... ]
Steve Ebersole closed HIBERNATE-112.
------------------------------------
Resolution: Rejected
> Schema auto generation creates columns in alphabetical order for compound primary keys
> --------------------------------------------------------------------------------------
>
> Key: HIBERNATE-112
> URL: https://issues.jboss.org/browse/HIBERNATE-112
> Project: Hibernate Integration
> Issue Type: Bug
> Environment: JBoss AS 5.0.1 with EJB3 entities / Hibernate with MySQL Server 5.1
> Reporter: Jochen Reinhardt
> Assignee: Steve Ebersole
>
> Schema auto generation creates columns in alphabetical order.
> I would not mind that, but it also affects the creation of primary key indexes. These are rather useless from a database point of view, as the database will only be able to use an index for searching if the columns that are searched for are a prefix of the key. Alphabetical column order is not what one expects. Instead, I would want that my columns are sorted in the same way they appear in my annotated POJO class. I hope I am not missing some simple configuration issue...
> I have a rather complex setup with my entities and relations, using compound primary keys and references. In an entity that maps a complex m:n relationship between two entities with additional properties... Please let me know if you need more details.
> I'm using @Embedded on a primary key class and @EmbeddedId in all my entities.
> I already posted in the Hibernate forums, but I did not get an answer yet, nor did I find any information about my specific problem. The only peace of information I found so far is, that the alphabetical column sort order was introduced because of some issues related to foreign key constraints in clustered environments. As it is already somewhat urgent, I decided to submit a bug report.
> A colleague of mine found the following in some other forum and I looked up in the source code, too - it's still there. But I do not know if it is correct in general and it only does not work for my setup.
> Cite:
> Hi all,
> I am using EJB3 with hibernate.hbm2ddl.auto=update. I notice the primary keys is been created in database in alphabetic order and not like the order defined at the embedded class. I look at the source code of Hibernate Annotations and found in AnnotationBinder class a Collections.sort at line 1024 with this comment:
> //order so that property are used in the same order when binding native query
> In my project I have primary keys with 4 or 5 fields, and many queries use only 2 ou 3 of them and are running very slow, and the cause was the wrong order of the primary keys in the database.
> I guest that sort is for fixing another bug, but is really annoying, because I need to look each primary key and adjust its order by hand.
> Is there another solution?
> Thanks in advance.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 8 months