That's a shame. I was under the assumption that this would be a way to keep things more secure.. only open JBWeb to the outside world. This causes a problem which effectively blows guaranteed delivery when using JBoss Messaging if you're running on 0.0.0.0 but not if on localhost. Pulling out a network plug results in a socket exception that affects the ability for my java based message producer from putting things on the queue.. even though it's on the same machine using localhost. I seem to be only able to get rid of this if messaging is bound to localhost only rather than 0.0.0.0. I'll look for a workaround. Cheers, Jon View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4159729#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...