On the topic of missing resources

[nickarls]

The current upstream master currently says upon finding a mismatch in datasource definition/lookup something like

JBAS014775:    New missing/unsatisfied dependencies:

      service jboss.naming.context.java.jboss.datasources.testDS (missing) depen

dents: [service jboss.persistenceunit."Test.war#primary"]

Although it well, says what happens, is the contextual information available so that the message could be something like

"Sorry to bother you but when I tried to deploy test.war I noticed that it was JPA enabled (I found a persistence.xml in test.war/WEB-INF\classes\META-INF).

Upon futher investigation I noticed that the persistence unit called "primary" was looking for a JNDI bound datasource at "java:jboss/datasources/testDS". This, however,

was not found but I found these instead:

java:jboss/datasources/badtestDS (defined in test-ds-xml in the standalone/deployments folder)

java:jboss/datasources/exampleDS (defined in standalone/configuration/xml in the datasources subsystem)

I might of course guess but I suggest that you match the two JNDI names yourself (perhaps there was a typo or difference in the JNDI prefix)?

Have a nice day!

  Yours truly, AS 7.2.0"

other messages could be

"While I was looking through the datasource definition I noticed that you referenced a driver named "ojdbc6" in the datasource "foo" defined in  standalone/configuration/xml in the datasources subsystem,

however, no driver matching that name was found defined. What I found was a driver named

"com.oracle.db"

Perhaps you were referring to that?

Have a nice day!

  Yours truly, AS 7.2.0"

or

"While I was looking through the datasource definition I noticed that you referenced a driver named "ojdbc6" in the datasource "foo" defined in  standalone/configuration/xml in the datasources subsystem,

however, the driver definition references a module "com.oracle.db.drv" which was not found in the JBoss Modules system. I found the following interesting modules

"com.oracle.db.drivermodule"

Perhaps you were referring to that?

Have a nice day!

  Yours truly, AS 7.2.0"

[brian.stansberry]

Do you have any thoughts on how to accomplish this? Those log messages are very nice because they include a ton of contextual information. The problem is assembling the contextual information.

[nickarls]

Not yet, still stepping through the debugger in ApplicationServerService.start(final StartContext context) in the "AS 7 Internal Architecture Overview" article ;-)

But if you're asking a question like that, I'm guessing I'm SOL ;-)