Re: [EXT]Re: 404 for j_security_check

[Christopher Schultz]

Rick,

On 3/19/24 12:58, Rick Noel wrote:

Thanks for the help, I agree with all your statements.

I now see the  JSESSIONID cookies.

I found a bug in my code. My issue was nothing to do with Tomcat behavior.


Sorry for you, but glad it wasn't us :)

-chris


-Original Message-
From: Christopher Schultz 
Sent: Sunday, March 17, 2024 10:57 AM
To: users@tomcat.apache.org
Subject: Re: [EXT]Re: 404 for j_security_check

[You don't often get email from ch...@christopherschultz.net. Learn why this is 
important at https://aka.ms/LearnAboutSenderIdentification ]

Rick,

On 3/15/24 13:49, Rick Noel wrote:


I really only want auth once

All hits to jsp pages after a successful login do not trigger the Auth process 
again.

But hits to java action class servlets do trigger the Auth process

Its  like session data is being lost for some pages but not for others


Can you watch the HTTP headers for your interaction to see what's happening? 
The browser should be sending JSESSIONID cookies with each request. If the 
server isn't sending any Set-Cookie header, the browser should leave things as 
they are.

Please note that Tomcat will send Set-Cookie when a session is created (by 
default, every JSP will create a session IIRC if you declare it to use 
sessions), plus Tomcat will rotate the session identifier as part of the 
authentication process. If you have code on the client that is storing the 
session and using it later, if your session id is being updated during 
authentication you need to make sure it gets updated everywhere the client is 
using it.


I was thinking maybe this is reason..

The Expires header specifies when content will expire, or how long content is 
"fresh."
After this time, the Portal Server will always check back with the remote 
server to see if the content has changed.
Most Web servers allow setting an absolute time to expire, a time
based on the last time that the client saw the object (last access time), or a 
time based on the last time the document changed on your server (last 
modification time).

In JSP, we can set caching to forever using the Expires header like so.

response.setDateHeader("Expires",Long.MAX_VALUE)

BUT I do not want to change my application code, I just want to tell
Tomcat 10 to stop Expiring cache so that session log in data is not
lost


No, the cache here refers to the client's resource (e.g. page, image,
etc.) cache. It has nothing to do with what's happening on the server.


My main question is
I want to know how to configure Tomcat 10 to not loose session data
that tells the user has successfully logged in


Are you properly encoding your URLs in your page like with 
HttpServletResponse.encodeURL()? If you are using cookie-based session-tracking 
it probably won't matter, but it's best practice to always do that to ensure 
your URLs are generated properly.

-chris


-Original Message-
From: Christopher Schultz 
Sent: Friday, March 15, 2024 12:19 PM
To: users@tomcat.apache.org
Subject: [EXT]Re: 404 for j_security_check

[You don't often get email from ch...@christopherschultz.net. Learn
why this is important at https://aka.ms/LearnAboutSenderIdentification
]

Rick,

On 3/14/24 15:37, Rick Noel wrote:

After moving from tomcat 9 to tomcat 10 after a user successfully
logs in and then hits a restricted page, the login page is hit again
but on this second login hit I get 404 page not found

This is actually expected, since j_security_check is only supposed to be used 
when the container (Tomcat) interrupts a user workflow to request 
authentication.


How do I set the correct path in my  login jsp so that
j_security_check is found?

BTW  I actually am wondering why a  successful logged on user would
even be sent to the log in page again?

That's more of a question for your application than anything else.


My login page  is ->   /membership/login.jsp

Here is how I set the path to  j_security_check in above login.jsp



My restricted  web.xml snippet


Are you doing what I call a "direct login" where you have a "login page"
that most users hit first. Like from example.com/app/ where there is no initial 
request for a protected resource? Or are your users always (1) requesting a 
protected resource then (2) Tomcat requests authentication then (3) the user is 
forwarded to the resource originally requested in (1)?




