[
https://issues.jboss.org/browse/AS7-6046?page=com.atlassian.jira.plugin.s...
]
Paul Hinds commented on AS7-6046:
---------------------------------
We found the root cause error. Exactly as described above. It took 3 people 4 hours, hence
the issue. So I set up a jboss with only this bug to see what gets printed and verified
there is no error printed at the point the error occurs.
If you can't give an XML reference when the XML is being parsed, and you could still
print something useful at the point the DS loading fails that would better than the
current situation.
Logging indicates "missing dependency" not the cause of the
error.
------------------------------------------------------------------
Key: AS7-6046
URL:
https://issues.jboss.org/browse/AS7-6046
Project: Application Server 7
Issue Type: Feature Request
Components: Domain Management
Affects Versions: 7.1.3.Final (EAP)
Reporter: Paul Hinds
Assignee: Brian Stansberry
Fix For: 7.2.0.CR1
If the Data sources config is incorrect so that the <driver> element does not match
an existing driver, the error message is cryptic.
JBAS014775: New missing/unsatisfied dependencies:
service jboss.jdbc-driver.db2xa (missing) dependents: [service
jboss.data-source.java:jboss/datasources/myDS]
I would expect a log message at ERROR level, there is no error message while other data
sources are loaded.
Missing dependencies is printed on a line with no error level and the text of the message
does not relate to the XML.
I would expect the error message to indicate something about where to fix the error.
e.g an XPath
subsystem[xmlns="urn:jboss:domain:datasources:1.0"]/datasources/datasource/driver.
or some text that indicates the <driver> element is the problem.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:
http://www.atlassian.com/software/jira