You seem to have missed the "Please remove all of the commented parts.." part
of the request.
rakesh k wrote:
Hi
Thanks for replying for on my question.
Please find the details below, you had requested. sorry for troubling you
much , i ma hereby providing the details of server.xml below.
Hi
Thanks for replying for on my question.
Please find the details below, you had requested. sorry for troubling you
much , i ma hereby providing the details of server.xml below.
Got it thanks! Will try that
On Mon, Aug 15, 2011 at 12:54 PM, Mark Thomas wrote:
> On 15/08/2011 20:39, Mohit Anchlia wrote:
>>
>> On Mon, Aug 15, 2011 at 12:17 PM, Pid wrote:
>>>
>>> On 15/08/2011 18:05, Mohit Anchlia wrote:
Is this even possible with tomcat?
>>>
>>> In Tomcat 7.0:
>
Hi Charles,
Thanks for taking the time to answer. I'm using Tomcat 6.0 on Solaris
I understand it's not ideal, however, I have to work this way because of a
framework built for a different platform. The deployment mechanisms are such
that they don't deploy to ROOT.
Anyway with you're inspiring w
> From: Furst, Carl [mailto:carl.fu...@mlb.com]
> Subject: Why is the tomcat welcome page showing?
> In server.xml I have a Host section set up with a Context that
> has a path set to "".
Unfortunate that you choose to use the least desirable method of setting the
default webapp.
> I see in t
To follow up on this.. I removed the ROOT folder from the webapps.. and it
still shows up even when I have re-defined the default Context.
Where does the welcome page get rendered?
Thanks,
Carl Furst
-Original Message-
From: Furst, Carl [mailto:carl.fu...@mlb.com]
Sent: Monday, Augus
Hey all,
In server.xml I have a Host section set up with a Context that has a path
set to "". I see in the logs that the webapp assigned to that path is indeed
executing when I hit '/'. However the browser shows the Tomcat homepage.
"If you're seeing this page via a web browser, it means you've
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Karl,
On 8/15/2011 2:09 PM, Lataxes, Karl wrote:
> I wrote the code to generate the session id and add it as an HTTP
> header at the recommendation of someone on the users list.
Not to open a whole can of worms, but why are you generating your own
s
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Chema,
On 8/12/2011 2:56 PM, Chema wrote:
>> Why bother?
>>
>> " As soon as the user logs out of one web application (for example,
>> by invalidating the corresponding session if form based login is
>> used), the user's sessions in all web applicatio
On 15.08.2011 21:20, Pid wrote:
> On 15/08/2011 19:09, Lataxes, Karl wrote:
>> I wrote the code to generate the session id and add it as an HTTP header at
>> the recommendation of someone on the users list. The problem now is
>> appending the jvmroute to the generated session id in order to get
> From: Jesse Farinacci [mailto:jie...@gmail.com]
> Subject: Re: Tomcat war context path
> You could also bundle a META-INF/context.xml file which looks something akin
> to:
>
>
Pretty much wrong on all counts:
1) The path attribute is not allowed when the element is in
META-INF/context.x
On 15/08/2011 20:45, Jesse Farinacci wrote:
Greetings,
On Mon, Aug 15, 2011 at 3:39 PM, Mohit Anchlia wrote:
Currently when I deploy abc-SNAPSHOT-01.war I access is something like
http://localhost:8080/abc-SNAPSHOT-01.war
How can I change the context root such that I can access it as
http://l
On 15/08/2011 20:39, Mohit Anchlia wrote:
On Mon, Aug 15, 2011 at 12:17 PM, Pid wrote:
On 15/08/2011 18:05, Mohit Anchlia wrote:
Is this even possible with tomcat?
In Tomcat 7.0:
abc##SNAPSHOT-01.war
abc##SNAPSHOT-02.war
abc##SNAPSHOT-03.war
abc##SNAPSHOT-04.war
etc
Sorry I don't
Greetings,
On Mon, Aug 15, 2011 at 3:39 PM, Mohit Anchlia wrote:
Currently when I deploy abc-SNAPSHOT-01.war I access is something like
http://localhost:8080/abc-SNAPSHOT-01.war
How can I change the context root such that I can access it as
http://localhost:8080/abc?
On Mon, Aug 15, 2011 at 12:17 PM, Pid wrote:
> On 15/08/2011 18:05, Mohit Anchlia wrote:
>> Is this even possible with tomcat?
>
> In Tomcat 7.0:
>
> abc##SNAPSHOT-01.war
> abc##SNAPSHOT-02.war
> abc##SNAPSHOT-03.war
> abc##SNAPSHOT-04.war
>
> etc
Sorry I don't follow. What do I need to do ch
On 15/08/2011 19:09, Lataxes, Karl wrote:
> I wrote the code to generate the session id and add it as an HTTP header at
> the recommendation of someone on the users list. The problem now is
> appending the jvmroute to the generated session id in order to get session
> stickiness to work. If th
On 15/08/2011 18:05, Mohit Anchlia wrote:
> Is this even possible with tomcat?
In Tomcat 7.0:
abc##SNAPSHOT-01.war
abc##SNAPSHOT-02.war
abc##SNAPSHOT-03.war
abc##SNAPSHOT-04.war
etc
> On Thu, Aug 11, 2011 at 12:32 PM, Mohit Anchlia
> wrote:
>> Currently when I deploy abc-SNAPSHOT-01.war
I wrote the code to generate the session id and add it as an HTTP header at the
recommendation of someone on the users list. The problem now is appending the
jvmroute to the generated session id in order to get session stickiness to
work. If there were some way for the servlet to retrieve the
Thanks Chris, for your answers.
My understanding was that tomcat figures out the changes in the re-deployed war
file and starts to explode it in order to overwrite the existing exploded
directories in order to serve the changes in war file. But it looks like it
does not overwrite the exploded f
On 15/08/2011 17:49, Johannes Ernst wrote:
> I will try that, thanks, and report back.
>
> If it works, will that create one ClassLoader for foo.war, or two (one per
> context?)
Two. Always.
Mark
-
To unsubscribe, e-mail: user
Is this even possible with tomcat?
On Thu, Aug 11, 2011 at 12:32 PM, Mohit Anchlia wrote:
> Currently when I deploy abc-SNAPSHOT-01.war I access is something like
> http://localhost:8080/abc-SNAPSHOT-01.war
>
> How can I change the context root such that I can access it as
> http://localhost:8080
On 15.08.2011 17:09, Lataxes, Karl wrote:
> Yes, the space before "servlet" is a copy/paste error.
>
> I made the LogFormat additions to httpd.conf, set the mod_jk logging level to
> "debug" and ran some additional tests.
>
> The session id did appear in the access_log I generated:
>
> 2000-1-2
I will try that, thanks, and report back.
If it works, will that create one ClassLoader for foo.war, or two (one per
context?)
On Aug 15, 2011, at 9:43, Mark Thomas wrote:
> On 15/08/2011 17:38, Johannes Ernst wrote:
>> I'd like to run the same web app at multiple paths in Tomcat 6, e.g.
>>
2011/8/15 Chen Paz :
>
> Hi,
>
> I am using a servlet to intercept form based authentication in order to
> insert attribute into the request
What parameter do you want to insert into the request ?
I don't know, but maybe you can do the same with a custom realm
Or, using by Spring Security
On 15/08/2011 17:38, Johannes Ernst wrote:
> I'd like to run the same web app at multiple paths in Tomcat 6, e.g.
> /foo1 -> foo.war
> /foo2 -> foo.war
>
> I was thinking of creating
> $CATALINA_BASE/conf/[enginename]/[hostname]/foo1.xml
> $CATALINA_BASE/conf/[enginename]/[
I'd like to run the same web app at multiple paths in Tomcat 6, e.g.
/foo1 -> foo.war
/foo2 -> foo.war
I was thinking of creating
$CATALINA_BASE/conf/[enginename]/[hostname]/foo1.xml
$CATALINA_BASE/conf/[enginename]/[hostname]/foo2.xml
with different entries for dat
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Chuck,
On 8/15/2011 9:49 AM, Caldarale, Charles R wrote:
>> From: Chen Paz [mailto:chen@expand.com] Subject:
>> j_security_check and RequestDispatcher forward
>
>> I am using a servlet to intercept form based authentication in
>> order to insert
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
G,
On 8/12/2011 4:59 PM, exquisite wrote:
> Now when i renamed my war to ROOT.war and drop it in webapps folder
> (without any context in server.xml), it deploys fine for the first
> time as the root app (Creates a ROOT folder in webapps), but if i
Yes, the space before "servlet" is a copy/paste error.
I made the LogFormat additions to httpd.conf, set the mod_jk logging level to
"debug" and ran some additional tests.
The session id did appear in the access_log I generated:
2000-1-200-ap-1313413815567
In the mod_jk.log, I also noted sever
Filter is not possible. AFAIK you can not use filter before j_security_check in
Tomcat...
-Original Message-
From: Caldarale, Charles R [mailto:chuck.caldar...@unisys.com]
Sent: Monday, August 15, 2011 4:50 PM
To: Tomcat Users List
Subject: RE: j_security_check and RequestDispatcher forw
> From: Chen Paz [mailto:chen@expand.com]
> Subject: j_security_check and RequestDispatcher forward
> I am using a servlet to intercept form based authentication in order
> to insert attribute into the request and then to redirect the request
> to j_security_check using RequestDispatcher.
I
Hi,
I am using a servlet to intercept form based authentication in order to insert
attribute into the request and then to redirect the request to j_security_check
using RequestDispatcher.
But I'm getting a 404 page with the following error:
type Status report
message /myApp/j_security_chec
32 matches
Mail list logo