I am attempting to deploy my java app to OpenShift Express.
The app runs fine on my local tomcat and on CloudFoundry platform. I have created the app in the management console, and have then pushed my app code to the openshift created git repository.
When I perform the push, I see that the maven build has completed successfully with no errors, however, if I then check the status of the app (using the command: rhc app status) then I get the following errors displayed:
at org.jboss.as.jpa.processor.JPAAnnotationParseProcessor.deploy(JPAAnnotationParseProcessor.java:90)
at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:113) [jboss-as-server-7.1.0.Final.jar:7.1.0.Final]
... 5 more
2012/04/04 15:01:42,138 INFO [org.jboss.as.server] (DeploymentScanner-threads - 2) JBAS015870: Deploy of deployment "ROOT.war" was rolled back with failure message {"JBAS014671: Failed services" => {"jboss.deployment.unit.\"ROOT.war\".DEPENDENCIES" => "org.jboss.msc.service.StartException in service jboss.deployment.unit.\"ROOT.war\".DEPENDENCIES: Failed to process phase DEPENDENCIES of deployment \"ROOT.war\""}}
2012/04/04 15:01:42,462 INFO [org.jboss.as.server.deployment] (MSC service thread 1-3) JBAS015877: Stopped deployment ROOT.war in 320ms
2012/04/04 15:01:42,464 INFO [org.jboss.as.controller] (DeploymentScanner-threads - 2) JBAS014774: Service status report
JBAS014777: Services which failed to start: service jboss.deployment.unit."ROOT.war".DEPENDENCIES: org.jboss.msc.service.StartException in service jboss.deployment.unit."ROOT.war".DEPENDENCIES: Failed to process phase DEPENDENCIES of deployment "ROOT.war"
2012/04/04 15:01:42,539 ERROR [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) {"JBAS014653: Composite operation failed and was rolled back. Steps that failed:" => {"Operation step-2" => {"JBAS014671: Failed services" => {"jboss.deployment.unit.\"ROOT.war\".DEPENDENCIES" => "org.jboss.msc.service.StartException in service jboss.deployment.unit.\"ROOT.war\".DEPENDENCIES: Failed to process phase DEPENDENCIES of deployment \"ROOT.war\""}}}}
As well as this error, I can see the end of a stacktrace, so have tried to tail the logs of the application using rhc-tail-file command, but when I do that I get the following error: Error in trying to tail files
Has anyone come across this or have any advice on how to resolve?
Go ahead and SSH into your application using the same UUID and hostname as your git repository. If you go into appname/logs you should be able to see the complete logs.
Once you get that you should have a better sense of the error.
Related
I get the following exception when I run JBoss:
Failed to start service org.wildfly.network.interface.cluster:
org.jboss.msc.service.StartException in service org.wildfly.network.interface.cluster:
WFLYSRV0082: failed to resolve interface cluster at
org.jboss.as.server.services.net.NetworkInterfaceService.start(NetworkInterfaceService.java:96)
This is rather generic. Does anyone know how to get more details about the root cause?
Any idea which jar file contains org.jboss.as.server.services.net.NetworkInterfaceService class?
One of our JBoss Application Server version 7.1 is failing to deploy ear applications during the startup process. I have tried many different values for the default-timeout parameter (600secs, 1200secs, 2400secs) in the deployment scanner section of the standalone.xml file. It keeps on failing with the same message no matter the value set for the default-timeout.
It used to work just fine till yesterday with the default-timeout set at 300 secs. Please find the error message in the "Error Message" section below.
Along with trying out different default-timeout values, i have also tried removing cache such as renaming or removing tmp directory several times before restarting.
What can I try to fix this?
Error Message:
15:46:01,732 ERROR [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) JBAS015052: Did not receive a response to the deployment operation within the allowed timeout period [600 seconds]. Check the server configuration file and the server logs to find more about the status of the deployment.
15:46:01,734 ERROR [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) JBAS015052: Did not receive a response to the deployment operation within the allowed timeout period [600 seconds]. Check the server configuration file and the server logs to find more about the status of the deployment.
15:46:01,733 INFO [org.jboss.as.server] (DeploymentScanner-threads - 2) JBAS015871: Deploy of deployment "ServerApps.ear" was rolled back with no failure message
15:46:01,736 ERROR [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) JBAS015052: Did not receive a response to the deployment operation within the allowed timeout period [600 seconds]. Check the server configuration file and the server logs to find more about the status of the deployment.
15:46:01,736 INFO [org.jboss.as.server] (DeploymentScanner-threads - 2) JBAS015871: Deploy of deployment "bpm.ear" was rolled back with no failure message
15:46:01,776 INFO [javax.enterprise.resource.webservices.jaxws.servlet.http] (MSC service thread 1-1) WSSERVLET15: JAX-WS servlet destroyed
15:46:01,779 INFO [javax.enterprise.resource.webservices.jaxws.server.http] (MSC service thread 1-1) WSSERVLET13: JAX-WS context listener destroyed
The error may cause due to the init() method of Servlet or other EE component was calling System.exit() which triggers shutdown hook to run. The JBoss Modular Service Container or MSC registers a hook and when triggered it shuts down the container. The container shutdown operation needs to wait until the EAR deployment over so that it knows if the deployment succeeded or failed. This may cause the deadlock as the System.exit() call waits until the hooks finish its execution and deadlock will be broken when the deployment gets failed due to timeout and release the MSC and continue with the shutdown.
You can try to collect the thread dumps and see if there is
A "MSC service thread" which has called into System.exit() or Runtime.exit(), and is waiting until the shutdown hooks complete.
The "MSC Shutdown Hook" thread, which is waiting for a CountDownlatch
Every time I deploy a war file in wildfly 10, I got this following error :
Cannot upload deployment: {"WFLYCTL0080: Failed services" =>
{"jboss.deployment.unit.\"member.war\".FIRST_MODULE_USE" =>
"org.jboss.msc.service.StartException in service
jboss.deployment.unit.\"member.war\".FIRST_MODULE_USE: WFLYSRV0153:
Failed to process phase FIRST_MODULE_USE of deployment \"member.war\"
Caused by:
org.jboss.as.server.deployment.DeploymentUnitProcessingException:
WFLYJCA0064: Exception deploying datasource java:/PostgresDS Caused
by: org.jboss.msc.service.DuplicateServiceException: Service
jboss.data-source.\"jboss.naming.context.java.PostgresDS\" is already
registered"},"WFLYCTL0412: Required services that are not installed:"
=> ["jboss.deployment.unit.\"member.war\".FIRST_MODULE_USE"],"WFLYCTL0180:
Services with missing/unavailable dependencies" => undefined}
It happens when I changed my persistence.xml and *-ds.xml which is telling my application to use the PostgresDS as its datasource.
Without looking at the files, it seems like you are registering your data source twice, once in the *-ds.xml and once in the persistence.xml (or maybe in the standalone.xml?).
Regarding missing/unavailable dependencies, are you certain the the Postgres SQL Module is installed in Wildfly and the driver is configured in the standalone.xml?
See also:
Wildfly DuplicateServiceException
How to add PostgreSQL datasource to WildFly 9.0?
I want to deploy an EJB Maven project and when I try so, an error message appears like this.
The error message :
17:45:21,005 ERROR [org.jboss.as.controller.management-operation] (DeploymentScanner-threads - 2) JBAS014613: Operation ("deploy") failed - address: ([("deployment" => "dashboard-ejb.jar")]) - failure description: {"JBAS014771: Services with missing/unavailable dependencies" => ["jboss.persistenceunit.\"dashboard-ejb.jar#dashboard-ejb\".FIRST_PHASE is missing [jboss.naming.context.java.dsOoredoo]"]}
To note, I've created a datasource called dsOoredoo.
Does anyone have an idea?
I recently installed Wildfly-10.0.0.Final. To get my feet wet, I created an elementary EJB that does not require a database connection. For some reason when I try to deploy the EJB, I get the following error:
Cannot upload deployment: {"WFLYCTL0080: Failed services" => {"jboss.deployment.unit.\"JavaEE_Wildfly1.jar\".
FIRST_MODULE_USE" => "org.jboss.msc.service.StartException in service jboss.deployment.unit.
\"JavaEE_Wildfly1.jar\".
FIRST_MODULE_USE: WFLYSRV0153: Failed to process phase FIRST_MODULE_USE of deployment \"JavaEE_Wildfly1.jar\"
Caused by: javax.persistence.PersistenceException: WFLYJPA0057: PersistenceProvider 'org.eclipse.persistence.jpa.PersistenceProvider' not found"}}
Since I am not using a database, do I still have to specify a Persistence provider? I do not have a persistence.xml because I did not think I needed one.
I don't think you need a persistence.xml. Check out this EJB-In-A-War wildfly quickstart for an example of a #Stateless EJB deployed without a persistence.xml.