How to define dependency between Service Archive Resource - SAR and DataSource in Red Hat JBoss Enterprise Application Platfor 6.x?

Solution Verified - Updated -

Issue

  • If migration process has been performed from JBoss EAP 5.x to JBoss EAP 6.x, there should be configuration issue of defining dependency between DataSource and Services.

  • JBoss EAP 5.x has <depends> tag in DataSource file (*-ds.xml) to define dependency on other services, whereas this kind of configuration is removed from JBoss EAP 6.x and single file standalone*.xml or domain.xml introduced to provide DataSource entry.

  • In JBoss EAP 5.x the SAR - Service Archive Resources provided Mbeans dependency could be defined using <depends> tag.

  • If such tags are being used in DataSource entry of standalone*.xml or domain.xml in JBoss EAP 6.x, then following kind of exceptions will be thrown at the time of server start-up as it is not supported in JBoss EAP 6.x where as @org.jboss.ejb3.annotation.Service and @org.jboss.ejb3.annotation.Management are no longer supported which could be used to define Services.

JBAS014775:    New missing/unsatisfied dependencies:
service jboss.mbean.service."jboss.as:subsystem=datasources,data-source=MySqlDS".create (missing) dependents: [service jboss.mbean.service."service.server.monitor:service=MyMonitor".create]
service jboss.mbean.service."jboss.as:subsystem=datasources,data-source=MySqlDS".start (missing) dependents: [service jboss.mbean.service."service.server.monitor:service=MyMonitor".start]

Environment

  • Red Hat JBoss Enterprise Application Platform
    • 6.x

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Close

Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.