External
/external/*


radiovoodoo


NONE




Auth
/auth/*


radiovoodoo


NONE



FORM

/membership/login.jsp
/membership/error.jsp




Those NONE lines look weird to me. 
Why are you explicitly specifying those? What part of your configuration actually requests 
authentication and authorization?

-chris

-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

CAUTION: This email originated from outside of the organization. Do 

RE: [EXT]Re: 404 for j_security_check

[Rick Noel]

Chris,

Thanks for the help, I agree with all your statements.

I now see the  JSESSIONID cookies.

I found a bug in my code. My issue was nothing to do with Tomcat behavior.

Rick Noel
Systems Programmer | Westwood One
rn...@westwoodone.com

-Original Message-
From: Christopher Schultz  
Sent: Sunday, March 17, 2024 10:57 AM
To: users@tomcat.apache.org
Subject: Re: [EXT]Re: 404 for j_security_check

[You don't often get email from ch...@christopherschultz.net. Learn why this is 
important at https://aka.ms/LearnAboutSenderIdentification ]

Rick,

On 3/15/24 13:49, Rick Noel wrote:
>
> I really only want auth once
>
> All hits to jsp pages after a successful login do not trigger the Auth 
> process again.
>
> But hits to java action class servlets do trigger the Auth process
>
> Its  like session data is being lost for some pages but not for others

Can you watch the HTTP headers for your interaction to see what's happening? 
The browser should be sending JSESSIONID cookies with each request. If the 
server isn't sending any Set-Cookie header, the browser should leave things as 
they are.

Please note that Tomcat will send Set-Cookie when a session is created (by 
default, every JSP will create a session IIRC if you declare it to use 
sessions), plus Tomcat will rotate the session identifier as part of the 
authentication process. If you have code on the client that is storing the 
session and using it later, if your session id is being updated during 
authentication you need to make sure it gets updated everywhere the client is 
using it.

> I was thinking maybe this is reason..
>
> The Expires header specifies when content will expire, or how long content is 
> "fresh."
> After this time, the Portal Server will always check back with the remote 
> server to see if the content has changed.
> Most Web servers allow setting an absolute time to expire, a time 
> based on the last time that the client saw the object (last access time), or 
> a time based on the last time the document changed on your server (last 
> modification time).
>
> In JSP, we can set caching to forever using the Expires header like 
> so.
>
> response.setDateHeader("Expires",Long.MAX_VALUE)
>
> BUT I do not want to change my application code, I just want to tell 
> Tomcat 10 to stop Expiring cache so that session log in data is not 
> lost

No, the cache here refers to the client's resource (e.g. page, image,
etc.) cache. It has nothing to do with what's happening on the server.

> My main question is
> I want to know how to configure Tomcat 10 to not loose session data 
> that tells the user has successfully logged in

Are you properly encoding your URLs in your page like with 
HttpServletResponse.encodeURL()? If you are using cookie-based session-tracking 
it probably won't matter, but it's best practice to always do that to ensure 
your URLs are generated properly.

-chris

> -Original Message-
> From: Christopher Schultz 
> Sent: Friday, March 15, 2024 12:19 PM
> To: users@tomcat.apache.org
> Subject: [EXT]Re: 404 for j_security_check
>
> [You don't often get email from ch...@christopherschultz.net. Learn 
> why this is important at https://aka.ms/LearnAboutSenderIdentification 
> ]
>
> Rick,
>
> On 3/14/24 15:37, Rick Noel wrote:
>> After moving from tomcat 9 to tomcat 10 after a user successfully 
>> logs in and then hits a restricted page, the login page is hit again 
>> but on this second login hit I get 404 page not found
> This is actually expected, since j_security_check is only supposed to be used 
> when the container (Tomcat) interrupts a user workflow to request 
> authentication.
>
>> How do I set the correct path in my  login jsp so that 
>> j_security_check is found?
>>
>> BTW  I actually am wondering why a  successful logged on user would 
>> even be sent to the log in page again?
> That's more of a question for your application than anything else.
>
>> My login page  is ->   /membership/login.jsp
>>
>> Here is how I set the path to  j_security_check in above login.jsp
>>
>> 
>>
>> My restricted  web.xml snippet
>
> Are you doing what I call a "direct login" where you have a "login page"
> that most users hit first. Like from example.com/app/ where there is no 
> initial request for a protected resource? Or are your users always (1) 
> requesting a protected resource then (2) Tomcat requests authentication then 
> (3) the user is forwarded to the resource originally requested in (1)?
>
>> 
>> 
>> External
>> /external/*
>> 
>> 
>> radiovoodoo
>&g

Re: [EXT]Re: 404 for j_security_check

[Christopher Schultz]

Rick,

On 3/15/24 13:49, Rick Noel wrote:


I really only want auth once

All hits to jsp pages after a successful login do not trigger the Auth process 
again.

But hits to java action class servlets do trigger the Auth process

Its  like session data is being lost for some pages but not for others


Can you watch the HTTP headers for your interaction to see what's 
happening? The browser should be sending JSESSIONID cookies with each 
request. If the server isn't sending any Set-Cookie header, the browser 
should leave things as they are.


Please note that Tomcat will send Set-Cookie when a session is created 
(by default, every JSP will create a session IIRC if you declare it to 
use sessions), plus Tomcat will rotate the session identifier as part of 
the authentication process. If you have code on the client that is 
storing the session and using it later, if your session id is being 
updated during authentication you need to make sure it gets updated 
everywhere the client is using it.



I was thinking maybe this is reason..

The Expires header specifies when content will expire, or how long content is 
"fresh."
After this time, the Portal Server will always check back with the remote 
server to see if the content has changed.
Most Web servers allow setting an absolute time to expire, a time based on the 
last time that the client saw the object (last access time),
or a time based on the last time the document changed on your server (last 
modification time).

In JSP, we can set caching to forever using the Expires header like so.

response.setDateHeader("Expires",Long.MAX_VALUE)

BUT I do not want to change my application code, I just want to tell Tomcat 10 
to stop
Expiring cache so that session log in data is not lost


No, the cache here refers to the client's resource (e.g. page, image, 
etc.) cache. It has nothing to do with what's happening on the server.



My main question is
I want to know how to configure Tomcat 10 to not loose session data that tells 
the user has successfully logged in


Are you properly encoding your URLs in your page like with 
HttpServletResponse.encodeURL()? If you are using cookie-based 
session-tracking it probably won't matter, but it's best practice to 
always do that to ensure your URLs are generated properly.


-chris


-Original Message-
From: Christopher Schultz 
Sent: Friday, March 15, 2024 12:19 PM
To: users@tomcat.apache.org
Subject: [EXT]Re: 404 for j_security_check

[You don't often get email from ch...@christopherschultz.net. Learn why this is 
important at https://aka.ms/LearnAboutSenderIdentification ]

Rick,

On 3/14/24 15:37, Rick Noel wrote:

After moving from tomcat 9 to tomcat 10 after a user successfully logs
in and then hits a restricted page, the login page is hit again but on
this second login hit I get 404 page not found

This is actually expected, since j_security_check is only supposed to be used 
when the container (Tomcat) interrupts a user workflow to request 
authentication.


How do I set the correct path in my  login jsp so that
j_security_check is found?

BTW  I actually am wondering why a  successful logged on user would
even be sent to the log in page again?

That's more of a question for your application than anything else.


My login page  is ->   /membership/login.jsp

Here is how I set the path to  j_security_check in above login.jsp



My restricted  web.xml snippet


Are you doing what I call a "direct login" where you have a "login page"
that most users hit first. Like from example.com/app/ where there is no initial 
request for a protected resource? Or are your users always (1) requesting a 
protected resource then (2) Tomcat requests authentication then (3) the user is 
forwarded to the resource originally requested in (1)?




External
/external/*


radiovoodoo


NONE




Auth
/auth/*


radiovoodoo


NONE



FORM

/membership/login.jsp
/membership/error.jsp




Those NONE lines look weird to me. 
Why are you explicitly specifying those? What part of your configuration actually requests 
authentication and authorization?

-chris

-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

CAUTION: This email originated from outside of the organization. Do not click 
links or open attachments unless you know the sender and you are sure the 
content is safe. Please report the message using the Report Message feature in 
your email client if you believe the email is suspicious.


-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org



-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.o

RE: [EXT]Re: 404 for j_security_check

[Rick Noel]

I really only want auth once

All hits to jsp pages after a successful login do not trigger the Auth process 
again.

But hits to java action class servlets do trigger the Auth process

Its  like session data is being lost for some pages but not for others

I was thinking maybe this is reason..


The Expires header specifies when content will expire, or how long content is 
"fresh."
After this time, the Portal Server will always check back with the remote 
server to see if the content has changed.
Most Web servers allow setting an absolute time to expire, a time based on the 
last time that the client saw the object (last access time),
or a time based on the last time the document changed on your server (last 
modification time).

In JSP, we can set caching to forever using the Expires header like so.

response.setDateHeader("Expires",Long.MAX_VALUE)

BUT I do not want to change my application code, I just want to tell Tomcat 10 
to stop
Expiring cache so that session log in data is not lost

My main question is  
I want to know how to configure Tomcat 10 to not loose session data that tells 
the user has successfully logged in




Rick Noel
Systems Programmer | Westwood One
rn...@westwoodone.com

-Original Message-
From: Christopher Schultz  
Sent: Friday, March 15, 2024 12:19 PM
To: users@tomcat.apache.org
Subject: [EXT]Re: 404 for j_security_check

[You don't often get email from ch...@christopherschultz.net. Learn why this is 
important at https://aka.ms/LearnAboutSenderIdentification ]

Rick,

On 3/14/24 15:37, Rick Noel wrote:
> After moving from tomcat 9 to tomcat 10 after a user successfully logs 
> in and then hits a restricted page, the login page is hit again but on 
> this second login hit I get 404 page not found
This is actually expected, since j_security_check is only supposed to be used 
when the container (Tomcat) interrupts a user workflow to request 
authentication.

> How do I set the correct path in my  login jsp so that 
> j_security_check is found?
>
> BTW  I actually am wondering why a  successful logged on user would 
> even be sent to the log in page again?
That's more of a question for your application than anything else.

> My login page  is ->   /membership/login.jsp
>
> Here is how I set the path to  j_security_check in above login.jsp
>
> 
>
> My restricted  web.xml snippet

Are you doing what I call a "direct login" where you have a "login page"
that most users hit first. Like from example.com/app/ where there is no initial 
request for a protected resource? Or are your users always (1) requesting a 
protected resource then (2) Tomcat requests authentication then (3) the user is 
forwarded to the resource originally requested in (1)?

> 
> 
> External
> /external/*
> 
> 
> radiovoodoo
> 
> 
> NONE
> 
> 
> 
> 
> Auth
> /auth/*
> 
> 
> radiovoodoo
> 
> 
> NONE
> 
> 
> 
> FORM
> 
> /membership/login.jsp
> /membership/error.jsp
> 
> 

Those NONE lines look weird to me. 
Why are you explicitly specifying those? What part of your configuration 
actually requests authentication and authorization?

-chris

-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

CAUTION: This email originated from outside of the organization. Do not click 
links or open attachments unless you know the sender and you are sure the 
content is safe. Please report the message using the Report Message feature in 
your email client if you believe the email is suspicious.


-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

Re: 404 for j_security_check

[Christopher Schultz]

Rick,

On 3/14/24 15:37, Rick Noel wrote:

After moving from tomcat 9 to tomcat 10 after a user successfully
logs in and then hits a restricted page, the login page is hit again
but on this second login hit I get 404 page not found
This is actually expected, since j_security_check is only supposed to be 
used when the container (Tomcat) interrupts a user workflow to request 
authentication.



How do I set the correct path in my  login jsp so that
j_security_check is found?

BTW  I actually am wondering why a  successful logged on user would
even be sent to the log in page again?

That's more of a question for your application than anything else.


My login page  is ->   /membership/login.jsp

Here is how I set the path to  j_security_check in above login.jsp



My restricted  web.xml snippet


Are you doing what I call a "direct login" where you have a "login page" 
that most users hit first. Like from example.com/app/ where there is no 
initial request for a protected resource? Or are your users always (1) 
requesting a protected resource then (2) Tomcat requests authentication 
then (3) the user is forwarded to the resource originally requested in (1)?





External
/external/*


radiovoodoo


NONE




Auth
/auth/*


radiovoodoo


NONE



FORM

/membership/login.jsp
/membership/error.jsp




Those NONE lines look weird 
to me. Why are you explicitly specifying those? What part of your 
configuration actually requests authentication and authorization?


-chris

-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

Re: 404 response to URLs with trailing decimal

[Mark Thomas]

On April 19, 2019 5:32:11 PM UTC, Mark Reyes  wrote:
>Hello,
>
>I find that Tomcat 8 will not serve up static content with a trailing
>decimal in
>the URL.  A response code of 404 is served up, not the static content.
>
>My configuration is a symbolic link in the webapps/ directory. e.g.
>
> 
>
>   allowLinking="true"
>
> 
>
>A sample request URL that fails is:
> http://localhost:8080/externalData/trailingDot.
>
>I have tried to URL encode the period in the request, but the problem
>still
>exists.
>Is this a bug in Tomcat?  If so, should I send in a bug request?
>Below are the instance specifics.
>
>Thank you.
>mark.re...@ucop.edu
>
>Server version: Apache Tomcat/8.0.24
>Server built:   Jul 1 2015 20:19:55 UTC
>Server number:  8.0.24.0
>OS Name:Linux
>OS Version: 4.14.104-78.84.amzn1.x86_64
>Architecture:   amd64
>JVM Version:1.8.0_201-b09
>JVM Vendor: Oracle Corporation
>
>-
>To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
>For additional commands, e-mail: users-h...@tomcat.apache.org

Assuming the file /externalData/trailingDot. exists then yes, that looks like a 
bug.

Mark

-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

Re: 404 - servlet not found (7.0.52)

[Zemian Deng]

Tomcat should emit a parse error during deployment / startup of your
application something like

"SEVERE [localhost-startStop-1]
org.apache.tomcat.util.descriptor.web.WebXmlParser.parseWebXml Parse error
in application web.xml"

However the Tomcat server itself will continue to load and run. It just
that your webapp alone will failed to deploy.


On Tue, Aug 1, 2017 at 6:39 AM, Christoph Kukulies 
wrote:

> Argh. I solved it. I had a dangling servlet-mapping section in my web.xml.
> Weird, that tomcat doesn't report on this, or does it?
>
>
> Am 01.08.2017 um 12:09 schrieb Christoph Kukulies:
>
>> I'm pulling my hairs at the moment for a servlet is not being found which
>> worked before.
>>
>> I have a class in webapps/servlets/WEB-INF/classes/My.class and sections
>> in web.xml for this:
>>
>> 
>> My
>> My
>> 
>>
>> and a mapping:
>>
>> 
>> My
>> /servlet/My
>> 
>>
>>
>> What I did last was to add another class Mytest in the same directory.
>> But it gave an error 404 (found later that I forgot the mapping for that
>> class), deleted the lines for the servlet section for that again .
>>
>> I also deleted ~/work/Catalina and reverted everything back to the old
>> state (where only My was defined).
>>
>>
>> Now work/Catalina/localhost/servlets is empty (!?).
>>
>> The invoking page is:
>>
>> 
>> 
>> 
>>
>>
>> 
>> 
>>
>>
>>
>> I'm clueless at the moment.
>>
>> --
>>
>> Christoph
>>
>>
>>
>>
>>
>> -
>> To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
>> For additional commands, e-mail: users-h...@tomcat.apache.org
>>
>>
>
> -
> To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
> For additional commands, e-mail: users-h...@tomcat.apache.org
>
>

Re: 404 - servlet not found (7.0.52)

[Christoph Kukulies]

Argh. I solved it. I had a dangling servlet-mapping section in my 
web.xml. Weird, that tomcat doesn't report on this, or does it?


Am 01.08.2017 um 12:09 schrieb Christoph Kukulies:
I'm pulling my hairs at the moment for a servlet is not being found 
which worked before.


I have a class in webapps/servlets/WEB-INF/classes/My.class and 
sections in web.xml for this:



My
My


and a mapping:


My
/servlet/My



What I did last was to add another class Mytest in the same directory. 
But it gave an error 404 (found later that I forgot the mapping for 
that class), deleted the lines for the servlet section for that again .


I also deleted ~/work/Catalina and reverted everything back to the old 
state (where only My was defined).



Now work/Catalina/localhost/servlets is empty (!?).

The invoking page is:




   
   





I'm clueless at the moment.

--

Christoph





-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org




-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

Re: 404 errors accessing webapp URLs using local IP address on fresh Tomcat 8.5.9 install

[modjklist]

Thanks for the help Christopher, 

I resolved this by adding 192.168.0.2 to hostB's httpd.conf file as a 
VirtualHost, then including JkMount for mod_jk. 

- Original Message -

From: "Christopher Schultz" <ch...@christopherschultz.net> 
To: "Tomcat Users List" <users@tomcat.apache.org> 
Sent: Tuesday, January 10, 2017 11:50:27 AM 
Subject: Re: 404 errors accessing webapp URLs using local IP address on fresh 
Tomcat 8.5.9 install 

-BEGIN PGP SIGNED MESSAGE- 
Hash: SHA256 

To whom it may concern, 

On 1/9/17 12:57 AM, modjkl...@comcast.net wrote: 
> I have two Linux servers connected via a cross-connect cable with 
> internal IP addresses 192.168.0.1 (hostA) and 192.168.0.2 (hostB). 
> 
> 
> hostA runs CentOS 5, and hostB CentOS 7. 
> 
> hostB runs Apache 2.4.x, and Tomcat 8.5.9. All web traffic gets 
> routed to port 443 (e.g. HTTPS) of Apache web server hostB. All web 
> application traffic (e.g. 
> https://www.example.com/mywebapp/somepage) is then passed to Tomcat 
> via mod_jk version 1.2.42 on port 8009. Additionally, hostB Apache 
> web server is configured to listen on 192.168.0.2 port 8009 (hostA 
> Apache web server is not configured as such). 
> 
> If hostA attempts to access a webpage on hostB (via hostB external 
> IP address) from a browser or command line, such as: [root@hostA 
> ~]# curl -I http://www.example.com/mywebapp/somepage 
> 
> it returns status 200 (good). 
> 
> Now, if I modify the hostA /etc/hosts file hostA accesses to my 
> website (www.example.com) on hostB through the cross-connect cable 
> (e.g. 192.168.0.2 rather than the external IP address), the webpage 
> returns error 404. 
> 
> What can I change to get status 200? 
> 
> My web addresses are xxx.xxx.xxx.xxx (e.g. IPv4). I know Tomcat 
> configures IPv6 by default. So, I modified the setenv.sh as 
> follows: 
> 
> CATALINA_OPTS="-Xms512M -Xmx1024M -Djava.awt.headless=true 
> -Djava.net.preferIPv4Stack=true 
> -Djava.net.preferIPv4Addresses=true" 
> 
> This didn't change the result. 
> 
> As another clue, I observe that hostA always reports status 200 
> (good) when accessing any hostB webpage in www.example.com that is 
> NOT part of /mywebapp, for both internal and external IP addresses. 
> 
> 
> Any ideas what I can try to resolve this? I'm new to Tomcat and 
> this is fresh install (previously used GlassFish) on a brand new 
> server. Thanks in advance for any advice. 

What does hostA say when you issue "host [hostB]" from the command-line? 

- -chris 
-BEGIN PGP SIGNATURE- 
Comment: GPGTools - http://gpgtools.org 
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ 

iQIcBAEBCAAGBQJYdTsDAAoJEBzwKT+lPKRYQY8QAL2d3o6cqoNJ4ENxOA9al6i+ 
VETnlJ5JjDsAC0hzbd0c8eRZj8NryptV9hbx7nmVeIRNs+Pgr56BxIsmih+QGT+p 
vDCdeJEfcYXPdStpPOmBu1u+FfCJDIUEFevxigqYsvav/1UUXdoV3aW8ThyQaddd 
30ecS9NmTaijYZjHA/ufTOymuFgSnwAwkO7PbwV1hWG/JNqnXNLM+Dywkv/5CqH/ 
DpbquCyiDrvDZVCBsvOUIRGfXyH3czxOHycGfl8GarNoskuvrc9gxHkSwc3HvIau 
qlfd7g9SICwrLeVcm02SbTkkUJV/xIV6p5csPMKt5bID3+MciX+XjOoFlo6GWVGY 
6UtZ0OFvznvgb2wgOMEmf9N1ORqj1a8765VDae2oTJhpNoygW55/WwJT/s24gohz 
xEGTw5Fqddo8s8IzTWbIOChWSwQ1V/1gtjJJgn/O/JUyAobFvMipWAGLztfo/w4V 
+shtlh/+rRAigFrgc7cYAfp4+SMbnDCD4MBJHBdrgjAQuH1bg4+CbdN6WkhNsi0+ 
rcPFUJUQPxmdN1HtYAUmeXXEfMPuMJNhP3Dsq6L7RpEmKAFdkwrPe2AXkP/TzbeH 
yy/4M1Ng1EBMZuWHnEylo3o0A4qtp139o3B/gJiwZ5CVnQXxCwv0MsjiY9Z6wPPm 
FuzFy8TTIECLskz4vn5C 
=LNg6 
-END PGP SIGNATURE- 

- 
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org 
For additional commands, e-mail: users-h...@tomcat.apache.org 

Re: 404 errors accessing webapp URLs using local IP address on fresh Tomcat 8.5.9 install

[Christopher Schultz]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

To whom it may concern,

On 1/9/17 12:57 AM, modjkl...@comcast.net wrote:
> I have two Linux servers connected via a cross-connect cable with
> internal IP addresses 192.168.0.1 (hostA) and 192.168.0.2 (hostB).
> 
> 
> hostA runs CentOS 5, and hostB CentOS 7.
> 
> hostB runs Apache 2.4.x, and Tomcat 8.5.9. All web traffic gets
> routed to port 443 (e.g. HTTPS) of Apache web server hostB. All web
> application traffic (e.g.
> https://www.example.com/mywebapp/somepage) is then passed to Tomcat
> via mod_jk version 1.2.42 on port 8009. Additionally, hostB Apache
> web server is configured to listen on 192.168.0.2 port 8009 (hostA
> Apache web server is not configured as such).
> 
> If hostA attempts to access a webpage on hostB (via hostB external
> IP address) from a browser or command line, such as: [root@hostA
> ~]# curl -I http://www.example.com/mywebapp/somepage
> 
> it returns status 200 (good).
> 
> Now, if I modify the hostA /etc/hosts file hostA accesses to my
> website (www.example.com) on hostB through the cross-connect cable
> (e.g. 192.168.0.2 rather than the external IP address), the webpage
> returns error 404.
> 
> What can I change to get status 200?
> 
> My web addresses are xxx.xxx.xxx.xxx (e.g. IPv4). I know Tomcat
> configures IPv6 by default. So, I modified the setenv.sh as
> follows:
> 
> CATALINA_OPTS="-Xms512M -Xmx1024M -Djava.awt.headless=true
> -Djava.net.preferIPv4Stack=true
> -Djava.net.preferIPv4Addresses=true"
> 
> This didn't change the result.
> 
> As another clue, I observe that hostA always reports status 200
> (good) when accessing any hostB webpage in www.example.com that is
> NOT part of /mywebapp, for both internal and external IP addresses.
> 
> 
> Any ideas what I can try to resolve this? I'm new to Tomcat and
> this is fresh install (previously used GlassFish) on a brand new
> server. Thanks in advance for any advice.

What does hostA say when you issue "host [hostB]" from the command-line?

- -chris
-BEGIN PGP SIGNATURE-
Comment: GPGTools - http://gpgtools.org
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iQIcBAEBCAAGBQJYdTsDAAoJEBzwKT+lPKRYQY8QAL2d3o6cqoNJ4ENxOA9al6i+
VETnlJ5JjDsAC0hzbd0c8eRZj8NryptV9hbx7nmVeIRNs+Pgr56BxIsmih+QGT+p
vDCdeJEfcYXPdStpPOmBu1u+FfCJDIUEFevxigqYsvav/1UUXdoV3aW8ThyQaddd
30ecS9NmTaijYZjHA/ufTOymuFgSnwAwkO7PbwV1hWG/JNqnXNLM+Dywkv/5CqH/
DpbquCyiDrvDZVCBsvOUIRGfXyH3czxOHycGfl8GarNoskuvrc9gxHkSwc3HvIau
qlfd7g9SICwrLeVcm02SbTkkUJV/xIV6p5csPMKt5bID3+MciX+XjOoFlo6GWVGY
6UtZ0OFvznvgb2wgOMEmf9N1ORqj1a8765VDae2oTJhpNoygW55/WwJT/s24gohz
xEGTw5Fqddo8s8IzTWbIOChWSwQ1V/1gtjJJgn/O/JUyAobFvMipWAGLztfo/w4V
+shtlh/+rRAigFrgc7cYAfp4+SMbnDCD4MBJHBdrgjAQuH1bg4+CbdN6WkhNsi0+
rcPFUJUQPxmdN1HtYAUmeXXEfMPuMJNhP3Dsq6L7RpEmKAFdkwrPe2AXkP/TzbeH
yy/4M1Ng1EBMZuWHnEylo3o0A4qtp139o3B/gJiwZ5CVnQXxCwv0MsjiY9Z6wPPm
FuzFy8TTIECLskz4vn5C
=LNg6
-END PGP SIGNATURE-

-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

Re: 404 errors accessing webapp URLs using local IP address on fresh Tomcat 8.5.9 install

[modjklist]

I should mention that to configure hostB (e.g. 192.168.0.2) to listen to hostA 
(e.g. 192.168.0.1), I simply added 

Listen 192.168.0.2:80 
Listen 192.168.0.2:443 

to hostB httpd.conf file. I did not create a virtual host (is that OK?). I also 
didn't modify httpd.conf on hostA. 

- Original Message -

From: modjkl...@comcast.net 
To: "Tomcat Users List"  
Sent: Sunday, January 8, 2017 9:57:32 PM 
Subject: 404 errors accessing webapp URLs using local IP address on fresh 
Tomcat 8.5.9 install 

I have two Linux servers connected via a cross-connect cable with internal IP 
addresses 192.168.0.1 (hostA) and 192.168.0.2 (hostB). 

hostA runs CentOS 5, and hostB CentOS 7. 

hostB runs Apache 2.4.x, and Tomcat 8.5.9. All web traffic gets routed to port 
443 (e.g. HTTPS) of Apache web server hostB. All web application traffic (e.g. 
https://www.example.com/mywebapp/somepage) is then passed to Tomcat via mod_jk 
version 1.2.42 on port 8009. Additionally, hostB Apache web server is 
configured to listen on 192.168.0.2 port 8009 (hostA Apache web server is not 
configured as such). 

If hostA attempts to access a webpage on hostB (via hostB external IP address) 
from a browser or command line, such as: 
[root@hostA ~]# curl -I http://www.example.com/mywebapp/somepage 

it returns status 200 (good). 

Now, if I modify the hostA /etc/hosts file hostA accesses to my website 
(www.example.com) on hostB through the cross-connect cable (e.g. 192.168.0.2 
rather than the external IP address), the webpage returns error 404. 

What can I change to get status 200? 

My web addresses are xxx.xxx.xxx.xxx (e.g. IPv4). I know Tomcat configures IPv6 
by default. So, I modified the setenv.sh as follows: 

CATALINA_OPTS="-Xms512M -Xmx1024M -Djava.awt.headless=true 
-Djava.net.preferIPv4Stack=true -Djava.net.preferIPv4Addresses=true" 

This didn't change the result. 

As another clue, I observe that hostA always reports status 200 (good) when 
accessing any hostB webpage in www.example.com that is NOT part of /mywebapp, 
for both internal and external IP addresses. 

Any ideas what I can try to resolve this? I'm new to Tomcat and this is fresh 
install (previously used GlassFish) on a brand new server. Thanks in advance 
for any advice. 

Re: 404 during application redeploying

[Mark Thomas]

On 07/08/2015 10:00, Pavel Cibulka wrote:
 Hi, I'm using Tomcat 8.0.23 on Ubuntu 14.04. When I redeploy application
 (by replacing WAR file), tomcat returns 404 for short period of time. Is
 this intended?

Yes.

 I have found in:
 https://bz.apache.org/bugzilla/show_bug.cgi?id=53024
 Bug 53024 - Accessing Servlet while Reloading context gives 404 error
 Mark Thomas 2012-05-08 19:08:09 UTC
 Thanks for the test case. This has been fixed in trunk and 7.0.x and will
 be included in 7.0.28 onwards.
 I also took the opportunity to improve the handling when a watched resource
 (such as web.xml) changes. This is now handled with a reload (so no 404s)
 rather than stop followed by a start.
 
 It seems to me, that Tomcat should pause requests on redeploy instead of
 returning 404. Or does this works differently for WAR files?

It depends.

redeploy != reload and which you get depends on circumstances. I
strongly recommend that you read this page:
http://tomcat.apache.org/tomcat-7.0-doc/config/automatic-deployment.html

There are a number of ways you could get the reload behaviour you want.

1. Use an external context.xml file. Updates to the WAR would then only
result in a reload.

2. Use parallel deployment

http://tomcat.apache.org/tomcat-7.0-doc/config/context.html#Parallel_deployment

HTH,

Mark

-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

Re: 404 during application redeploying

[Pavel Cibulka]

redeploy != reload

I see now. External context.xml seems good to me.

Thanks for help.

Pavel Cibulka

On Fri, Aug 7, 2015 at 11:25 AM, Mark Thomas ma...@apache.org wrote:

 On 07/08/2015 10:00, Pavel Cibulka wrote:
  Hi, I'm using Tomcat 8.0.23 on Ubuntu 14.04. When I redeploy application
  (by replacing WAR file), tomcat returns 404 for short period of time. Is
  this intended?

 Yes.

  I have found in:
  https://bz.apache.org/bugzilla/show_bug.cgi?id=53024
  Bug 53024 - Accessing Servlet while Reloading context gives 404 error
  Mark Thomas 2012-05-08 19:08:09 UTC
  Thanks for the test case. This has been fixed in trunk and 7.0.x and
 will
  be included in 7.0.28 onwards.
  I also took the opportunity to improve the handling when a watched
 resource
  (such as web.xml) changes. This is now handled with a reload (so no 404s)
  rather than stop followed by a start.
 
  It seems to me, that Tomcat should pause requests on redeploy instead of
  returning 404. Or does this works differently for WAR files?

 It depends.

 redeploy != reload and which you get depends on circumstances. I
 strongly recommend that you read this page:
 http://tomcat.apache.org/tomcat-7.0-doc/config/automatic-deployment.html

 There are a number of ways you could get the reload behaviour you want.

 1. Use an external context.xml file. Updates to the WAR would then only
 result in a reload.

 2. Use parallel deployment


 http://tomcat.apache.org/tomcat-7.0-doc/config/context.html#Parallel_deployment

 HTH,

 Mark

 -
 To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
 For additional commands, e-mail: users-h...@tomcat.apache.org

Re: 404 - Might there be something wrong with my permissions?

[Konstantin Kolinko]

2013/11/21 Fredrik Andersson fredan...@hotmail.com:
 Hello Tomcat-experts!

It is hard to read you message.

 I have recently bought some space at a webhotel that uses Apache HTTP server 
 as front before a Tomcat 6.0.37.My account at the webhotel is said to support 
 Struts and Hibernate and such technics.At home I have developed a app that 
 uses those technics and of course it runs fine in a similar environment as 
 the one at the webhotel. I can deploy my app as a ROOT-app or a ordinary app 
 and the Struts works perfectly.
 At the webhotel I have tried to deploy it booth as a ROOT-app and as a 
 MYAPP-webapp-1.0.0.war-file
 Now I have stripped the app down to just a struts2-hello-world-app.
 But at the webhotel I just keep getting this when I try to access the 
 ActionClass through struts.xml:
 HTTP Status 404 - There is no Action mapped for namespace [/] and action name 
 [welcome] associated with context path [/MYAPP-webapp-1.0.0].type Status 
 reportmessage There is no Action mapped for namespace [/] and action name 
 [welcome] associated with context path [/MYAPP-webapp-1.0.0].description The 
 requested resource is not available.

 Unfortenatly the support guys at the webhotel says they lack knowledge of 
 Tomcat so they can not help me out.

If you want to change your hosting provider, there are a number of offers at
http://wiki.apache.org/tomcat/PoweredBy#Hosting_providers

 But today I at least found this exception in the catalina.log just after my 
 attempt yo access a struts-path:
 /-- Encapsulated exception \ java.lang.NullPointerException: 
 permission can't be null at 
 java.security.AccessController.checkPermission(Unknown Source) at 
 java.lang.SecurityManager.checkPermission(Unknown Source) at 
 ognl.OgnlRuntime.invokeMethod(OgnlRuntime.java:834) at 
 ognl.OgnlRuntime.callAppropriateMethod(OgnlRuntime.java:1280) at 
 ognl.OgnlRuntime.setMethodValue(OgnlRuntime.java:1481) at 
 ognl.ObjectPropertyAccessor.setPossibleProperty(ObjectPropertyAccessor.java:85)
  at ognl.ObjectPropertyAccessor.setProperty(ObjectPropertyAccessor.java:162) 
 at 
 com.opensymphony.xwork2.ognl.accessor.ObjectAccessor.setProperty(ObjectAccessor.java:27)
  at ognl.OgnlRuntime.setProperty(OgnlRuntime.java:2318) at 
 com.opensymphony.xwork2.ognl.accessor.CompoundRootAccessor.setProperty(CompoundRootAccessor.java:77)
  at ognl.OgnlRuntime.setProperty(OgnlRuntime.java:2318) at 
 ognl.ASTProperty.setValueBody(ASTProperty.java:127) at 
 ognl.SimpleNode.evaluateSetValueBody(SimpleNode.java:220) at 
 ognl.SimpleNode.setValue(SimpleNode.java:301) at 
 ognl.Ognl.setValue(Ognl.java:737) at 
 com.opensymphony.xwork2.ognl.OgnlUtil.setValue(OgnlUtil.java:217) at 
 com.opensymphony.xwork2.ognl.OgnlValueStack.trySetValue(OgnlValueStack.java:186)
  at 
 com.opensymphony.xwork2.ognl.OgnlValueStack.setValue(OgnlValueStack.java:173) 
 at 
 com.opensymphony.xwork2.ognl.OgnlValueStack.setParameter(OgnlValueStack.java:151)
  at 
 com.opensymphony.xwork2.interceptor.ParametersInterceptor.setParameters(ParametersInterceptor.java:292)
  at 
 com.opensymphony.xwork2.interceptor.ParametersInterceptor.doIntercept(ParametersInterceptor.java:203)
  at 
 com.opensymphony.xwork2.interceptor.MethodFilterInterceptor.intercept(MethodFilterInterceptor.java:98)
  at 
 com.opensymphony.xwork2.DefaultActionInvocation.invoke(DefaultActionInvocation.java:249)
  at 
 com.opensymphony.xwork2.interceptor.ParametersInterceptor.doIntercept(ParametersInterceptor.java:211)
  at 
 com.opensymphony.xwork2.interceptor.MethodFilterInterceptor.intercept(MethodFilterInterceptor.java:98)
  at 
 com.opensymphony.xwork2.DefaultActionInvocation.invoke(DefaultActionInvocation.java:249)
  at 
 com.opensymphony.xwork2.interceptor.StaticParametersInterceptor.intercept(StaticParametersInterceptor.java:190)
  at 
 com.opensymphony.xwork2.DefaultActionInvocation.invoke(DefaultActionInvocation.java:249)
  at 
 org.apache.struts2.interceptor.MultiselectInterceptor.intercept(MultiselectInterceptor.java:75)
  at 
 com.opensymphony.xwork2.DefaultActionInvocation.invoke(DefaultActionInvocation.java:249)
  at 
 org.apache.struts2.interceptor.CheckboxInterceptor.intercept(CheckboxInterceptor.java:90)
  at 
 com.opensymphony.xwork2.DefaultActionInvocation.invoke(DefaultActionInvocation.java:249)
  at 
 org.apache.struts2.interceptor.FileUploadInterceptor.intercept(FileUploadInterceptor.java:243)
  at 
 com.opensymphony.xwork2.DefaultActionInvocation.invoke(DefaultActionInvocation.java:249)
  at 
 com.opensymphony.xwork2.interceptor.ModelDrivenInterceptor.intercept(ModelDrivenInterceptor.java:100)
  at 
 com.opensymphony.xwork2.DefaultActionInvocation.invoke(DefaultActionInvocation.java:249)
  at 
 com.opensymphony.xwork2.interceptor.ScopedModelDrivenInterceptor.intercept(ScopedModelDrivenInterceptor.java:141)
  at 
 com.opensymphony.xwork2.DefaultActionInvocation.invoke(DefaultActionInvocation.java:249)
  at 
 

RE: 404 - Might there be something wrong with my permissions?

[Fredrik Andersson]

Hello Konstantin!Thanks for your reply!Yes the message got really hard to read, 
it looked fine when I send it!My apologies for that!I will start to investigate 
your advice right away!Sounds really interesting!I will get back as soon I got 
any new info!Best regards and thanks alot again!/Fredrik

 Date: Thu, 21 Nov 2013 17:10:58 +0400
 Subject: Re: 404 - Might there be something wrong with my permissions?
 From: knst.koli...@gmail.com
 To: users@tomcat.apache.org
 
 2013/11/21 Fredrik Andersson fredan...@hotmail.com:
  Hello Tomcat-experts!
 
 It is hard to read you message.
 
  I have recently bought some space at a webhotel that uses Apache HTTP 
  server as front before a Tomcat 6.0.37.My account at the webhotel is said 
  to support Struts and Hibernate and such technics.At home I have developed 
  a app that uses those technics and of course it runs fine in a similar 
  environment as the one at the webhotel. I can deploy my app as a ROOT-app 
  or a ordinary app and the Struts works perfectly.
  At the webhotel I have tried to deploy it booth as a ROOT-app and as a 
  MYAPP-webapp-1.0.0.war-file
  Now I have stripped the app down to just a struts2-hello-world-app.
  But at the webhotel I just keep getting this when I try to access the 
  ActionClass through struts.xml:
  HTTP Status 404 - There is no Action mapped for namespace [/] and action 
  name [welcome] associated with context path [/MYAPP-webapp-1.0.0].type 
  Status reportmessage There is no Action mapped for namespace [/] and action 
  name [welcome] associated with context path 
  [/MYAPP-webapp-1.0.0].description The requested resource is not available.
 
  Unfortenatly the support guys at the webhotel says they lack knowledge of 
  Tomcat so they can not help me out.
 
 If you want to change your hosting provider, there are a number of offers at
 http://wiki.apache.org/tomcat/PoweredBy#Hosting_providers
 
  But today I at least found this exception in the catalina.log just after my 
  attempt yo access a struts-path:
  /-- Encapsulated exception \ java.lang.NullPointerException: 
  permission can't be null at 
  java.security.AccessController.checkPermission(Unknown Source) at 
  java.lang.SecurityManager.checkPermission(Unknown Source) at 
  ognl.OgnlRuntime.invokeMethod(OgnlRuntime.java:834) at 
  ognl.OgnlRuntime.callAppropriateMethod(OgnlRuntime.java:1280) at 
  ognl.OgnlRuntime.setMethodValue(OgnlRuntime.java:1481) at 
  ognl.ObjectPropertyAccessor.setPossibleProperty(ObjectPropertyAccessor.java:85)
   at 
  ognl.ObjectPropertyAccessor.setProperty(ObjectPropertyAccessor.java:162) at 
  com.opensymphony.xwork2.ognl.accessor.ObjectAccessor.setProperty(ObjectAccessor.java:27)
   at ognl.OgnlRuntime.setProperty(OgnlRuntime.java:2318) at 
  com.opensymphony.xwork2.ognl.accessor.CompoundRootAccessor.setProperty(CompoundRootAccessor.java:77)
   at ognl.OgnlRuntime.setProperty(OgnlRuntime.java:2318) at 
  ognl.ASTProperty.setValueBody(ASTProperty.java:127) at 
  ognl.SimpleNode.evaluateSetValueBody(SimpleNode.java:220) at 
  ognl.SimpleNode.setValue(SimpleNode.java:301) at 
  ognl.Ognl.setValue(Ognl.java:737) at 
  com.opensymphony.xwork2.ognl.OgnlUtil.setValue(OgnlUtil.java:217) at 
  com.opensymphony.xwork2.ognl.OgnlValueStack.trySetValue(OgnlValueStack.java:186)
   at 
  com.opensymphony.xwork2.ognl.OgnlValueStack.setValue(OgnlValueStack.java:173)
   at 
  com.opensymphony.xwork2.ognl.OgnlValueStack.setParameter(OgnlValueStack.java:151)
   at 
  com.opensymphony.xwork2.interceptor.ParametersInterceptor.setParameters(ParametersInterceptor.java:292)
   at 
  com.opensymphony.xwork2.interceptor.ParametersInterceptor.doIntercept(ParametersInterceptor.java:203)
   at 
  com.opensymphony.xwork2.interceptor.MethodFilterInterceptor.intercept(MethodFilterInterceptor.java:98)
   at 
  com.opensymphony.xwork2.DefaultActionInvocation.invoke(DefaultActionInvocation.java:249)
   at 
  com.opensymphony.xwork2.interceptor.ParametersInterceptor.doIntercept(ParametersInterceptor.java:211)
   at 
  com.opensymphony.xwork2.interceptor.MethodFilterInterceptor.intercept(MethodFilterInterceptor.java:98)
   at 
  com.opensymphony.xwork2.DefaultActionInvocation.invoke(DefaultActionInvocation.java:249)
   at 
  com.opensymphony.xwork2.interceptor.StaticParametersInterceptor.intercept(StaticParametersInterceptor.java:190)
   at 
  com.opensymphony.xwork2.DefaultActionInvocation.invoke(DefaultActionInvocation.java:249)
   at 
  org.apache.struts2.interceptor.MultiselectInterceptor.intercept(MultiselectInterceptor.java:75)
   at 
  com.opensymphony.xwork2.DefaultActionInvocation.invoke(DefaultActionInvocation.java:249)
   at 
  org.apache.struts2.interceptor.CheckboxInterceptor.intercept(CheckboxInterceptor.java:90)
   at 
  com.opensymphony.xwork2.DefaultActionInvocation.invoke(DefaultActionInvocation.java:249)
   at 
  org.apache.struts2.interceptor.FileUploadInterceptor.intercept(FileUploadInterceptor.java:243)
   at 
  com.opensymphony.xwork2

RE: 404 - Might there be something wrong with my permissions?

[Fredrik Andersson]

Hello guys!
I started my tomcat at home with catalina.bat start -security.
During startup I at once got a lot of exceptions, please see this 
pastie:http://pastie.org/8499210
When I try to access the webapp I get 404 right away.At the production server I 
at least could access the jsp:s direct, but through struts I got 404.Now at 
home I just get 404 in both ways.
One interesting thing is that it looks like the app do not got permissions to 
load the struts-default.xml:
Caused by: Caught exception while loading file struts-default.xml
...that could be the same issue in production since no struts is working at all.
I have not worked with permissions before but examing the catalina.policy with 
polycytool I see there is alot of settings like:java.util.PropertyPermission 
java.vm.version read...that I guess means that it is OK to read the 
System.getProperty(java.vm.version);
If you draw any conclusion about my app like is there any permission I need to 
set to make it work (I guess it must be able to read struts-default.xml for 
eg), please let me know. 
Then I will get in contact with the webhotel-support and try to ask them to 
tell me if they got that permission-settings.
Best regardsFredrik




 From: fredan...@hotmail.com
 To: users@tomcat.apache.org
 Subject: RE: 404 - Might there be something wrong with my permissions?
 Date: Thu, 21 Nov 2013 15:46:07 +
 
 Hello Konstantin!Thanks for your reply!Yes the message got really hard to 
 read, it looked fine when I send it!My apologies for that!I will start to 
 investigate your advice right away!Sounds really interesting!I will get back 
 as soon I got any new info!Best regards and thanks alot again!/Fredrik
 
  Date: Thu, 21 Nov 2013 17:10:58 +0400
  Subject: Re: 404 - Might there be something wrong with my permissions?
  From: knst.koli...@gmail.com
  To: users@tomcat.apache.org
  
  2013/11/21 Fredrik Andersson fredan...@hotmail.com:
   Hello Tomcat-experts!
  
  It is hard to read you message.
  
   I have recently bought some space at a webhotel that uses Apache HTTP 
   server as front before a Tomcat 6.0.37.My account at the webhotel is said 
   to support Struts and Hibernate and such technics.At home I have 
   developed a app that uses those technics and of course it runs fine in a 
   similar environment as the one at the webhotel. I can deploy my app as a 
   ROOT-app or a ordinary app and the Struts works perfectly.
   At the webhotel I have tried to deploy it booth as a ROOT-app and as a 
   MYAPP-webapp-1.0.0.war-file
   Now I have stripped the app down to just a struts2-hello-world-app.
   But at the webhotel I just keep getting this when I try to access the 
   ActionClass through struts.xml:
   HTTP Status 404 - There is no Action mapped for namespace [/] and action 
   name [welcome] associated with context path [/MYAPP-webapp-1.0.0].type 
   Status reportmessage There is no Action mapped for namespace [/] and 
   action name [welcome] associated with context path 
   [/MYAPP-webapp-1.0.0].description The requested resource is not available.
  
   Unfortenatly the support guys at the webhotel says they lack knowledge of 
   Tomcat so they can not help me out.
  
  If you want to change your hosting provider, there are a number of offers at
  http://wiki.apache.org/tomcat/PoweredBy#Hosting_providers
  
   But today I at least found this exception in the catalina.log just after 
   my attempt yo access a struts-path:
   /-- Encapsulated exception \ java.lang.NullPointerException: 
   permission can't be null at 
   java.security.AccessController.checkPermission(Unknown Source) at 
   java.lang.SecurityManager.checkPermission(Unknown Source) at 
   ognl.OgnlRuntime.invokeMethod(OgnlRuntime.java:834) at 
   ognl.OgnlRuntime.callAppropriateMethod(OgnlRuntime.java:1280) at 
   ognl.OgnlRuntime.setMethodValue(OgnlRuntime.java:1481) at 
   ognl.ObjectPropertyAccessor.setPossibleProperty(ObjectPropertyAccessor.java:85)
at 
   ognl.ObjectPropertyAccessor.setProperty(ObjectPropertyAccessor.java:162) 
   at 
   com.opensymphony.xwork2.ognl.accessor.ObjectAccessor.setProperty(ObjectAccessor.java:27)
at ognl.OgnlRuntime.setProperty(OgnlRuntime.java:2318) at 
   com.opensymphony.xwork2.ognl.accessor.CompoundRootAccessor.setProperty(CompoundRootAccessor.java:77)
at ognl.OgnlRuntime.setProperty(OgnlRuntime.java:2318) at 
   ognl.ASTProperty.setValueBody(ASTProperty.java:127) at 
   ognl.SimpleNode.evaluateSetValueBody(SimpleNode.java:220) at 
   ognl.SimpleNode.setValue(SimpleNode.java:301) at 
   ognl.Ognl.setValue(Ognl.java:737) at 
   com.opensymphony.xwork2.ognl.OgnlUtil.setValue(OgnlUtil.java:217) at 
   com.opensymphony.xwork2.ognl.OgnlValueStack.trySetValue(OgnlValueStack.java:186)
at 
   com.opensymphony.xwork2.ognl.OgnlValueStack.setValue(OgnlValueStack.java:173)
at 
   com.opensymphony.xwork2.ognl.OgnlValueStack.setParameter(OgnlValueStack.java:151)
at 
   com.opensymphony.xwork2

Re: 404 Errors for all apps in Tomcat 7.0.23

[Pid *]

On 27 Dec 2011, at 15:43, David Hoffer dhoff...@gmail.com wrote:

 I just installed Tomcat 7.0.23 using Windows 64 bit installer and
 deployed a couple apps via the manager application, however when I run
 them I get HTTP Status 404 errors.  However I see that I get the same
 error for the standard default apps, docs, examples, etc.  The only
 URL that works is http://IP:8080/manager/html.

 In the log I see:
 Dec 27, 2011 3:28:29 PM org.apache.catalina.core.StandardHostValve custom
 SEVERE: Exception Processing ErrorPage[errorCode=404,
 location=/WEB-INF/jsp/404.jsp]
 java.lang.NullPointerException

What about before that during startup?


p



at 
 org.apache.catalina.core.StandardHostValve.custom(StandardHostValve.java:455)
at 
 org.apache.catalina.core.StandardHostValve.status(StandardHostValve.java:324)
at 
 org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:193)
at 
 org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:98)
at 
 org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:928)
at 
 org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:118)
at 
 org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:407)
at 
 org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:987)
at 
 org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:539)
at 
 org.apache.tomcat.util.net.JIoEndpoint$SocketProcessor.run(JIoEndpoint.java:298)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)

 What do I have to do to enable the apps?

 -
 To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
 For additional commands, e-mail: users-h...@tomcat.apache.org


-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

Re: 404 Errors for all apps in Tomcat 7.0.23

[David Hoffer]

No errors are reported at start up, here is the catalina log.

2011-12-27 17:57:07 Commons Daemon procrun stderr initialized
Dec 27, 2011 5:57:08 PM org.apache.catalina.core.AprLifecycleListener init
INFO: The APR based Apache Tomcat Native library which allows optimal
performance in production environments was not found on the
java.library.path: C:\Program Files (x86)\Apache Software
Foundation\Tomcat
7.0\bin;C:\Windows\Sun\Java\bin;C:\Windows\system32;C:\Windows;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;;.
Dec 27, 2011 5:57:08 PM org.apache.coyote.AbstractProtocol init
INFO: Initializing ProtocolHandler [http-bio-8080]
Dec 27, 2011 5:57:08 PM org.apache.coyote.AbstractProtocol init
INFO: Initializing ProtocolHandler [ajp-bio-8009]
Dec 27, 2011 5:57:08 PM org.apache.catalina.startup.Catalina load
INFO: Initialization processed in 426 ms
Dec 27, 2011 5:57:08 PM org.apache.catalina.core.StandardService startInternal
INFO: Starting service Catalina
Dec 27, 2011 5:57:08 PM org.apache.catalina.core.StandardEngine startInternal
INFO: Starting Servlet Engine: Apache Tomcat/7.0.23
Dec 27, 2011 5:57:08 PM org.apache.catalina.startup.HostConfig deployDirectory
INFO: Deploying web application directory C:\Program Files
(x86)\Apache Software Foundation\Tomcat 7.0\webapps\docs
Dec 27, 2011 5:57:08 PM org.apache.catalina.startup.ContextConfig
getDefaultWebXmlFragment
INFO: No global web.xml found
Dec 27, 2011 5:57:08 PM org.apache.catalina.startup.HostConfig deployDirectory
INFO: Deploying web application directory C:\Program Files
(x86)\Apache Software Foundation\Tomcat 7.0\webapps\examples
Dec 27, 2011 5:57:08 PM org.apache.catalina.startup.HostConfig deployDirectory
INFO: Deploying web application directory C:\Program Files
(x86)\Apache Software Foundation\Tomcat 7.0\webapps\host-manager
Dec 27, 2011 5:57:08 PM org.apache.catalina.startup.HostConfig deployDirectory
INFO: Deploying web application directory C:\Program Files
(x86)\Apache Software Foundation\Tomcat 7.0\webapps\manager
Dec 27, 2011 5:57:08 PM org.apache.catalina.startup.HostConfig deployDirectory
INFO: Deploying web application directory C:\Program Files
(x86)\Apache Software Foundation\Tomcat 7.0\webapps\ROOT
Dec 27, 2011 5:57:08 PM org.apache.coyote.AbstractProtocol start
INFO: Starting ProtocolHandler [http-bio-8080]
Dec 27, 2011 5:57:08 PM org.apache.coyote.AbstractProtocol start
INFO: Starting ProtocolHandler [ajp-bio-8009]
Dec 27, 2011 5:57:08 PM org.apache.catalina.startup.Catalina start
INFO: Server startup in 416 ms

-Dave



On Tue, Dec 27, 2011 at 10:29 AM, Pid * p...@pidster.com wrote:
 On 27 Dec 2011, at 15:43, David Hoffer dhoff...@gmail.com wrote:

 I just installed Tomcat 7.0.23 using Windows 64 bit installer and
 deployed a couple apps via the manager application, however when I run
 them I get HTTP Status 404 errors.  However I see that I get the same
 error for the standard default apps, docs, examples, etc.  The only
 URL that works is http://IP:8080/manager/html.

 In the log I see:
 Dec 27, 2011 3:28:29 PM org.apache.catalina.core.StandardHostValve custom
 SEVERE: Exception Processing ErrorPage[errorCode=404,
 location=/WEB-INF/jsp/404.jsp]
 java.lang.NullPointerException

 What about before that during startup?


 p



    at 
 org.apache.catalina.core.StandardHostValve.custom(StandardHostValve.java:455)
    at 
 org.apache.catalina.core.StandardHostValve.status(StandardHostValve.java:324)
    at 
 org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:193)
    at 
 org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:98)
    at 
 org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:928)
    at 
 org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:118)
    at 
 org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:407)
    at 
 org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:987)
    at 
 org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:539)
    at 
 org.apache.tomcat.util.net.JIoEndpoint$SocketProcessor.run(JIoEndpoint.java:298)
    at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source)
    at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
    at java.lang.Thread.run(Unknown Source)

 What do I have to do to enable the apps?

 -
 To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
 For additional commands, e-mail: users-h...@tomcat.apache.org


 -
 To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
 For additional commands, e-mail: users-h...@tomcat.apache.org


-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional 

Re: 404 Errors for all apps in Tomcat 7.0.23

[Christopher Schultz]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

David,

On 12/27/11 10:42 AM, David Hoffer wrote:
 I just installed Tomcat 7.0.23 using Windows 64 bit installer and 
 deployed a couple apps via the manager application, however when I
 run them I get HTTP Status 404 errors.  However I see that I get
 the same error for the standard default apps, docs, examples, etc.
 The only URL that works is http://IP:8080/manager/html.
 
 In the log I see: Dec 27, 2011 3:28:29 PM
 org.apache.catalina.core.StandardHostValve custom SEVERE: Exception
 Processing ErrorPage[errorCode=404, location=/WEB-INF/jsp/404.jsp] 
 java.lang.NullPointerException at
 org.apache.catalina.core.StandardHostValve.custom(StandardHostValve.java:455)

Is
 
that stack trace complete? It seems to indicate that
/WEB-INF/jsp/404.jsp is being invoked, but that JSP isn't actually
executing. The only thing I can think of is that the JSP can't be
found while processing an error (404?) and do you get this error as well.

Have you made any modifications to Tomcat other than enabling the
manager webapp and deploying some webapps onto it?

 What do I have to do to enable the apps?

Deployment ought to enable the apps. What does the manager show in
the list of deployed webapps?

- -chris
-BEGIN PGP SIGNATURE-
Version: GnuPG/MacGPG2 v2.0.17 (Darwin)
Comment: GPGTools - http://gpgtools.org
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAk76R7QACgkQ9CaO5/Lv0PBjiQCgjCT7wt2tDxFEbJr0bgXTLRvu
zHkAnRMrr52g8R+Ggu3MAljah1i4dooK
=BW8D
-END PGP SIGNATURE-

-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

Re: 404 Errors for all apps in Tomcat 7.0.23

[David Hoffer]

Yes that was a full log of that file.

The only change I made was in the Manager App's config I increased the
size of the max file size because one of my apps is bigger than 50MB,
so I just made a change to the web.xml in the manager app.

The http://IP:8080/manger/html page shows the correct list of apps but
if you click on any of the applications (path) I get the 404
error...and I have undeployed all my apps so the problem exists with
the standard sample apps too.

Should I try a different Tomcat version?

-Dave

On Tue, Dec 27, 2011 at 3:33 PM, Christopher Schultz
ch...@christopherschultz.net wrote:
 -BEGIN PGP SIGNED MESSAGE-
 Hash: SHA1

 David,

 On 12/27/11 10:42 AM, David Hoffer wrote:
 I just installed Tomcat 7.0.23 using Windows 64 bit installer and
 deployed a couple apps via the manager application, however when I
 run them I get HTTP Status 404 errors.  However I see that I get
 the same error for the standard default apps, docs, examples, etc.
 The only URL that works is http://IP:8080/manager/html.

 In the log I see: Dec 27, 2011 3:28:29 PM
 org.apache.catalina.core.StandardHostValve custom SEVERE: Exception
 Processing ErrorPage[errorCode=404, location=/WEB-INF/jsp/404.jsp]
 java.lang.NullPointerException at
 org.apache.catalina.core.StandardHostValve.custom(StandardHostValve.java:455)

 Is

 that stack trace complete? It seems to indicate that
 /WEB-INF/jsp/404.jsp is being invoked, but that JSP isn't actually
 executing. The only thing I can think of is that the JSP can't be
 found while processing an error (404?) and do you get this error as well.

 Have you made any modifications to Tomcat other than enabling the
 manager webapp and deploying some webapps onto it?

 What do I have to do to enable the apps?

 Deployment ought to enable the apps. What does the manager show in
 the list of deployed webapps?

 - -chris
 -BEGIN PGP SIGNATURE-
 Version: GnuPG/MacGPG2 v2.0.17 (Darwin)
 Comment: GPGTools - http://gpgtools.org
 Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

 iEYEARECAAYFAk76R7QACgkQ9CaO5/Lv0PBjiQCgjCT7wt2tDxFEbJr0bgXTLRvu
 zHkAnRMrr52g8R+Ggu3MAljah1i4dooK
 =BW8D
 -END PGP SIGNATURE-

 -
 To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
 For additional commands, e-mail: users-h...@tomcat.apache.org


-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

Re: 404 Errors for all apps in Tomcat 7.0.23

[Konstantin Kolinko]

2011/12/28 David Hoffer dhoff...@gmail.com:
 Yes that was a full log of that file.

 The only change I made was in the Manager App's config I increased the
 size of the max file size because one of my apps is bigger than 50MB,
 so I just made a change to the web.xml in the manager app.

 The http://IP:8080/manger/html page shows the correct list of apps but
 if you click on any of the applications (path) I get the 404
 error...and I have undeployed all my apps so the problem exists with
 the standard sample apps too.


You cited only one of log files. What is in other log files? What is
in localhost*.log? What is in access log?

Try to stop Tomcat and delete everything from the work directory. (I
wonder whether *.class files for the JSPs are there. That is, whether
the directory is writable.)

The same with logs directory. Clear it, move old logs somewhere.

What Java version are you using? (It is a bit odd that the path shown
in the log is C:\Windows\Sun\Java\bin).

Best regards,
Konstantin Kolinko

-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

Re: 404 Errors for all apps in Tomcat 7.0.23

[David Hoffer]

Localhost.log:
Dec 28, 2011 2:19:18 AM org.apache.catalina.core.ApplicationContext log
INFO: ContextListener: contextInitialized()
Dec 28, 2011 2:19:18 AM org.apache.catalina.core.ApplicationContext log
INFO: SessionListener: contextInitialized()

localhost_access.log is empty at startup until I click on one of the
apps in the manager page, then it has:
172.31.255.154 - admin [28/Dec/2011:02:37:27 +] GET /manager/html
HTTP/1.1 200 15821
172.31.255.154 - - [28/Dec/2011:02:37:27 +] GET
/manager/images/asf-logo.gif HTTP/1.1 404 952
172.31.255.154 - - [28/Dec/2011:02:37:27 +] GET
/manager/images/tomcat.gif HTTP/1.1 404 952
172.31.255.154 - - [28/Dec/2011:02:37:27 +] GET /favicon.ico
HTTP/1.1 404 952
172.31.255.154 - - [28/Dec/2011:02:37:31 +] GET /docs HTTP/1.1 302 -
172.31.255.154 - - [28/Dec/2011:02:37:31 +] GET /docs/ HTTP/1.1 404 952
172.31.255.154 - - [28/Dec/2011:02:37:31 +] GET /favicon.ico
HTTP/1.1 404 952


I don't know why the one log references Java in the Windows
folder...that folder does not exist.  I have added Java to the system
path (it wasn't there before) so now that log file has this line:
INFO: The APR based Apache Tomcat Native library which allows optimal
performance in production environments was not found on the
java.library.path: C:\Program Files (x86)\Apache Software
Foundation\Tomcat
7.0\bin;C:\Windows\Sun\Java\bin;C:\Windows\system32;C:\Windows;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Program
Files (x86)\Java\jre6\bin;.

My Java version is 1.6.0_30

I did stop Tomcat and was able to manually delete the logs and work
folders and then I restarted.  Windows lets me delete these files but
does prompt me asking that I will need to be an administrator which it
allows me to do.  Tomcat is running as a service, could it be that it
doesn't have enough rights to do something?  It is creating contents
in both the log and work folders...

This is running on OS - Windows 7 64bit Enterprise VM.

Thanks,
-Dave


On Tue, Dec 27, 2011 at 5:43 PM, Konstantin Kolinko
knst.koli...@gmail.com wrote:
 2011/12/28 David Hoffer dhoff...@gmail.com:
 Yes that was a full log of that file.

 The only change I made was in the Manager App's config I increased the
 size of the max file size because one of my apps is bigger than 50MB,
 so I just made a change to the web.xml in the manager app.

 The http://IP:8080/manger/html page shows the correct list of apps but
 if you click on any of the applications (path) I get the 404
 error...and I have undeployed all my apps so the problem exists with
 the standard sample apps too.


 You cited only one of log files. What is in other log files? What is
 in localhost*.log? What is in access log?

 Try to stop Tomcat and delete everything from the work directory. (I
 wonder whether *.class files for the JSPs are there. That is, whether
 the directory is writable.)

 The same with logs directory. Clear it, move old logs somewhere.

 What Java version are you using? (It is a bit odd that the path shown
 in the log is C:\Windows\Sun\Java\bin).

 Best regards,
 Konstantin Kolinko

 -
 To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
 For additional commands, e-mail: users-h...@tomcat.apache.org


-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

Re: 404 with mod_jk

[Michael Powe]

On Thu, Jul 15, 2010 at 01:52:17AM -0400, Michael Powe wrote:
 On Thu, Jul 15, 2010 at 02:28:52AM +0200, André Warnier wrote:
  Michael Powe wrote:
 
  To install mod_jk, I resorted to my good friend Google, and used a
  tutorial to set up the connector.  In that tutorial, the method used
  was to create a properties file (workers.properties) which set up the
  worker `worker1'.  
  ...
  I'm installing a clean version of Apache, built from httpd.apache.org
  sources, in /usr/local in order to get around all the weird (IMO)
  configuration for the version installed in Ubuntu by default.  At this
  point, I've fiddled so many things I've lost track of where I'm at.
  Sometimes, when you can't get something to work, it's best to return
  to first principles.
 
  I will not often say this, but I believe your problems may stem from the 
  above, and that you would do better by using the pre-packaged versions of 
  things (except Tomcat)
 
  1) it is hard to judge the correctness of a tutorial found on Google.
  The mod_jk instructions on the mod_jk pages of the Tomcat website are 
  pretty good, and they are at least accurate and up-to-date.
 
 True.  One of them was the `quick start for the impatient' on the
 mod_jk doc page.
  
  2) the standard Apache packages for Debian and Ubuntu are quite good, and a 
  lot easier to install and maintain than working everything out from scratch.
  I suggest the following order :
  apt-get install sun-java6-jdk
  (then Tomcat, but for Tomcat, I suggest installing it from the Tomcat site 
  distribution)
  apt-get install apache2
  apt-get install libapache2-mod-jk
  (the last 2 work out of the box and take max. 3 minutes altogether)

Well, it never rains but it pours.  After doing `sudo apt-get purge
apache2':

po...@ubuntu:~$ sudo apt-get install apache2
Reading package lists... Done
Building dependency tree   
Reading state information... Done
The following extra packages will be installed:
  apache2-mpm-worker
The following NEW packages will be installed:
  apache2 apache2-mpm-worker
0 upgraded, 2 newly installed, 0 to remove and 221 not upgraded.
Need to get 0B/3,846B of archives.
After this operation, 119kB of additional disk space will be used.
Do you want to continue [Y/n]? 
Selecting previously deselected package apache2-mpm-worker.
(Reading database ... 166454 files and directories currently
installed.)
Unpacking apache2-mpm-worker (from
.../apache2-mpm-worker_2.2.14-5ubuntu8_i386.deb) ...
Selecting previously deselected package apache2.
Unpacking apache2 (from .../apache2_2.2.14-5ubuntu8_i386.deb) ...
Setting up apache2-mpm-worker (2.2.14-5ubuntu8) ...
No apache MPM package installed

Now, the Apache installation is completely broken and will not install
properly.  That's the problem with these package systems:  no error
messages to indicate what might have gone wrong and nontrivial to
figure it out.  We'll see what they say over in ubuntu forums.  I
could shoot myself or go to bed.  I choose bed.

Thanks.

mp

-- 
Michael Powemich...@trollope.orgNaugatuck CT USA

He speaks well, he's well-read, but he's an idiot.
  -- N.D. Kalu, describing Rush Limbaugh


pgplCYZ1R46Yl.pgp
Description: PGP signature

Re: 404 with mod_jk

[Rainer Jung]

On 13.07.2010 23:17, Michael Powe wrote:

Hello,

I asked this question in the httpd list but no joy.

I have set up tomcat 6 and IBM httpd server to proxy requests using
mod_jk.

IBM_HTTP_Server/6.0.2 Apache/2.0.47 (Unix) mod_jk/1.2.30 Server at
localhost Port 80

I have followed all instructions as nearly as I can make
out.

The mod_jk log shows:

[Tue Jul 13 16:41:02 2010] [7639:50215792] [trace]
map_uri_to_worker_ext::jk_uri_worker_map.c (951): enter
[Tue Jul 13 16:41:02 2010] [7639:50215792] [debug]
map_uri_to_worker_ext::jk_uri_worker_map.c (1036): Attempting to map
URI '/TlTaggerTest/target.jsp' from 9 maps
[Tue Jul 13 16:41:02 2010] [7639:50215792] [trace]
find_match::jk_uri_worker_map.c (839): enter
[Tue Jul 13 16:41:02 2010] [7639:50215792] [debug]
find_match::jk_uri_worker_map.c (850): Attempting to map context URI
'/TlTaggerTest/*.jsp=worker1' source 'JkMount'
[Tue Jul 13 16:41:02 2010] [7639:50215792] [debug]
find_match::jk_uri_worker_map.c (863): Found a wildchar match
'/TlTaggerTest/*.jsp=worker1'
[Tue Jul 13 16:41:02 2010] [7639:50215792] [trace]
find_match::jk_uri_worker_map.c (866): exit
[Tue Jul 13 16:41:02 2010] [7639:50215792] [trace]
map_uri_to_worker_ext::jk_uri_worker_map.c (1065): exit


The next lines should have been:

... [7639:50215792] [trace] jk_handler::mod_jk.c (2383): enter
... [7639:50215792] [debug] jk_handler::mod_jk.c (2462): Into handler 
jakarta-servlet worker=worker1 r-proxyreq=0


It seems there is some other module, that handles the request instead of 
mod_jk or the handler is not set correctly. If you compiled to module 
yourself, you can easily find out by applying a little change:


2366 static int jk_handler(request_rec * r)
2367 {
2368 const char *worker_name;
2369 jk_server_conf_t *xconf;
2370 int rc, dmt = 1;
2371
2372 /* We do DIR_MAGIC_TYPE here to make sure TC gets all requests, 
even
2373  * if they are directory requests, in case there are no static 
files
2374  * visible to Apache and/or DirectoryIndex was not used. This 
is only

2375  * used when JkOptions has ForwardDirectories set. */
2376 /* Not for me, try next handler */
2377 if (strcmp(r-handler, JK_HANDLER)
2378  (dmt = strcmp(r-handler, DIR_MAGIC_TYPE)))
2379 return DECLINED;
2380

