Skip to main content

This content has been archived and is no longer being updated. Links may not function; however, this content may be relevant to outdated versions of the product.

Support Article

AES server does not start with JBoss and Pega 7.1.7

SA-13033

Summary



JBoss EAP 6.3 server start with error "JBAS014775: New missing/unsatisfied dependencies: service jboss.jdbc-driver.mssql (missing)" caused by unavailability of the module that provides the JDBC driver.

User environment details:
  • Pega 7.1.7
  • JBoss EAP  6.3.3 GA
  • Linux version: 2.6.32-504.12.2.el6.x86_64
  • Microsoft SQL Server 11.00.5058
  • Microsoft JDBC Driver 4.0 for SQL Server 4.0.2206.100


Error Messages

ERROR [org.jboss.as.controller.management-operation] (ServerService Thread Pool -- 31) JBAS014612: Operation ("add") failed - address: ([
("subsystem" => "datasources"),
("jdbc-driver" => "mssql")
]) - failure description: "JBAS010441: Failed to load module for driver [my_module_driver]"

JBAS014775:    New missing/unsatisfied dependencies:
      service jboss.jdbc-driver.mssql (missing) dependents: [service jboss.driver-demander.java:/jdbc/PegaRULES, service jboss.data-source.java:/jdbc/PegaRULES] 

JBAS015875: JBoss EAP 6.3.3.GA (AS 7.4.3.Final-redhat-2) started (with errors) in 9047ms - Started 899 of 966 services (41 services failed or missing dependencies, 96 services are lazy, passive or on-demand)


Steps to Reproduce

  1. Create the JDBC datasource as described at page 26 in the Pega 7.1.7 Installation Guide for JBoss Red Hat EAP on MSSQL 
  2. Define a JDBC driver provided by a missing or unresolved module. For example.:

<driver name="mssql" module="com.mssql.sqljdbc4">
    <driver-class>com.microsoft.sqlserver.jdbc.SQLServerDriver</driver-class>
</driver>


Root Cause



The root cause of this problem is defect/misconfiguration in the operating environment: Wrong path assigned to the JBOSS_MODULEPATH environment variable used to determine the JBoss modules directory.
This caused the load failure of the module that provides the JDBC driver required to create the PegaRULES data source.


Resolution



This issue is resolved by making the following change to the operating environment:

Defined the JBOSS_MODULEPATH environment variable to include the directory path that contains the JDBC driver module. 
For example, assuming the JDBC driver module is within the following path "/var/opt/jboss_opt/modules/com/msql/sqljdbc4/main" the environment variable must contain the path "/var/opt/jboss_opt/modules"

Refer to Chapter 6 of the JBoss Enterprise Application Platform 6.3 Administration and Configuration Guide for reference on how to define JDBC data sources on JBoss EAP 6.3.

 

Suggest Edit

Published August 13, 2015 - Updated October 8, 2020

Did you find this content helpful? Yes No

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.

We'd prefer it if you saw us at our best.

Pega Community has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice
Contact us