I had a similar problem and found that my tightVNC client was causing it, stopped tightVNC, Jboss started up sweet, then I restarted the tightVNC client and that was then fine.
I found it by doing a netstat at the cmd console and see what it brings up. Regards, Stephen... View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3831127#3831127 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3831127 ------------------------------------------------------- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
