"chip_schoch" wrote : Well Tim, here is what I have determined. I have three MBean Services that handle jms messages. They are essentially the same codebase. If any one of them has a scoped loader I get the exception I sent initially. | | But only on the ones that load and initialize AFTER the one with the scoped loader. If a service without it loads and initializes before another one that has its loader scoped, then the first one works fine. | | Not scoping the loader is not really an issue for me except that without it I don't seem to be able to separate my log4j log files on a per service basis using the TCLFilter. Is there any known work around for this? | | Thanks Hi, It seems I have the same issue. I'm a newer of jboss. First of all, will you please explain the word scoped? The second is I have the same NPE when creating a connection. The following is my codes. | ConnectionFactory factory = (ConnectionFactory) ctx | .lookup("java:/JmsXA"); | Destination dest = (Destination) ctx.lookup("topic/testTopic"); | Connection conn = factory.createConnection(); | Is this a bug of jboss? Thank you very much. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4198292#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...