I have seen this problem. It is happening because JBoss cannot get out to validate an xml
file. If you are behnd a firewall this can cause it.
I got past this by passing the following parameters to JBoss 5.
-Dhttp.proxyHost=x.x.x.x -Dhttp.proxyPort=yyyy
where x.x.x.x is the hostname of your proxy, and yyyy is the port.
I am thinking it may still work with 4.2.2.
Good luck,
Edward
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4125350#...
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...