Before line 2372 add the following lines:

if (JK_IS_DEBUG_LEVEL(xconf-log)) {
jk_log(xconf-log, JK_LOG_DEBUG,
   Starting jk handler, Apache thinks it should use '%s',
   r-handler ? r-handler : NULL);
}

Regards,

Rainer

-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

Re: 404 with mod_jk

[Michael Powe]

Hello,

Thank you!  I did compile the module myself, wanting to be sure it was
properly compatible with my target environments.

I'll mod the code and see what new information is logged.

Thanks.

mp

On Thu, Jul 15, 2010 at 01:54:48PM +0200, Rainer Jung wrote:
 On 13.07.2010 23:17, Michael Powe wrote:
 Hello,
 
 I asked this question in the httpd list but no joy.
 
 I have set up tomcat 6 and IBM httpd server to proxy requests using
 mod_jk.
 
 IBM_HTTP_Server/6.0.2 Apache/2.0.47 (Unix) mod_jk/1.2.30 Server at
 localhost Port 80
 
 I have followed all instructions as nearly as I can make
 out.
 
 The mod_jk log shows:
 
 [Tue Jul 13 16:41:02 2010] [7639:50215792] [trace]
 map_uri_to_worker_ext::jk_uri_worker_map.c (951): enter
 [Tue Jul 13 16:41:02 2010] [7639:50215792] [debug]
 map_uri_to_worker_ext::jk_uri_worker_map.c (1036): Attempting to map
 URI '/TlTaggerTest/target.jsp' from 9 maps
 [Tue Jul 13 16:41:02 2010] [7639:50215792] [trace]
 find_match::jk_uri_worker_map.c (839): enter
 [Tue Jul 13 16:41:02 2010] [7639:50215792] [debug]
 find_match::jk_uri_worker_map.c (850): Attempting to map context URI
 '/TlTaggerTest/*.jsp=worker1' source 'JkMount'
 [Tue Jul 13 16:41:02 2010] [7639:50215792] [debug]
 find_match::jk_uri_worker_map.c (863): Found a wildchar match
 '/TlTaggerTest/*.jsp=worker1'
 [Tue Jul 13 16:41:02 2010] [7639:50215792] [trace]
 find_match::jk_uri_worker_map.c (866): exit
 [Tue Jul 13 16:41:02 2010] [7639:50215792] [trace]
 map_uri_to_worker_ext::jk_uri_worker_map.c (1065): exit
 
 The next lines should have been:
 
 ... [7639:50215792] [trace] jk_handler::mod_jk.c (2383): enter
 ... [7639:50215792] [debug] jk_handler::mod_jk.c (2462): Into handler 
 jakarta-servlet worker=worker1 r-proxyreq=0
 
 It seems there is some other module, that handles the request instead of 
 mod_jk or the handler is not set correctly. If you compiled to module 
 yourself, you can easily find out by applying a little change:
 
 2366 static int jk_handler(request_rec * r)
 2367 {
 2368 const char *worker_name;
 2369 jk_server_conf_t *xconf;
 2370 int rc, dmt = 1;
 2371
 2372 /* We do DIR_MAGIC_TYPE here to make sure TC gets all requests, 
 even
 2373  * if they are directory requests, in case there are no static 
 files
 2374  * visible to Apache and/or DirectoryIndex was not used. This 
 is only
 2375  * used when JkOptions has ForwardDirectories set. */
 2376 /* Not for me, try next handler */
 2377 if (strcmp(r-handler, JK_HANDLER)
 2378  (dmt = strcmp(r-handler, DIR_MAGIC_TYPE)))
 2379 return DECLINED;
 2380
 
 Before line 2372 add the following lines:
 
 if (JK_IS_DEBUG_LEVEL(xconf-log)) {
 jk_log(xconf-log, JK_LOG_DEBUG,
Starting jk handler, Apache thinks it should use '%s',
r-handler ? r-handler : NULL);
 }
 
 Regards,
 
 Rainer
 
 -
 To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
 For additional commands, e-mail: users-h...@tomcat.apache.org

-- 
Michael Powemich...@trollope.orgNaugatuck CT USA
In every country and in every age, the priest has been hostile to
liberty.  He is always in alliance with the despot, abetting his
abuses in return for protection to his own. -- Thomas Jefferson to
Horatio G. Spafford, 1814. ME 14:119


pgpbbwaSM5eFq.pgp
Description: PGP signature

Re: 404 with mod_jk

[Rainer Jung]

On 14.07.2010 04:57, Michael Powe wrote:

Hello,

Thank you for the reply.

See below for comments.

On Wed, Jul 14, 2010 at 12:37:05AM +0200, Rainer Jung wrote:


On 13.07.2010 23:17, Michael Powe wrote:

Hello,

I asked this question in the httpd list but no joy.

I have set up tomcat 6 and IBM httpd server to proxy requests using
mod_jk.

IBM_HTTP_Server/6.0.2 Apache/2.0.47 (Unix) mod_jk/1.2.30 Server at
localhost Port 80

I have followed all instructions as nearly as I can make
out.





Since you already have trace logging enabled:

- is this all that gets logged in the jk log file for the request?


I rotated the mod_jk log and restarted the server.  I get a huge trace
log, 33K.  It appears to me to be initializing correctly, in the sense
that there are no error messages.


- can you see your worker worker1 getting configured during startup
(debug log messages)?


[Tue Jul 13 22:21:00 2010] [12002:3987136] [trace] 
uri_worker_map_dump::jk_uri_worker_map.c (195): exit
[Tue Jul 13 22:21:00 2010] [12002:3987136] [trace] 
uri_worker_map_open::jk_uri_worker_map.c (830): exit
[Tue Jul 13 22:21:00 2010] [12002:3987136] [trace] 
uri_worker_map_alloc::jk_uri_worker_map.c (240): exit
[Tue Jul 13 22:21:00 2010] [12002:3987136] [debug] init_jk::mod_jk.c (3112): 
Using fcntl() for locking.
[Tue Jul 13 22:21:00 2010] [12002:3987136] [debug] init_jk::mod_jk.c (3128): 
Setting default connection pool max size to 25
[Tue Jul 13 22:21:00 2010] [12002:3987136] [debug] 
jk_map_read_property::jk_map.c (491): Adding property 'worker.list' with value 
'worker1' to map.
[Tue Jul 13 22:21:00 2010] [12002:3987136] [debug] 
jk_map_read_property::jk_map.c (491): Adding property 'worker.worker1.type' 
with value 'ajp13' to map.
[Tue Jul 13 22:21:00 2010] [12002:3987136] [debug] 
jk_map_read_property::jk_map.c (491): Adding property 'worker.worker1.host' 
with value 'localhost' to map.
[Tue Jul 13 22:21:00 2010] [12002:3987136] [debug] 
jk_map_read_property::jk_map.c (491): Adding property 'worker.worker1.port' 
with value '8009' to map.
[Tue Jul 13 22:21:00 2010] [12002:3987136] [trace] 
jk_map_resolve_references::jk_map.c (766): enter
[Tue Jul 13 22:21:00 2010] [12002:3987136] [debug] 
jk_map_resolve_references::jk_map.c (774): Checking for references with prefix 
worker. with wildcard (recursion 1)
[Tue Jul 13 22:21:00 2010] [12002:3987136] [trace] 
jk_map_resolve_references::jk_map.c (830): exit
[Tue Jul 13 22:21:00 2010] [12002:3987136] [trace] 
jk_shm_calculate_size::jk_shm.c (97): enter
[Tue Jul 13 22:21:00 2010] [12002:3987136] [debug] 
jk_shm_calculate_size::jk_shm.c (132): shared memory will contain 1 ajp workers 
of size 256 and 0 lb workers of size 320 with 0 members of size 320+256
[Tue Jul 13 22:21:00 2010] [12002:3987136] [trace] 
jk_shm_calculate_size::jk_shm.c (139): exit

[ ... ]

[Tue Jul 13 22:21:00 2010] [12002:3987136] [trace] wc_open::jk_worker.c (50): 
enter
[Tue Jul 13 22:21:00 2010] [12002:3987136] [debug] jk_map_dump::jk_map.c (589): 
Dump of map: 'ServerRoot' -  '/opt/IBMIHS'
[Tue Jul 13 22:21:00 2010] [12002:3987136] [debug] jk_map_dump::jk_map.c (589): 
Dump of map: 'worker.list' -  'worker1'
[Tue Jul 13 22:21:00 2010] [12002:3987136] [debug] jk_map_dump::jk_map.c (589): 
Dump of map: 'worker.worker1.type' -  'ajp13'
[Tue Jul 13 22:21:00 2010] [12002:3987136] [debug] jk_map_dump::jk_map.c (589): 
Dump of map: 'worker.worker1.host' -  'localhost'
[Tue Jul 13 22:21:00 2010] [12002:3987136] [debug] jk_map_dump::jk_map.c (589): 
Dump of map: 'worker.worker1.port' -  '8009'
[Tue Jul 13 22:21:00 2010] [12002:3987136] [trace] 
build_worker_map::jk_worker.c (236): enter
[Tue Jul 13 22:21:00 2010] [12002:3987136] [debug] 
build_worker_map::jk_worker.c (242): creating worker worker1
[Tue Jul 13 22:21:00 2010] [12002:3987136] [trace] 
wc_create_worker::jk_worker.c (126): enter
[Tue Jul 13 22:21:00 2010] [12002:3987136] [debug] 
wc_create_worker::jk_worker.c (146): about to create instance worker1 of ajp13
[Tue Jul 13 22:21:00 2010] [12002:3987136] [trace] 
ajp13_worker_factory::jk_ajp13_worker.c (80): enter
[Tue Jul 13 22:21:00 2010] [12002:3987136] [trace] 
ajp_worker_factory::jk_ajp_common.c (2892): enter
[Tue Jul 13 22:21:00 2010] [12002:3987136] [trace] 
ajp_worker_factory::jk_ajp_common.c (2934): exit
[Tue Jul 13 22:21:00 2010] [12002:3987136] [trace] 
ajp13_worker_factory::jk_ajp13_worker.c (92): exit
[Tue Jul 13 22:21:00 2010] [12002:3987136] [debug] 
wc_create_worker::jk_worker.c (159): about to validate and init worker1
[Tue Jul 13 22:21:00 2010] [12002:3987136] [trace] validate::jk_ajp13_worker.c 
(35): enter
[Tue Jul 13 22:21:00 2010] [12002:3987136] [trace] 
ajp_validate::jk_ajp_common.c (2579): enter
[Tue Jul 13 22:21:00 2010] [12002:3987136] [debug] 
ajp_validate::jk_ajp_common.c (2605): worker worker1 contact is 'localhost:8009'
[Tue Jul 13 22:21:00 2010] [12002:3987136] [trace] jk_resolve::jk_connect.c 
(329): enter
[Tue Jul 13 22:21:00 2010] [12002:3987136] [trace] jk_resolve::jk_connect.c 

Re: 404 with mod_jk

[Michael Powe]

Hello,

Thanks again for looking at this.  Here are the log entries
corresponding to a jsp page request.

[Wed Jul 14 05:42:57 2010] [15992:48036720] [trace] 
map_uri_to_worker_ext::jk_uri_worker_map.c (951): enter
[Wed Jul 14 05:42:57 2010] [15992:48036720] [debug] 
map_uri_to_worker_ext::jk_uri_worker_map.c (1036): Attempting to map URI 
'/TlTaggerTest/target.jsp' from 1 maps 
[Wed Jul 14 05:42:57 2010] [15992:48036720] [trace] 
find_match::jk_uri_worker_map.c (839): enter
[Wed Jul 14 05:42:57 2010] [15992:48036720] [debug] 
find_match::jk_uri_worker_map.c (850): Attempting to map context URI 
'/TlTaggerTest/*.jsp=worker1' source 'JkMount' 
[Wed Jul 14 05:42:57 2010] [15992:48036720] [debug] 
find_match::jk_uri_worker_map.c (863): Found a wildchar match 
'/TlTaggerTest/*.jsp=worker1'
[Wed Jul 14 05:42:57 2010] [15992:48036720] [trace] 
find_match::jk_uri_worker_map.c (866): exit
[Wed Jul 14 05:42:57 2010] [15992:48036720] [trace] 
map_uri_to_worker_ext::jk_uri_worker_map.c (1065): exit
[Wed Jul 14 05:43:00 2010] [15992:48036720] [trace] 
map_uri_to_worker_ext::jk_uri_worker_map.c (951): enter
[Wed Jul 14 05:43:00 2010] [15992:48036720] [debug] 
map_uri_to_worker_ext::jk_uri_worker_map.c (1036): Attempting to map URI 
'/favicon.ico' from 1 maps
[Wed Jul 14 05:43:00 2010] [15992:48036720] [trace] 
find_match::jk_uri_worker_map.c (839): enter
[Wed Jul 14 05:43:00 2010] [15992:48036720] [debug] 
find_match::jk_uri_worker_map.c (850): Attempting to map context URI 
'/TlTaggerTest/*.jsp=worker1' source 'JkMount'
[Wed Jul 14 05:43:00 2010] [15992:48036720] [trace] 
find_match::jk_uri_worker_map.c (882): exit
[Wed Jul 14 05:43:00 2010] [15992:48036720] [trace] 
map_uri_to_worker_ext::jk_uri_worker_map.c (1068): exit
[Wed Jul 14 05:43:00 2010] [15992:48036720] [debug] jk_translate::mod_jk.c 
(3542): no match for /favicon.ico found
[Wed Jul 14 05:43:00 2010] [15992:48036720] [trace] 
map_uri_to_worker_ext::jk_uri_worker_map.c (951): enter
[Wed Jul 14 05:43:00 2010] [15992:48036720] [debug] 
map_uri_to_worker_ext::jk_uri_worker_map.c (1036): Attempting to map URI 
'/favicon.ico' from 1 maps
[Wed Jul 14 05:43:00 2010] [15992:48036720] [trace] 
find_match::jk_uri_worker_map.c (839): enter
[Wed Jul 14 05:43:00 2010] [15992:48036720] [debug] 
find_match::jk_uri_worker_map.c (850): Attempting to map context URI 
'/TlTaggerTest/*.jsp=worker1' source 'JkMount'
[Wed Jul 14 05:43:00 2010] [15992:48036720] [trace] 
find_match::jk_uri_worker_map.c (882): exit
[Wed Jul 14 05:43:00 2010] [15992:48036720] [trace] 
map_uri_to_worker_ext::jk_uri_worker_map.c (1068): exit
[Wed Jul 14 05:43:00 2010] [15992:48036720] [debug] jk_map_to_storage::mod_jk.c 
(3609): no match for /favicon.ico found

I hate top-posting but these log entries have made this email
ridiculously long; plus, I'm ssh'ed into a terminal window and some
emacs key strokes are intercepted locally, so editing is somewhat
limited. 

Thanks again.

mp

On Wed, Jul 14, 2010 at 11:09:19AM +0200, Rainer Jung wrote:
 On 14.07.2010 04:57, Michael Powe wrote:
 Hello,
 
 Thank you for the reply.
 
 See below for comments.
 
 On Wed, Jul 14, 2010 at 12:37:05AM +0200, Rainer Jung wrote:
 
 On 13.07.2010 23:17, Michael Powe wrote:
 Hello,
 
 I asked this question in the httpd list but no joy.
 
 I have set up tomcat 6 and IBM httpd server to proxy requests using
 mod_jk.
 
 IBM_HTTP_Server/6.0.2 Apache/2.0.47 (Unix) mod_jk/1.2.30 Server at
 localhost Port 80
 
 I have followed all instructions as nearly as I can make
 out.
 
 
 
 Since you already have trace logging enabled:
 
 - is this all that gets logged in the jk log file for the request?
 
 I rotated the mod_jk log and restarted the server.  I get a huge trace
 log, 33K.  It appears to me to be initializing correctly, in the sense
 that there are no error messages.
 
 - can you see your worker worker1 getting configured during startup
 (debug log messages)?
 
 [Tue Jul 13 22:21:00 2010] [12002:3987136] [trace] 
 uri_worker_map_dump::jk_uri_worker_map.c (195): exit
 [Tue Jul 13 22:21:00 2010] [12002:3987136] [trace] 
 uri_worker_map_open::jk_uri_worker_map.c (830): exit
 [Tue Jul 13 22:21:00 2010] [12002:3987136] [trace] 
 uri_worker_map_alloc::jk_uri_worker_map.c (240): exit
 [Tue Jul 13 22:21:00 2010] [12002:3987136] [debug] init_jk::mod_jk.c 
 (3112): Using fcntl() for locking.
 [Tue Jul 13 22:21:00 2010] [12002:3987136] [debug] init_jk::mod_jk.c 
 (3128): Setting default connection pool max size to 25
 [Tue Jul 13 22:21:00 2010] [12002:3987136] [debug] 
 jk_map_read_property::jk_map.c (491): Adding property 'worker.list' with 
 value 'worker1' to map.
 [Tue Jul 13 22:21:00 2010] [12002:3987136] [debug] 
 jk_map_read_property::jk_map.c (491): Adding property 
 'worker.worker1.type' with value 'ajp13' to map.
 [Tue Jul 13 22:21:00 2010] [12002:3987136] [debug] 
 jk_map_read_property::jk_map.c (491): Adding property 
 'worker.worker1.host' with value 'localhost' to map.
 [Tue Jul 13 22:21:00 2010] [12002:3987136] [debug] 
 

Re: 404 with mod_jk

[André Warnier]

Mmmm. Taking into account all previous communications, this looks really strange.  It 
looks as if mod_jk is being called, is finding a match with its URI map, but then is not 
even making any attempt at contacting the Tomcat worker...


On the other hand, assuming that your IBM webserver is some clone of Apache (which is what 
the configuration looks like), then I find your VirtualHost section rather strange.

One would normally expect something like

Listen 80
NameVirtualHosts *:80
...
VirtualHost *:80
  ServerName localhost
...
/VirtualHost

I don't know if this could interfere with mod_jk, but maybe it does.


Michael Powe wrote:

Hello,

Thanks again for looking at this.  Here are the log entries
corresponding to a jsp page request.

[Wed Jul 14 05:42:57 2010] [15992:48036720] [trace] 
map_uri_to_worker_ext::jk_uri_worker_map.c (951): enter
[Wed Jul 14 05:42:57 2010] [15992:48036720] [debug] map_uri_to_worker_ext::jk_uri_worker_map.c (1036): Attempting to map URI '/TlTaggerTest/target.jsp' from 1 maps 
[Wed Jul 14 05:42:57 2010] [15992:48036720] [trace] find_match::jk_uri_worker_map.c (839): enter
[Wed Jul 14 05:42:57 2010] [15992:48036720] [debug] find_match::jk_uri_worker_map.c (850): Attempting to map context URI '/TlTaggerTest/*.jsp=worker1' source 'JkMount' 
[Wed Jul 14 05:42:57 2010] [15992:48036720] [debug] find_match::jk_uri_worker_map.c (863): Found a wildchar match '/TlTaggerTest/*.jsp=worker1'

[Wed Jul 14 05:42:57 2010] [15992:48036720] [trace] 
find_match::jk_uri_worker_map.c (866): exit
[Wed Jul 14 05:42:57 2010] [15992:48036720] [trace] 
map_uri_to_worker_ext::jk_uri_worker_map.c (1065): exit
[Wed Jul 14 05:43:00 2010] [15992:48036720] [trace] 
map_uri_to_worker_ext::jk_uri_worker_map.c (951): enter
[Wed Jul 14 05:43:00 2010] [15992:48036720] [debug] 
map_uri_to_worker_ext::jk_uri_worker_map.c (1036): Attempting to map URI 
'/favicon.ico' from 1 maps
[Wed Jul 14 05:43:00 2010] [15992:48036720] [trace] 
find_match::jk_uri_worker_map.c (839): enter
[Wed Jul 14 05:43:00 2010] [15992:48036720] [debug] 
find_match::jk_uri_worker_map.c (850): Attempting to map context URI 
'/TlTaggerTest/*.jsp=worker1' source 'JkMount'
[Wed Jul 14 05:43:00 2010] [15992:48036720] [trace] 
find_match::jk_uri_worker_map.c (882): exit
[Wed Jul 14 05:43:00 2010] [15992:48036720] [trace] 
map_uri_to_worker_ext::jk_uri_worker_map.c (1068): exit
[Wed Jul 14 05:43:00 2010] [15992:48036720] [debug] jk_translate::mod_jk.c 
(3542): no match for /favicon.ico found
[Wed Jul 14 05:43:00 2010] [15992:48036720] [trace] 
map_uri_to_worker_ext::jk_uri_worker_map.c (951): enter
[Wed Jul 14 05:43:00 2010] [15992:48036720] [debug] 
map_uri_to_worker_ext::jk_uri_worker_map.c (1036): Attempting to map URI 
'/favicon.ico' from 1 maps
[Wed Jul 14 05:43:00 2010] [15992:48036720] [trace] 
find_match::jk_uri_worker_map.c (839): enter
[Wed Jul 14 05:43:00 2010] [15992:48036720] [debug] 
find_match::jk_uri_worker_map.c (850): Attempting to map context URI 
'/TlTaggerTest/*.jsp=worker1' source 'JkMount'
[Wed Jul 14 05:43:00 2010] [15992:48036720] [trace] 
find_match::jk_uri_worker_map.c (882): exit
[Wed Jul 14 05:43:00 2010] [15992:48036720] [trace] 
map_uri_to_worker_ext::jk_uri_worker_map.c (1068): exit
[Wed Jul 14 05:43:00 2010] [15992:48036720] [debug] jk_map_to_storage::mod_jk.c 
(3609): no match for /favicon.ico found

I hate top-posting but these log entries have made this email
ridiculously long; plus, I'm ssh'ed into a terminal window and some
emacs key strokes are intercepted locally, so editing is somewhat
limited. 


Thanks again.

mp

On Wed, Jul 14, 2010 at 11:09:19AM +0200, Rainer Jung wrote:

On 14.07.2010 04:57, Michael Powe wrote:

Hello,

Thank you for the reply.

See below for comments.

On Wed, Jul 14, 2010 at 12:37:05AM +0200, Rainer Jung wrote:


On 13.07.2010 23:17, Michael Powe wrote:

Hello,

I asked this question in the httpd list but no joy.

I have set up tomcat 6 and IBM httpd server to proxy requests using
mod_jk.

IBM_HTTP_Server/6.0.2 Apache/2.0.47 (Unix) mod_jk/1.2.30 Server at
localhost Port 80

I have followed all instructions as nearly as I can make
out.


Since you already have trace logging enabled:

- is this all that gets logged in the jk log file for the request?

I rotated the mod_jk log and restarted the server.  I get a huge trace
log, 33K.  It appears to me to be initializing correctly, in the sense
that there are no error messages.


- can you see your worker worker1 getting configured during startup
(debug log messages)?
[Tue Jul 13 22:21:00 2010] [12002:3987136] [trace] 
uri_worker_map_dump::jk_uri_worker_map.c (195): exit
[Tue Jul 13 22:21:00 2010] [12002:3987136] [trace] 
uri_worker_map_open::jk_uri_worker_map.c (830): exit
[Tue Jul 13 22:21:00 2010] [12002:3987136] [trace] 
uri_worker_map_alloc::jk_uri_worker_map.c (240): exit
[Tue Jul 13 22:21:00 2010] [12002:3987136] [debug] init_jk::mod_jk.c 
(3112): Using fcntl() for locking.
[Tue Jul 13 22:21:00 2010] [12002:3987136] [debug] 

Re: 404 with mod_jk

[Michael Powe]

Hello,

See below.

On Wed, Jul 14, 2010 at 12:13:11PM +0200, André Warnier wrote:

 Mmmm. Taking into account all previous communications, this looks really 
 strange.  It looks as if mod_jk is being called, is finding a match with 
 its URI map, but then is not even making any attempt at contacting the 
 Tomcat worker...
 
 On the other hand, assuming that your IBM webserver is some clone of Apache 
 (which is what the configuration looks like), then I find your 
 VirtualHost section rather strange.
 One would normally expect something like
 
 Listen 80
 NameVirtualHosts *:80
 ...
 VirtualHost *:80
   ServerName localhost
 ...
 /VirtualHost
 
 I don't know if this could interfere with mod_jk, but maybe it does.
 

The VirtualHost section was created by the ApacheConfig option in
Tomcat.  It actually creates a separate mod_jk.conf file that is to be
included via an Include line, but I copied it into the httpd.conf file
because I made some modifications to the original.  That is just
because unless I disable the auto config in server.xml, the conf file
is regenerated every time Tomcat is restarted.

The modifications were to comment out the mounts I didn't want to use,
and add a DocumentRoot for local (non-jsp) files, as well as change
the JkMount directive to point only to .jsp files.

Thanks.

mp

 
 Michael Powe wrote:
 Hello,
 
 Thanks again for looking at this.  Here are the log entries
 corresponding to a jsp page request.
 
 [Wed Jul 14 05:42:57 2010] [15992:48036720] [trace] 
 map_uri_to_worker_ext::jk_uri_worker_map.c (951): enter
 [Wed Jul 14 05:42:57 2010] [15992:48036720] [debug] 
 map_uri_to_worker_ext::jk_uri_worker_map.c (1036): Attempting to map URI 
 '/TlTaggerTest/target.jsp' from 1 maps [Wed Jul 14 05:42:57 2010] 
 [15992:48036720] [trace] find_match::jk_uri_worker_map.c (839): enter
 [Wed Jul 14 05:42:57 2010] [15992:48036720] [debug] 
 find_match::jk_uri_worker_map.c (850): Attempting to map context URI 
 '/TlTaggerTest/*.jsp=worker1' source 'JkMount' [Wed Jul 14 05:42:57 2010] 
 [15992:48036720] [debug] find_match::jk_uri_worker_map.c (863): Found a 
 wildchar match '/TlTaggerTest/*.jsp=worker1'
 [Wed Jul 14 05:42:57 2010] [15992:48036720] [trace] 
 find_match::jk_uri_worker_map.c (866): exit
 [Wed Jul 14 05:42:57 2010] [15992:48036720] [trace] 
 map_uri_to_worker_ext::jk_uri_worker_map.c (1065): exit
 [Wed Jul 14 05:43:00 2010] [15992:48036720] [trace] 
 map_uri_to_worker_ext::jk_uri_worker_map.c (951): enter
 [Wed Jul 14 05:43:00 2010] [15992:48036720] [debug] 
 map_uri_to_worker_ext::jk_uri_worker_map.c (1036): Attempting to map URI 
 '/favicon.ico' from 1 maps
 [Wed Jul 14 05:43:00 2010] [15992:48036720] [trace] 
 find_match::jk_uri_worker_map.c (839): enter
 [Wed Jul 14 05:43:00 2010] [15992:48036720] [debug] 
 find_match::jk_uri_worker_map.c (850): Attempting to map context URI 
 '/TlTaggerTest/*.jsp=worker1' source 'JkMount'
 [Wed Jul 14 05:43:00 2010] [15992:48036720] [trace] 
 find_match::jk_uri_worker_map.c (882): exit
 [Wed Jul 14 05:43:00 2010] [15992:48036720] [trace] 
 map_uri_to_worker_ext::jk_uri_worker_map.c (1068): exit
 [Wed Jul 14 05:43:00 2010] [15992:48036720] [debug] jk_translate::mod_jk.c 
 (3542): no match for /favicon.ico found
 [Wed Jul 14 05:43:00 2010] [15992:48036720] [trace] 
 map_uri_to_worker_ext::jk_uri_worker_map.c (951): enter
 [Wed Jul 14 05:43:00 2010] [15992:48036720] [debug] 
 map_uri_to_worker_ext::jk_uri_worker_map.c (1036): Attempting to map URI 
 '/favicon.ico' from 1 maps
 [Wed Jul 14 05:43:00 2010] [15992:48036720] [trace] 
 find_match::jk_uri_worker_map.c (839): enter
 [Wed Jul 14 05:43:00 2010] [15992:48036720] [debug] 
 find_match::jk_uri_worker_map.c (850): Attempting to map context URI 
 '/TlTaggerTest/*.jsp=worker1' source 'JkMount'
 [Wed Jul 14 05:43:00 2010] [15992:48036720] [trace] 
 find_match::jk_uri_worker_map.c (882): exit
 [Wed Jul 14 05:43:00 2010] [15992:48036720] [trace] 
 map_uri_to_worker_ext::jk_uri_worker_map.c (1068): exit
 [Wed Jul 14 05:43:00 2010] [15992:48036720] [debug] 
 jk_map_to_storage::mod_jk.c (3609): no match for /favicon.ico found
 
 I hate top-posting but these log entries have made this email
 ridiculously long; plus, I'm ssh'ed into a terminal window and some
 emacs key strokes are intercepted locally, so editing is somewhat
 limited. 
 
 Thanks again.
 
 mp
 
 On Wed, Jul 14, 2010 at 11:09:19AM +0200, Rainer Jung wrote:
 On 14.07.2010 04:57, Michael Powe wrote:
 Hello,
 
 Thank you for the reply.
 
 See below for comments.
 
 On Wed, Jul 14, 2010 at 12:37:05AM +0200, Rainer Jung wrote:
 
 On 13.07.2010 23:17, Michael Powe wrote:
 Hello,
 
 I asked this question in the httpd list but no joy.
 
 I have set up tomcat 6 and IBM httpd server to proxy requests using
 mod_jk.
 
 IBM_HTTP_Server/6.0.2 Apache/2.0.47 (Unix) mod_jk/1.2.30 Server at
 localhost Port 80
 
 I have followed all instructions as nearly as I can make
 out.
 
 Since you already have trace logging enabled:
 
 - is this all that gets 

Re: 404 with mod_jk

[Konstantin Kolinko]

2010/7/14 Michael Powe mich...@trollope.org:
 VirtualHost localhost
(...)
 #    JkMount /host-manager ajp13
 #    JkMount /host-manager/* ajp13
 
     JkMount /TlTaggerTest/*.jsp worker1
 /VirtualHost
 

 The VirtualHost section was created by the ApacheConfig option in
 Tomcat.

Trivial question:  are you sure, that your worker name is correct
(worker1 vs. ajp13).  I am curious, why Tomcat-generated
configuration has different worker name.

Best regards,
Konstantin Kolinko

-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

Re: 404 with mod_jk

[Rainer Jung]

On 14.07.2010 14:37, Konstantin Kolinko wrote:

2010/7/14 Michael Powemich...@trollope.org:

VirtualHost localhost

(...)

#JkMount /host-manager ajp13
#JkMount /host-manager/* ajp13

JkMount /TlTaggerTest/*.jsp worker1
/VirtualHost



The VirtualHost section was created by the ApacheConfig option in
Tomcat.


Trivial question:  are you sure, that your worker name is correct
(worker1 vs. ajp13).  I am curious, why Tomcat-generated
configuration has different worker name.


The auto configuration feature of Tomcat should be deprecated. It is of 
no real use except for a trivial starter configuration. It *always* uses 
a single worker named ajp13.


Because of this feature (I guess because) mod_jk has a builtin worker 
named ajp13, which even if no worker named ajp13 is explicitely 
defined tries to contact localhost at 8009 if the a URL is mounted to a 
worker named ajp13. Legacy stuff.


Nevertheless, although the config the OP uses is not sufficient for 
prime time, it should work. I didn't yet have the time to compare, where 
exactly the log lines stop compared with a working request.


Regards,

Rainer

-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

Re: 404 with mod_jk

[Michael Powe]

On Wed, Jul 14, 2010 at 04:37:17PM +0200, Rainer Jung wrote:
 On 14.07.2010 14:37, Konstantin Kolinko wrote:
 2010/7/14 Michael Powemich...@trollope.org:
 VirtualHost localhost
 (...)
 #JkMount /host-manager ajp13
 #JkMount /host-manager/* ajp13
 
 JkMount /TlTaggerTest/*.jsp worker1
 /VirtualHost
 
 
 The VirtualHost section was created by the ApacheConfig option in
 Tomcat.
 
 Trivial question:  are you sure, that your worker name is correct
 (worker1 vs. ajp13).  I am curious, why Tomcat-generated
 configuration has different worker name.
 
 The auto configuration feature of Tomcat should be deprecated. It is of 
 no real use except for a trivial starter configuration. It *always* uses 
 a single worker named ajp13.
 
 Because of this feature (I guess because) mod_jk has a builtin worker 
 named ajp13, which even if no worker named ajp13 is explicitely 
 defined tries to contact localhost at 8009 if the a URL is mounted to a 
 worker named ajp13. Legacy stuff.
 
 Nevertheless, although the config the OP uses is not sufficient for 
 prime time, it should work. I didn't yet have the time to compare, where 
 exactly the log lines stop compared with a working request.

Hello,

The evolution of this process is as follows.  I am updating an Apache
module with some additional functionality.  This module is installed
in two places, one an Apache 2.0 server and the other an IBM httpd
server.  In both instances, Apache is serving pages in front of a
Tomcat server.  Additionally, the module needs to run in multiple
virtual hosts.  Therefore, I have to recreate the production design
locally, in order to be able to install my module and test my new
additions.

To install mod_jk, I resorted to my good friend Google, and used a
tutorial to set up the connector.  In that tutorial, the method used
was to create a properties file (workers.properties) which set up the
worker `worker1'.  

Failing to get that process working, I fell back to the ApacheConfig
directive, given the possibility that I might be leaving out something
simple yet critical in my `hand-rolled' method.  I just changed the
worker name back to `worker1' because I didn't want to keep fiddling
with the conf files, and `worker1' was already in place.  Really, I
just used ApacheConfig to get something to compare to my existing
setup.

I really appreciate your taking time to look at this.  It is such a
huge time-waster for me.  I'm spending more time setting up the test
environment than on my code.

I'm installing a clean version of Apache, built from httpd.apache.org
sources, in /usr/local in order to get around all the weird (IMO)
configuration for the version installed in Ubuntu by default.  At this
point, I've fiddled so many things I've lost track of where I'm at.
Sometimes, when you can't get something to work, it's best to return
to first principles.

Thanks.

mp

-- 
Michael Powemich...@trollope.orgNaugatuck CT USA


And your crybaby whiny opinion would be.?


pgpZDJceFOHaq.pgp
Description: PGP signature

Re: 404 with mod_jk

[André Warnier]

Michael Powe wrote:
...


To install mod_jk, I resorted to my good friend Google, and used a
tutorial to set up the connector.  In that tutorial, the method used
was to create a properties file (workers.properties) which set up the
worker `worker1'.  


...

I'm installing a clean version of Apache, built from httpd.apache.org
sources, in /usr/local in order to get around all the weird (IMO)
configuration for the version installed in Ubuntu by default.  At this
point, I've fiddled so many things I've lost track of where I'm at.
Sometimes, when you can't get something to work, it's best to return
to first principles.

I will not often say this, but I believe your problems may stem from the above, and that 
you would do better by using the pre-packaged versions of things (except Tomcat)

.
1) it is hard to judge the correctness of a tutorial found on Google.
The mod_jk instructions on the mod_jk pages of the Tomcat website are pretty good, and 
they are at least accurate and up-to-date.


2) the standard Apache packages for Debian and Ubuntu are quite good, and a lot easier to 
install and maintain than working everything out from scratch.

I suggest the following order :
apt-get install sun-java6-jdk
(then Tomcat, but for Tomcat, I suggest installing it from the Tomcat site 
distribution)
apt-get install apache2
apt-get install libapache2-mod-jk
(the last 2 work out of the box and take max. 3 minutes altogether)

Then you just need to add a workers.properties file and your JkMount mappings, and 
you'll be up and running in no time.


The weird configuration things you are mentioning for Apache, are quite easy to follow 
once you get over the initial surprise, and are actually a clever way to facilitate 
enabling/disabling modules and virtual hosts.

I offer to explain summarily, maybe off-list, if you have trouble there.

This all does not mean that it would not be interesting to find out where your current 
problem is.  But as Konstantin and/or Rainer mentioned, I believe the first thing would be 
to get out of the auto-configure thing.  I do not believe that this part has been well 
maintained since quite a while now.



-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

Re: 404 with mod_jk

[Michael Powe]

On Thu, Jul 15, 2010 at 02:28:52AM +0200, André Warnier wrote:
 Michael Powe wrote:

 To install mod_jk, I resorted to my good friend Google, and used a
 tutorial to set up the connector.  In that tutorial, the method used
 was to create a properties file (workers.properties) which set up the
 worker `worker1'.  
 ...
 I'm installing a clean version of Apache, built from httpd.apache.org
 sources, in /usr/local in order to get around all the weird (IMO)
 configuration for the version installed in Ubuntu by default.  At this
 point, I've fiddled so many things I've lost track of where I'm at.
 Sometimes, when you can't get something to work, it's best to return
 to first principles.

 I will not often say this, but I believe your problems may stem from the 
 above, and that you would do better by using the pre-packaged versions of 
 things (except Tomcat)

 1) it is hard to judge the correctness of a tutorial found on Google.
 The mod_jk instructions on the mod_jk pages of the Tomcat website are 
 pretty good, and they are at least accurate and up-to-date.

True.  One of them was the `quick start for the impatient' on the
mod_jk doc page.
 
 2) the standard Apache packages for Debian and Ubuntu are quite good, and a 
 lot easier to install and maintain than working everything out from scratch.
 I suggest the following order :
 apt-get install sun-java6-jdk
 (then Tomcat, but for Tomcat, I suggest installing it from the Tomcat site 
 distribution)
 apt-get install apache2
 apt-get install libapache2-mod-jk
 (the last 2 work out of the box and take max. 3 minutes altogether)
 
 Then you just need to add a workers.properties file and your JkMount 
 mappings, and you'll be up and running in no time.
 
 The weird configuration things you are mentioning for Apache, are quite 
 easy to follow once you get over the initial surprise, and are actually a 
 clever way to facilitate enabling/disabling modules and virtual hosts.
 I offer to explain summarily, maybe off-list, if you have trouble there.

Well, it can't hurt for me to uninstall/reinstall to get things back
to a clean configuration.

Also, there's more to the weirdness of the Apache installation than
just the module/vh setup.  First, they've arbitrarily renamed some
elements (e.g., replaced `httpd' with `apache2' in various places),
which serves no useful purpose.  Second, `apxs' (renamed to `apxs2')
does not work correctly for compiling and installing my existing
module.  Maybe it works if you create one from scratch, I don't
know. Nor does `apachectl' (renamed to `apache2ctl').  `apache2ctl'
fails sometimes with the weird message `bad user name
${APACHE_RUN_USER}', meaning I take it that this variable is not
properly exported unless you run `/etc/init.d/apache2'.  Which only
takes `start|stop|restart|reload' for arguments.  (And setting the var
in the shell does not work.)  Third, you have files needed for
development/admin work in /etc/apache2, /var/lib/apache2 and
/usr/share/apache2 -- I mean, WTF?

For me, the summary of all that is that I installed the IBM server
into /opt and all the module-related stuff (apxs) and control stuff
(apachectl) just works.  And I'm not giving props to IBM so much as
I'm saying that the design of the installation for Ubuntu was not
intended for usage as a development package.  

/rant

I'll do as you suggest regarding the OOB installation and see where I
get.  I spent most of today working on my module, so at least I have a
feeling of progress.

Thanks.

mp 
 
-- 
Michael Powemich...@trollope.orgNaugatuck CT USA
I'll carry your books, I'll carry a tune, I'll carry on, carry over,
carry forward, Cary Grant, cash  carry, Carry Me Back To Old
Virginia, I'll even Hara Kari if you show me how, but I will *not*
carry a gun.  -- Hawkeye, M*A*S*H


pgpA74AJDIOI1.pgp
Description: PGP signature

Re: 404 with mod_jk

[Rainer Jung]

On 13.07.2010 23:17, Michael Powe wrote:

Hello,

I asked this question in the httpd list but no joy.

I have set up tomcat 6 and IBM httpd server to proxy requests using
mod_jk.

IBM_HTTP_Server/6.0.2 Apache/2.0.47 (Unix) mod_jk/1.2.30 Server at
localhost Port 80

I have followed all instructions as nearly as I can make
out.

The mod_jk log shows:

[Tue Jul 13 16:41:02 2010] [7639:50215792] [trace]
map_uri_to_worker_ext::jk_uri_worker_map.c (951): enter
[Tue Jul 13 16:41:02 2010] [7639:50215792] [debug]
map_uri_to_worker_ext::jk_uri_worker_map.c (1036): Attempting to map
URI '/TlTaggerTest/target.jsp' from 9 maps
[Tue Jul 13 16:41:02 2010] [7639:50215792] [trace]
find_match::jk_uri_worker_map.c (839): enter
[Tue Jul 13 16:41:02 2010] [7639:50215792] [debug]
find_match::jk_uri_worker_map.c (850): Attempting to map context URI
'/TlTaggerTest/*.jsp=worker1' source 'JkMount'
[Tue Jul 13 16:41:02 2010] [7639:50215792] [debug]
find_match::jk_uri_worker_map.c (863): Found a wildchar match
'/TlTaggerTest/*.jsp=worker1'
[Tue Jul 13 16:41:02 2010] [7639:50215792] [trace]
find_match::jk_uri_worker_map.c (866): exit
[Tue Jul 13 16:41:02 2010] [7639:50215792] [trace]
map_uri_to_worker_ext::jk_uri_worker_map.c (1065): exit

The Apache access log shows:

localhost - - [13/Jul/2010:16:41:02 -0400] GET
/TlTaggerTest/target.jsp  404 332 - Mozilla/5.0 (X11; U; Linux
i686; en-US; rv:1.9.2.3) Gecko/20100423 Ubuntu/10.04 (lucid)
Firefox/3.6.3 -

No indication on the Tomcat side of any activity.

The ajp13 connector is enabled.  Both mod_jk and ajp13 connector are
on port 8009.

The files are available directly from Tomcat through port 8080.

The local files (in htdocs) are properly served.

localhost - - [13/Jul/2010:16:58:01 -0400] GET
/TlTaggerTest/target.html  200 67 - Mozilla/5.0 (X11; U; Linux
i686; en-US; rv:1.9.2.3) Gecko/20100423 Ubuntu/10.04 (lucid)
Firefox/3.6.3 -

I sure would appreciate any pointers for troubleshooting or
resolution.

Thanks.

mp


Since you already have trace logging enabled:

- is this all that gets logged in the jk log file for the request?

- can you see your worker worker1 getting configured during startup
(debug log messages)?

- anything in the httpd error log? Maybe your mod_jk module file is not 
really compatible with your web server binary and you get process crashes?


If those remarks do not help, we will need your configuration and more 
complete logs.


Regards,

Rainer

-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

Re: 404 with mod_jk

[Michael Powe]

Hello,

Thank you for the reply.

See below for comments.

On Wed, Jul 14, 2010 at 12:37:05AM +0200, Rainer Jung wrote:

 On 13.07.2010 23:17, Michael Powe wrote:
 Hello,
 
 I asked this question in the httpd list but no joy.
 
 I have set up tomcat 6 and IBM httpd server to proxy requests using
 mod_jk.
 
 IBM_HTTP_Server/6.0.2 Apache/2.0.47 (Unix) mod_jk/1.2.30 Server at
 localhost Port 80
 
 I have followed all instructions as nearly as I can make
 out.
 

 
 Since you already have trace logging enabled:
 
 - is this all that gets logged in the jk log file for the request?

I rotated the mod_jk log and restarted the server.  I get a huge trace
log, 33K.  It appears to me to be initializing correctly, in the sense
that there are no error messages.  
 
 - can you see your worker worker1 getting configured during startup
 (debug log messages)?

[Tue Jul 13 22:21:00 2010] [12002:3987136] [trace] 
uri_worker_map_dump::jk_uri_worker_map.c (195): exit
[Tue Jul 13 22:21:00 2010] [12002:3987136] [trace] 
uri_worker_map_open::jk_uri_worker_map.c (830): exit
[Tue Jul 13 22:21:00 2010] [12002:3987136] [trace] 
uri_worker_map_alloc::jk_uri_worker_map.c (240): exit
[Tue Jul 13 22:21:00 2010] [12002:3987136] [debug] init_jk::mod_jk.c (3112): 
Using fcntl() for locking.
[Tue Jul 13 22:21:00 2010] [12002:3987136] [debug] init_jk::mod_jk.c (3128): 
Setting default connection pool max size to 25
[Tue Jul 13 22:21:00 2010] [12002:3987136] [debug] 
jk_map_read_property::jk_map.c (491): Adding property 'worker.list' with value 
'worker1' to map.
[Tue Jul 13 22:21:00 2010] [12002:3987136] [debug] 
jk_map_read_property::jk_map.c (491): Adding property 'worker.worker1.type' 
with value 'ajp13' to map.
[Tue Jul 13 22:21:00 2010] [12002:3987136] [debug] 
jk_map_read_property::jk_map.c (491): Adding property 'worker.worker1.host' 
with value 'localhost' to map.
[Tue Jul 13 22:21:00 2010] [12002:3987136] [debug] 
jk_map_read_property::jk_map.c (491): Adding property 'worker.worker1.port' 
with value '8009' to map.
[Tue Jul 13 22:21:00 2010] [12002:3987136] [trace] 
jk_map_resolve_references::jk_map.c (766): enter 
[Tue Jul 13 22:21:00 2010] [12002:3987136] [debug] 
jk_map_resolve_references::jk_map.c (774): Checking for references with prefix 
worker. with wildcard (recursion 1)
[Tue Jul 13 22:21:00 2010] [12002:3987136] [trace] 
jk_map_resolve_references::jk_map.c (830): exit
[Tue Jul 13 22:21:00 2010] [12002:3987136] [trace] 
jk_shm_calculate_size::jk_shm.c (97): enter
[Tue Jul 13 22:21:00 2010] [12002:3987136] [debug] 
jk_shm_calculate_size::jk_shm.c (132): shared memory will contain 1 ajp workers 
of size 256 and 0 lb workers of size 320 with 0 members of size 320+256
[Tue Jul 13 22:21:00 2010] [12002:3987136] [trace] 
jk_shm_calculate_size::jk_shm.c (139): exit

[ ... ]

[Tue Jul 13 22:21:00 2010] [12002:3987136] [trace] wc_open::jk_worker.c (50): 
enter
[Tue Jul 13 22:21:00 2010] [12002:3987136] [debug] jk_map_dump::jk_map.c (589): 
Dump of map: 'ServerRoot' - '/opt/IBMIHS'
[Tue Jul 13 22:21:00 2010] [12002:3987136] [debug] jk_map_dump::jk_map.c (589): 
Dump of map: 'worker.list' - 'worker1'
[Tue Jul 13 22:21:00 2010] [12002:3987136] [debug] jk_map_dump::jk_map.c (589): 
Dump of map: 'worker.worker1.type' - 'ajp13'
[Tue Jul 13 22:21:00 2010] [12002:3987136] [debug] jk_map_dump::jk_map.c (589): 
Dump of map: 'worker.worker1.host' - 'localhost'
[Tue Jul 13 22:21:00 2010] [12002:3987136] [debug] jk_map_dump::jk_map.c (589): 
Dump of map: 'worker.worker1.port' - '8009'
[Tue Jul 13 22:21:00 2010] [12002:3987136] [trace] 
build_worker_map::jk_worker.c (236): enter
[Tue Jul 13 22:21:00 2010] [12002:3987136] [debug] 
build_worker_map::jk_worker.c (242): creating worker worker1
[Tue Jul 13 22:21:00 2010] [12002:3987136] [trace] 
wc_create_worker::jk_worker.c (126): enter
[Tue Jul 13 22:21:00 2010] [12002:3987136] [debug] 
wc_create_worker::jk_worker.c (146): about to create instance worker1 of ajp13
[Tue Jul 13 22:21:00 2010] [12002:3987136] [trace] 
ajp13_worker_factory::jk_ajp13_worker.c (80): enter
[Tue Jul 13 22:21:00 2010] [12002:3987136] [trace] 
ajp_worker_factory::jk_ajp_common.c (2892): enter
[Tue Jul 13 22:21:00 2010] [12002:3987136] [trace] 
ajp_worker_factory::jk_ajp_common.c (2934): exit
[Tue Jul 13 22:21:00 2010] [12002:3987136] [trace] 
ajp13_worker_factory::jk_ajp13_worker.c (92): exit
[Tue Jul 13 22:21:00 2010] [12002:3987136] [debug] 
wc_create_worker::jk_worker.c (159): about to validate and init worker1
[Tue Jul 13 22:21:00 2010] [12002:3987136] [trace] validate::jk_ajp13_worker.c 
(35): enter
[Tue Jul 13 22:21:00 2010] [12002:3987136] [trace] 
ajp_validate::jk_ajp_common.c (2579): enter
[Tue Jul 13 22:21:00 2010] [12002:3987136] [debug] 
ajp_validate::jk_ajp_common.c (2605): worker worker1 contact is 'localhost:8009'
[Tue Jul 13 22:21:00 2010] [12002:3987136] [trace] jk_resolve::jk_connect.c 
(329): enter
[Tue Jul 13 22:21:00 2010] [12002:3987136] [trace] jk_resolve::jk_connect.c 
(406): exit
[Tue Jul 13 22:21:00 

Re: 404 for JSPs

[Christopher Schultz]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Clay,

On 12/20/2009 9:32 PM, Clay McCoy wrote:
 When I run embedded Tomcat my jsps 404, but my servlets work. When I
 run standard (by putting my war on the Tomcat/webapps directory) my
 servlets 404 but my jsps work (without any css). Can anyone shed some
 light on this? My startup script for embedded is here:
 http://gist.github.com/259737

- From reading all the information you provided, I would guess that, in an
embedded environment, Tomcat does not automatically read conf/web.xml to
configure the default webapps provided by Tomcat (when /not/ running
embedded).

Specifically, you are missing the definition of the JspServlet and the
DefaultServlet. The JspServlet is usually mapped to *.jsp and *.jspx and
(duh) provides JSP capabilities for those URIs. The DefaultServlet is
usually mapped to / (meaning everything that doesn't match anything
else) and provides the typical plain-old file serving for things like
static content (*.css, etc.).

I suspect that, since you are running in an embedded environment, you
will have to explicitly load these definitions. I'm not familiar enough
with the embedded API to know if you can load more than one web.xml file
for a single Context, but this is essentially what you'll need to do.
You might want to merge conf/web.xml into your webapp's WEB-INF/web.xml
file if you are always going to run your webapp embedded in this way:
you'll save yourself a lot of headache by doing it this way.

Hope that helps,
- -chris
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.10 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAksyRFcACgkQ9CaO5/Lv0PD+nQCgiwmITqPsPm26zgCYKGDeFVkD
u18AoJpwy4d2URYUr5Vtkd3gLJ+oTTJq
=TvQK
-END PGP SIGNATURE-

-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

Re: 404 for JSPs

[Clay McCoy]

Oh, and no errors in the logs.


On 12/20/09 8:32 PM, Clay McCoy cmc...@acteksoft.com wrote:

When I run embedded Tomcat my jsps 404, but my servlets work.
When I run standard (by putting my war on the Tomcat/webapps directory) my 
servlets 404 but my jsps work (without any css).
Can anyone shed some light on this?
My startup script for embedded is here: http://gist.github.com/259737

Thanks,
Clay

-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

Re: 404 for JSPs

[Konstantin Kolinko]

2009/12/21 Clay McCoy cmc...@acteksoft.com:
 When I run embedded Tomcat my jsps 404, but my servlets work.

I guess that you do not have the Jsp servlet configured. See conf/web.xml.

-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

Re: 404 for JSPs

[Clay McCoy]

Thank you, this got me closer.  I have two questions:

1)  My current web.xml didn't configure the jsp servlet.  I haven't had do 
configure that for a number of other containers.  I don't understand why I had 
to do this specifically for Tomcat.  It also seems bizarre that the jsps worked 
without this jsp servlet in my standard Tomcat deployment.  What should I have 
read to know about Tomcat needing a jsp servlet and possibly other related 
gotchas?

2) I now get this error.  I'm guessing that this means that I need to do 
something to configure my custom tags?

javax.servlet.ServletException: 
javax.servlet.jsp.tagext.TagAttributeInfo.init(Ljava/lang/String;ZLjava/lang/String;ZZLjava/lang/String;ZZLjava/lang/String;Ljava/lang/String;)V
at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:275)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
at 
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
at 
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at 
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233)
at 
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
at 
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:128)
at 
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
at 
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
at 
org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:286)
at 
org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:845)
at 
org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:583)
at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447)
at java.lang.Thread.run(Thread.java:637)



On 12/20/09 8:56 PM, Konstantin Kolinko knst.koli...@gmail.com wrote:

2009/12/21 Clay McCoy cmc...@acteksoft.com:
 When I run embedded Tomcat my jsps 404, but my servlets work.

I guess that you do not have the Jsp servlet configured. See conf/web.xml.

-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org



-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

Re: 404 for JSPs

[Clay McCoy]

Apparently Groovy 1.7 rc2 uses an outdated jsp api (2.0) and Tomcat 6 uses 2.1  
This conflict was causing me problems.  Of all the libraries, I was very 
surprised to see the conflict between the latest Tomcat and Groovy.
Things still aren't right, but I don't know how to report what I am seeing yet.
Thanks,
Clay

On 12/20/09 10:24 PM, Clay McCoy cmc...@acteksoft.com wrote:

Thank you, this got me closer.  I have two questions:

1)  My current web.xml didn't configure the jsp servlet.  I haven't had do 
configure that for a number of other containers.  I don't understand why I had 
to do this specifically for Tomcat.  It also seems bizarre that the jsps worked 
without this jsp servlet in my standard Tomcat deployment.  What should I have 
read to know about Tomcat needing a jsp servlet and possibly other related 
gotchas?

2) I now get this error.  I'm guessing that this means that I need to do 
something to configure my custom tags?

javax.servlet.ServletException: 
javax.servlet.jsp.tagext.TagAttributeInfo.init(Ljava/lang/String;ZLjava/lang/String;ZZLjava/lang/String;ZZLjava/lang/String;Ljava/lang/String;)V
at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:275)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
at 
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
at 
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at 
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233)
at 
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
at 
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:128)
at 
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
at 
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
at 
org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:286)
at 
org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:845)
at 
org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:583)
at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447)
at java.lang.Thread.run(Thread.java:637)



On 12/20/09 8:56 PM, Konstantin Kolinko knst.koli...@gmail.com wrote:

2009/12/21 Clay McCoy cmc...@acteksoft.com:
 When I run embedded Tomcat my jsps 404, but my servlets work.

I guess that you do not have the Jsp servlet configured. See conf/web.xml.

-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org



-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org



-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

Re: 404 for JSPs

[Konstantin Kolinko]

2009/12/21 Clay McCoy cmc...@acteksoft.com:
 Thank you, this got me closer.  I have two questions:

 1)  My current web.xml didn't configure the jsp servlet.  I haven't had do 
 configure that for a number of other containers.  I don't understand why I 
 had to do this specifically for Tomcat.

You do not have to do it here either.  conf/web.xml provides it for
you.  You may say that it is merged with your web.xml.  I do not know
what happened in your case. Maybe you need to read that file
programmatically, or maybe it just was not found.

 It also seems bizarre that the jsps worked without this jsp servlet in my 
standard Tomcat deployment.  What should I have read to know about Tomcat 
needing a jsp servlet and possibly other related gotchas?

Embedded tomcat is not a 'standard' deployment.

 Apparently Groovy 1.7 rc2 uses an outdated jsp api (2.0) and Tomcat 6 uses 2.1

Tomcat uses whatever version is specified in your web.xml file.

-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

Re: 404 error message

[Pid]

On 27/11/2009 04:18, ennidhi wrote:


Hi,
I am getting this 404 error on the second request to the same page. First
time its is working fine. hwta might be the reason?

Thanks


Hard to tell from the limited information you supplied.


p



-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

Re: 404 error message

[pieroxy]

Let's consider one simple question: My car doesn't work the second time.
What could be wrong with it?

Try to answer that, you'll se why we can't answer you.

2009/11/27 Pid p...@pidster.com

 On 27/11/2009 04:18, ennidhi wrote:


 Hi,
I am getting this 404 error on the second request to the same page.
 First
 time its is working fine. hwta might be the reason?

 Thanks


 Hard to tell from the limited information you supplied.



 p



 -
 To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
 For additional commands, e-mail: users-h...@tomcat.apache.org




-- 
-- pieroxy

RE: 404 Error troubleshooting

[Mike Baranski]

Thanks for the help, all, I got it going.  There was also an error in the
Apache xmlrpc documentation that was giving me fits, too.

-Original Message-
From: Kris Schneider [mailto:kschnei...@gmail.com]
Sent: Friday, September 11, 2009 1:09 PM
To: Tomcat Users List
Subject: Re: 404 Error troubleshooting

On Fri, Sep 11, 2009 at 1:06 PM, Kris Schneider kschnei...@gmail.com
wrote:
 On Fri, Sep 11, 2009 at 12:59 PM, Mike Baranski
 list-subscripti...@secmgmt.com wrote:
 Yes, restarted Tomcat (I also opened the war and opened the web.xml
inside
 of it to make sure it was what I thought it was).

 No deploy errors, either.

 make sure you include the app's context (Path value in manager) in
 the request...

 --
 Kris Schneider

whoops, didn't notice that Charles had addressed this a couple minutes
earlier...

--
Kris Schneider

-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org


-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

RE: 404 Error troubleshooting

[Martin Gainty]

couold you detail what the mistake is..also which page(s) contain the misconfig
?
Martin Gainty 
__ 
Verzicht und Vertraulichkeitanmerkung/Note de déni et de confidentialité
 
Diese Nachricht ist vertraulich. Sollten Sie nicht der vorgesehene Empfaenger 
sein, so bitten wir hoeflich um eine Mitteilung. Jede unbefugte Weiterleitung 
oder Fertigung einer Kopie ist unzulaessig. Diese Nachricht dient lediglich dem 
Austausch von Informationen und entfaltet keine rechtliche Bindungswirkung. 
Aufgrund der leichten Manipulierbarkeit von E-Mails koennen wir keine Haftung 
fuer den Inhalt uebernehmen.
Ce message est confidentiel et peut être privilégié. Si vous n'êtes pas le 
destinataire prévu, nous te demandons avec bonté que pour satisfaire informez 
l'expéditeur. N'importe quelle diffusion non autorisée ou la copie de ceci est 
interdite. Ce message sert à l'information seulement et n'aura pas n'importe 
quel effet légalement obligatoire. Étant donné que les email peuvent facilement 
être sujets à la manipulation, nous ne pouvons accepter aucune responsabilité 
pour le contenu fourni.




 From: list-subscripti...@secmgmt.com
 To: users@tomcat.apache.org
 Subject: RE: 404 Error troubleshooting
 Date: Mon, 14 Sep 2009 13:09:52 -0400
 
 Thanks for the help, all, I got it going.  There was also an error in the
 Apache xmlrpc documentation that was giving me fits, too.
 
 -Original Message-
 From: Kris Schneider [mailto:kschnei...@gmail.com]
 Sent: Friday, September 11, 2009 1:09 PM
 To: Tomcat Users List
 Subject: Re: 404 Error troubleshooting
 
 On Fri, Sep 11, 2009 at 1:06 PM, Kris Schneider kschnei...@gmail.com
 wrote:
  On Fri, Sep 11, 2009 at 12:59 PM, Mike Baranski
  list-subscripti...@secmgmt.com wrote:
  Yes, restarted Tomcat (I also opened the war and opened the web.xml
 inside
  of it to make sure it was what I thought it was).
 
  No deploy errors, either.
 
  make sure you include the app's context (Path value in manager) in
  the request...
 
  --
  Kris Schneider
 
 whoops, didn't notice that Charles had addressed this a couple minutes
 earlier...
 
 --
 Kris Schneider
 
 -
 To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
 For additional commands, e-mail: users-h...@tomcat.apache.org
 
 
 -
 To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
 For additional commands, e-mail: users-h...@tomcat.apache.org
 

_
Bing brings you health info from trusted sources.
http://www.bing.com/search?q=pet+allergyform=MHEINApubl=WLHMTAGcrea=TXT_MHEINA_Health_Health_PetAllergy_1x1

RE: 404 Error troubleshooting

[Martin Gainty]

you can see the posted request and response as well as the entire DOM tree with 
firebug plugin for firefox

http://getfirebug.com

hth
Martin Gainty 
__ 
Verzicht und Vertraulichkeitanmerkung/Note de déni et de confidentialité
 
Diese Nachricht ist vertraulich. Sollten Sie nicht der vorgesehene Empfaenger 
sein, so bitten wir hoeflich um eine Mitteilung. Jede unbefugte Weiterleitung 
oder Fertigung einer Kopie ist unzulaessig. Diese Nachricht dient lediglich dem 
Austausch von Informationen und entfaltet keine rechtliche Bindungswirkung. 
Aufgrund der leichten Manipulierbarkeit von E-Mails koennen wir keine Haftung 
fuer den Inhalt uebernehmen.
Ce message est confidentiel et peut être privilégié. Si vous n'êtes pas le 
destinataire prévu, nous te demandons avec bonté que pour satisfaire informez 
l'expéditeur. N'importe quelle diffusion non autorisée ou la copie de ceci est 
interdite. Ce message sert à l'information seulement et n'aura pas n'importe 
quel effet légalement obligatoire. Étant donné que les email peuvent facilement 
être sujets à la manipulation, nous ne pouvons accepter aucune responsabilité 
pour le contenu fourni.




 From: list-subscripti...@secmgmt.com
 To: users@tomcat.apache.org
 Subject: 404 Error troubleshooting
 Date: Fri, 11 Sep 2009 11:09:04 -0400
 
 I have a webapp, which shows up in the manager, but gives a 404 error every
 time I try to access it.
 
 Can someone let me know how to turn on debugging and see what exactly is
 going on?  It's an XMLRPC app (not that it makes a difference), and I have
 my web.xml servlet filter setup properly (according to the documentation).
 
 Thanks,
 Mike.
 
 
 
 
 -
 To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
 For additional commands, e-mail: users-h...@tomcat.apache.org
 

_
With Windows Live, you can organize, edit, and share your photos.
http://www.windowslive.com/Desktop/PhotoGallery

RE: 404 Error troubleshooting

[Caldarale, Charles R]

 From: Mike Baranski [mailto:list-subscripti...@secmgmt.com]
 Subject: 404 Error troubleshooting
 
 I have a webapp, which shows up in the manager, but gives a 404 error
 every time I try to access it.

When posting questions, provide some real information:

1) Tomcat version?

2) Any front end on Tomcat, or is it running standalone?

3) JRE/JDK version?

4) Platform you're running on?

5) The URL you're using?

6) Contents of WEB-INF/web.xml?

7) Contents of any Context element you have for the webapp?

8) Any errors recorded in the Tomcat logs?

 Can someone let me know how to turn on debugging and see what 
 exactly is going on?

The default Tomcat configuration logs all errors.  Modify 
conf/logging.properties if you want more detail.  However, start by enabling 
the AccessLogValve in conf/server.xml to see what requests Tomcat is actually 
getting.

 - Chuck


THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY 
MATERIAL and is thus for use only by the intended recipient. If you received 
this in error, please contact the sender and delete the e-mail and its 
attachments from all computers.


-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

RE: 404 Error troubleshooting

[Mike Baranski]

-Original Message-
From: Caldarale, Charles R [mailto:chuck.caldar...@unisys.com]
Sent: Friday, September 11, 2009 11:49 AM
To: Tomcat Users List
Subject: RE: 404 Error troubleshooting

 From: Mike Baranski [mailto:list-subscripti...@secmgmt.com]
 Subject: 404 Error troubleshooting

 I have a webapp, which shows up in the manager, but gives a 404 error
 every time I try to access it.

When posting questions, provide some real information:

1) Tomcat version?

2) Any front end on Tomcat, or is it running standalone?

3) JRE/JDK version?

4) Platform you're running on?

5) The URL you're using?

6) Contents of WEB-INF/web.xml?

7) Contents of any Context element you have for the webapp?

8) Any errors recorded in the Tomcat logs?

 Can someone let me know how to turn on debugging and see what
 exactly is going on?

The default Tomcat configuration logs all errors.  Modify
conf/logging.properties if you want more detail.  However, start by
enabling the AccessLogValve in conf/server.xml to see what requests
Tomcat is actually getting.

 - Chuck


Tomcat 5.5
Linux (FC 7)
JDK 1.6
Standalone

Web.xml:
?xml version=1.0 encoding=ISO-8859-1?
!DOCTYPE web-app PUBLIC -//Sun Microsystems, Inc.//DTD Web Application
2.3//EN http://java.sun.com/dtd/web-app_2_3.dtd;
web-app

display-nameSecurity Managment Consulting/display-name

   servlet
servlet-nameXmlRpcServlet/servlet-name
 
servlet-classorg.apache.xmlrpc.webserver.XmlRpcServlet/servlet-class
/servlet

servlet-mapping
servlet-nameXmlRpcServlet/servlet-name
url-pattern/xmlrpc-status/url-pattern
/servlet-mapping

/web-app

Access Log:
127.0.0.1 - - [11/Sep/2009:12:41:25 -0400] POST /xmlrpc-status/ HTTP/1.0
404 997


-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

RE: 404 Error troubleshooting

[Caldarale, Charles R]

 From: Mike Baranski [mailto:list-subscripti...@secmgmt.com]
 Subject: RE: 404 Error troubleshooting
 
 url-pattern/xmlrpc-status/url-pattern
 
 Access Log:
 127.0.0.1 - - [11/Sep/2009:12:41:25 -0400] POST /xmlrpc-status/ HTTP/1.0

Your url-pattern doesn't match the submitted URL; change the pattern value to 
/xmlrpc-status/* (without the quotes).

 - Chuck


THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY 
MATERIAL and is thus for use only by the intended recipient. If you received 
this in error, please contact the sender and delete the e-mail and its 
attachments from all computers.


-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

RE: 404 Error troubleshooting

[Mike Baranski]

127.0.0.1 - - [11/Sep/2009:12:50:19 -0400] POST /xmlrpc-status/ HTTP/1.0
404 997

?xml version=1.0 encoding=ISO-8859-1?
!DOCTYPE web-app PUBLIC -//Sun Microsystems, Inc.//DTD Web Application
2.3//EN http://java.sun.com/dtd/web-app_2_3.dtd;
web-app

display-nameSecurity Managment Consulting/display-name

   servlet
servlet-nameXmlRpcServlet/servlet-name
 
servlet-classorg.apache.xmlrpc.webserver.XmlRpcServlet/servlet-class
/servlet

servlet-mapping
servlet-nameXmlRpcServlet/servlet-name
url-pattern/xmlrpc-status/*/url-pattern
/servlet-mapping

/web-app

-Original Message-
From: Caldarale, Charles R [mailto:chuck.caldar...@unisys.com]
Sent: Friday, September 11, 2009 12:47 PM
To: Tomcat Users List
Subject: RE: 404 Error troubleshooting

 From: Mike Baranski [mailto:list-subscripti...@secmgmt.com]
 Subject: RE: 404 Error troubleshooting

 url-pattern/xmlrpc-status/url-pattern

 Access Log:
 127.0.0.1 - - [11/Sep/2009:12:41:25 -0400] POST /xmlrpc-status/
HTTP/1.0

Your url-pattern doesn't match the submitted URL; change the pattern
value to /xmlrpc-status/* (without the quotes).

 - Chuck


THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY
MATERIAL and is thus for use only by the intended recipient. If you
received this in error, please contact the sender and delete the e-mail
and its attachments from all computers.


-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org


-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

RE: 404 Error troubleshooting

[Caldarale, Charles R]

 From: Mike Baranski [mailto:list-subscripti...@secmgmt.com]
 Subject: RE: 404 Error troubleshooting
 
 127.0.0.1 - - [11/Sep/2009:12:50:19 -0400] POST /xmlrpc-status/
 HTTP/1.0
 404 997

Did you reload the webapp or restart Tomcat after making the change?

Also, check the logs for deployment errors.

 - Chuck


THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY 
MATERIAL and is thus for use only by the intended recipient. If you received 
this in error, please contact the sender and delete the e-mail and its 
attachments from all computers.


-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

RE: 404 Error troubleshooting

[Mike Baranski]

Yes, restarted Tomcat (I also opened the war and opened the web.xml inside
of it to make sure it was what I thought it was).

No deploy errors, either.

-Original Message-
From: Caldarale, Charles R [mailto:chuck.caldar...@unisys.com]
Sent: Friday, September 11, 2009 12:54 PM
To: Tomcat Users List
Subject: RE: 404 Error troubleshooting

 From: Mike Baranski [mailto:list-subscripti...@secmgmt.com]
 Subject: RE: 404 Error troubleshooting

 127.0.0.1 - - [11/Sep/2009:12:50:19 -0400] POST /xmlrpc-status/
 HTTP/1.0
 404 997

Did you reload the webapp or restart Tomcat after making the change?

Also, check the logs for deployment errors.

 - Chuck


THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY
MATERIAL and is thus for use only by the intended recipient. If you
received this in error, please contact the sender and delete the e-mail
and its attachments from all computers.


-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org


-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

RE: 404 Error troubleshooting

[Caldarale, Charles R]

 From: Mike Baranski [mailto:list-subscripti...@secmgmt.com]
 Subject: RE: 404 Error troubleshooting
 
 Yes, restarted Tomcat (I also opened the war and opened the web.xml
 inside of it to make sure it was what I thought it was).

What is the name of the .war file?

Where is it located?

The URL you're using requires that the webapp be deployed as ROOT (the 
default).  If you have not deployed it as ROOT, you'll need to include the 
webapp name in the URL.

 - Chuck


THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY 
MATERIAL and is thus for use only by the intended recipient. If you received 
this in error, please contact the sender and delete the e-mail and its 
attachments from all computers.


-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

Re: 404 Error troubleshooting

[Kris Schneider]

On Fri, Sep 11, 2009 at 12:59 PM, Mike Baranski
list-subscripti...@secmgmt.com wrote:
 Yes, restarted Tomcat (I also opened the war and opened the web.xml inside
 of it to make sure it was what I thought it was).

 No deploy errors, either.

make sure you include the app's context (Path value in manager) in
the request...

-- 
Kris Schneider

-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

Re: 404 Error troubleshooting

[Kris Schneider]

On Fri, Sep 11, 2009 at 1:06 PM, Kris Schneider kschnei...@gmail.com wrote:
 On Fri, Sep 11, 2009 at 12:59 PM, Mike Baranski
 list-subscripti...@secmgmt.com wrote:
 Yes, restarted Tomcat (I also opened the war and opened the web.xml inside
 of it to make sure it was what I thought it was).

 No deploy errors, either.

 make sure you include the app's context (Path value in manager) in
 the request...

 --
 Kris Schneider

whoops, didn't notice that Charles had addressed this a couple minutes
earlier...

-- 
Kris Schneider

-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

RE: 404 after adding web.xml

[Caldarale, Charles R]

 From: Shoan Motwani [mailto:[EMAIL PROTECTED]
 Subject: 404 after adding web.xml

 But after adding webapp/WEB-INF/web.xml containing the
 following, I don't get anything other than a 404.

Look in the Tomcat logs for error messages about deployment of your webapp.

 servlet-mapping
 servlet-nameCh3 Beer/servlet-name
 url-pattern/SelectBeer.do/url-pattern
 servlet-mapping

The last line above should be /servlet-mapping.

 - Chuck


THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY 
MATERIAL and is thus for use only by the intended recipient. If you received 
this in error, please contact the sender and delete the e-mail and its 
attachments from all computers.

-
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: 404 after adding web.xml

[Shoan Motwani]

On Thu, Nov 13, 2008 at 9:14 AM, Caldarale, Charles R
[EMAIL PROTECTED] wrote:
 From: Shoan Motwani [mailto:[EMAIL PROTECTED]
 Subject: 404 after adding web.xml

 But after adding webapp/WEB-INF/web.xml containing the
 following, I don't get anything other than a 404.

 Look in the Tomcat logs for error messages about deployment of your webapp.

 servlet-mapping
 servlet-nameCh3 Beer/servlet-name
 url-pattern/SelectBeer.do/url-pattern
 servlet-mapping

 The last line above should be /servlet-mapping.

That did it. Thanks.

Peace,
Shoan.

-
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: 404 returned trying to find Perl script

[Mark Thomas]

[EMAIL PROTECTED] wrote:

I have a form that sends its data to a Perl script under Tomcat 6.0.16.
I get an error message The requested resource
(/perlTest/WEB-INF/cgi-bin/form.pl) is not available. The form.pl file
is, in fact, in that folder. I'm running Windows XP. Permissions have
been set properly (using Cygwin chmod) to 0755.

I just upgraded to Tomcat 6.0.16. I used to have my perl scripts in the
cgi-bin folder under the root context. I see now the cgi-bin folder has
been moved to 'WEB-INF'.

This is reflected in %CATALINA_HOME%/conf/web.xml in an init-param
element as follows:

init-param
  param-namecgiPathPrefix/param-name
  param-valueWEB-INF/cgi/param-value
/init-param

in the cgi servlet definition.


Your script should therefore be in /perlTest/WEB-INF/cgi/form.pl


The servlet-mapping element appears as follows:

servlet-mapping
servlet-namecgi/servlet-name
url-pattern/cgi-bin/*/url-pattern
/servlet-mapping


And you should request it using:
cgi-bin/form.pl


Mark

-
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: 404 returned trying to find Perl script

[Doug.Thomas]

That worked. Thanks!

-Original Message-
From: Mark Thomas [mailto:[EMAIL PROTECTED] 
Sent: Friday, March 07, 2008 1:33 PM
To: Tomcat Users List
Subject: Re: 404 returned trying to find Perl script

[EMAIL PROTECTED] wrote:
 I have a form that sends its data to a Perl script under Tomcat
6.0.16.
 I get an error message The requested resource
 (/perlTest/WEB-INF/cgi-bin/form.pl) is not available. The form.pl
file
 is, in fact, in that folder. I'm running Windows XP. Permissions have
 been set properly (using Cygwin chmod) to 0755.
 
 I just upgraded to Tomcat 6.0.16. I used to have my perl scripts in
the
 cgi-bin folder under the root context. I see now the cgi-bin folder
has
 been moved to 'WEB-INF'.
 
 This is reflected in %CATALINA_HOME%/conf/web.xml in an init-param
 element as follows:
 
 init-param
   param-namecgiPathPrefix/param-name
   param-valueWEB-INF/cgi/param-value
 /init-param
 
 in the cgi servlet definition.

Your script should therefore be in /perlTest/WEB-INF/cgi/form.pl
 
 The servlet-mapping element appears as follows:
 
 servlet-mapping
 servlet-namecgi/servlet-name
 url-pattern/cgi-bin/*/url-pattern
 /servlet-mapping

And you should request it using:
cgi-bin/form.pl


Mark

-
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


-
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: 404 message when trying to test a servlet

[Dean]

Thanks for the info.  However, I am new to tomcat and servlets and as such
am still somewhat unclear as to the resolution to this problem.  Can you
clarify.  What exactly is servlet - mapping?

Thanks,

D

-Original Message-
From: news [mailto:[EMAIL PROTECTED] On Behalf Of Bill Barker
Sent: Saturday, May 26, 2007 8:06 PM
To: users@tomcat.apache.org
Subject: Re: 404 message when trying to test a servlet


Dean [EMAIL PROTECTED] wrote in message 
news:[EMAIL PROTECTED]
 Greetings,



 I suspect the class file may be in the wrong directory.  I get the message
 /basic-servlet/servlet/CurrencyConverter  , which is confusing in that the
 class file is in the following directory C:\Program Files\Apache Software
 Foundation\Tomcat 4.1\webapps\basic-servlet\WEB-INF\classes.  The html 
 page
 is being found ok but when I do a submit and it tries to bring up the
 servlet I get the above.


The invoker servlet has been disabled in the default config for ages 
(because it is evil :).  You can enable it at your own risk in conf/web.xml,

but that isn't recommended.  Use an explicit servlet-mapping instead.

Having classes in the default package will prevent you from upgrading later 
on.  You really should put your class in a package.



 I really appreciate any help you can give.



 P.s. when I start tomcat I only get the following messages

 Starting service Tomcat-Standalone

 Apache Tomcat/4.1.36-LE-jdk14



 I am able to access http://localhost:8080/index.jsp



 Sincerely,



 D



 




-
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


-
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: 404 message when trying to test a servlet

[Bill Barker]

Dean [EMAIL PROTECTED] wrote in message 
news:[EMAIL PROTECTED]
 Greetings,



 I suspect the class file may be in the wrong directory.  I get the message
 /basic-servlet/servlet/CurrencyConverter  , which is confusing in that the
 class file is in the following directory C:\Program Files\Apache Software
 Foundation\Tomcat 4.1\webapps\basic-servlet\WEB-INF\classes.  The html 
 page
 is being found ok but when I do a submit and it tries to bring up the
 servlet I get the above.


The invoker servlet has been disabled in the default config for ages 
(because it is evil :).  You can enable it at your own risk in conf/web.xml, 
but that isn't recommended.  Use an explicit servlet-mapping instead.

Having classes in the default package will prevent you from upgrading later 
on.  You really should put your class in a package.



 I really appreciate any help you can give.



 P.s. when I start tomcat I only get the following messages

 Starting service Tomcat-Standalone

 Apache Tomcat/4.1.36-LE-jdk14



 I am able to access http://localhost:8080/index.jsp



 Sincerely,



 D



 




-
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: 404 and originally requested URL

[Simon Stone]

Have you tried using the request.getHeader(Referer) to get the page that
sent the previous request


Propes, Barry L [GCG-NAOT] wrote:
 
 did you check your logs? Did they tell you anything?
 
 -Original Message-
 From: Guilhem SEMPERE [mailto:[EMAIL PROTECTED]
 Sent: Wednesday, April 18, 2007 10:00 AM
 To: users@tomcat.apache.org
 Subject: 404 and originally requested URL
 
 
 Hi
 
 I am using Tomcat 5.5, having set it up so that any 404 error redirects 
 to a 404.jsp I have written for custom handling.
 
 Now I need access to the originally requested URL (the one which 
 couldn't be found).  I couldn't find a way to do this.  All info I can 
 get is that the requested URL is now 404.jsp, which I am not interested
 in.
 
 Any help much appreciated.  Thanks in advance,
 
 Guilhem
 
 
 -
 To start a new topic, e-mail: users@tomcat.apache.org
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]
 
 
 -
 To start a new topic, e-mail: users@tomcat.apache.org
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]
 
 
 

-- 
View this message in context: 
http://www.nabble.com/RE%3A-404-and-originally-requested-URL-tf3601601.html#a10077336
Sent from the Tomcat - User mailing list archive at Nabble.com.


-
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: 404 and originally requested URL

[Propes, Barry L]

did you check your logs? Did they tell you anything?

-Original Message-
From: Guilhem SEMPERE [mailto:[EMAIL PROTECTED]
Sent: Wednesday, April 18, 2007 10:00 AM
To: users@tomcat.apache.org
Subject: 404 and originally requested URL


Hi

I am using Tomcat 5.5, having set it up so that any 404 error redirects 
to a 404.jsp I have written for custom handling.

Now I need access to the originally requested URL (the one which 
couldn't be found).  I couldn't find a way to do this.  All info I can 
get is that the requested URL is now 404.jsp, which I am not interested in.

Any help much appreciated.  Thanks in advance,

Guilhem


-
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


-
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: 404 and originally requested URL

[Hassan Schroeder]

On 4/18/07, Guilhem SEMPERE [EMAIL PROTECTED] wrote:


Now I need access to the originally requested URL (the one which
couldn't be found).  I couldn't find a way to do this.


The Servlet Spec is your friend -- SRV 8.4.2, specifically :-)

HTH,
--
Hassan Schroeder  [EMAIL PROTECTED]

-
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: 404 and originally requested URL

[David Brown]

What does the referrer request header give you ?

Propes, Barry L wrote:

did you check your logs? Did they tell you anything?

-Original Message-
From: Guilhem SEMPERE [mailto:[EMAIL PROTECTED]
Sent: Wednesday, April 18, 2007 10:00 AM
To: users@tomcat.apache.org
Subject: 404 and originally requested URL


Hi

I am using Tomcat 5.5, having set it up so that any 404 error redirects 
to a 404.jsp I have written for custom handling.


Now I need access to the originally requested URL (the one which 
couldn't be found).  I couldn't find a way to do this.  All info I can 
get is that the requested URL is now 404.jsp, which I am not interested in.


Any help much appreciated.  Thanks in advance,

Guilhem


-
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


-
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


  


-
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: 404 and originally requested URL

[Rashmi Rubdi]

On 4/18/07, Hassan Schroeder [EMAIL PROTECTED] wrote:

On 4/18/07, Guilhem SEMPERE [EMAIL PROTECTED] wrote:

 Now I need access to the originally requested URL (the one which
 couldn't be found).  I couldn't find a way to do this.

The Servlet Spec is your friend -- SRV 8.4.2, specifically :-)



No, none of the methods listed under SRV 8.4.2 show the referring URL
information, also
the Referer header is null.

Put these in 404.jsp

%=request.getRequestURI()%br/ Shows the URL of the 404 page and
not the page that sent it to the 404 page.

%=request.getContextPath()%br/
%=request.getServletPath()%br/
%=request.getPathInfo()%br/
%=request.getQueryString()%br/

The referer header is null
%=request.getHeader(referer)%

Hmm... there really doesn't seem to be a way to get the URL of the
page that caused the 404 error, inside the 404.jsp page --- probably
possible with a Filter.

Also AccessLogValve captures all URLs.


-Rashmi

-
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: 404 and originally requested URL

[Hassan Schroeder]

On 4/18/07, Rashmi Rubdi [EMAIL PROTECTED] wrote:


 The Servlet Spec is your friend -- SRV 8.4.2, specifically :-)



No, none of the methods listed under SRV 8.4.2 show the referring URL
information


You misunderstand -- there is no reference to the referrer in the
original posting, nor is it relevant.

The page being requested that was *not found* and hence caused
the /forward/ to the custom 404 page /is/ identified by the request
attributes mentioned in SRV 8.4.2 -- javax.servlet.forward.request_uri
and so on.

--
Hassan Schroeder  [EMAIL PROTECTED]

-
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: 404 and originally requested URL

[Rashmi Rubdi]

Well, the wording in the servlet spec The values of these attributes
must be equal to the return values of the... don't reflect what I
see:

I was thinking that request.getRequestURI returns the same results as
request.getAttribute(javax.servlet.forward.request_uri)

request.getRequestURI gives the URL of the 404 page but,

request.getAttribute(javax.servlet.forward.request_uri) gives the
URL of the invalid page that forwarded to the 404 page.

Anyway, as you mentioned the OP should be able to get the forward URL
from javax.servlet.forward.request_uri

-Rashmi

On 4/18/07, Hassan Schroeder [EMAIL PROTECTED] wrote:

On 4/18/07, Rashmi Rubdi [EMAIL PROTECTED] wrote:

  The Servlet Spec is your friend -- SRV 8.4.2, specifically :-)

 No, none of the methods listed under SRV 8.4.2 show the referring URL
 information

You misunderstand -- there is no reference to the referrer in the
original posting, nor is it relevant.

The page being requested that was *not found* and hence caused
the /forward/ to the custom 404 page /is/ identified by the request
attributes mentioned in SRV 8.4.2 -- javax.servlet.forward.request_uri
and so on.

--
Hassan Schroeder  [EMAIL PROTECTED]

-
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]




-
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: 404 and originally requested URL

[Hassan Schroeder]

On 4/18/07, Rashmi Rubdi [EMAIL PROTECTED] wrote:

Well, the wording in the servlet spec The values of these attributes
must be equal to the return values of the... don't reflect what I
see:



I was thinking that request.getRequestURI returns the same results as
request.getAttribute(javax.servlet.forward.request_uri)


Read the entire sentence:

The values of these attributes must be equal to the return values
of the HttpServletRequest methods getRequestURI, getContextPath,
getServletPath, getPathInfo, getQueryString respectively, invoked on
the request object passed to *the first servlet object in the call chain*
that received the request from the client.

The 404 page is *not* the first servlet object so obviously those
values are not the same.

HTH,
--
Hassan Schroeder  [EMAIL PROTECTED]

-
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: 404 and originally requested URL

[Rashmi Rubdi]

Ok, now I get it.

Sorry, it was my mistake for not reading the sentence carefully.

-Rashmi

On 4/18/07, Hassan Schroeder [EMAIL PROTECTED] wrote:

On 4/18/07, Rashmi Rubdi [EMAIL PROTECTED] wrote:
 Well, the wording in the servlet spec The values of these attributes
 must be equal to the return values of the... don't reflect what I
 see:

 I was thinking that request.getRequestURI returns the same results as
 request.getAttribute(javax.servlet.forward.request_uri)

Read the entire sentence:

 The values of these attributes must be equal to the return values
 of the HttpServletRequest methods getRequestURI, getContextPath,
 getServletPath, getPathInfo, getQueryString respectively, invoked on
 the request object passed to *the first servlet object in the call chain*
 that received the request from the client.

The 404 page is *not* the first servlet object so obviously those
values are not the same.

HTH,
--
Hassan Schroeder  [EMAIL PROTECTED]

-
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]




-
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: 404 error when a newly created file is requested

[EDMOND KEMOKAI]

I ran into a similar problem in trying to serve static content with tomcat,
tomcat had trouble retrieving dynamically created content unless it was
already in the webapp at start, at least that was my experience. Since
you're trying to create a jsp, why don't you create one jsp and pass it your
preview data, then return that to the user. Even if tomcat could serve newly
created jsp, i don't see why you'll create a .jsp page every time the user
hits a preview button, one jsp should do. Also you may want to look into
autoDeploy etc.. config properties, there are options you can enable to make
tomcat notice changes in servlet code (including jsp), I am not sure they
apply to newly added JSPs.

On 12/15/06, Carl [EMAIL PROTECTED] wrote:


 Environment:  Tomcat 5.5.17, Windows XP

Background:  I have a jsp page that contains a javascript rich text editor
that I use to create snippets of HTML code that are stored in a database and
later displayed on other pages.  Since the snippets can contain some custom
tags, I have a 'Preview' button that reads the snippet directly from the
editor, reads a 'preview' jsp file from the file system, places the snippet
in the correct place in the file, writes the 'preview' file with the snippet
to a temporary file and opens a new window (using javascript) which requests
the temporary page from Tomcat.

Problem:  I can see the newly created temporary file in the file system.
I can open it with an editor and it is all good.  But, Tomcat returns a 404
error for approximately one minute and then will serve the page upon hitting
only the refresh.

Analysis:  I suspect the system is holding onto the newly written file
until it hits some timeout but I have tried everything I can think of to
make certain the file has been 'released'.  The relevent parts of the copy
process:

try {

 File tempFile = File.createTempFile(preview, .jsp, new
File(C:/projects/EtrakWebApp/web/jsp/tempfiles));

// read the preview jsp
 FileWriter fw = new FileWriter(tempFile);

File infile = new File(destinationDir+preview.jsp);

if( infile.exists() )
{
FileReader fr = new FileReader(infile);

BufferedReader in = new BufferedReader(fr);

while(true)
{
String line = in.readLine();

if( line==null )
break;

System.out.println(line +line );

// insert the text
if( line.contains(insert_preview_text) )
{
fw.write(previewText+\n);
}
else {
fw.write(line+\n);
}
}

fr.close();
in.close();
}

fw.flush();
fw.close();
   fw = null;
}
catch (FileNotFoundException fnf)
{
fnf.printStackTrace();
}
catch (Exception ex)
{
ex.printStackTrace();
}

return returnFileName;
Anyone have any ideas?

TIA,

Carl Kabbe



No virus found in this outgoing message.
Checked by AVG Free Edition.
Version: 7.1.409 / Virus Database: 268.15.19/587 - Release Date:
12/14/2006




-
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]





--
talk trash and carry a small stick.
PAUL KRUGMAN (NYT)

Re: 404 Error when trying to connect Tomcat Manager

[Foo Shyn]

Hi,

i was using web at port 8080. But anyway, i found out the root cause. Some 
guy at the live server side there deleted the manager folder under the 
server folder.
After replacing the folder and the xml file in it. everything runs smooth 
again.


Thanx for the ideas and replies!

Regards,
FooShyn
- Original Message - 
From: Propes, Barry L [EMAIL PROTECTED]

To: Tomcat Users List users@tomcat.apache.org
Sent: Friday, July 21, 2006 6:20 AM
Subject: RE: 404 Error when trying to connect Tomcat Manager


through the web at port 8080 you're accessing this? Or just in your 
directory on a desktop or server?


-Original Message-
From: Foo Shyn [mailto:[EMAIL PROTECTED]
Sent: Thursday, July 20, 2006 2:06 AM
To: Tomcat Users List
Subject: 404 Error when trying to connect Tomcat Manager


Hi guys,

Was facing a problem when trying to connect to Tomcat Manager. I manage to 
access to the index.jsp page but when i click on the Manager link it gives 
me a 404 error. I'd check the manager web.xml and application and they look 
fine to me. Is there any cause that will make this happen??

I'm using Tomcat 4.1

Thanx.
Regards,
FooShyn

-
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]




-
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: 404 Error when trying to connect Tomcat Manager

[Shirode, Sangita \(Sangita\)]

You need to add the following line in the
tomcathome/conf/tomcat-users.xml file

 user username=admin password= roles=manager/ 

And login with admin and blank password to tomcat manager


sangita

-Original Message-
From: Foo Shyn [mailto:[EMAIL PROTECTED] 
Sent: Thursday, July 20, 2006 12:36 PM
To: Tomcat Users List
Subject: 404 Error when trying to connect Tomcat Manager

Hi guys,

Was facing a problem when trying to connect to Tomcat Manager. I manage
to access to the index.jsp page but when i click on the Manager link it
gives me a 404 error. I'd check the manager web.xml and application and
they look fine to me. Is there any cause that will make this happen??
I'm using Tomcat 4.1

Thanx.
Regards,
FooShyn


-
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: 404 persists for one servlet while another works fine

[Martin Gainty]

Good Afternoon Siomara-

More importantly what does the servlet's servlet-mapping entry look like in 
your web.xml?

Martin --
*
This email message and any files transmitted with it contain confidential
information intended only for the person(s) to whom this email message is
addressed.  If you have received this email message in error, please notify
the sender immediately by telephone or email and destroy the original
message without making a copy.  Thank you.



- Original Message - 
From: [EMAIL PROTECTED]
To: users@tomcat.apache.org
Sent: Friday, July 07, 2006 5:01 PM
Subject: 404 persists for one servlet while another works fine


 Hi all again,
 
 I am facing a weird problem. I got 2 servlets. One of them works pretty fine
 while the other one is not found. Both are in the same place. I think the
 problem has to do with path. 
 
 The first servlet I call directly from index.htm, it preforms a search in a
 database table and displays results in a jsp form. This works fine. I see
 the rows of the table.
 
 This jsp page has a link to a registerWhatever.htm form, and this
 registerWhatever.htm form has a button that calls the other servlet. This is
 where I get the error. The 404 message.
 
 type Status report
 message /Sisc/servlet/RegistraMarcaPropriedade
 description The requested resource (/Sisc/servlet/RegistraMarcaPropriedade)
 is not available
 The address I see is perfect just like the other one:
 http://localhost:8899/Sisc/servlet/RegistraMarcaPropriedade
 This is driving me crazy. It was working fine before and the only thing I
 did was:
 turned a htm form to a jsp form to display the results of the search. Before
 I had a static htm form with a link to registerWhatever.htm form (with
 fields and a button to include data into the database). 
 How can I always start my redirection from the application root folder?
 Any help is welcome
 
 Siomara
 
 
 -
 To start a new topic, e-mail: users@tomcat.apache.org
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]
 

Re: 404

[Martin Gainty]

I guess if your a PHP guy I think you'll like it..Sorry sir the domain 
www.mycompany.com is taken!

Check the port number assigned to Tomcat i.e.
connector port=8080 ...
and use the port number to access your site
http://localhost:8080

HTH
Martin--

This email message and any files transmitted with it contain confidential
information intended only for the person(s) to whom this email message is
addressed.  If you have received this email message in error, please notify
the sender immediately by telephone or email and destroy the original
message without making a copy.  Thank you.

- Original Message - 
From: Ole Ersoy [EMAIL PROTECTED]

To: Tomcat Users List users@tomcat.apache.org
Sent: Sunday, June 04, 2006 4:14 PM
Subject: 404



Hey Everybody,

I'm trying to access setup access for
www.mycompany.com,
however I get a 404.

If I try accessing tomcat on my internal network like
this (This is from a machine different than from what
tomcat is running on):

http://192.168.1.4:8080/manager/html

I get access.

However, when trying from a machine outside my
internal network like this:

http://www.mycompany.com:8080/manager/html

I get a 404.

I have setup NAT on my router to forward to port 8080
and I tested my ISP to make sure it's not blocking
port 8080.  So port 8080 is open on the router, and I
also have it open on the firewall for the machine
running tomcat.  There is nothing else inbetween.

I also tried the ip address directly from outside the
internal network like this:

http://67.234.33.22:8080/manager/html and I still get
a 404.

Any ideas on how to trouble shoot this?  Tomcat is
running on Linux Fedora 3.

Thanks a gazillion!

Cheers,
- Ole


__
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam
protection around
http://mail.yahoo.com

__
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around
http://mail.yahoo.com

-
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]




-
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: 404

[Mark Thomas]

When starting a new thread (ie sending a message to the list about a
new topic) please do not reply to an existing message and change the
subject line. To many of the list archiving services and mail clients
used by list subscribers this  makes your new message appear as part
of the old thread. This makes it harder for other users to find
relevant information when searching the lists.

This is known as thread hijacking and is behaviour that is frowned
upon on this list. Frequent offenders will be removed from the list.
It should also be noted that many list subscribers automatically
ignore any messages that hijack another thread.

The correct procedure is to create a new message with a new subject.
This will start a new thread.

Mark
tomcat-user-owner

-
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: 404

[Ole Ersoy]

Whoops - Sorry - I should have thought about that -
Thanks for the heads up.

Cheers,
- Ole


--- Mark Thomas [EMAIL PROTECTED] wrote:

 When starting a new thread (ie sending a message to
 the list about a
 new topic) please do not reply to an existing
 message and change the
 subject line. To many of the list archiving services
 and mail clients
 used by list subscribers this  makes your new
 message appear as part
 of the old thread. This makes it harder for other
 users to find
 relevant information when searching the lists.
 
 This is known as thread hijacking and is behaviour
 that is frowned
 upon on this list. Frequent offenders will be
 removed from the list.
 It should also be noted that many list subscribers
 automatically
 ignore any messages that hijack another thread.
 
 The correct procedure is to create a new message
 with a new subject.
 This will start a new thread.
 
 Mark
 tomcat-user-owner
 

-
 To start a new topic, e-mail:
 users@tomcat.apache.org
 To unsubscribe, e-mail:
 [EMAIL PROTECTED]
 For additional commands, e-mail:
 [EMAIL PROTECTED]
 
 


__
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com 

-
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: 404

[Ole Ersoy]

Thanks Martin - I think I got it now - after updating
/etc/hosts with the domain name.  Yeah ... I was just
using www.mycompany.com as an example...would be
pretty cool to own that though!

Cheers,
- Ole

--- Martin Gainty [EMAIL PROTECTED] wrote:

 I guess if your a PHP guy I think you'll like
 it..Sorry sir the domain 
 www.mycompany.com is taken!
 Check the port number assigned to Tomcat i.e.
 connector port=8080 ...
 and use the port number to access your site
 http://localhost:8080
 
 HTH
 Martin--
 
 This email message and any files transmitted with it
 contain confidential
 information intended only for the person(s) to whom
 this email message is
 addressed.  If you have received this email message
 in error, please notify
 the sender immediately by telephone or email and
 destroy the original
 message without making a copy.  Thank you.
 
 - Original Message - 
 From: Ole Ersoy [EMAIL PROTECTED]
 To: Tomcat Users List users@tomcat.apache.org
 Sent: Sunday, June 04, 2006 4:14 PM
 Subject: 404
 
 
  Hey Everybody,
 
  I'm trying to access setup access for
  www.mycompany.com,
  however I get a 404.
 
  If I try accessing tomcat on my internal network
 like
  this (This is from a machine different than from
 what
  tomcat is running on):
 
  http://192.168.1.4:8080/manager/html
 
  I get access.
 
  However, when trying from a machine outside my
  internal network like this:
 
  http://www.mycompany.com:8080/manager/html
 
  I get a 404.
 
  I have setup NAT on my router to forward to port
 8080
  and I tested my ISP to make sure it's not blocking
  port 8080.  So port 8080 is open on the router,
 and I
  also have it open on the firewall for the machine
  running tomcat.  There is nothing else inbetween.
 
  I also tried the ip address directly from outside
 the
  internal network like this:
 
  http://67.234.33.22:8080/manager/html and I still
 get
  a 404.
 
  Any ideas on how to trouble shoot this?  Tomcat is
  running on Linux Fedora 3.
 
  Thanks a gazillion!
 
  Cheers,
  - Ole
 
 
  __
  Do You Yahoo!?
  Tired of spam?  Yahoo! Mail has the best spam
  protection around
  http://mail.yahoo.com
 
  __
  Do You Yahoo!?
  Tired of spam?  Yahoo! Mail has the best spam
 protection around
  http://mail.yahoo.com
 
 

-
  To start a new topic, e-mail:
 users@tomcat.apache.org
  To unsubscribe, e-mail:
 [EMAIL PROTECTED]
  For additional commands, e-mail:
 [EMAIL PROTECTED]
 
  
 

-
 To start a new topic, e-mail:
 users@tomcat.apache.org
 To unsubscribe, e-mail:
 [EMAIL PROTECTED]
 For additional commands, e-mail:
 [EMAIL PROTECTED]
 
 


__
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com 

-
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: 404

[Edoardo Panfili]

[EMAIL PROTECTED] ha scritto:

Why when I go to http://localhost/ I get a directory listing containing
those 2 elements:

[DIR] Parent Directory 15-Apr-2006 15:22 -
[DIR] apache2-default/ 15-Apr-2006 15:22 -

And when I go to http://localhost/index.jsp I get a file not found error
although THE FILE EXISTS !


Have you tried
http://localhost:8080/
?

or
http://localhost:8080/APPLICATION_NAME/index.jsp
?

Edoardo Panfili

--
[EMAIL PROTECTED]
AIM: edoardopn
Jabber: [EMAIL PROTECTED]
tel:075 9142766

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: 404

[Mark Thomas]

When starting a new thread (ie sending a message to the list about a
new topic) please do not reply to an existing message and change the
subject line. To many of the list archiving services and mail clients
used by list subscribers this  makes your new message appear as part
of the old thread. This makes it harder for other users to find
relevant information when searching the lists.

This is known as thread hijacking and is behaviour that is frowned
upon on this list. Frequent offenders will be removed from the list.
It should also be noted that many list subscribers automatically
ignore any messages that hijack another thread.

The correct procedure is to create a new message with a new subject.
This will start a new thread.

Mark
tomcat-user-owner


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: 404

[jonathan . pare]

Yes I've tried with the port number (in my case it's 80) and also with the
APPLICATION_NAME.

But the weird thing is that yesterday everything was going fine and now I
get that directory listing instead of the jsp page.

Here's what I get when I click on the apache2-default directory:
  ---
   If you can see this, it means that the installation of the Apache web
 server software on this system was successful. You may now add content to
   this directory and replace this page.

 Seeing this instead of the website you expected?

 This page is here because the site administrator has changed the
configuration of this web server. Please contact the person responsible for
  maintaining this server with questions. The Apache Software Foundation,
 which wrote the web server software this site administrator is using, has
 nothing to do with maintaining this site and cannot help resolve
   configuration issues.
  ---

Is there something that I could have changed in one of the config file
that's causing that ?
All I remember is changing:
-the owner of the /usr/local/tomcat/webapps/root/ from root to myself so
I could edit the files.
-I renamed the file web.xml to web_bak.xml but I put it back the way is
was.

Thanks for your help.



   
 Edoardo Panfili   
 [EMAIL PROTECTED] 
A 
   Tomcat Users List   
 2006-04-17 12:44  users@tomcat.apache.org   
cc 
   
 Veuillez répondre   Objet 
 à Re: 404 
   Tomcat Users   
   List   
 [EMAIL PROTECTED] 
 che.org  
   
   




[EMAIL PROTECTED] ha scritto:
 Why when I go to http://localhost/ I get a directory listing containing
 those 2 elements:

 [DIR] Parent Directory 15-Apr-2006 15:22 -
 [DIR] apache2-default/ 15-Apr-2006 15:22 -

 And when I go to http://localhost/index.jsp I get a file not found error
 although THE FILE EXISTS !

Have you tried
http://localhost:8080/
?

or
http://localhost:8080/APPLICATION_NAME/index.jsp
?

Edoardo Panfili

--
[EMAIL PROTECTED]
AIM: edoardopn
Jabber: [EMAIL PROTECTED]
tel:075 9142766

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]






-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: 404

[Marc Farrow]

So what do you have running on port 80?  Apache or Tomcat?

On 4/17/06, [EMAIL PROTECTED] [EMAIL PROTECTED]
wrote:


 Yes I've tried with the port number (in my case it's 80) and also with the
 APPLICATION_NAME.

 But the weird thing is that yesterday everything was going fine and now I
 get that directory listing instead of the jsp page.

 Here's what I get when I click on the apache2-default directory:
  ---
   If you can see this, it means that the installation of the Apache web
 server software on this system was successful. You may now add content to
   this directory and replace this page.

 Seeing this instead of the website you expected?

 This page is here because the site administrator has changed the
 configuration of this web server. Please contact the person responsible
 for
 maintaining this server with questions. The Apache Software Foundation,
 which wrote the web server software this site administrator is using, has
 nothing to do with maintaining this site and cannot help resolve
   configuration issues.
  ---

 Is there something that I could have changed in one of the config file
 that's causing that ?
 All I remember is changing:
 -the owner of the /usr/local/tomcat/webapps/root/ from root to myself so
 I could edit the files.
 -I renamed the file web.xml to web_bak.xml but I put it back the way is
 was.

 Thanks for your help.




 Edoardo Panfili
 [EMAIL PROTECTED]
A
   Tomcat Users List
 2006-04-17 12:44  users@tomcat.apache.org
cc

 Veuillez répondre   Objet
 à Re: 404
   Tomcat Users
   List
 [EMAIL PROTECTED]
 che.org






 [EMAIL PROTECTED] ha scritto:
  Why when I go to http://localhost/ I get a directory listing containing
  those 2 elements:
 
  [DIR] Parent Directory 15-Apr-2006 15:22 -
  [DIR] apache2-default/ 15-Apr-2006 15:22 -
 
  And when I go to http://localhost/index.jsp I get a file not found error
  although THE FILE EXISTS !

 Have you tried
 http://localhost:8080/
 ?

 or
 http://localhost:8080/APPLICATION_NAME/index.jsp
 ?

 Edoardo Panfili

 --
 [EMAIL PROTECTED]
 AIM: edoardopn
 Jabber: [EMAIL PROTECTED]
 tel:075 9142766

 -
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]






 -
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]




--
Marc Farrow

Re: 404

[David Kerber]

If you took all the defaults, as it says in that document, Tomcat is on 
8080, not 80.  So try:


http://localhost:8080



[EMAIL PROTECTED] wrote:


Sorry guys about my reply to another thread, I didn't realize.

I'm new at this so...

I only installed tomcat following this guide:
http://www.ubuntuforums.org/showthread.php?t=44006highlight=tomcat

Maybe apache comes with tomcat (I didn't manually installed apache) ? But I
thing it's tomcat who's running on port 80.

 


So what do you have running on port 80?  Apache or Tomcat?

On 4/17/06, [EMAIL PROTECTED] [EMAIL PROTECTED]
wrote:


Yes I've tried with the port number (in my case it's 80) and also with
   


the
 


APPLICATION_NAME.

But the weird thing is that yesterday everything was going fine and now I
get that directory listing instead of the jsp page.

Here's what I get when I click on the apache2-default directory:
---
 If you can see this, it means that the installation of the Apache web
server software on this system was successful. You may now add content to
 this directory and replace this page.

   Seeing this instead of the website you expected?

   This page is here because the site administrator has changed the
configuration of this web server. Please contact the person responsible
for
maintaining this server with questions. The Apache Software Foundation,
which wrote the web server software this site administrator is using, has
   nothing to do with maintaining this site and cannot help resolve
 configuration issues.
---

Is there something that I could have changed in one of the config file
that's causing that ?
All I remember is changing:
-the owner of the /usr/local/tomcat/webapps/root/ from root to myself
   


so
 


I could edit the files.
-I renamed the file web.xml to web_bak.xml but I put it back the way is
was.

Thanks for your help.




   Edoardo Panfili
   [EMAIL PROTECTED]
  A
 Tomcat Users List
   2006-04-17 12:44  users@tomcat.apache.org
  cc

   Veuillez répondre   Objet
   à Re: 404
 Tomcat Users
 List
   [EMAIL PROTECTED]
   che.org






[EMAIL PROTECTED] ha scritto:
   


Why when I go to http://localhost/ I get a directory listing containing
those 2 elements:

[DIR] Parent Directory 15-Apr-2006 15:22 -
[DIR] apache2-default/ 15-Apr-2006 15:22 -

And when I go to http://localhost/index.jsp I get a file not found
 


error
 


although THE FILE EXISTS !
 


Have you tried
http://localhost:8080/
?

or
http://localhost:8080/APPLICATION_NAME/index.jsp
?

Edoardo Panfili

--
[EMAIL PROTECTED]
AIM: edoardopn
Jabber: [EMAIL PROTECTED]
tel:075 9142766

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]






-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


   




--
Marc Farrow
 





-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: 404

[jonathan . pare]

I didn't take the default. I changed the port to 80:

File:
usr/local/tomcat/conf/server.xml

Changed this:
Connector port=8080 ...
  maxThreads=150 minSpareThreads=25 ...

to this:
Connector port=80 ...
  maxThreads=150 minSpareThreads=25 ...


What's bugging me is that my server was running fine and I must have
changed something somewhere but I don't know what !



   
 David Kerber  
 [EMAIL PROTECTED] 
 .net   A 
   Tomcat Users List   
 2006-04-17 13:20  users@tomcat.apache.org   
cc 
   
 Veuillez répondre   Objet 
 à Re: 404 
   Tomcat Users   
   List   
 [EMAIL PROTECTED] 
 che.org  
   
   




If you took all the defaults, as it says in that document, Tomcat is on
8080, not 80.  So try:

http://localhost:8080



[EMAIL PROTECTED] wrote:

Sorry guys about my reply to another thread, I didn't realize.

I'm new at this so...

I only installed tomcat following this guide:
http://www.ubuntuforums.org/showthread.php?t=44006highlight=tomcat

Maybe apache comes with tomcat (I didn't manually installed apache) ? But
I
thing it's tomcat who's running on port 80.



So what do you have running on port 80?  Apache or Tomcat?

On 4/17/06, [EMAIL PROTECTED] [EMAIL PROTECTED]
wrote:


Yes I've tried with the port number (in my case it's 80) and also with


the


APPLICATION_NAME.

But the weird thing is that yesterday everything was going fine and now I
get that directory listing instead of the jsp page.

Here's what I get when I click on the apache2-default directory:
 ---
  If you can see this, it means that the installation of the Apache web
server software on this system was successful. You may now add content to
  this directory and replace this page.

Seeing this instead of the website you expected?

This page is here because the site administrator has changed the
configuration of this web server. Please contact the person responsible
for
maintaining this server with questions. The Apache Software Foundation,
which wrote the web server software this site administrator is using, has
nothing to do with maintaining this site and cannot help resolve
  configuration issues.
 ---

Is there something that I could have changed in one of the config file
that's causing that ?
All I remember is changing:
-the owner of the /usr/local/tomcat/webapps/root/ from root to myself


so


I could edit the files.
-I renamed the file web.xml to web_bak.xml but I put it back the way is
was.

Thanks for your help.




Edoardo Panfili
[EMAIL PROTECTED]
   A
  Tomcat Users List
2006-04-17 12:44  users@tomcat.apache.org
   cc

Veuillez répondre   Objet
à Re: 404
  Tomcat Users
  List
[EMAIL PROTECTED]
che.org






[EMAIL PROTECTED] ha scritto:


Why when I go to http://localhost/ I get a directory listing containing
those 2 elements:

[DIR] Parent Directory 15-Apr-2006 15:22 -
[DIR] apache2-default/ 15-Apr-2006 15:22 -

And when I go to http://localhost/index.jsp I get a file not found


error


although THE FILE EXISTS !


Have you tried
http://localhost:8080/
?

or
http://localhost:8080/APPLICATION_NAME/index.jsp
?

Edoardo Panfili

--
[EMAIL PROTECTED]
AIM: edoardopn
Jabber: [EMAIL PROTECTED]
tel:075 9142766

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]






-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]






--
Marc

Re: 404

[Edoardo Panfili]

[EMAIL PROTECTED] ha scritto:

I didn't take the default. I changed the port to 80:

File:
usr/local/tomcat/conf/server.xml

Changed this:
Connector port=8080 ...
  maxThreads=150 minSpareThreads=25 ...

to this:
Connector port=80 ...
  maxThreads=150 minSpareThreads=25 ...


What's bugging me is that my server was running fine and I must have
changed something somewhere but I don't know what !

If you have some time you can download tomcat from tomcat.apache.org and 
then use diff to find the differences from the original configuration 
files.


Edoardo Panfili

--
[EMAIL PROTECTED]
AIM: edoardopn
Jabber: [EMAIL PROTECTED]
tel:075 9142766

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: 404

[jonathan . pare]

What are the files that I should check if they're ok ?

/usr/local/tomcat/conf/server.xml
/usr/loca/tomcat/webapps/root/WEB-INF/web.xml

what should I look for in those files ? Could you show me examples of
working configuration

Is there other config files I should check ?

Thanks



   
 [EMAIL PROTECTED] 
 jardins.com   
 A 
 2006-04-17 13:29  Tomcat Users List 
   users@tomcat.apache.org   
cc 
 Veuillez répondre 
 à   Objet 
   Tomcat Users   Re: 404 
   List   
 [EMAIL PROTECTED] 
 che.org  
   
   
   





I didn't take the default. I changed the port to 80:

File:
usr/local/tomcat/conf/server.xml

Changed this:
Connector port=8080 ...
  maxThreads=150 minSpareThreads=25 ...

to this:
Connector port=80 ...
  maxThreads=150 minSpareThreads=25 ...


What's bugging me is that my server was running fine and I must have
changed something somewhere but I don't know what !




 David Kerber
 [EMAIL PROTECTED]
 .net   A
   Tomcat Users List
 2006-04-17 13:20  users@tomcat.apache.org
cc

 Veuillez répondre   Objet
 à Re: 404
   Tomcat Users
   List
 [EMAIL PROTECTED]
 che.org






If you took all the defaults, as it says in that document, Tomcat is on
8080, not 80.  So try:

http://localhost:8080



[EMAIL PROTECTED] wrote:

Sorry guys about my reply to another thread, I didn't realize.

I'm new at this so...

I only installed tomcat following this guide:
http://www.ubuntuforums.org/showthread.php?t=44006highlight=tomcat

Maybe apache comes with tomcat (I didn't manually installed apache) ? But
I
thing it's tomcat who's running on port 80.



So what do you have running on port 80?  Apache or Tomcat?

On 4/17/06, [EMAIL PROTECTED] [EMAIL PROTECTED]
wrote:


Yes I've tried with the port number (in my case it's 80) and also with


the


APPLICATION_NAME.

But the weird thing is that yesterday everything was going fine and now I
get that directory listing instead of the jsp page.

Here's what I get when I click on the apache2-default directory:
 ---
  If you can see this, it means that the installation of the Apache web
server software on this system was successful. You may now add content to
  this directory and replace this page.

Seeing this instead of the website you expected?

This page is here because the site administrator has changed the
configuration of this web server. Please contact the person responsible
for
maintaining this server with questions. The Apache Software Foundation,
which wrote the web server software this site administrator is using, has
nothing to do with maintaining this site and cannot help resolve
  configuration issues.
 ---

Is there something that I could have changed in one of the config file
that's causing that ?
All I remember is changing:
-the owner of the /usr/local/tomcat/webapps/root/ from root to myself


so


I could edit the files.
-I renamed the file web.xml to web_bak.xml but I put it back the way is
was.

Thanks for your help.




Edoardo Panfili
[EMAIL PROTECTED]
   A
  Tomcat Users List
2006-04-17 12:44  users@tomcat.apache.org
   cc

Veuillez répondre   Objet
à Re: 404
  Tomcat Users
  List
[EMAIL PROTECTED]
che.org






[EMAIL

Re: 404

[Edoardo Panfili]

[EMAIL PROTECTED] ha scritto:

What are the files that I should check if they're ok ?

/usr/local/tomcat/conf/server.xml

I use the default file, It works good for me.
I have the configuration for the application inside the application 
folder: $tomcatHome/webapp/APPLICATION_NAME/META-INF/context.xml file




/usr/loca/tomcat/webapps/root/WEB-INF/web.xml

take a look at logs file in $tomcatHome/logs


if something gone wrong during startup you can find details inside this 
directory.


Edoardo Panfili
--
[EMAIL PROTECTED]
AIM: edoardopn
Jabber: [EMAIL PROTECTED]
tel:075 9142766

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: 404 resource not found

[Mark Space]

Mark Space wrote:

I've already tried increasing the logging to debug, but I see 
nothing untoward in the logs, just a lot of [info].  I've tried 
eyeballing the web.xml file and the directory paths several times and 
I can see my typo.  I



That's should have been can't see my typo...


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: 404 resource not found

[Caldarale, Charles R]

 From: Mark Space [mailto:[EMAIL PROTECTED] 
 Subject: 404 resource not found
 
 2. The app is installed in (Tomcat_home)/webapps/ROOT/Beer-v1

That's at least one problem - your app should be under webapps, not
webapps/ROOT.  Your app was never deployed.  Follow the examples.

 - Chuck


THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY
MATERIAL and is thus for use only by the intended recipient. If you
received this in error, please contact the sender and delete the e-mail
and its attachments from all computers.

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: 404 resource not found

[Caldarale, Charles R]

 From: Mark Space [mailto:[EMAIL PROTECTED] 
 Subject: Re: 404 resource not found
 
 So, is ROOT the default app?  This said to use ROOT: 
 http://www.coreservlets.com/Apache-Tomcat-Tutorial/

I'd suggest using the real Tomcat and Servlet documentation first, and
then referring to 3rd party doc only if necessary for clarification -
but beware, since a good bit of it is out of date and some simply wrong.

ROOT indeed is the location of the default app, and apps are not
intended to be nested inside one another.  Note that the above tutorial
always uses webapps/ROOT/WEB-INF, not webapps/ROOT/myapp/WEB-INF like
you tried to do.  All the examples in that tutorial are merely providing
extra pages for the default app rather than additional apps.

I'd also suggest reading the servlet spec from the Sun web site, as it
provides much detail that is intentionally not duplicated in the Tomcat
doc.  You can get the spec here:
http://jcp.org/aboutJava/communityprocess/final/jsr154/index.html

 - Chuck


THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY
MATERIAL and is thus for use only by the intended recipient. If you
received this in error, please contact the sender and delete the e-mail
and its attachments from all computers.

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]