One Star

Issues while attempting to deploy drools-guvnor to JBoss 7.0.2-as

I'm attempting to deploy drools-guvnor.war to a JBoss 7.0.2-as server, standalone mode, (with JDK 1.6.0_27-64) by uploading the war in to the system via the JBoss Console and then enabling the deployment. During the deployment phase I'm receiving the errors (below) in the server.log.
The top portion of the error output is referring to errors with the jar files within the war file, which I haven't extracted or otherwise modified so not sure the best way to try and resolve this error. I need to deploy the drools engine to a few other servers and am trying to ensure it's stable on this server, and has a reproducible stable deployment method with which to use on any subsequent instances.
After the first failed deployment attempt, I located the JSF library files which are required for Tomcat deployment and copied them to <JBOSS>/standalone/lib in the event that those libraries were part of the issue. They don't appear to be.
Any ideas?
-----------
16:01:59,266 INFO (MSC service thread 1-4) Starting deployment of "drools-guvnor.war"
16:02:08,017 INFO (Finalizer) HHH00030:Cleaning up connection pool
16:02:08,187 WARN (MSC service thread 1-1) Class Path entry derbyLocale_de_DE.jar in "/content/drools-guvnor.war/WEB-INF/lib/derby-10.2.1.6.jar" does not point to a valid jar for a Class-Path reference.
16:02:08,187 WARN (MSC service thread 1-1) Class Path entry derbyLocale_es.jar in "/content/drools-guvnor.war/WEB-INF/lib/derby-10.2.1.6.jar" does not point to a valid jar for a Class-Path reference.
16:02:08,187 WARN (MSC service thread 1-1) Class Path entry derbyLocale_fr.jar in "/content/drools-guvnor.war/WEB-INF/lib/derby-10.2.1.6.jar" does not point to a valid jar for a Class-Path reference.
16:02:08,187 WARN (MSC service thread 1-1) Class Path entry derbyLocale_it.jar in "/content/drools-guvnor.war/WEB-INF/lib/derby-10.2.1.6.jar" does not point to a valid jar for a Class-Path reference.
16:02:08,187 WARN (MSC service thread 1-1) Class Path entry derbyLocale_ja_JP.jar in "/content/drools-guvnor.war/WEB-INF/lib/derby-10.2.1.6.jar" does not point to a valid jar for a Class-Path reference.
16:02:08,188 WARN (MSC service thread 1-1) Class Path entry derbyLocale_ko_KR.jar in "/content/drools-guvnor.war/WEB-INF/lib/derby-10.2.1.6.jar" does not point to a valid jar for a Class-Path reference.
16:02:08,188 WARN (MSC service thread 1-1) Class Path entry derbyLocale_pt_BR.jar in "/content/drools-guvnor.war/WEB-INF/lib/derby-10.2.1.6.jar" does not point to a valid jar for a Class-Path reference.
16:02:08,188 WARN (MSC service thread 1-1) Class Path entry derbyLocale_zh_CN.jar in "/content/drools-guvnor.war/WEB-INF/lib/derby-10.2.1.6.jar" does not point to a valid jar for a Class-Path reference.
16:02:08,188 WARN (MSC service thread 1-1) Class Path entry derbyLocale_zh_TW.jar in "/content/drools-guvnor.war/WEB-INF/lib/derby-10.2.1.6.jar" does not point to a valid jar for a Class-Path reference.
16:02:08,204 WARN (MSC service thread 1-1) Encountered invalid class name "org.xmlpull.mxp1.MXParser,org.xmlpull.mxp1_serializer.MXSerializer" for service type "org.xmlpull.v1.XmlPullParserFactory"
16:02:08,209 INFO (MSC service thread 1-1) read persistence.xml for ACL
16:02:08,212 WARN (MSC service thread 1-1) Invalid signature for method postConstruct annotated with javax.annotation.PostConstruct on class org.jboss.seam.persistence.EntityManagerProxyInterceptor, signature must be void methodName(InvocationContext ctx)
16:02:08,213 WARN (MSC service thread 1-1) Invalid signature for method postConstruct annotated with javax.annotation.PostConstruct on class org.jboss.seam.persistence.HibernateSessionProxyInterceptor, signature must be void methodName(InvocationContext ctx)
16:02:08,214 INFO (MSC service thread 1-1) added javax.persistence.api, javaee.api, org.jboss.as.jpa, org.javassist dependencies to drools-guvnor.war
16:02:08,215 INFO (MSC service thread 1-1) added (default provider) org.hibernate dependency to application deployment (since 1 PU(s) didn't specify jboss.as.jpa.providerModule)
16:02:08,215 INFO (MSC service thread 1-1) added org.hibernate dependency to application deployment
16:02:08,422 INFO (MSC service thread 1-4) JNDI bindings for session bean named EjbSynchronizations in deployment unit deployment "drools-guvnor.war" are as follows:
java:global/drools-guvnor/EjbSynchronizations!org.jboss.seam.transaction.LocalEjbSynchronizations
java:app/drools-guvnor/EjbSynchronizations!org.jboss.seam.transaction.LocalEjbSynchronizations
java:module/EjbSynchronizations!org.jboss.seam.transaction.LocalEjbSynchronizations
java:global/drools-guvnor/EjbSynchronizations
java:app/drools-guvnor/EjbSynchronizations
java:module/EjbSynchronizations
16:02:08,423 INFO (MSC service thread 1-4) JNDI bindings for session bean named TimerServiceDispatcher in deployment unit deployment "drools-guvnor.war" are as follows:
java:global/drools-guvnor/TimerServiceDispatcher!org.jboss.seam.async.LocalTimerServiceDispatcher
java:app/drools-guvnor/TimerServiceDispatcher!org.jboss.seam.async.LocalTimerServiceDispatcher
java:module/TimerServiceDispatcher!org.jboss.seam.async.LocalTimerServiceDispatcher
java:global/drools-guvnor/TimerServiceDispatcher
java:app/drools-guvnor/TimerServiceDispatcher
java:module/TimerServiceDispatcher
16:02:08,759 INFO (MSC service thread 1-1) Deploying JDBC-compliant driver class org.apache.derby.jdbc.AutoloadedDriver (version 10.2)
16:02:08,773 INFO (MSC service thread 1-4) starting Persistence Unit Service 'drools-guvnor.war#ACL'
16:02:08,774 INFO (MSC service thread 1-4) HHH00204Smiley Tonguerocessing PersistenceUnitInfo
16:02:08,785 INFO (MSC service thread 1-4) HHH00402:Using Hibernate built-in connection pool (not for production use!)
16:02:08,907 INFO (MSC service thread 1-4) HHH00115:Hibernate connection pool size: 20
16:02:08,909 INFO (MSC service thread 1-4) HHH00006:Autocommit mode: true
16:02:08,909 INFO (MSC service thread 1-4) HHH00401:using driver at URL
16:02:08,910 INFO (MSC service thread 1-4) HHH00046:Connection properties: {user=sa, password=****, autocommit=true, release_mode=auto}
16:02:08,911 WARN (MSC service thread 1-4) HHH00342:Could not obtain connection to query metadata : No suitable driver found for jdbc:hsqldb:mem:unit-testing-jpa
16:02:08,911 INFO (MSC service thread 1-4) HHH00400:Using dialect: org.hibernate.dialect.HSQLDialect
16:02:08,919 INFO (MSC service thread 1-4) HHH00422Smiley Very Happyisabling contextual LOB creation as connection was null
16:02:08,920 INFO (MSC service thread 1-4) HHH00268:Transaction strategy: org.hibernate.engine.transaction.internal.jdbc.JdbcTransactionFactory
16:02:08,920 INFO (MSC service thread 1-4) HHH00397:Using ASTQueryTranslatorFactory
16:02:08,927 ERROR (MSC service thread 1-4) MSC00001: Failed to start service jboss.persistenceunit."drools-guvnor.war#ACL": org.jboss.msc.service.StartException in service jboss.persistenceunit."drools-guvnor.war#ACL": Failed to start service
at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1780)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:662)
Caused by: java.lang.ClassCastException: org.dom4j.DocumentFactory cannot be cast to org.dom4j.DocumentFactory
at org.dom4j.DocumentFactory.getInstance(DocumentFactory.java:97)
at org.dom4j.DocumentHelper.getDocumentFactory(DocumentHelper.java:36)
at org.dom4j.DocumentHelper.createDocument(DocumentHelper.java:41)
at org.hibernate.envers.configuration.RevisionInfoConfiguration.generateDefaultRevisionInfoXmlMapping(RevisionInfoConfiguration.java:86)
at org.hibernate.envers.configuration.RevisionInfoConfiguration.configure(RevisionInfoConfiguration.java:322)
at org.hibernate.envers.configuration.AuditConfiguration.<init>(AuditConfiguration.java:94)
at org.hibernate.envers.configuration.AuditConfiguration.getFor(AuditConfiguration.java:134)
at org.hibernate.envers.event.EnversIntegrator.integrate(EnversIntegrator.java:63)
at org.hibernate.internal.SessionFactoryImpl.<init>(SessionFactoryImpl.java:294)
at org.hibernate.cfg.Configuration.buildSessionFactory(Configuration.java:1722)
at org.hibernate.ejb.EntityManagerFactoryImpl.<init>(EntityManagerFactoryImpl.java:76)
at org.hibernate.ejb.Ejb3Configuration.buildEntityManagerFactory(Ejb3Configuration.java:899)
at org.hibernate.ejb.Ejb3Configuration.buildEntityManagerFactory(Ejb3Configuration.java:884)
at org.hibernate.ejb.HibernatePersistence.createContainerEntityManagerFactory(HibernatePersistence.java:73)
at org.jboss.as.jpa.service.PersistenceUnitService.createContainerEntityManagerFactory(PersistenceUnitService.java:143)
at org.jboss.as.jpa.service.PersistenceUnitService.start(PersistenceUnitService.java:77)
at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1824)
at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1759)
... 3 more
16:02:09,135 INFO (HttpManagementService-threads - 4) Deployment of "drools-guvnor.war" was rolled back with failure message {"Failed services" => {"jboss.persistenceunit.\"drools-guvnor.war#ACL\"" => "org.jboss.msc.service.StartException in service jboss.persistenceunit.\"drools-guvnor.war#ACL\": Failed to start service"}}
16:02:09,136 INFO (HttpManagementService-threads - 4) Service status report
Services which failed to start:
service jboss.persistenceunit."drools-guvnor.war#ACL": org.jboss.msc.service.StartException in service jboss.persistenceunit."drools-guvnor.war#ACL": Failed to start service
16:02:10,465 INFO (MSC service thread 1-3) Stopped deployment drools-guvnor.war in 1328ms
2 REPLIES
One Star

Re: Issues while attempting to deploy drools-guvnor to JBoss 7.0.2-as

Hi
Try this: expand drools-guvnor.war as a regular folder, but keep it's full name including the .war extension.
drools-guvnor is not stable in JBOSS7.
Best regards!
Pedro
One Star

Re: Issues while attempting to deploy drools-guvnor to JBoss 7.0.2-as

Thank you Pedro for the reply. I received information that 4.2.2GA is the preferred version to be used, so I'll go ahead and give that a try first since it seems that might have the best results.