6:50 p.m.
Paul Hinds created AS7-6046:
-------------------------------
Summary: 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: Logging
Affects Versions: 7.1.3.Final (EAP)
Reporter: Paul Hinds
Assignee: James Perkins
Priority: Minor
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
8:49 p.m.
[
https://issues.jboss.org/browse/AS7-6046?page=com.atlassian.jira.plugin.s...
]
Brian Stansberry updated AS7-6046:
----------------------------------
Component/s: Domain Management
(was: Logging)
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: James Perkins
Priority: Minor
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
8:49 p.m.
[
https://issues.jboss.org/browse/AS7-6046?page=com.atlassian.jira.plugin.s...
]
Brian Stansberry updated AS7-6046:
----------------------------------
Assignee: (was: James Perkins)
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
Priority: Minor
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
8:57 p.m.
[
https://issues.jboss.org/browse/AS7-6046?page=com.atlassian.jira.plugin.s...
]
Brian Stansberry commented on AS7-6046:
---------------------------------------
It is unlikely that an error message referencing the xml file will be provided; certainly
not in AS 7. The parsing is long finished by the time the missing dependency is detected
and the logic that detects the failure is generic and unaware that the faulty
configuration came from xml vs a management client like the CLI or admin console.
However, there should be an ERROR level log message during boot. There won't be if you
add the datasource post-boot via the CLI or admin console, since in that case the error
message is propagated to the client. But during boot there should be and if there
isn't, that's a bug.
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
Priority: Minor
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
9:03 p.m.
[
https://issues.jboss.org/browse/AS7-6046?page=com.atlassian.jira.plugin.s...
]
Brian Stansberry commented on AS7-6046:
---------------------------------------
OK, I see the problem. ServiceVerificationHandler is reporting the error by calling
OperationContext.getFailureDescription() and modifying that, and not by throwing an
OperationFailedException. The logic that logs at ERROR during boot is in a catch block for
an OFE, so it doesn't get invoked.
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
Priority: Minor
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
9:03 p.m.
[
https://issues.jboss.org/browse/AS7-6046?page=com.atlassian.jira.plugin.s...
]
Brian Stansberry updated AS7-6046:
----------------------------------
Fix Version/s: 7.2.0.CR1
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
Priority: Minor
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
9:03 p.m.
[
https://issues.jboss.org/browse/AS7-6046?page=com.atlassian.jira.plugin.s...
]
Brian Stansberry updated AS7-6046:
----------------------------------
Priority: Major (was: Minor)
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
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
9:20 p.m.
[
https://issues.jboss.org/browse/AS7-6046?page=com.atlassian.jira.plugin.s...
]
Brian Stansberry reassigned AS7-6046:
-------------------------------------
Assignee: Brian Stansberry
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
2:02 a.m.
[
https://issues.jboss.org/browse/AS7-6046?page=com.atlassian.jira.plugin.s...
]
jaikiran pai commented on AS7-6046:
-----------------------------------
I'm not exactly sure what the incorrect configuration is. Paul can you please add the
exact xml config and the incorrect value which leads to this? The reason I'm curious
is because, just recently I fixed a part in the datasource subsystem where the real ERROR
is indeed reported from the driver addition code. Here's the relevant PR which has
been merged to both 7.1 and master branches https://github.com/jbossas/jboss-as/pull/3250.
The JIRA for that was https://issues.jboss.org/browse/AS7-5751
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
2:04 a.m.
[
https://issues.jboss.org/browse/AS7-6046?page=com.atlassian.jira.plugin.s...
]
jaikiran pai commented on AS7-6046:
-----------------------------------
{quote}
I'm curious is because, just recently I fixed a part in the datasource subsystem where
the real ERROR is indeed reported from the driver addition code.
{quote}
That fix was done post 7.1.3.EAP by the way. So you'll need to build that branch from
github to test it, if you want to.
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
12:17 p.m.
[
https://issues.jboss.org/browse/AS7-6046?page=com.atlassian.jira.plugin.s...
]
Brian Stansberry commented on AS7-6046:
---------------------------------------
From the looks of the "New missing/unsatisfied
dependencies", I'm guessing it's something like this:
{code}
<datasource ...>
<driver>db2xa</driver>
...
</datasource>
...
<driver name="db2typoa" ...>
{code}
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
12:32 p.m.
[
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
4166
days inactive
4167
days old
11 comments
3 participants
participants (3)
-
Brian Stansberry (JIRA) -
jaikiran pai (JIRA)
-
Paul Hinds (JIRA)