GM node 2 Cluster Server Down. JBAS014775: New missing/unsatisfied dependencies: service jboss.jdbc-driver.ojdbc5-11_2_0_1_0_jar (missing) dependents: [service jboss.driver-demander.java:/jdbc/WPDS3, service jboss.data-source.java:/jdbc/eurekifyDS

Document ID : KB000015597
Last Modified Date : 14/02/2018
Show Technical Document Details
Introduction:

 

 

Question:

Node 2 went down and the following displaying in the Eurekify.log:

08:15:52,602 INFO [org.jboss.as.controller] (Controller Boot Thread) JBAS014774: Service status report 

JBAS014775: New missing/unsatisfied dependencies: 
service jboss.jdbc-driver.ojdbc5-11_2_0_1_0_jar (missing) dependents: [service jboss.driver-demander.java:/jdbc/WPDS3, service jboss.data-source.java:/jdbc/eurekifyDS, service jboss.driver-demander.java:/jdbc/WPDS2, service jboss.data-source.java:/jdbc/eurekifyReportdbDS, JBAS014799: ... and 9 more ] 

08:15:52,633 INFO [org.jboss.as] (Controller Boot Thread) JBAS015961: Http management interface listening on http://127.0.0.1:9990/management 
08:15:52,633 INFO [org.jboss.as] (Controller Boot Thread) JBAS015951: Admin console listening on http://127.0.0.1:9990 
08:15:52,633 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 10000ms - Started 233 of 353 services (24 services failed or missing dependencies, 143 services are lazy, passive or on-demand) 

Environment:
Windows2 node clusterGovernance ManagerVersion: 12.6
Answer:

This was caused by the node 2 war files not being deployed.  This caused the "*.undeployed" files in the \deployments folder which caused node 2 not to start.

Please follow the steps below. 

1. Stop node 2 (shut down Jboss service) 
2. Navigate to \CA\jboss-eap-6.3\standalone\deployments
3. Find all files with extension ******.undeployed
4. Change the extension with from .undeployed to .deployed.
5. Restart Jboss starts to deploy all the ear file.