Wow.. I actually found someone with the same issue!

What's probably the most frustrating thing about Oc4j is that its impossible to find someone else with the same experiences. Shit, finding a tool that even mentions deploying onto OC4J is downright astounding.

OC4J is such a troubled tangled web of random error messages that searching for things generally comes up with one or two hits, that have nothing to do with what you're doing. So, I was shocked to find someone else with a problem that I recently became confronted with, and have yet to solve. (And, in fact, its stopping one aspect of my application from being self-managed... *cries*... develops have to actually touch the production database to fix something that it can fix itself.. *cries*)

ACayci is an unfortunate soul that has attempted to allow a JMX Operation to do something with JNDI through OEM, and has hit upon the nasty "NO JNDI FOR YOU!" exception.

Its a scary error. Cause, JMX should invoking the classes under the same classpath that the application is deployed in.. i mean.. OEM is getting a list of MBeans FROM that class loader, right? maybe?

DnlCYan replies with what I'll summarize as a "haha!"... basically responding that OC4J is rather particular about having every orion specific deployment description file inside of the application's ear/war.... which leads you down the path of finding out just how many xml documents you need to now version and hack into your ear... there is a freaking reason the ANT Ear task only expects an application.xml... its all that should be there.


So, in my case, I'm tempted to move the connection pool into my application as opposed to looking up through JNDI as the work-around. Shit, I'm sure the commons connection pool is even better than what OC4J provides...and I can change it at RUNTIME to allow more or less connections in the pool.

I wont drag this on, but, if someone has been able to actually get OEM's crazy JMX runtime to discover JNDI things (specifically container managed database connections)..... Well, I dont know what to tell you to do.... there should be a freaking wiki on it... but.. *sighs*

Where do I write my bug report? Shit, I can write a verifiable test case in about an hour...