Tracing what happens before EARDeployer starts

[smokingapipe]

I'm new to JBoss internals. I'm having a very strange problem: I have two applications in EAR files. When I deploy them on my desktop machine here (localhost) I get normal log messages. When I set up a virtual-host entry in jboss-web.xml, and the corresponding Host entries in jbossweb/server.xml, I get no log messages, or System.out, or anything from the web apps.

In a normal situation, the first log message I see is the EARDeployer message. When it is on the real server with virtual hosts, the EARs do in fact deploy, but there is no EARDeployer message on console, or any other message from these EARs, no matter what logging method I use, even System.out.println(). Of course exceptions don't show up, so this whole system is almost useless in production because I can only guess at where problems are.

I have spent about three days working on this and am not getting anywyere. My next step is to go through the JBoss source code to figure out where these log messages are being dropped. It looks like EARDeployer is the first thing that's missing so maybe I should start there.

Can anyone suggest how I get started in the JBoss source to trace this?

[starksm64]

Its a pure logging issue. You will have to start with debugging the org.jboss.logging.Logger calls. None of the deployers have dropped messages. Something has screwed up where the Logger plugin.

[smokingapipe]

Ok, I need to start tracing on the org.jboss.logging.Logger. The one way to always get a message to the console, regardless of how (mis) configured loggers and System.out can be, is (thanks to Java 6) System.console.printf() so I can make an instrumented version of the org.jboss.logging.Logger. Time for me to learn how to build JBoss parts and get them installed. I will post what I find.

[smokingapipe]

And the problem is solved. One of the applications on the server was misbehaving and somehow disabling the entire logging system and System.out globally. It would be nice if JBoss would somehow block that from happening or at least intercept it and log a warning, but anyway, it's the fault of the web app.

[juha]

RuntimePermission.setIO

But I've never tried running AS with security manager enabled.