Details
-
Bug
-
Resolution: Done
-
Major
-
7.1.3.Final (EAP)
-
None
Description
I've seen many users running into issues when they are trying to configure a datasource and end up pointing to an incorrect module name for the JDBC driver. No where in the logs do we report why the JDBC driver install failed and users find it difficult to understand the real cause until someone points them to the incorrect module name.
Looking at the code which adds the JDBC driver (JdbcDriverAdd) I see that we aren't reporting the real module load failure correctly.