[JBoss Portal] - Use Apache mod_proxy or mod_rewrite to redirect to jboss por
by dehaven_becker
Hello,
I'm having trouble fronting my instance of Jboss Portal V.2.6 with Apache Http Server. I downloaded and installed the portal bundled with Jboss AS.
There are two issues:
1. I can successfully redirect to the portal using mod_proxy and/or mod_rewrite to get to the portal under port 8080 but there are no images or decorations on the portal once it paints in the browser. It's just text. This is really ugly. When I use localhost:8080 it's beautiful!
2. When I click the Login, Dashboard, Admin etc links I get an error because the links have port 8080 hard coded in them. I can edit the URL in the browser to take out the :8080 and then it works (in ugly text format mentioned in issue 1 above) until I click another one of the links like Admin Dashboard etc. Then it breaks again because:8080 is back in the hard coded link.
Can some one please tell me how to get around these two items. It is important that I continue to use Apache to front the portal because there are other applications that use this instance of Apache.
Thanks in advance!
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4091796#4091796
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4091796
18Â years, 6Â months
[Clustering/JBoss] - Re: HA-JMS
by bstansberryï¼ jboss.com
Yes, this problem would only occur in 4.2 and later.
In 4.2, if you don't pass -b at startup, JBoss will almost all services (e.g. JNDI) to 127.0.0.1. This is a security precaution; basically the server is not remotely available unless you say you want it to be.
An exception to this is JGroups channels, which will communicate using the default interface if you don't set -b. This allows servers to cluster. So, your servers clustered.
For services based on the HAPartition (e.g. HASingleton) the nodes in the cluster are identified by taking the IP address and port that the JNDI service is bound to. I won't go into the details as to why this is, other than to say the goal is to detect/prevent the same node joining the group twice. This breaks down if the nodes in the group are all binding JNDI to localhost, since every node has the same id!! You can see this in your log:
2007-09-24 07:37:55,512 INFO [org.jboss.ha.framework.interfaces.HAPartition.lifecycle.DefaultPartition] New cluster view for partition DefaultPartition (id: 1, delta: 1) : [127.0.0.1:1099, 127.0.0.1:1099]
Having two nodes with the same id like that must be messing up the master node election process. Hence my suggestion to use -b.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4091794#4091794
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4091794
18Â years, 6Â months