This content has been marked as final. Show 1 reply
So, who is responsible for detecting the system properties? I know the remoting code in HTTPClientInvoker used to look at these settings but it definitely does not do so now. Is this a bug introduced into remoting? Or is JBossWS (and, by implication, any other remoting client) now expected to check these system properties and ensure the metadata is appropriately configured?
HttpClientInvoker quit looking at the system properties "http.proxyHost" and "http.proxyPort" as of the changes made for JBREM-569 "HTTP(S) proxy broken". In fact, my understanding is that these system properties should be handled automatically by the Java runtime. See, for example, http://www.developer.com/java/other/article.php/1551421.
Could you look further into what's really going on? Maybe run AS with TRACE logging turned on for Remoting in .../server/$CONFIG/conf/jboss-log4j.xml.