Well a first pass at using a relative URL didn't work..
However Util.resolveURL has something interesting in it:
| public static URL resolveURL(String urlValue) throws MalformedURLException
|{
| if (urlValue == null)
| return null;
|
| URL externalURL = n
Thanks for pointing that out. I wasn't aware that you could do something like:
http://virtualhost.domain.com:8443/invoker/readonly/JMXInvokerServlet
And bypass the whole InvokerURLPrefix/InvokerURLSuffix mechanism.
I still have a couple of problems though:
1) I want the machine to be accessibl
oh oh... none of the xml tags can be seen ! sorry about that... under the
Naming bean and the HttpInvoker bean :
| :8443/invoker/readonly/JMXInvokerServlet
|
| http://:8443/invoker/readonly/JMXInvokerServlet
|
|
View the original post :
http://www.jboss.com/in
After the lookup, the server sends the addresses specified in
deploy/http-invoker.sar/META-INF/jboss-service.xml to the client (when using
http).
Try this option :
a) delet the attribute "UseHostName" and
b) add an InvokerURL attribute and
c) change the ports used in the file to your 8443 port
This seems to be related to a similar problem I posted here:
[url]
http://www.jboss.com/index.html?module=bb&op=viewtopic&t=61514[/url]
In general, the whole JNDI infrastructure seems to rely on the JBoss
Application Server being in DNS and being directly accessible to clients (and
not behind a
