0 Replies Latest reply on Aug 4, 2015 7:15 AM by mzg351

    Ticket Monster deployment error

    mzg351 Newbie

      Hi,

      I've been following the ticket monster tutorial and finished the 2nd one. When I tried to run the project on server at the end of 2nd tutorial, I had the following problem:

       

      JBWEB000065: HTTP Status 404 - /ticket-monster/

       

      JBWEB000309: type JBWEB000067: Status report

       

      JBWEB000068: message /ticket-monster/

       

      JBWEB000069: description JBWEB000124: The requested resource is not available.

       

      JBoss Web/7.4.8.Final-redhat-4

       

      I've onlied modified the model in java sources during the2nd tutorial and at the end of the 1st tutorial I didn't have any problems with deployment. Here is my full error from the console:

       

      15:23:07,187 INFO  [org.jboss.modules] (main) JBoss Modules version 1.3.3.Final-redhat-1

      15:23:09,633 INFO  [org.jboss.msc] (main) JBoss MSC version 1.1.5.Final-redhat-1

      15:23:10,145 INFO  [org.jboss.as] (MSC service thread 1-7) JBAS015899: JBoss EAP 6.3.0.GA (AS 7.4.0.Final-redhat-19) starting

      15:23:19,310 INFO  [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) JBAS015003: Found ticket-monster.war in deployment directory. To trigger deployment create a file called ticket-monster.war.dodeploy

      15:23:19,620 INFO  [org.jboss.as.server] (Controller Boot Thread) JBAS015888: Creating http management service using socket-binding (management-http)

      15:23:19,630 INFO  [org.xnio] (MSC service thread 1-5) XNIO Version 3.0.10.GA-redhat-1

      15:23:19,776 INFO  [org.xnio.nio] (MSC service thread 1-5) XNIO NIO Implementation Version 3.0.10.GA-redhat-1

      15:23:20,038 WARN  [org.jboss.as.txn] (ServerService Thread Pool -- 44) JBAS010153: Node identifier property is set to the default value. Please make sure it is unique.

      15:23:20,189 INFO  [org.jboss.as.security] (ServerService Thread Pool -- 42) JBAS013171: Activating Security Subsystem

      15:23:20,189 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 29) JBAS010280: Activating Infinispan subsystem.

      15:23:20,287 INFO  [org.jboss.as.naming] (ServerService Thread Pool -- 37) JBAS011800: Activating Naming Subsystem

      15:23:20,296 INFO  [org.jboss.as.webservices] (ServerService Thread Pool -- 46) JBAS015537: Activating WebServices Extension

      15:23:20,327 INFO  [org.jboss.as.jsf] (ServerService Thread Pool -- 35) JBAS012605: Activated the following JSF Implementations: [main, 1.2]

      15:23:20,748 INFO  [org.jboss.as.security] (MSC service thread 1-6) JBAS013170: Current PicketBox version=4.0.19.SP8-redhat-1

      15:23:21,152 INFO  [org.jboss.remoting] (MSC service thread 1-5) JBoss Remoting version (unknown)

      15:23:21,355 INFO  [org.jboss.as.connector.logging] (MSC service thread 1-8) JBAS010408: Starting JCA Subsystem (IronJacamar 1.0.26.Final-redhat-1)

      15:23:23,570 INFO  [org.jboss.as.naming] (MSC service thread 1-4) JBAS011802: Starting Naming Service

      15:23:23,572 INFO  [org.jboss.as.mail.extension] (MSC service thread 1-11) JBAS015400: Bound mail session [java:jboss/mail/Default]

      15:23:23,715 INFO  [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 25) JBAS010403: Deploying JDBC-compliant driver class org.h2.Driver (version 1.3)

      15:23:27,219 INFO  [org.apache.coyote.http11.Http11Protocol] (MSC service thread 1-16) JBWEB003001: Coyote HTTP/1.1 initializing on : http-localhost/127.0.0.1:8080

      15:23:27,291 INFO  [org.apache.coyote.http11.Http11Protocol] (MSC service thread 1-16) JBWEB003000: Coyote HTTP/1.1 starting on: http-localhost/127.0.0.1:8080

      15:23:29,008 INFO  [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-1) JBAS010400: Bound data source [java:jboss/datasources/ExampleDS]

      15:23:29,351 INFO  [org.jboss.as.server.deployment.scanner] (MSC service thread 1-5) JBAS015012: Started FileSystemDeploymentService for directory /Applications/jbdevstudio/runtimes/jboss-eap/standalone/deployments

      15:23:29,538 INFO  [org.jboss.as.remoting] (MSC service thread 1-6) JBAS017100: Listening on 127.0.0.1:4447

      15:23:29,538 INFO  [org.jboss.as.remoting] (MSC service thread 1-7) JBAS017100: Listening on 127.0.0.1:9999

      15:23:29,611 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-10) JBAS015876: Starting deployment of "ticket-monster.war" (runtime-name: "ticket-monster.war")

      15:23:30,181 INFO  [org.jboss.ws.common.management] (MSC service thread 1-9) JBWS022052: Starting JBoss Web Services - Stack CXF Server 4.3.0.Final-redhat-3

      15:23:32,600 INFO  [org.jboss.as.jpa] (MSC service thread 1-8) JBAS011401: Read persistence.xml for primary

      15:23:32,600 INFO  [org.jboss.as.jpa] (MSC service thread 1-8) JBAS011401: Read persistence.xml for ticket-monster-persistence-unit

      15:23:32,734 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-7) MSC000001: Failed to start service jboss.deployment.unit."ticket-monster.war".DEPENDENCIES: org.jboss.msc.service.StartException in service jboss.deployment.unit."ticket-monster.war".DEPENDENCIES: JBAS018733: Failed to process phase DEPENDENCIES of deployment "ticket-monster.war"

          at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:166) [jboss-as-server-7.4.0.Final-redhat-19.jar:7.4.0.Final-redhat-19]

          at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1980) [jboss-msc-1.1.5.Final-redhat-1.jar:1.1.5.Final-redhat-1]

          at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1913) [jboss-msc-1.1.5.Final-redhat-1.jar:1.1.5.Final-redhat-1]

          at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:895) [classes.jar:1.6.0_65]

          at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:918) [classes.jar:1.6.0_65]

          at java.lang.Thread.run(Thread.java:695) [classes.jar:1.6.0_65]

      Caused by: java.lang.IllegalArgumentException: JBAS011470: Persistence unitName was not specified and there are 2 persistence unit definitions in application deployment deployment "ticket-monster.war".  Either change the application deployment to have only one persistence unit definition or specify the unitName for each reference to a persistence unit.

          at org.jboss.as.jpa.container.PersistenceUnitSearch.ambiguousPUError(PersistenceUnitSearch.java:171)

          at org.jboss.as.jpa.container.PersistenceUnitSearch.findWithinDeployment(PersistenceUnitSearch.java:151)

          at org.jboss.as.jpa.container.PersistenceUnitSearch.findPersistenceUnitSupplier(PersistenceUnitSearch.java:74)

          at org.jboss.as.jpa.container.PersistenceUnitSearch.resolvePersistenceUnitSupplier(PersistenceUnitSearch.java:63)

          at org.jboss.as.jpa.processor.JPAAnnotationProcessor.getPersistenceUnit(JPAAnnotationProcessor.java:358)

          at org.jboss.as.jpa.processor.JPAAnnotationProcessor.getBindingSource(JPAAnnotationProcessor.java:289)

          at org.jboss.as.jpa.processor.JPAAnnotationProcessor.processField(JPAAnnotationProcessor.java:167)

          at org.jboss.as.jpa.processor.JPAAnnotationProcessor.processPersistenceAnnotations(JPAAnnotationProcessor.java:134)

          at org.jboss.as.jpa.processor.JPAAnnotationProcessor.deploy(JPAAnnotationProcessor.java:96)

          at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:159) [jboss-as-server-7.4.0.Final-redhat-19.jar:7.4.0.Final-redhat-19]

          ... 5 more

       

      15:23:33,082 INFO  [org.jboss.as.server] (ServerService Thread Pool -- 26) JBAS018559: Deployed "ticket-monster.war" (runtime-name : "ticket-monster.war")

      15:23:33,086 INFO  [org.jboss.as.controller] (Controller Boot Thread) JBAS014774: Service status report

      JBAS014777:   Services which failed to start:      service jboss.deployment.unit."ticket-monster.war".DEPENDENCIES: org.jboss.msc.service.StartException in service jboss.deployment.unit."ticket-monster.war".DEPENDENCIES: JBAS018733: Failed to process phase DEPENDENCIES of deployment "ticket-monster.war"

       

      15:23:33,274 INFO  [org.jboss.as] (Controller Boot Thread) JBAS015961: Http management interface listening on http://127.0.0.1:9990/management

      15:23:33,275 INFO  [org.jboss.as] (Controller Boot Thread) JBAS015951: Admin console listening on http://127.0.0.1:9990

      15:23:33,275 ERROR [org.jboss.as] (Controller Boot Thread) JBAS015875: JBoss EAP 6.3.0.GA (AS 7.4.0.Final-redhat-19) started (with errors) in 29862ms - Started 157 of 196 services (1 services failed or missing dependencies, 56 services are lazy, passive or on-demand)

       

      Here's the code for the XML file in the webapp:

       

      ticket-monster-ds.xml · GitHub

       

       

      And here's the screenshot of my deployments folder under EAP_HOME (after getting the error):

      Screen Shot 2015-08-04 at 11.57.01.png

       

      And here is the overview of the jboss-eap server.. It didn't have any problems by the end of the first tutorial..

       

      Screen Shot 2015-08-04 at 12.02.38.png

      Here is a link to the 2nd part of the tutorial: Building the persistence layer with JPA2 and Bean Validation

      Thanks in advance!