If migration process has been performed from
JBoss EAP 5.xto
JBoss EAP 6.x, there should be configuration issue of defining
dependency between DataSource and Services.
JBoss EAP 5.xhas
DataSource file (*-ds.xml)to define dependency on other services, whereas this kind of configuration is removed from
JBoss EAP 6.xand single file
domain.xmlintroduced to provide DataSource entry.
JBoss EAP 5.xthe
SAR - Service Archive Resources provided Mbeans dependencycould be defined using
If such tags are being used in DataSource entry of
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.xwhere as
@org.jboss.ejb3.annotation.Managementare 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]
- Red Hat JBoss Enterprise Application Platform
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.