Yeah, I'll post this in some other forum. It is certainly a bug and it's very easily reproducible. I need to report it on some other forum. Virt. hosts are working fine. The only two problems I encountered were 1. Seam-managed persistence contexts were not being isolated between apps. I fixed this by using different SMPC names. And 2. Logging stops working entirely. So I spent about 6 hours so far trying to get a simple log message to work in a virt. host. This isn't a problem with Seam or JBoss. It's a problem with Sun's logging implementation. Logging should be reliable and not sensitive to config settings. I'm starting to think this is a Tomcat issue because even System.out.println isn't working. What this means is that maybe the console logger is working fine, but the console itself isn't working. I think I have seen this behavior before in Tomcat. I should maybe write a JNDI logger that sends directly to console and is non-interceptable by anything at the Java layer. This really really should have been including with Sun Java, since the 1.4 days. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4001962#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...