You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jetspeed-user@portals.apache.org by brunp <pa...@gmail.com> on 2009/05/06 20:49:52 UTC
Running Jetspeed within Tomcat behind Apache
So.....I have Jetspeed properly updated, the first login page shows up a
little funny and contains a *# character which I think is somehow making is
way from the jetspeed_macros.vm file.
However, more importantly, when I try to log in, the IP portion of the URL
seems to move over to wanting to load up the page from 127.0.0.1?
Would this be related to improper redirect rules within the httpd.conf files
within Apache? I did remove the proxyName and proxyPort configuration from
within Tomcat, which apparently was required in version 2.0, but I think is
no longer required in 2.1.3 of Jetspeed.
Help appreciated.
Paul
--
View this message in context: http://www.nabble.com/Running-Jetspeed-within-Tomcat-behind-Apache-tp23413109p23413109.html
Sent from the Jetspeed - User mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-user-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-user-help@portals.apache.org
Re: strange Jetspeed heap usage
Posted by Randy Watler <wa...@wispertel.net>.
Roberto,
We have been load testing 2.1.3 and 2.2, but not necessarily letting
them sit idle. So, I cannot really verify what you are seeing. However,
there are plenty of potential sources of this behavior. One that comes
to mind is the PAM which monitors portlet applications for deployment
changes. There are also background processes to manage internal caches.
However, with these things, its almost always something one would not
initially expect.
I would assume you are seeing real behavior and not something unique.
Further research would be required to know for sure, hence the JIRA issue.
Randy
Roberto Rossi wrote:
> I wll do it in the next days... but can you confirm this strange
> behaviour or this is a very personal and isolated issue?
> Is there a Jetspeed running thread consuming cpu or memory?
>
> ROb.
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-user-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-user-help@portals.apache.org
Re: strange Jetspeed heap usage
Posted by Roberto Rossi <ro...@cone.it>.
I wll do it in the next days... but can you confirm this strange
behaviour or this is a very personal and isolated issue?
Is there a Jetspeed running thread consuming cpu or memory?
ROb.
Re: strange Jetspeed heap usage
Posted by Randy Watler <wa...@wispertel.net>.
Roberto,
Please file a JIRA issue with your observations since we are making a
concerted effort to clean up Jetspeed's memory usage and footprint. It
would be a handy place to submit your graph to us. It would be most
helpful if you could do the same for 2.2 if you have time to test there
as well.
Also, please note that a cache reporting portlet has been added to
Jetspeed administrative pages so that you can examine the current cache
counts and memory usage. That is available in the latest version of
2.1.3 post branch and 2.2 trunk.
Thanks,
Randy
Roberto Rossi wrote:
> I'd like to share with you my personal Jetspeed 2.1.3 heap usage
> analysis.
>
> After Jetspeed startup (together with j2-admin web app and another our
> internal web app), I found a strange heap usage graph (through JConsole)
> even without no requests being processed.
> The Heap starts from 40Mb about, then it increases regularly to 70Mb
> about. At this point a PSYoungGen brings it back to 40Mb about.
> This routine executes forever even if no requests are processed by the
> portal.
>
> Is it a normal Jetspeed behaviour or is it a particular issue?
> In the past, I found another user talking about this issue but no one
> explained him the reason (http://markmail.org/search/?q=jetspeed+idle
> +heap#query:jetspeed%20idle%20heap+page:1+mid:qi2fgmsz2mw7lfw5
> +state:results).
> I can send you a png image showing this.
>
> Roberto
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-user-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-user-help@portals.apache.org
strange Jetspeed heap usage
Posted by Roberto Rossi <ro...@cone.it>.
I'd like to share with you my personal Jetspeed 2.1.3 heap usage
analysis.
After Jetspeed startup (together with j2-admin web app and another our
internal web app), I found a strange heap usage graph (through JConsole)
even without no requests being processed.
The Heap starts from 40Mb about, then it increases regularly to 70Mb
about. At this point a PSYoungGen brings it back to 40Mb about.
This routine executes forever even if no requests are processed by the
portal.
Is it a normal Jetspeed behaviour or is it a particular issue?
In the past, I found another user talking about this issue but no one
explained him the reason (http://markmail.org/search/?q=jetspeed+idle
+heap#query:jetspeed%20idle%20heap+page:1+mid:qi2fgmsz2mw7lfw5
+state:results).
I can send you a png image showing this.
Roberto
Re: Running Jetspeed within Tomcat behind Apache
Posted by brunp <pa...@gmail.com>.
I tried doing that, no difference for me between changing that value between
true/false. I suspect that
since I am using my own Login Servlets/etc (not the one's that have been
distributed w/ Jetspeed), that this parameter is in affect not really
used???
Paul
David Sean Taylor-3 wrote:
>
>>
>>
>> brunp wrote:
>>>
>>> Here is the thing, with ProxyName and ProxyPort defined in the
>>> server.xml
>>> file for Tomcat, the login
>>> works and redirects me to the login page as if I were to login
>>> using the
>>> proxyname instead.
>>>
>>> The login works without a problem at that point because the FQDN is
>>> defined in my hosts file and on
>>> the DNS server.
>>>
>>> However, if I remove ProxyName and ProxyPort, then the only page
>>> visible
>>> is my login page, but the
>>> minute I hit login and issue the redirect call within my
>>> LoginProxyServlet
>>> class, all goes to hell.....so
>>> it has something to do with the redirect rules.
>>>
>>> Paul
>>>
>>>
>>
>> On another note, and it is likely realted, nobody has yet been able to
>> provide details on the following Jetspeed parameter:
>>
>> portalurl.relative.only
>>
>> I had originally assumed that upgrading to Jetspeed 2.1.3 would
>> allow me to
>> get away from using DNS names and get me into using IP addresses.
>>
>> However, I have yet to determine if this parameter has an effect or
>> not.
>> Could anyone let me know how I can test this out?
>>
>
>
>
>
> Try changing this parameter by setting it to true in
> jetspeed.properties, restart server and look at the URLs generated ,
> they will now be relative
>
> portalurl.relative.only=true
>
> This setting as true will generate all Portal URLs without schema,
> servername or port. Defining this to true (default = false) means
> requesting secure Portlet URLs won't have any effect anymore. But a
> proxy frontend (like Apache) can still be used for securing the whole
> site.
>
> See:
>
> https://issues.apache.org/jira/browse/JS2-275
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: jetspeed-user-unsubscribe@portals.apache.org
> For additional commands, e-mail: jetspeed-user-help@portals.apache.org
>
>
>
--
View this message in context: http://www.nabble.com/Running-Jetspeed-within-Tomcat-behind-Apache-tp23413109p23521882.html
Sent from the Jetspeed - User mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-user-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-user-help@portals.apache.org
Re: Running Jetspeed within Tomcat behind Apache
Posted by David Sean Taylor <d....@onehippo.com>.
>
>
> brunp wrote:
>>
>> Here is the thing, with ProxyName and ProxyPort defined in the
>> server.xml
>> file for Tomcat, the login
>> works and redirects me to the login page as if I were to login
>> using the
>> proxyname instead.
>>
>> The login works without a problem at that point because the FQDN is
>> defined in my hosts file and on
>> the DNS server.
>>
>> However, if I remove ProxyName and ProxyPort, then the only page
>> visible
>> is my login page, but the
>> minute I hit login and issue the redirect call within my
>> LoginProxyServlet
>> class, all goes to hell.....so
>> it has something to do with the redirect rules.
>>
>> Paul
>>
>>
>
> On another note, and it is likely realted, nobody has yet been able to
> provide details on the following Jetspeed parameter:
>
> portalurl.relative.only
>
> I had originally assumed that upgrading to Jetspeed 2.1.3 would
> allow me to
> get away from using DNS names and get me into using IP addresses.
>
> However, I have yet to determine if this parameter has an effect or
> not.
> Could anyone let me know how I can test this out?
>
Try changing this parameter by setting it to true in
jetspeed.properties, restart server and look at the URLs generated ,
they will now be relative
portalurl.relative.only=true
This setting as true will generate all Portal URLs without schema,
servername or port. Defining this to true (default = false) means
requesting secure Portlet URLs won't have any effect anymore. But a
proxy frontend (like Apache) can still be used for securing the whole
site.
See:
https://issues.apache.org/jira/browse/JS2-275
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-user-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-user-help@portals.apache.org
Re: Running Jetspeed within Tomcat behind Apache
Posted by brunp <pa...@gmail.com>.
brunp wrote:
>
> Here is the thing, with ProxyName and ProxyPort defined in the server.xml
> file for Tomcat, the login
> works and redirects me to the login page as if I were to login using the
> proxyname instead.
>
> The login works without a problem at that point because the FQDN is
> defined in my hosts file and on
> the DNS server.
>
> However, if I remove ProxyName and ProxyPort, then the only page visible
> is my login page, but the
> minute I hit login and issue the redirect call within my LoginProxyServlet
> class, all goes to hell.....so
> it has something to do with the redirect rules.
>
> Paul
>
>
On another note, and it is likely realted, nobody has yet been able to
provide details on the following Jetspeed parameter:
portalurl.relative.only
I had originally assumed that upgrading to Jetspeed 2.1.3 would allow me to
get away from using DNS names and get me into using IP addresses.
However, I have yet to determine if this parameter has an effect or not.
Could anyone let me know how I can test this out?
Paul
--
View this message in context: http://www.nabble.com/Running-Jetspeed-within-Tomcat-behind-Apache-tp23413109p23509620.html
Sent from the Jetspeed - User mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-user-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-user-help@portals.apache.org
Re: Running Jetspeed within Tomcat behind Apache
Posted by brunp <pa...@gmail.com>.
Here is the thing, with ProxyName and ProxyPort defined in the server.xml
file for Tomcat, the login
works and redirects me to the login page as if I were to login using the
proxyname instead.
The login works without a problem at that point because the FQDN is defined
in my hosts file and on
the DNS server.
However, if I remove ProxyName and ProxyPort, then the only page visible is
my login page, but the
minute I hit login and issue the redirect call within my LoginProxyServlet
class, all goes to hell.....so
it has something to do with the redirect rules.
Paul
--
View this message in context: http://www.nabble.com/Running-Jetspeed-within-Tomcat-behind-Apache-tp23413109p23507978.html
Sent from the Jetspeed - User mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-user-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-user-help@portals.apache.org
Re: Running Jetspeed within Tomcat behind Apache
Posted by David Dyer <dd...@artifact-software.com>.
Lots of things might be happening, Any dumps or other useful info in
the log files?
A) Are you actually reaching the LoginServlet, DefaultLoginModule and
LoginRedirectorServlet ?
B) What is the LoginRedirectorServlet mapped to in the web.xml ?
C) It may simply be a page not found.
-What profiling rule does the user you're attempting to login have?
-Is your pages directory set up to actually provide a default page
(psml file) according to that profiling rule?
To the people who know more about apache (most of my direct experience
has been working simply within tomcat) is there something in the
httpd.conf that needs to be set to allow the portal to respond from
localhost? I know I've run into issues there with portlet webapps
running under jetspeed not being able to serve out images until it was
updated.
brunp wrote:
> Equivalent to a "Page not found" error, or something to that affect. I was
> going to try a couple things tomorrow to see if I can get around the error.
>
> Paul
>
>
> David Dyer wrote:
>
>> What actually happens when you redirect to
>>
>> https://127.0.0.1:8080/portal/login/redirector ?
>>
>>
>> brunp wrote:
>>
>>> I figured as much, but if the ServletRequest returns 127.0.0.1:8080 as
>>> the
>>> servername when building the URL, then you are pooched unless you
>>> override
>>> and replace the HttpServletRequest class.
>>>
>>> Again, I had thought the property mentioned above was to enable us to use
>>> relative URL redirecting???
>>>
>>> Paul
>>>
>>>
>>> ronatartifact wrote:
>>>
>>>
>>>> I could be way off base here but I would think that your redirect has to
>>>> be something that your browser is going to have to be able to interpret.
>>>> That would mean that you have to specify your "front door"
>>>> https://10.35.5.99/portal/login/redirector in your custom code.
>>>>
>>>> Not sure that I am telling you anything that you do not already know.
>>>>
>>>> Ron
>>>>
>>>> brunp wrote:
>>>>
>>>>
>>>>> There are two systems involved. My notebook (i.e., used for browsing to
>>>>> the
>>>>> site) and the linux server that is running apache/linux.
>>>>>
>>>>> So, I enter "https://10.35.5.199/portal", where portal is the jetspeed
>>>>> root
>>>>> directory. The login page shows up and within the LoginProxyServlet,
>>>>> which
>>>>> is custom, I want to redirect to /portal/login/redirector,
>>>>> and when that occurs, my browser is then attempting to connect to
>>>>> https://127.0.0.1:8080/portal/login/redirector
>>>>>
>>>>>
>>>>> IF proxyName and ProxyPort are defined in Server.xml for tomcat, and I
>>>>> browse by FQDN, I get a redirect URL of: https://<FQDN name of
>>>>> server>/portal/login/redirector, which is a valid site.
>>>>>
>>>>> So.....that is the state of play.....trying to another locaiton on the
>>>>> same
>>>>> server.
>>>>>
>>>>>
>>>>>
>>>>> ronatartifact wrote:
>>>>>
>>>>>
>>>>>
>>>>>> localhost is the name of 127.0.0.1.
>>>>>>
>>>>>> Are you trying to redirect to localhost or some other site?
>>>>>>
>>>>>> Ron
>>>>>>
>>>>>> brunp wrote:
>>>>>>
>>>>>>
>>>>>>
>>>>>>> Thank you to all......so, I can get to my "login" page after making
>>>>>>> some
>>>>>>> macro adjustments, however, when I press login, my LoginServlet pipes
>>>>>>> out
>>>>>>> some logs, I redirect to another location, but it appears that the
>>>>>>> redirect
>>>>>>> replaces the IP address w/ 127.0.0.1
>>>>>>>
>>>>>>> So something within the Apache configuration and/or the redirect
>>>>>>> rules
>>>>>>> is
>>>>>>> replacing the x-forward-host
>>>>>>> with localhost...
>>>>>>>
>>>>>>> Paul
>>>>>>>
>>>>>>>
>>>>>>> hemantmalik wrote:
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>> You can use mod_jk module as well and then can connect to AJP
>>>>>>>> connector
>>>>>>>> of
>>>>>>>> tomcat as mentioned by Bhaskar.
>>>>>>>>
>>>>>>>> On Thu, May 7, 2009 at 9:41 PM, Bhaskar Roy
>>>>>>>> <bh...@chikpea.com>
>>>>>>>> wrote:
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>> Use ajp protocol, much easier!
>>>>>>>>>
>>>>>>>>> Thanks
>>>>>>>>> Bhaskar
>>>>>>>>> http://lims.chikpea.com
>>>>>>>>>
>>>>>>>>> On Thu, May 7, 2009 at 6:32 PM, Ron Wheeler
>>>>>>>>> <rw...@artifact-software.com>wrote:
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>> brunp wrote:
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>> I have this in profiler.xml:
>>>>>>>>>>>
>>>>>>>>>>> 158 <bean id='HostnameCriterionResolver'
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>> class='org.apache.jetspeed.profiler.rules.impl.HostnameCriterionResolver'>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>>> 159 <!-- use the dot prefix, for ex: "accounting.xyz.com"
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>> returns
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>>> "accounting" -->
>>>>>>>>>>> 160 <constructor-arg type="boolean" index="0">
>>>>>>>>>>> 161 <value>false</value>
>>>>>>>>>>> 162 </constructor-arg>
>>>>>>>>>>> 163 </bean>
>>>>>>>>>>>
>>>>>>>>>>> Paul Brun Quotes: I have this in mine too.....
>>>>>>>>>>>
>>>>>>>>>>> I will have to look into the mod_rewrite stuff tomorrow. No time
>>>>>>>>>>> this
>>>>>>>>>>> evening....
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>> I am not sure if this is the same thing that you are trying to do
>>>>>>>>>> but
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>> we
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>> have Apache proxying Jetspeed 2.1.2 and 2.1.3 in exactly the same
>>>>>>>>>> way.
>>>>>>>>>> There are no modifications to the Tomcat application .
>>>>>>>>>> Since the Jetspeed portal is reachable as localhost:8080 from the
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>> server
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>> that Apache runs on, we just added a set of proxy statements to
>>>>>>>>>> the
>>>>>>>>>> httpd-vhost.conf to proxy www.mydomain.com/myportal to
>>>>>>>>>> localhost:8080/myportal and created a dummy index.html on the
>>>>>>>>>> apache
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>> site
>>>>>>>>> to
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>> redirect www.mydomain.com to locahost:8080/myportal so the user
>>>>>>>>>> can
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>> just
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>> ask for http://www.mydomain.com
>>>>>>>>>>
>>>>>>>>>> If the tomcat is on another server, adjust your proxy destinations
>>>>>>>>>> accordingly.
>>>>>>>>>>
>>>>>>>>>> You need to enable Apache's mod_proxy but after that it is
>>>>>>>>>> trivial.
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> Ron
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> ---------------------------------------------------------------------
>>>>>>>>>> To unsubscribe, e-mail:
>>>>>>>>>> jetspeed-user-unsubscribe@portals.apache.org
>>>>>>>>>> For additional commands, e-mail:
>>>>>>>>>> jetspeed-user-help@portals.apache.org
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>> ---------------------------------------------------------------------
>>>>>> To unsubscribe, e-mail: jetspeed-user-unsubscribe@portals.apache.org
>>>>>> For additional commands, e-mail: jetspeed-user-help@portals.apache.org
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: jetspeed-user-unsubscribe@portals.apache.org
>>>> For additional commands, e-mail: jetspeed-user-help@portals.apache.org
>>>>
>>>>
>>>>
>>>>
>>>>
>>>
>>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: jetspeed-user-unsubscribe@portals.apache.org
>> For additional commands, e-mail: jetspeed-user-help@portals.apache.org
>>
>>
>>
>>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-user-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-user-help@portals.apache.org
Re: Running Jetspeed within Tomcat behind Apache
Posted by brunp <pa...@gmail.com>.
Equivalent to a "Page not found" error, or something to that affect. I was
going to try a couple things tomorrow to see if I can get around the error.
Paul
David Dyer wrote:
>
> What actually happens when you redirect to
>
> https://127.0.0.1:8080/portal/login/redirector ?
>
>
> brunp wrote:
>> I figured as much, but if the ServletRequest returns 127.0.0.1:8080 as
>> the
>> servername when building the URL, then you are pooched unless you
>> override
>> and replace the HttpServletRequest class.
>>
>> Again, I had thought the property mentioned above was to enable us to use
>> relative URL redirecting???
>>
>> Paul
>>
>>
>> ronatartifact wrote:
>>
>>> I could be way off base here but I would think that your redirect has to
>>> be something that your browser is going to have to be able to interpret.
>>> That would mean that you have to specify your "front door"
>>> https://10.35.5.99/portal/login/redirector in your custom code.
>>>
>>> Not sure that I am telling you anything that you do not already know.
>>>
>>> Ron
>>>
>>> brunp wrote:
>>>
>>>> There are two systems involved. My notebook (i.e., used for browsing to
>>>> the
>>>> site) and the linux server that is running apache/linux.
>>>>
>>>> So, I enter "https://10.35.5.199/portal", where portal is the jetspeed
>>>> root
>>>> directory. The login page shows up and within the LoginProxyServlet,
>>>> which
>>>> is custom, I want to redirect to /portal/login/redirector,
>>>> and when that occurs, my browser is then attempting to connect to
>>>> https://127.0.0.1:8080/portal/login/redirector
>>>>
>>>>
>>>> IF proxyName and ProxyPort are defined in Server.xml for tomcat, and I
>>>> browse by FQDN, I get a redirect URL of: https://<FQDN name of
>>>> server>/portal/login/redirector, which is a valid site.
>>>>
>>>> So.....that is the state of play.....trying to another locaiton on the
>>>> same
>>>> server.
>>>>
>>>>
>>>>
>>>> ronatartifact wrote:
>>>>
>>>>
>>>>> localhost is the name of 127.0.0.1.
>>>>>
>>>>> Are you trying to redirect to localhost or some other site?
>>>>>
>>>>> Ron
>>>>>
>>>>> brunp wrote:
>>>>>
>>>>>
>>>>>> Thank you to all......so, I can get to my "login" page after making
>>>>>> some
>>>>>> macro adjustments, however, when I press login, my LoginServlet pipes
>>>>>> out
>>>>>> some logs, I redirect to another location, but it appears that the
>>>>>> redirect
>>>>>> replaces the IP address w/ 127.0.0.1
>>>>>>
>>>>>> So something within the Apache configuration and/or the redirect
>>>>>> rules
>>>>>> is
>>>>>> replacing the x-forward-host
>>>>>> with localhost...
>>>>>>
>>>>>> Paul
>>>>>>
>>>>>>
>>>>>> hemantmalik wrote:
>>>>>>
>>>>>>
>>>>>>
>>>>>>> You can use mod_jk module as well and then can connect to AJP
>>>>>>> connector
>>>>>>> of
>>>>>>> tomcat as mentioned by Bhaskar.
>>>>>>>
>>>>>>> On Thu, May 7, 2009 at 9:41 PM, Bhaskar Roy
>>>>>>> <bh...@chikpea.com>
>>>>>>> wrote:
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>> Use ajp protocol, much easier!
>>>>>>>>
>>>>>>>> Thanks
>>>>>>>> Bhaskar
>>>>>>>> http://lims.chikpea.com
>>>>>>>>
>>>>>>>> On Thu, May 7, 2009 at 6:32 PM, Ron Wheeler
>>>>>>>> <rw...@artifact-software.com>wrote:
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>> brunp wrote:
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>> I have this in profiler.xml:
>>>>>>>>>>
>>>>>>>>>> 158 <bean id='HostnameCriterionResolver'
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>> class='org.apache.jetspeed.profiler.rules.impl.HostnameCriterionResolver'>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>>> 159 <!-- use the dot prefix, for ex: "accounting.xyz.com"
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>> returns
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>>> "accounting" -->
>>>>>>>>>> 160 <constructor-arg type="boolean" index="0">
>>>>>>>>>> 161 <value>false</value>
>>>>>>>>>> 162 </constructor-arg>
>>>>>>>>>> 163 </bean>
>>>>>>>>>>
>>>>>>>>>> Paul Brun Quotes: I have this in mine too.....
>>>>>>>>>>
>>>>>>>>>> I will have to look into the mod_rewrite stuff tomorrow. No time
>>>>>>>>>> this
>>>>>>>>>> evening....
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>> I am not sure if this is the same thing that you are trying to do
>>>>>>>>> but
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>> we
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>> have Apache proxying Jetspeed 2.1.2 and 2.1.3 in exactly the same
>>>>>>>>> way.
>>>>>>>>> There are no modifications to the Tomcat application .
>>>>>>>>> Since the Jetspeed portal is reachable as localhost:8080 from the
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>> server
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>> that Apache runs on, we just added a set of proxy statements to
>>>>>>>>> the
>>>>>>>>> httpd-vhost.conf to proxy www.mydomain.com/myportal to
>>>>>>>>> localhost:8080/myportal and created a dummy index.html on the
>>>>>>>>> apache
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>> site
>>>>>>>> to
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>> redirect www.mydomain.com to locahost:8080/myportal so the user
>>>>>>>>> can
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>> just
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>> ask for http://www.mydomain.com
>>>>>>>>>
>>>>>>>>> If the tomcat is on another server, adjust your proxy destinations
>>>>>>>>> accordingly.
>>>>>>>>>
>>>>>>>>> You need to enable Apache's mod_proxy but after that it is
>>>>>>>>> trivial.
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> Ron
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> ---------------------------------------------------------------------
>>>>>>>>> To unsubscribe, e-mail:
>>>>>>>>> jetspeed-user-unsubscribe@portals.apache.org
>>>>>>>>> For additional commands, e-mail:
>>>>>>>>> jetspeed-user-help@portals.apache.org
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>> ---------------------------------------------------------------------
>>>>> To unsubscribe, e-mail: jetspeed-user-unsubscribe@portals.apache.org
>>>>> For additional commands, e-mail: jetspeed-user-help@portals.apache.org
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>
>>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: jetspeed-user-unsubscribe@portals.apache.org
>>> For additional commands, e-mail: jetspeed-user-help@portals.apache.org
>>>
>>>
>>>
>>>
>>
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: jetspeed-user-unsubscribe@portals.apache.org
> For additional commands, e-mail: jetspeed-user-help@portals.apache.org
>
>
>
--
View this message in context: http://www.nabble.com/Running-Jetspeed-within-Tomcat-behind-Apache-tp23413109p23494860.html
Sent from the Jetspeed - User mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-user-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-user-help@portals.apache.org
Re: Running Jetspeed within Tomcat behind Apache
Posted by David Dyer <dd...@artifact-software.com>.
What actually happens when you redirect to
https://127.0.0.1:8080/portal/login/redirector ?
brunp wrote:
> I figured as much, but if the ServletRequest returns 127.0.0.1:8080 as the
> servername when building the URL, then you are pooched unless you override
> and replace the HttpServletRequest class.
>
> Again, I had thought the property mentioned above was to enable us to use
> relative URL redirecting???
>
> Paul
>
>
> ronatartifact wrote:
>
>> I could be way off base here but I would think that your redirect has to
>> be something that your browser is going to have to be able to interpret.
>> That would mean that you have to specify your "front door"
>> https://10.35.5.99/portal/login/redirector in your custom code.
>>
>> Not sure that I am telling you anything that you do not already know.
>>
>> Ron
>>
>> brunp wrote:
>>
>>> There are two systems involved. My notebook (i.e., used for browsing to
>>> the
>>> site) and the linux server that is running apache/linux.
>>>
>>> So, I enter "https://10.35.5.199/portal", where portal is the jetspeed
>>> root
>>> directory. The login page shows up and within the LoginProxyServlet,
>>> which
>>> is custom, I want to redirect to /portal/login/redirector,
>>> and when that occurs, my browser is then attempting to connect to
>>> https://127.0.0.1:8080/portal/login/redirector
>>>
>>>
>>> IF proxyName and ProxyPort are defined in Server.xml for tomcat, and I
>>> browse by FQDN, I get a redirect URL of: https://<FQDN name of
>>> server>/portal/login/redirector, which is a valid site.
>>>
>>> So.....that is the state of play.....trying to another locaiton on the
>>> same
>>> server.
>>>
>>>
>>>
>>> ronatartifact wrote:
>>>
>>>
>>>> localhost is the name of 127.0.0.1.
>>>>
>>>> Are you trying to redirect to localhost or some other site?
>>>>
>>>> Ron
>>>>
>>>> brunp wrote:
>>>>
>>>>
>>>>> Thank you to all......so, I can get to my "login" page after making
>>>>> some
>>>>> macro adjustments, however, when I press login, my LoginServlet pipes
>>>>> out
>>>>> some logs, I redirect to another location, but it appears that the
>>>>> redirect
>>>>> replaces the IP address w/ 127.0.0.1
>>>>>
>>>>> So something within the Apache configuration and/or the redirect rules
>>>>> is
>>>>> replacing the x-forward-host
>>>>> with localhost...
>>>>>
>>>>> Paul
>>>>>
>>>>>
>>>>> hemantmalik wrote:
>>>>>
>>>>>
>>>>>
>>>>>> You can use mod_jk module as well and then can connect to AJP
>>>>>> connector
>>>>>> of
>>>>>> tomcat as mentioned by Bhaskar.
>>>>>>
>>>>>> On Thu, May 7, 2009 at 9:41 PM, Bhaskar Roy <bh...@chikpea.com>
>>>>>> wrote:
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>> Use ajp protocol, much easier!
>>>>>>>
>>>>>>> Thanks
>>>>>>> Bhaskar
>>>>>>> http://lims.chikpea.com
>>>>>>>
>>>>>>> On Thu, May 7, 2009 at 6:32 PM, Ron Wheeler
>>>>>>> <rw...@artifact-software.com>wrote:
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>> brunp wrote:
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>> I have this in profiler.xml:
>>>>>>>>>
>>>>>>>>> 158 <bean id='HostnameCriterionResolver'
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>> class='org.apache.jetspeed.profiler.rules.impl.HostnameCriterionResolver'>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>>> 159 <!-- use the dot prefix, for ex: "accounting.xyz.com"
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>> returns
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>>> "accounting" -->
>>>>>>>>> 160 <constructor-arg type="boolean" index="0">
>>>>>>>>> 161 <value>false</value>
>>>>>>>>> 162 </constructor-arg>
>>>>>>>>> 163 </bean>
>>>>>>>>>
>>>>>>>>> Paul Brun Quotes: I have this in mine too.....
>>>>>>>>>
>>>>>>>>> I will have to look into the mod_rewrite stuff tomorrow. No time
>>>>>>>>> this
>>>>>>>>> evening....
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>> I am not sure if this is the same thing that you are trying to do
>>>>>>>> but
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>> we
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>> have Apache proxying Jetspeed 2.1.2 and 2.1.3 in exactly the same
>>>>>>>> way.
>>>>>>>> There are no modifications to the Tomcat application .
>>>>>>>> Since the Jetspeed portal is reachable as localhost:8080 from the
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>> server
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>> that Apache runs on, we just added a set of proxy statements to the
>>>>>>>> httpd-vhost.conf to proxy www.mydomain.com/myportal to
>>>>>>>> localhost:8080/myportal and created a dummy index.html on the apache
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>> site
>>>>>>> to
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>> redirect www.mydomain.com to locahost:8080/myportal so the user can
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>> just
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>> ask for http://www.mydomain.com
>>>>>>>>
>>>>>>>> If the tomcat is on another server, adjust your proxy destinations
>>>>>>>> accordingly.
>>>>>>>>
>>>>>>>> You need to enable Apache's mod_proxy but after that it is trivial.
>>>>>>>>
>>>>>>>>
>>>>>>>> Ron
>>>>>>>>
>>>>>>>>
>>>>>>>> ---------------------------------------------------------------------
>>>>>>>> To unsubscribe, e-mail: jetspeed-user-unsubscribe@portals.apache.org
>>>>>>>> For additional commands, e-mail:
>>>>>>>> jetspeed-user-help@portals.apache.org
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: jetspeed-user-unsubscribe@portals.apache.org
>>>> For additional commands, e-mail: jetspeed-user-help@portals.apache.org
>>>>
>>>>
>>>>
>>>>
>>>>
>>>
>>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: jetspeed-user-unsubscribe@portals.apache.org
>> For additional commands, e-mail: jetspeed-user-help@portals.apache.org
>>
>>
>>
>>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-user-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-user-help@portals.apache.org
Re: Running Jetspeed within Tomcat behind Apache
Posted by brunp <pa...@gmail.com>.
I figured as much, but if the ServletRequest returns 127.0.0.1:8080 as the
servername when building the URL, then you are pooched unless you override
and replace the HttpServletRequest class.
Again, I had thought the property mentioned above was to enable us to use
relative URL redirecting???
Paul
ronatartifact wrote:
>
> I could be way off base here but I would think that your redirect has to
> be something that your browser is going to have to be able to interpret.
> That would mean that you have to specify your "front door"
> https://10.35.5.99/portal/login/redirector in your custom code.
>
> Not sure that I am telling you anything that you do not already know.
>
> Ron
>
> brunp wrote:
>> There are two systems involved. My notebook (i.e., used for browsing to
>> the
>> site) and the linux server that is running apache/linux.
>>
>> So, I enter "https://10.35.5.199/portal", where portal is the jetspeed
>> root
>> directory. The login page shows up and within the LoginProxyServlet,
>> which
>> is custom, I want to redirect to /portal/login/redirector,
>> and when that occurs, my browser is then attempting to connect to
>> https://127.0.0.1:8080/portal/login/redirector
>>
>>
>> IF proxyName and ProxyPort are defined in Server.xml for tomcat, and I
>> browse by FQDN, I get a redirect URL of: https://<FQDN name of
>> server>/portal/login/redirector, which is a valid site.
>>
>> So.....that is the state of play.....trying to another locaiton on the
>> same
>> server.
>>
>>
>>
>> ronatartifact wrote:
>>
>>> localhost is the name of 127.0.0.1.
>>>
>>> Are you trying to redirect to localhost or some other site?
>>>
>>> Ron
>>>
>>> brunp wrote:
>>>
>>>> Thank you to all......so, I can get to my "login" page after making
>>>> some
>>>> macro adjustments, however, when I press login, my LoginServlet pipes
>>>> out
>>>> some logs, I redirect to another location, but it appears that the
>>>> redirect
>>>> replaces the IP address w/ 127.0.0.1
>>>>
>>>> So something within the Apache configuration and/or the redirect rules
>>>> is
>>>> replacing the x-forward-host
>>>> with localhost...
>>>>
>>>> Paul
>>>>
>>>>
>>>> hemantmalik wrote:
>>>>
>>>>
>>>>> You can use mod_jk module as well and then can connect to AJP
>>>>> connector
>>>>> of
>>>>> tomcat as mentioned by Bhaskar.
>>>>>
>>>>> On Thu, May 7, 2009 at 9:41 PM, Bhaskar Roy <bh...@chikpea.com>
>>>>> wrote:
>>>>>
>>>>>
>>>>>
>>>>>> Use ajp protocol, much easier!
>>>>>>
>>>>>> Thanks
>>>>>> Bhaskar
>>>>>> http://lims.chikpea.com
>>>>>>
>>>>>> On Thu, May 7, 2009 at 6:32 PM, Ron Wheeler
>>>>>> <rw...@artifact-software.com>wrote:
>>>>>>
>>>>>>
>>>>>>
>>>>>>> brunp wrote:
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>> I have this in profiler.xml:
>>>>>>>>
>>>>>>>> 158 <bean id='HostnameCriterionResolver'
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>> class='org.apache.jetspeed.profiler.rules.impl.HostnameCriterionResolver'>
>>>>>>
>>>>>>
>>>>>>>> 159 <!-- use the dot prefix, for ex: "accounting.xyz.com"
>>>>>>>>
>>>>>>>>
>>>>>> returns
>>>>>>
>>>>>>
>>>>>>>> "accounting" -->
>>>>>>>> 160 <constructor-arg type="boolean" index="0">
>>>>>>>> 161 <value>false</value>
>>>>>>>> 162 </constructor-arg>
>>>>>>>> 163 </bean>
>>>>>>>>
>>>>>>>> Paul Brun Quotes: I have this in mine too.....
>>>>>>>>
>>>>>>>> I will have to look into the mod_rewrite stuff tomorrow. No time
>>>>>>>> this
>>>>>>>> evening....
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>> I am not sure if this is the same thing that you are trying to do
>>>>>>> but
>>>>>>>
>>>>>>>
>>>>>> we
>>>>>>
>>>>>>
>>>>>>> have Apache proxying Jetspeed 2.1.2 and 2.1.3 in exactly the same
>>>>>>> way.
>>>>>>> There are no modifications to the Tomcat application .
>>>>>>> Since the Jetspeed portal is reachable as localhost:8080 from the
>>>>>>>
>>>>>>>
>>>>>> server
>>>>>>
>>>>>>
>>>>>>> that Apache runs on, we just added a set of proxy statements to the
>>>>>>> httpd-vhost.conf to proxy www.mydomain.com/myportal to
>>>>>>> localhost:8080/myportal and created a dummy index.html on the apache
>>>>>>>
>>>>>>>
>>>>>> site
>>>>>> to
>>>>>>
>>>>>>
>>>>>>> redirect www.mydomain.com to locahost:8080/myportal so the user can
>>>>>>>
>>>>>>>
>>>>>> just
>>>>>>
>>>>>>
>>>>>>> ask for http://www.mydomain.com
>>>>>>>
>>>>>>> If the tomcat is on another server, adjust your proxy destinations
>>>>>>> accordingly.
>>>>>>>
>>>>>>> You need to enable Apache's mod_proxy but after that it is trivial.
>>>>>>>
>>>>>>>
>>>>>>> Ron
>>>>>>>
>>>>>>>
>>>>>>> ---------------------------------------------------------------------
>>>>>>> To unsubscribe, e-mail: jetspeed-user-unsubscribe@portals.apache.org
>>>>>>> For additional commands, e-mail:
>>>>>>> jetspeed-user-help@portals.apache.org
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>
>>>>>
>>>>
>>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: jetspeed-user-unsubscribe@portals.apache.org
>>> For additional commands, e-mail: jetspeed-user-help@portals.apache.org
>>>
>>>
>>>
>>>
>>
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: jetspeed-user-unsubscribe@portals.apache.org
> For additional commands, e-mail: jetspeed-user-help@portals.apache.org
>
>
>
--
View this message in context: http://www.nabble.com/Running-Jetspeed-within-Tomcat-behind-Apache-tp23413109p23438890.html
Sent from the Jetspeed - User mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-user-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-user-help@portals.apache.org
Re: Running Jetspeed within Tomcat behind Apache
Posted by Ron Wheeler <rw...@artifact-software.com>.
I could be way off base here but I would think that your redirect has to
be something that your browser is going to have to be able to interpret.
That would mean that you have to specify your "front door"
https://10.35.5.99/portal/login/redirector in your custom code.
Not sure that I am telling you anything that you do not already know.
Ron
brunp wrote:
> There are two systems involved. My notebook (i.e., used for browsing to the
> site) and the linux server that is running apache/linux.
>
> So, I enter "https://10.35.5.199/portal", where portal is the jetspeed root
> directory. The login page shows up and within the LoginProxyServlet, which
> is custom, I want to redirect to /portal/login/redirector,
> and when that occurs, my browser is then attempting to connect to
> https://127.0.0.1:8080/portal/login/redirector
>
>
> IF proxyName and ProxyPort are defined in Server.xml for tomcat, and I
> browse by FQDN, I get a redirect URL of: https://<FQDN name of
> server>/portal/login/redirector, which is a valid site.
>
> So.....that is the state of play.....trying to another locaiton on the same
> server.
>
>
>
> ronatartifact wrote:
>
>> localhost is the name of 127.0.0.1.
>>
>> Are you trying to redirect to localhost or some other site?
>>
>> Ron
>>
>> brunp wrote:
>>
>>> Thank you to all......so, I can get to my "login" page after making some
>>> macro adjustments, however, when I press login, my LoginServlet pipes out
>>> some logs, I redirect to another location, but it appears that the
>>> redirect
>>> replaces the IP address w/ 127.0.0.1
>>>
>>> So something within the Apache configuration and/or the redirect rules is
>>> replacing the x-forward-host
>>> with localhost...
>>>
>>> Paul
>>>
>>>
>>> hemantmalik wrote:
>>>
>>>
>>>> You can use mod_jk module as well and then can connect to AJP connector
>>>> of
>>>> tomcat as mentioned by Bhaskar.
>>>>
>>>> On Thu, May 7, 2009 at 9:41 PM, Bhaskar Roy <bh...@chikpea.com>
>>>> wrote:
>>>>
>>>>
>>>>
>>>>> Use ajp protocol, much easier!
>>>>>
>>>>> Thanks
>>>>> Bhaskar
>>>>> http://lims.chikpea.com
>>>>>
>>>>> On Thu, May 7, 2009 at 6:32 PM, Ron Wheeler
>>>>> <rw...@artifact-software.com>wrote:
>>>>>
>>>>>
>>>>>
>>>>>> brunp wrote:
>>>>>>
>>>>>>
>>>>>>
>>>>>>> I have this in profiler.xml:
>>>>>>>
>>>>>>> 158 <bean id='HostnameCriterionResolver'
>>>>>>>
>>>>>>>
>>>>>>>
>>>>> class='org.apache.jetspeed.profiler.rules.impl.HostnameCriterionResolver'>
>>>>>
>>>>>
>>>>>>> 159 <!-- use the dot prefix, for ex: "accounting.xyz.com"
>>>>>>>
>>>>>>>
>>>>> returns
>>>>>
>>>>>
>>>>>>> "accounting" -->
>>>>>>> 160 <constructor-arg type="boolean" index="0">
>>>>>>> 161 <value>false</value>
>>>>>>> 162 </constructor-arg>
>>>>>>> 163 </bean>
>>>>>>>
>>>>>>> Paul Brun Quotes: I have this in mine too.....
>>>>>>>
>>>>>>> I will have to look into the mod_rewrite stuff tomorrow. No time this
>>>>>>> evening....
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>> I am not sure if this is the same thing that you are trying to do but
>>>>>>
>>>>>>
>>>>> we
>>>>>
>>>>>
>>>>>> have Apache proxying Jetspeed 2.1.2 and 2.1.3 in exactly the same way.
>>>>>> There are no modifications to the Tomcat application .
>>>>>> Since the Jetspeed portal is reachable as localhost:8080 from the
>>>>>>
>>>>>>
>>>>> server
>>>>>
>>>>>
>>>>>> that Apache runs on, we just added a set of proxy statements to the
>>>>>> httpd-vhost.conf to proxy www.mydomain.com/myportal to
>>>>>> localhost:8080/myportal and created a dummy index.html on the apache
>>>>>>
>>>>>>
>>>>> site
>>>>> to
>>>>>
>>>>>
>>>>>> redirect www.mydomain.com to locahost:8080/myportal so the user can
>>>>>>
>>>>>>
>>>>> just
>>>>>
>>>>>
>>>>>> ask for http://www.mydomain.com
>>>>>>
>>>>>> If the tomcat is on another server, adjust your proxy destinations
>>>>>> accordingly.
>>>>>>
>>>>>> You need to enable Apache's mod_proxy but after that it is trivial.
>>>>>>
>>>>>>
>>>>>> Ron
>>>>>>
>>>>>>
>>>>>> ---------------------------------------------------------------------
>>>>>> To unsubscribe, e-mail: jetspeed-user-unsubscribe@portals.apache.org
>>>>>> For additional commands, e-mail: jetspeed-user-help@portals.apache.org
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>
>>>>
>>>
>>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: jetspeed-user-unsubscribe@portals.apache.org
>> For additional commands, e-mail: jetspeed-user-help@portals.apache.org
>>
>>
>>
>>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-user-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-user-help@portals.apache.org
Re: Running Jetspeed within Tomcat behind Apache
Posted by brunp <pa...@gmail.com>.
There are two systems involved. My notebook (i.e., used for browsing to the
site) and the linux server that is running apache/linux.
So, I enter "https://10.35.5.199/portal", where portal is the jetspeed root
directory. The login page shows up and within the LoginProxyServlet, which
is custom, I want to redirect to /portal/login/redirector,
and when that occurs, my browser is then attempting to connect to
https://127.0.0.1:8080/portal/login/redirector
IF proxyName and ProxyPort are defined in Server.xml for tomcat, and I
browse by FQDN, I get a redirect URL of: https://<FQDN name of
server>/portal/login/redirector, which is a valid site.
So.....that is the state of play.....trying to another locaiton on the same
server.
ronatartifact wrote:
>
> localhost is the name of 127.0.0.1.
>
> Are you trying to redirect to localhost or some other site?
>
> Ron
>
> brunp wrote:
>> Thank you to all......so, I can get to my "login" page after making some
>> macro adjustments, however, when I press login, my LoginServlet pipes out
>> some logs, I redirect to another location, but it appears that the
>> redirect
>> replaces the IP address w/ 127.0.0.1
>>
>> So something within the Apache configuration and/or the redirect rules is
>> replacing the x-forward-host
>> with localhost...
>>
>> Paul
>>
>>
>> hemantmalik wrote:
>>
>>> You can use mod_jk module as well and then can connect to AJP connector
>>> of
>>> tomcat as mentioned by Bhaskar.
>>>
>>> On Thu, May 7, 2009 at 9:41 PM, Bhaskar Roy <bh...@chikpea.com>
>>> wrote:
>>>
>>>
>>>> Use ajp protocol, much easier!
>>>>
>>>> Thanks
>>>> Bhaskar
>>>> http://lims.chikpea.com
>>>>
>>>> On Thu, May 7, 2009 at 6:32 PM, Ron Wheeler
>>>> <rw...@artifact-software.com>wrote:
>>>>
>>>>
>>>>> brunp wrote:
>>>>>
>>>>>
>>>>>> I have this in profiler.xml:
>>>>>>
>>>>>> 158 <bean id='HostnameCriterionResolver'
>>>>>>
>>>>>>
>>>> class='org.apache.jetspeed.profiler.rules.impl.HostnameCriterionResolver'>
>>>>
>>>>>> 159 <!-- use the dot prefix, for ex: "accounting.xyz.com"
>>>>>>
>>>> returns
>>>>
>>>>>> "accounting" -->
>>>>>> 160 <constructor-arg type="boolean" index="0">
>>>>>> 161 <value>false</value>
>>>>>> 162 </constructor-arg>
>>>>>> 163 </bean>
>>>>>>
>>>>>> Paul Brun Quotes: I have this in mine too.....
>>>>>>
>>>>>> I will have to look into the mod_rewrite stuff tomorrow. No time this
>>>>>> evening....
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>> I am not sure if this is the same thing that you are trying to do but
>>>>>
>>>> we
>>>>
>>>>> have Apache proxying Jetspeed 2.1.2 and 2.1.3 in exactly the same way.
>>>>> There are no modifications to the Tomcat application .
>>>>> Since the Jetspeed portal is reachable as localhost:8080 from the
>>>>>
>>>> server
>>>>
>>>>> that Apache runs on, we just added a set of proxy statements to the
>>>>> httpd-vhost.conf to proxy www.mydomain.com/myportal to
>>>>> localhost:8080/myportal and created a dummy index.html on the apache
>>>>>
>>>> site
>>>> to
>>>>
>>>>> redirect www.mydomain.com to locahost:8080/myportal so the user can
>>>>>
>>>> just
>>>>
>>>>> ask for http://www.mydomain.com
>>>>>
>>>>> If the tomcat is on another server, adjust your proxy destinations
>>>>> accordingly.
>>>>>
>>>>> You need to enable Apache's mod_proxy but after that it is trivial.
>>>>>
>>>>>
>>>>> Ron
>>>>>
>>>>>
>>>>> ---------------------------------------------------------------------
>>>>> To unsubscribe, e-mail: jetspeed-user-unsubscribe@portals.apache.org
>>>>> For additional commands, e-mail: jetspeed-user-help@portals.apache.org
>>>>>
>>>>>
>>>>>
>>>
>>
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: jetspeed-user-unsubscribe@portals.apache.org
> For additional commands, e-mail: jetspeed-user-help@portals.apache.org
>
>
>
--
View this message in context: http://www.nabble.com/Running-Jetspeed-within-Tomcat-behind-Apache-tp23413109p23435029.html
Sent from the Jetspeed - User mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-user-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-user-help@portals.apache.org
Re: Running Jetspeed within Tomcat behind Apache
Posted by Ron Wheeler <rw...@artifact-software.com>.
localhost is the name of 127.0.0.1.
Are you trying to redirect to localhost or some other site?
Ron
brunp wrote:
> Thank you to all......so, I can get to my "login" page after making some
> macro adjustments, however, when I press login, my LoginServlet pipes out
> some logs, I redirect to another location, but it appears that the redirect
> replaces the IP address w/ 127.0.0.1
>
> So something within the Apache configuration and/or the redirect rules is
> replacing the x-forward-host
> with localhost...
>
> Paul
>
>
> hemantmalik wrote:
>
>> You can use mod_jk module as well and then can connect to AJP connector of
>> tomcat as mentioned by Bhaskar.
>>
>> On Thu, May 7, 2009 at 9:41 PM, Bhaskar Roy <bh...@chikpea.com>
>> wrote:
>>
>>
>>> Use ajp protocol, much easier!
>>>
>>> Thanks
>>> Bhaskar
>>> http://lims.chikpea.com
>>>
>>> On Thu, May 7, 2009 at 6:32 PM, Ron Wheeler
>>> <rw...@artifact-software.com>wrote:
>>>
>>>
>>>> brunp wrote:
>>>>
>>>>
>>>>> I have this in profiler.xml:
>>>>>
>>>>> 158 <bean id='HostnameCriterionResolver'
>>>>>
>>>>>
>>> class='org.apache.jetspeed.profiler.rules.impl.HostnameCriterionResolver'>
>>>
>>>>> 159 <!-- use the dot prefix, for ex: "accounting.xyz.com"
>>>>>
>>> returns
>>>
>>>>> "accounting" -->
>>>>> 160 <constructor-arg type="boolean" index="0">
>>>>> 161 <value>false</value>
>>>>> 162 </constructor-arg>
>>>>> 163 </bean>
>>>>>
>>>>> Paul Brun Quotes: I have this in mine too.....
>>>>>
>>>>> I will have to look into the mod_rewrite stuff tomorrow. No time this
>>>>> evening....
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>> I am not sure if this is the same thing that you are trying to do but
>>>>
>>> we
>>>
>>>> have Apache proxying Jetspeed 2.1.2 and 2.1.3 in exactly the same way.
>>>> There are no modifications to the Tomcat application .
>>>> Since the Jetspeed portal is reachable as localhost:8080 from the
>>>>
>>> server
>>>
>>>> that Apache runs on, we just added a set of proxy statements to the
>>>> httpd-vhost.conf to proxy www.mydomain.com/myportal to
>>>> localhost:8080/myportal and created a dummy index.html on the apache
>>>>
>>> site
>>> to
>>>
>>>> redirect www.mydomain.com to locahost:8080/myportal so the user can
>>>>
>>> just
>>>
>>>> ask for http://www.mydomain.com
>>>>
>>>> If the tomcat is on another server, adjust your proxy destinations
>>>> accordingly.
>>>>
>>>> You need to enable Apache's mod_proxy but after that it is trivial.
>>>>
>>>>
>>>> Ron
>>>>
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: jetspeed-user-unsubscribe@portals.apache.org
>>>> For additional commands, e-mail: jetspeed-user-help@portals.apache.org
>>>>
>>>>
>>>>
>>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-user-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-user-help@portals.apache.org
Re: Running Jetspeed within Tomcat behind Apache
Posted by brunp <pa...@gmail.com>.
Just adding some more information to this thread. The login page works. I can
see that I am hitting the LoginProxyServlet without a problem. At that point
is there is sort goes south. IT appears that prior to my response.redirect
call at the end of the doGet method, it inserts the Server Name of 127.0.0.1
from ServletRequest.getServerName()
I had thought the following property would resolve relative url redirects?
#----------------------------------------------------------------------------------
# Generate all Portal URLs without schema, servername or port.
# WARNING: Defining this to true (default = false) means requesting secure
Portlet URLs
# won't have any effect anymore.
# But a proxy frontend (like Apache) can still be used for securing
the whole site.
# See:
https://issues.apache.org/jira/browse/JS2-275#action_12474326
#----------------------------------------------------------------------------------
portalurl.relative.only=true
Please clarify.....
Paul
--
View this message in context: http://www.nabble.com/Running-Jetspeed-within-Tomcat-behind-Apache-tp23413109p23434446.html
Sent from the Jetspeed - User mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-user-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-user-help@portals.apache.org
Re: Running Jetspeed within Tomcat behind Apache
Posted by brunp <pa...@gmail.com>.
Thank you to all......so, I can get to my "login" page after making some
macro adjustments, however, when I press login, my LoginServlet pipes out
some logs, I redirect to another location, but it appears that the redirect
replaces the IP address w/ 127.0.0.1
So something within the Apache configuration and/or the redirect rules is
replacing the x-forward-host
with localhost...
Paul
hemantmalik wrote:
>
> You can use mod_jk module as well and then can connect to AJP connector of
> tomcat as mentioned by Bhaskar.
>
> On Thu, May 7, 2009 at 9:41 PM, Bhaskar Roy <bh...@chikpea.com>
> wrote:
>
>> Use ajp protocol, much easier!
>>
>> Thanks
>> Bhaskar
>> http://lims.chikpea.com
>>
>> On Thu, May 7, 2009 at 6:32 PM, Ron Wheeler
>> <rw...@artifact-software.com>wrote:
>>
>> > brunp wrote:
>> >
>> >> I have this in profiler.xml:
>> >>
>> >> 158 <bean id='HostnameCriterionResolver'
>> >>
>> class='org.apache.jetspeed.profiler.rules.impl.HostnameCriterionResolver'>
>> >> 159 <!-- use the dot prefix, for ex: "accounting.xyz.com"
>> returns
>> >> "accounting" -->
>> >> 160 <constructor-arg type="boolean" index="0">
>> >> 161 <value>false</value>
>> >> 162 </constructor-arg>
>> >> 163 </bean>
>> >>
>> >> Paul Brun Quotes: I have this in mine too.....
>> >>
>> >> I will have to look into the mod_rewrite stuff tomorrow. No time this
>> >> evening....
>> >>
>> >>
>> >>
>> >>
>> > I am not sure if this is the same thing that you are trying to do but
>> we
>> > have Apache proxying Jetspeed 2.1.2 and 2.1.3 in exactly the same way.
>> > There are no modifications to the Tomcat application .
>> > Since the Jetspeed portal is reachable as localhost:8080 from the
>> server
>> > that Apache runs on, we just added a set of proxy statements to the
>> > httpd-vhost.conf to proxy www.mydomain.com/myportal to
>> > localhost:8080/myportal and created a dummy index.html on the apache
>> site
>> to
>> > redirect www.mydomain.com to locahost:8080/myportal so the user can
>> just
>> > ask for http://www.mydomain.com
>> >
>> > If the tomcat is on another server, adjust your proxy destinations
>> > accordingly.
>> >
>> > You need to enable Apache's mod_proxy but after that it is trivial.
>> >
>> >
>> > Ron
>> >
>> >
>> > ---------------------------------------------------------------------
>> > To unsubscribe, e-mail: jetspeed-user-unsubscribe@portals.apache.org
>> > For additional commands, e-mail: jetspeed-user-help@portals.apache.org
>> >
>> >
>>
>
>
--
View this message in context: http://www.nabble.com/Running-Jetspeed-within-Tomcat-behind-Apache-tp23413109p23433365.html
Sent from the Jetspeed - User mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-user-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-user-help@portals.apache.org
Re: Running Jetspeed within Tomcat behind Apache
Posted by Hemant Malik <he...@gmail.com>.
You can use mod_jk module as well and then can connect to AJP connector of
tomcat as mentioned by Bhaskar.
On Thu, May 7, 2009 at 9:41 PM, Bhaskar Roy <bh...@chikpea.com> wrote:
> Use ajp protocol, much easier!
>
> Thanks
> Bhaskar
> http://lims.chikpea.com
>
> On Thu, May 7, 2009 at 6:32 PM, Ron Wheeler
> <rw...@artifact-software.com>wrote:
>
> > brunp wrote:
> >
> >> I have this in profiler.xml:
> >>
> >> 158 <bean id='HostnameCriterionResolver'
> >>
> class='org.apache.jetspeed.profiler.rules.impl.HostnameCriterionResolver'>
> >> 159 <!-- use the dot prefix, for ex: "accounting.xyz.com"
> returns
> >> "accounting" -->
> >> 160 <constructor-arg type="boolean" index="0">
> >> 161 <value>false</value>
> >> 162 </constructor-arg>
> >> 163 </bean>
> >>
> >> Paul Brun Quotes: I have this in mine too.....
> >>
> >> I will have to look into the mod_rewrite stuff tomorrow. No time this
> >> evening....
> >>
> >>
> >>
> >>
> > I am not sure if this is the same thing that you are trying to do but we
> > have Apache proxying Jetspeed 2.1.2 and 2.1.3 in exactly the same way.
> > There are no modifications to the Tomcat application .
> > Since the Jetspeed portal is reachable as localhost:8080 from the server
> > that Apache runs on, we just added a set of proxy statements to the
> > httpd-vhost.conf to proxy www.mydomain.com/myportal to
> > localhost:8080/myportal and created a dummy index.html on the apache site
> to
> > redirect www.mydomain.com to locahost:8080/myportal so the user can
> just
> > ask for http://www.mydomain.com
> >
> > If the tomcat is on another server, adjust your proxy destinations
> > accordingly.
> >
> > You need to enable Apache's mod_proxy but after that it is trivial.
> >
> >
> > Ron
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: jetspeed-user-unsubscribe@portals.apache.org
> > For additional commands, e-mail: jetspeed-user-help@portals.apache.org
> >
> >
>
Re: Running Jetspeed within Tomcat behind Apache
Posted by Bhaskar Roy <bh...@chikpea.com>.
Use ajp protocol, much easier!
Thanks
Bhaskar
http://lims.chikpea.com
On Thu, May 7, 2009 at 6:32 PM, Ron Wheeler
<rw...@artifact-software.com>wrote:
> brunp wrote:
>
>> I have this in profiler.xml:
>>
>> 158 <bean id='HostnameCriterionResolver'
>> class='org.apache.jetspeed.profiler.rules.impl.HostnameCriterionResolver'>
>> 159 <!-- use the dot prefix, for ex: "accounting.xyz.com" returns
>> "accounting" -->
>> 160 <constructor-arg type="boolean" index="0">
>> 161 <value>false</value>
>> 162 </constructor-arg>
>> 163 </bean>
>>
>> Paul Brun Quotes: I have this in mine too.....
>>
>> I will have to look into the mod_rewrite stuff tomorrow. No time this
>> evening....
>>
>>
>>
>>
> I am not sure if this is the same thing that you are trying to do but we
> have Apache proxying Jetspeed 2.1.2 and 2.1.3 in exactly the same way.
> There are no modifications to the Tomcat application .
> Since the Jetspeed portal is reachable as localhost:8080 from the server
> that Apache runs on, we just added a set of proxy statements to the
> httpd-vhost.conf to proxy www.mydomain.com/myportal to
> localhost:8080/myportal and created a dummy index.html on the apache site to
> redirect www.mydomain.com to locahost:8080/myportal so the user can just
> ask for http://www.mydomain.com
>
> If the tomcat is on another server, adjust your proxy destinations
> accordingly.
>
> You need to enable Apache's mod_proxy but after that it is trivial.
>
>
> Ron
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: jetspeed-user-unsubscribe@portals.apache.org
> For additional commands, e-mail: jetspeed-user-help@portals.apache.org
>
>
Re: Running Jetspeed within Tomcat behind Apache
Posted by Ron Wheeler <rw...@artifact-software.com>.
brunp wrote:
> I have this in profiler.xml:
>
> 158 <bean id='HostnameCriterionResolver'
> class='org.apache.jetspeed.profiler.rules.impl.HostnameCriterionResolver'>
> 159 <!-- use the dot prefix, for ex: "accounting.xyz.com" returns
> "accounting" -->
> 160 <constructor-arg type="boolean" index="0">
> 161 <value>false</value>
> 162 </constructor-arg>
> 163 </bean>
>
> Paul Brun Quotes: I have this in mine too.....
>
> I will have to look into the mod_rewrite stuff tomorrow. No time this
> evening....
>
>
>
I am not sure if this is the same thing that you are trying to do but we
have Apache proxying Jetspeed 2.1.2 and 2.1.3 in exactly the same way.
There are no modifications to the Tomcat application .
Since the Jetspeed portal is reachable as localhost:8080 from the server
that Apache runs on, we just added a set of proxy statements to the
httpd-vhost.conf to proxy www.mydomain.com/myportal to
localhost:8080/myportal and created a dummy index.html on the apache
site to redirect www.mydomain.com to locahost:8080/myportal so the user
can just ask for http://www.mydomain.com
If the tomcat is on another server, adjust your proxy destinations
accordingly.
You need to enable Apache's mod_proxy but after that it is trivial.
Ron
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-user-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-user-help@portals.apache.org
Re: Running Jetspeed within Tomcat behind Apache
Posted by brunp <pa...@gmail.com>.
I have this in profiler.xml:
158 <bean id='HostnameCriterionResolver'
class='org.apache.jetspeed.profiler.rules.impl.HostnameCriterionResolver'>
159 <!-- use the dot prefix, for ex: "accounting.xyz.com" returns
"accounting" -->
160 <constructor-arg type="boolean" index="0">
161 <value>false</value>
162 </constructor-arg>
163 </bean>
Paul Brun Quotes: I have this in mine too.....
I will have to look into the mod_rewrite stuff tomorrow. No time this
evening....
--
View this message in context: http://www.nabble.com/Running-Jetspeed-within-Tomcat-behind-Apache-tp23413109p23418543.html
Sent from the Jetspeed - User mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-user-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-user-help@portals.apache.org
Re: Running Jetspeed within Tomcat behind Apache
Posted by Mansour Al Akeel <ma...@gmail.com>.
While I haven't expreinced somehting like this, but I will try to help,
until (hopefully) someone else who have seen this gives us an
advice. See my comments.
On Wed May 06,2009 11:55 am, brunp wrote:
>
>
>
> brunp wrote:
> >
> > So.....I have Jetspeed properly updated, the first login page shows up a
> > little funny and contains a *# character which I think is somehow making
> > is way from the jetspeed_macros.vm file.
Noramly comments in vm starts with ## for single line. For mutli line:
#*
This is a multiline comment.
This is the second line
*#
Refere to end of page
http://velocity.apache.org/engine/devel/vtl-reference-guide.html
You may have deleted the first part, and left the closing comment ?
> >
> > However, more importantly, when I try to log in, the IP portion of the URL
> > seems to move over to wanting to load up the page from 127.0.0.1?
> >
I have this in profiler.xml:
158 <bean id='HostnameCriterionResolver' class='org.apache.jetspeed.profiler.rules.impl.HostnameCriterionResolver'>
159 <!-- use the dot prefix, for ex: "accounting.xyz.com" returns "accounting" -->
160 <constructor-arg type="boolean" index="0">
161 <value>false</value>
162 </constructor-arg>
163 </bean>
I don't know what it says in yours.
> > Would this be related to improper redirect rules within the httpd.conf
if you are using mod_rewrite, I don't think it has the ability to write
back the url in the browser, however, it might be resolving the
request and passing it to jetspeed which is resutling in it getting
the wrong hostname.
> > files within Apache? I did remove the proxyName and proxyPort
> > configuration from within Tomcat, which apparently was required in version
> > 2.0, but I think is no longer required in 2.1.3 of Jetspeed.
Would it be hard to put back the files you removed and see if that
resolves the issue ? You need to narrow down the cause, and isolate it
,so deal with every possibility separately. If you can disable
mod_rewrite, this will be a great idea. Try it, if it doesn't work then
put back the files you removed, and test it. Once it works fine, you can
tell what it causing the issue.
Let us know if that helped !
> >
> > Help appreciated.
> > Paul
> >
>
> Could this be part of the problem:
>
> @400000004a01dca32dcd22c4 [14:53:13] INFO [velocity] - Null reference
> [template 'decorations/layout/loginPage/header.vm', line 1, column 1] : $Id
> cannot be resolved.
> @400000004a01dca32ee954ac [14:53:13] INFO [velocity] - Null reference
> [template 'decorations/portlet/loginPortlet/decorator.vm', line 10, column
> 43] : ${decoratorId} cannot be resolved.
> @400000004a01dca32ef0da74 [14:53:13] INFO [velocity] - Null reference
> [template 'decorations/portlet/loginPortlet/decorator.vm', line 16, column
> 41] : ${decoratorId} cannot be resolved.
> @400000004a01dcc0383e27bc [14:53:42] INFO [velocity] - Null reference
> [template 'decorations/layout/loginPage/header.vm', line 1, column 1] : $Id
> cannot be resolved.
> @400000004a01dcc0386a8334 [14:53:42] INFO [velocity] - Null reference
> [template 'decorations/portlet/loginPortlet/decorator.vm', line 10, column
> 43] : ${decoratorId} cannot be resolved.
> @400000004a01dcc0386fd67c [14:53:42] INFO [velocity] - Null reference
> [template 'decorations/portlet/loginPortlet/decorator.vm', line 16, column
> 41] : ${decoratorId} cannot be resolved.
> @400000004a01dcd403b89554 [14:54:02] INFO [velocity] - Null reference
> [template 'decorations/layout/loginPage/header.vm', line 1, column 1] : $Id
> cannot be resolved.
> @400000004a01dcd403ed8fd4 [14:54:02] INFO [velocity] - Null reference
> [template 'decorations/portlet/loginPortlet/decorator.vm', line 10, column
> 43] : ${decoratorId} cannot be resolved.
> @400000004a01dcd403f35464 [14:54:02] INFO [velocity] - Null reference
> [template 'decorations/portlet/loginPortlet/decorator.vm', line 16, column
> 41] : ${decoratorId} cannot be resolved.
> @400000004a01dcdb04dd3f34 [14:54:09] INFO [velocity] - Null reference
> [template 'decorations/layout/loginPage/header.vm', line 1, column 1] : $Id
> cannot be resolved.
> @400000004a01dcdb053cc06c [14:54:09] INFO [velocity] - Null reference
> [template 'decorations/portlet/loginPortlet/decorator.vm', line 10, column
> 43] : ${decoratorId} cannot be resolved.
> @400000004a01dcdb0547d45c [14:54:09] INFO [velocity] - Null reference
> [template 'decorations/portlet/loginPortlet/decorator.vm', line 16, column
> 41] : ${decoratorId} cannot be resolved.
> @400000004a01dcde172a2ef4 [14:54:12] INFO [velocity] - Null reference
> [template 'decorations/layout/loginPage/header.vm', line 1, column 1] : $Id
> cannot be resolved.
> @400000004a01dcde17642e9c [14:54:12] INFO [velocity] - Null reference
> [template 'decorations/portlet/loginPortlet/decorator.vm', line 10, column
> 43] : ${decoratorId} cannot be resolved.
> @400000004a01dcde1768ed74 [14:54:12] INFO [velocity] - Null reference
> [template 'decorations/portlet/loginPortlet/decorator.vm', line 16, column
> 41] : ${decoratorId} cannot be resolved.
>
> --
> View this message in context: http://www.nabble.com/Running-Jetspeed-within-Tomcat-behind-Apache-tp23413109p23413204.html
> Sent from the Jetspeed - User mailing list archive at Nabble.com.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: jetspeed-user-unsubscribe@portals.apache.org
> For additional commands, e-mail: jetspeed-user-help@portals.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-user-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-user-help@portals.apache.org
Re: Running Jetspeed within Tomcat behind Apache
Posted by brunp <pa...@gmail.com>.
I will check all of these things out, but can I ask first the following:
With Jetspeed 2.1.3, am I able to access the site via IP or FQDN? i.e., do I
need to have ProxyName and ProxyPort defined within the server.xml for
tomcat?
Paul
brunp wrote:
>
>
>
> brunp wrote:
>>
>> So.....I have Jetspeed properly updated, the first login page shows up a
>> little funny and contains a *# character which I think is somehow making
>> is way from the jetspeed_macros.vm file.
>>
>> However, more importantly, when I try to log in, the IP portion of the
>> URL seems to move over to wanting to load up the page from 127.0.0.1?
>>
>> Would this be related to improper redirect rules within the httpd.conf
>> files within Apache? I did remove the proxyName and proxyPort
>> configuration from within Tomcat, which apparently was required in
>> version 2.0, but I think is no longer required in 2.1.3 of Jetspeed.
>>
>> Help appreciated.
>> Paul
>>
>
> Could this be part of the problem:
>
> @400000004a01dca32dcd22c4 [14:53:13] INFO [velocity] - Null reference
> [template 'decorations/layout/loginPage/header.vm', line 1, column 1] :
> $Id cannot be resolved.
> @400000004a01dca32ee954ac [14:53:13] INFO [velocity] - Null reference
> [template 'decorations/portlet/loginPortlet/decorator.vm', line 10, column
> 43] : ${decoratorId} cannot be resolved.
> @400000004a01dca32ef0da74 [14:53:13] INFO [velocity] - Null reference
> [template 'decorations/portlet/loginPortlet/decorator.vm', line 16, column
> 41] : ${decoratorId} cannot be resolved.
> @400000004a01dcc0383e27bc [14:53:42] INFO [velocity] - Null reference
> [template 'decorations/layout/loginPage/header.vm', line 1, column 1] :
> $Id cannot be resolved.
> @400000004a01dcc0386a8334 [14:53:42] INFO [velocity] - Null reference
> [template 'decorations/portlet/loginPortlet/decorator.vm', line 10, column
> 43] : ${decoratorId} cannot be resolved.
> @400000004a01dcc0386fd67c [14:53:42] INFO [velocity] - Null reference
> [template 'decorations/portlet/loginPortlet/decorator.vm', line 16, column
> 41] : ${decoratorId} cannot be resolved.
> @400000004a01dcd403b89554 [14:54:02] INFO [velocity] - Null reference
> [template 'decorations/layout/loginPage/header.vm', line 1, column 1] :
> $Id cannot be resolved.
> @400000004a01dcd403ed8fd4 [14:54:02] INFO [velocity] - Null reference
> [template 'decorations/portlet/loginPortlet/decorator.vm', line 10, column
> 43] : ${decoratorId} cannot be resolved.
> @400000004a01dcd403f35464 [14:54:02] INFO [velocity] - Null reference
> [template 'decorations/portlet/loginPortlet/decorator.vm', line 16, column
> 41] : ${decoratorId} cannot be resolved.
> @400000004a01dcdb04dd3f34 [14:54:09] INFO [velocity] - Null reference
> [template 'decorations/layout/loginPage/header.vm', line 1, column 1] :
> $Id cannot be resolved.
> @400000004a01dcdb053cc06c [14:54:09] INFO [velocity] - Null reference
> [template 'decorations/portlet/loginPortlet/decorator.vm', line 10, column
> 43] : ${decoratorId} cannot be resolved.
> @400000004a01dcdb0547d45c [14:54:09] INFO [velocity] - Null reference
> [template 'decorations/portlet/loginPortlet/decorator.vm', line 16, column
> 41] : ${decoratorId} cannot be resolved.
> @400000004a01dcde172a2ef4 [14:54:12] INFO [velocity] - Null reference
> [template 'decorations/layout/loginPage/header.vm', line 1, column 1] :
> $Id cannot be resolved.
> @400000004a01dcde17642e9c [14:54:12] INFO [velocity] - Null reference
> [template 'decorations/portlet/loginPortlet/decorator.vm', line 10, column
> 43] : ${decoratorId} cannot be resolved.
> @400000004a01dcde1768ed74 [14:54:12] INFO [velocity] - Null reference
> [template 'decorations/portlet/loginPortlet/decorator.vm', line 16, column
> 41] : ${decoratorId} cannot be resolved.
>
>
--
View this message in context: http://www.nabble.com/Running-Jetspeed-within-Tomcat-behind-Apache-tp23413109p23418132.html
Sent from the Jetspeed - User mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-user-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-user-help@portals.apache.org
Re: Running Jetspeed within Tomcat behind Apache
Posted by brunp <pa...@gmail.com>.
brunp wrote:
>
> So.....I have Jetspeed properly updated, the first login page shows up a
> little funny and contains a *# character which I think is somehow making
> is way from the jetspeed_macros.vm file.
>
> However, more importantly, when I try to log in, the IP portion of the URL
> seems to move over to wanting to load up the page from 127.0.0.1?
>
> Would this be related to improper redirect rules within the httpd.conf
> files within Apache? I did remove the proxyName and proxyPort
> configuration from within Tomcat, which apparently was required in version
> 2.0, but I think is no longer required in 2.1.3 of Jetspeed.
>
> Help appreciated.
> Paul
>
Could this be part of the problem:
@400000004a01dca32dcd22c4 [14:53:13] INFO [velocity] - Null reference
[template 'decorations/layout/loginPage/header.vm', line 1, column 1] : $Id
cannot be resolved.
@400000004a01dca32ee954ac [14:53:13] INFO [velocity] - Null reference
[template 'decorations/portlet/loginPortlet/decorator.vm', line 10, column
43] : ${decoratorId} cannot be resolved.
@400000004a01dca32ef0da74 [14:53:13] INFO [velocity] - Null reference
[template 'decorations/portlet/loginPortlet/decorator.vm', line 16, column
41] : ${decoratorId} cannot be resolved.
@400000004a01dcc0383e27bc [14:53:42] INFO [velocity] - Null reference
[template 'decorations/layout/loginPage/header.vm', line 1, column 1] : $Id
cannot be resolved.
@400000004a01dcc0386a8334 [14:53:42] INFO [velocity] - Null reference
[template 'decorations/portlet/loginPortlet/decorator.vm', line 10, column
43] : ${decoratorId} cannot be resolved.
@400000004a01dcc0386fd67c [14:53:42] INFO [velocity] - Null reference
[template 'decorations/portlet/loginPortlet/decorator.vm', line 16, column
41] : ${decoratorId} cannot be resolved.
@400000004a01dcd403b89554 [14:54:02] INFO [velocity] - Null reference
[template 'decorations/layout/loginPage/header.vm', line 1, column 1] : $Id
cannot be resolved.
@400000004a01dcd403ed8fd4 [14:54:02] INFO [velocity] - Null reference
[template 'decorations/portlet/loginPortlet/decorator.vm', line 10, column
43] : ${decoratorId} cannot be resolved.
@400000004a01dcd403f35464 [14:54:02] INFO [velocity] - Null reference
[template 'decorations/portlet/loginPortlet/decorator.vm', line 16, column
41] : ${decoratorId} cannot be resolved.
@400000004a01dcdb04dd3f34 [14:54:09] INFO [velocity] - Null reference
[template 'decorations/layout/loginPage/header.vm', line 1, column 1] : $Id
cannot be resolved.
@400000004a01dcdb053cc06c [14:54:09] INFO [velocity] - Null reference
[template 'decorations/portlet/loginPortlet/decorator.vm', line 10, column
43] : ${decoratorId} cannot be resolved.
@400000004a01dcdb0547d45c [14:54:09] INFO [velocity] - Null reference
[template 'decorations/portlet/loginPortlet/decorator.vm', line 16, column
41] : ${decoratorId} cannot be resolved.
@400000004a01dcde172a2ef4 [14:54:12] INFO [velocity] - Null reference
[template 'decorations/layout/loginPage/header.vm', line 1, column 1] : $Id
cannot be resolved.
@400000004a01dcde17642e9c [14:54:12] INFO [velocity] - Null reference
[template 'decorations/portlet/loginPortlet/decorator.vm', line 10, column
43] : ${decoratorId} cannot be resolved.
@400000004a01dcde1768ed74 [14:54:12] INFO [velocity] - Null reference
[template 'decorations/portlet/loginPortlet/decorator.vm', line 16, column
41] : ${decoratorId} cannot be resolved.
--
View this message in context: http://www.nabble.com/Running-Jetspeed-within-Tomcat-behind-Apache-tp23413109p23413204.html
Sent from the Jetspeed - User mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-user-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-user-help@portals.apache.org