[jbosstools-issues] [JBoss JIRA] (JBDS-2060) JBDS GWT Kitschensink example fails to deploy
Max Rydahl Andersen (JIRA)
jira-events at lists.jboss.org
Wed Mar 7 18:06:36 EST 2012
[ https://issues.jboss.org/browse/JBDS-2060?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12674930#comment-12674930 ]
Max Rydahl Andersen commented on JBDS-2060:
-------------------------------------------
The GWT archetype is targeting AS 7.1.
Thus its not a requirement it works on AS 7.0, even though it might be ok for that later on.
It's a mistake the example says it works with AS 7.0 - that should be fixed.
> JBDS GWT Kitschensink example fails to deploy
> ---------------------------------------------
>
> Key: JBDS-2060
> URL: https://issues.jboss.org/browse/JBDS-2060
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: central
> Affects Versions: 5.0.0.Beta1
> Environment: Version: 5.0.0.Beta1
> Build id: v20120307-0626-H98-Beta1
> Build date: 20120307-0626
> JBoss AS 7.0.2
> java version "1.6.0_30"
> Java(TM) SE Runtime Environment (build 1.6.0_30-b12)
> Java HotSpot(TM) 64-Bit Server VM (build 20.5-b03, mixed mode)
> RHEL6
> Reporter: Len DiMaggio
> Assignee: Snjezana Peco
> Priority: Critical
> Fix For: 5.0.0.Beta1
>
>
> The error raised on deployment is:
> 12:13:06,432 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-3) Bound data source [java:jboss/datasources/ExampleDS]
> 12:13:07,720 INFO [org.jboss.as.deployment] (MSC service thread 1-4) Started FileSystemDeploymentService for directory /opt/local/AS71/jboss-as-7.0.2.Final/standalone/deployments
> 12:13:07,748 INFO [org.jboss.as] (Controller Boot Thread) JBoss AS 7.0.2.Final "Arc" started in 11274ms - Started 93 of 148 services (55 services are passive or on-demand)
> 12:13:07,755 INFO [org.jboss.as.deployment] (DeploymentScanner-threads - 1) Found gwt-kitchensink.war in deployment directory. To trigger deployment create a file called gwt-kitchensink.war.dodeploy
> 12:13:07,785 INFO [org.jboss.as.server.deployment] (MSC service thread 1-8) Starting deployment of "gwt-kitchensink.war"
> 12:13:10,532 INFO [org.jboss.jpa] (MSC service thread 1-1) read persistence.xml for primary
> 12:13:10,562 INFO [org.jboss.as.jpa] (MSC service thread 1-8) added javax.persistence.api, javaee.api, org.jboss.as.jpa, org.javassist dependencies to gwt-kitchensink.war
> 12:13:10,564 INFO [org.jboss.as.jpa] (MSC service thread 1-8) added (default provider) org.hibernate dependency to application deployment (since 1 PU(s) didn't specify jboss.as.jpa.providerModule)
> 12:13:10,564 INFO [org.jboss.as.jpa] (MSC service thread 1-8) added org.hibernate dependency to application deployment
> 12:13:10,840 INFO [org.jboss.weld] (MSC service thread 1-6) Processing CDI deployment: gwt-kitchensink.war
> 12:13:10,858 ERROR [stderr] (MSC service thread 1-6) SLF4J: Class path contains multiple SLF4J bindings.
> 12:13:10,859 ERROR [stderr] (MSC service thread 1-6) SLF4J: Found binding in [vfs:/opt/local/AS71/jboss-as-7.0.2.Final/standalone/deployments/gwt-kitchensink.war/WEB-INF/lib/slf4j-log4j12-1.6.1.jar/org/slf4j/impl/StaticLoggerBinder.class]
> 12:13:10,867 ERROR [stderr] (MSC service thread 1-6) SLF4J: Found binding in [vfs:/opt/local/AS71/jboss-as-7.0.2.Final/standalone/deployments/gwt-kitchensink.war/WEB-INF/lib/weld-servlet-1.1.5.Final.jar/org/slf4j/impl/StaticLoggerBinder.class]
> 12:13:10,868 ERROR [stderr] (MSC service thread 1-6) SLF4J: See http://www.slf4j.org/codes.html#multiple_bindings for an explanation.
> 12:13:10,923 ERROR [stderr] (MSC service thread 1-1) log4j:WARN No appenders could be found for logger (org.jboss.errai.as7support.ErraiServiceActivator).
> 12:13:10,924 ERROR [stderr] (MSC service thread 1-1) log4j:WARN Please initialize the log4j system properly.
> 12:13:10,924 ERROR [stderr] (MSC service thread 1-1) log4j:WARN See http://logging.apache.org/log4j/1.2/faq.html#noconfig for more info.
> 12:13:11,649 INFO [org.jboss.weld] (MSC service thread 1-1) Starting Services for CDI deployment: gwt-kitchensink.war
> 12:13:11,685 INFO [org.jboss.weld.Version] (MSC service thread 1-1) WELD-000900 1.1.2 (Final)
> 12:13:11,734 INFO [org.jboss.jpa] (MSC service thread 1-5) starting Persistence Unit Service 'gwt-kitchensink.war#primary'
> 12:13:12,072 INFO [org.hibernate.annotations.common.Version] (MSC service thread 1-5) HCANN000001: Hibernate Commons Annotations {4.0.0.CR2}
> 12:13:12,086 INFO [org.hibernate.Version] (MSC service thread 1-5) HHH00412:Hibernate Core {4.0.0.CR2}
> 12:13:12,088 INFO [org.hibernate.cfg.Environment] (MSC service thread 1-5) HHH00206:hibernate.properties not found
> 12:13:12,091 INFO [org.hibernate.cfg.Environment] (MSC service thread 1-5) HHH00021:Bytecode provider name : javassist
> 12:13:12,122 INFO [org.hibernate.ejb.Ejb3Configuration] (MSC service thread 1-5) HHH00204:Processing PersistenceUnitInfo [
> name: primary
> ...]
> 12:13:12,412 INFO [org.hibernate.service.jdbc.connections.internal.ConnectionProviderInitiator] (MSC service thread 1-5) HHH00130:Instantiating explicit connection provider: org.hibernate.ejb.connection.InjectedDataSourceConnectionProvider
> 12:13:12,692 INFO [org.hibernate.dialect.Dialect] (MSC service thread 1-5) HHH00400:Using dialect: org.hibernate.dialect.H2Dialect
> 12:13:12,696 WARN [org.hibernate.dialect.H2Dialect] (MSC service thread 1-5) HHH00431:Unable to determine H2 database version, certain features may not work
> 12:13:12,698 INFO [org.hibernate.engine.jdbc.internal.LobCreatorBuilder] (MSC service thread 1-5) HHH00423:Disabling contextual LOB creation as JDBC driver reported JDBC version [3] less than 4
> 12:13:12,704 INFO [org.hibernate.engine.transaction.internal.TransactionFactoryInitiator] (MSC service thread 1-5) HHH00268:Transaction strategy: org.hibernate.engine.transaction.internal.jta.CMTTransactionFactory
> 12:13:12,711 INFO [org.hibernate.hql.internal.ast.ASTQueryTranslatorFactory] (MSC service thread 1-5) HHH00397:Using ASTQueryTranslatorFactory
> 12:13:12,823 INFO [org.hibernate.validator.util.Version] (MSC service thread 1-5) Hibernate Validator 4.2.0.Final
> 12:13:13,003 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-5) MSC00001: Failed to start service jboss.persistenceunit."gwt-kitchensink.war#primary": org.jboss.msc.service.StartException in service jboss.persistenceunit."gwt-kitchensink.war#primary": 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) [:1.6.0_30]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [:1.6.0_30]
> at java.lang.Thread.run(Thread.java:662) [:1.6.0_30]
> 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
> 12:13:13,213 INFO [org.jboss.as.server.controller] (DeploymentScanner-threads - 2) Deployment of "gwt-kitchensink.war" was rolled back with failure message {"Failed services" => {"jboss.persistenceunit.\"gwt-kitchensink.war#primary\"" => "org.jboss.msc.service.StartException in service jboss.persistenceunit.\"gwt-kitchensink.war#primary\": Failed to start service"}}
> 12:13:13,268 INFO [org.jboss.as.server.deployment] (MSC service thread 1-5) Stopped deployment gwt-kitchensink.war in 56ms
> 12:13:13,269 ERROR [org.jboss.as.deployment] (DeploymentScanner-threads - 1) {"Composite operation failed and was rolled back. Steps that failed:" => {"Operation step-2" => {"Failed services" => {"jboss.persistenceunit.\"gwt-kitchensink.war#primary\"" => "org.jboss.msc.service.StartException in service jboss.persistenceunit.\"gwt-kitchensink.war#primary\": Failed to start service"}}}}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the jbosstools-issues
mailing list