Created attachment 738872 [details] server.log Description of problem: The following error is found during the deployment of kie-ide.war when using JDK 6. 16:29:00,818 ERROR [org.jboss.msc.service.fail] (ServerService Thread Pool -- 53) MSC000001: Failed to start service jboss.persistenceunit."kie-ide.war#org.jbpm.domain": org.jboss.msc.service.StartException in service jboss.persistenceunit."kie-ide.war#org.jbpm.domain": javax.persistence.PersistenceException: [PersistenceUnit: org.jbpm.domain] Unable to build EntityManagerFactory at org.jboss.as.jpa.service.PersistenceUnitServiceImpl$1.run(PersistenceUnitServiceImpl.java:103) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [rt.jar:1.6.0_24] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [rt.jar:1.6.0_24] at java.lang.Thread.run(Thread.java:662) [rt.jar:1.6.0_24] at org.jboss.threads.JBossThread.run(JBossThread.java:122) Caused by: javax.persistence.PersistenceException: [PersistenceUnit: org.jbpm.domain] Unable to build EntityManagerFactory at org.hibernate.ejb.Ejb3Configuration.buildEntityManagerFactory(Ejb3Configuration.java:930) at org.hibernate.ejb.Ejb3Configuration.buildEntityManagerFactory(Ejb3Configuration.java:904) at org.hibernate.ejb.HibernatePersistence.createContainerEntityManagerFactory(HibernatePersistence.java:92) at org.jboss.as.jpa.service.PersistenceUnitServiceImpl.createContainerEntityManagerFactory(PersistenceUnitServiceImpl.java:200) at org.jboss.as.jpa.service.PersistenceUnitServiceImpl.access$600(PersistenceUnitServiceImpl.java:57) at org.jboss.as.jpa.service.PersistenceUnitServiceImpl$1.run(PersistenceUnitServiceImpl.java:99) ... 4 more Caused by: org.hibernate.service.spi.ServiceException: Unable to create requested service [org.hibernate.engine.spi.CacheImplementor] at org.hibernate.service.internal.AbstractServiceRegistryImpl.createService(AbstractServiceRegistryImpl.java:186) at org.hibernate.service.internal.AbstractServiceRegistryImpl.initializeService(AbstractServiceRegistryImpl.java:150) at org.hibernate.service.internal.AbstractServiceRegistryImpl.getService(AbstractServiceRegistryImpl.java:131) at org.hibernate.internal.SessionFactoryImpl.<init>(SessionFactoryImpl.java:264) at org.hibernate.cfg.Configuration.buildSessionFactory(Configuration.java:1750) at org.hibernate.ejb.EntityManagerFactoryImpl.<init>(EntityManagerFactoryImpl.java:94) at org.hibernate.ejb.Ejb3Configuration.buildEntityManagerFactory(Ejb3Configuration.java:920) ... 9 more Caused by: org.hibernate.cache.NoCacheRegionFactoryAvailableException: Second-level cache is used in the application, but property hibernate.cache.region.factory_class is not given, please either disable second level cache or set correct region factory class name to property hibernate.cache.region.factory_class (and make sure the second level cache provider, hibernate-infinispan, for example, is available in the classpath). at org.hibernate.cache.internal.NoCachingRegionFactory.buildTimestampsRegion(NoCachingRegionFactory.java:87) at org.hibernate.cache.spi.UpdateTimestampsCache.<init>(UpdateTimestampsCache.java:62) at org.hibernate.internal.CacheImpl.<init>(CacheImpl.java:72) at org.hibernate.engine.spi.CacheInitiator.initiateService(CacheInitiator.java:40) at org.hibernate.engine.spi.CacheInitiator.initiateService(CacheInitiator.java:35) at org.hibernate.service.internal.SessionFactoryServiceRegistryImpl.initiateService(SessionFactoryServiceRegistryImpl.java:91) at org.hibernate.service.internal.AbstractServiceRegistryImpl.createService(AbstractServiceRegistryImpl.java:176) ... 15 more Version-Release number of selected component (if applicable): BPMS 6.0.0 DR3 How reproducible: Steps to Reproduce: 1.Using oracle JDK 1.6.0_24+ to deploy kie-ide.war into EAP 6.1 2.Error happens during the deployment. 3. Noticed that there is no such issue when using oracle JDK7 Actual results: Expected results: Additional info:
Have to correct the report issue: The problem only happen to oracle JDK 1.6.0_24, not happen to oracle JDK 1.6.0_43. cc Lee What is the JRE you are using for reproducing the problem. I saw it is "java.lang.Thread.run(Thread.java:680) [classes.jar:1.6.0_43]" in your email.
It doesn't seem to be dependent on the jdk used - happened to me once with some 1.6 jdk, when I stopped the server and started it again, the error was gone. It seems to be a random bug.
Ryan, for me it's, java version "1.6.0_43" Java(TM) SE Runtime Environment (build 1.6.0_43-b01-447-11M4203)
(In reply to comment #2) > It doesn't seem to be dependent on the jdk used - happened to me once with > some 1.6 jdk, when I stopped the server and started it again, the error was > gone. > > It seems to be a random bug. Agree, I can even reproduce this by 1.7 jdk. This bug happens pretty randomly. But it is reproducable to me if you just try to restart the server for a couple of times. e
I have experienced this bug only 2-3 times from about 15 deployments of DR4 on jdk 1.7, EAP 6.1.Beta. Nevertheless, I got a hint that it might be caused by an improperly configured dependency. EAP 6 loads modules in parallel and it might happen that some module not listed as a dependency is actually required by the deployment but not loaded yet.
Issue disappeared for me after I added these dependencies to the module.xml: <dependencies> <module name="org.infinispan.cachestore.jdbc"/> <module name="org.hibernate"/> </dependencies> (file <server_dir>/modules/system/layers/bpms/org/jboss/as/product/bpms/module.xml for the bpms product)
My apologies, after trying a few times successfully, posting the above comment and trying again, it started failing again.
do you deploy dashbuilder web app on the same server? This was observed when both applications are deployed at the same time and currently workaround for this is to deploy first kie-ide and then dash builder application - which usually mean deploy it (dashbuilder) after application server is up. Alternatively we could try to enforce the given order of deployments (http://stackoverflow.com/questions/13364735/jboss-as-7-deploying-wars-in-certain-order)
Hi Maciej, Yes I deployed them both at the same time. I moved onto a new machine yesterday (not because of this issue) and I haven't experienced this issue yet on the new machine. Having said that, I just removed the dashbuilder war from the deployments directory on the old machine to test this, and kie-ide deployed and I was able to log in. Lee
Our installation procedure is to unzip the bpms distribution we provide which includes both the wars on top of EAP. So we expect customers to have both wars deployed at the same time when starting EAP.
The issue with dash-builder and kie-wb war when deployed together has been solved by upgrading dash-builder to hibernate4.
DR6: After multiple restarts with both business-central and dashbuilder deployed in parallel, this issue still has not manifested). Seems to be fixed.
Hi Zuzana, Doc Text has been added. Can you please review the CCFR.