We ran into some similar issues. Check the following: Your production environment may have some firewall or routing issues. Up the verbosity of your jboss server and see if it is showing any activity when your clients try to connect. It sounds to me like the client cannot reach the server. Perhaps you could even create and run a super stripped down and simple JNDI test client. Sometimes, production servers are multi-homed. Make sure that the 179.1.71.2 is the first bound (default ) NIC, or set the binding address on the startup using the run.bat -b option.
Good luck. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3844412#3844412 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3844412 ------------------------------------------------------- This SF.Net email is sponsored by OSTG. Have you noticed the changes on Linux.com, ITManagersJournal and NewsForge in the past few weeks? Now, one more big change to announce. We are now OSTG- Open Source Technology Group. Come see the changes on the new OSTG site. www.ostg.com _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
