tomcat-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Mark Eggers <its_toas...@yahoo.com>
Subject Re: Manager Doesn't Recognize context = "/"
Date Sat, 01 Feb 2014 21:16:28 GMT
On 1/31/2014 7:01 PM, Jerry Malcolm wrote:
> Well I turned on Firebug.  This is what it gives me.  Doesn't look
> like there is much useful info in here.  If there's something specific
> you are looking for that's not here, I can do more tracing.....
>
> ====This is the "response" tab content:
>
> POST stop?path=/Projectmanag...420E758A102ED89CE89346C
> 400 Bad Request
> local.texasweddingsltd.com
> 0 B
> 127.0.0.1:80
>
> 26ms
>
> Reload the page to get source for:
> http://local.texasweddingsltd.com/manager/html/stop?path=/Projectmanager&org.apache.catalina.filters.CSRF_NONCE=48BE489D7420E758A102ED89CE89346C
>
> ===== and this is the "parameters" tab content
>
> POST stop?path=/Projectmanag...420E758A102ED89CE89346C
> 400 Bad Request
> local.texasweddingsltd.com
> 0 B
> 127.0.0.1:80
>
> 26ms
>
> Response Headers
> Connectionclose
> Content-Typetext/plain; charset=ISO-8859-1
> DateSat, 01 Feb 2014 02:54:01 GMT
> ServerApache/2.0.59 (Win32) mod_jk/1.2.19 PHP/5.2.17
> Transfer-Encodingchunked
>
> Request Headers
> Accepttext/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
> Accept-Encodinggzip, deflate
> Accept-Languageen-US,en;q=0.5
> AuthorizationBasic am1hbGNvbG06MTIwNDA=
> Cache-Controlmax-age=0
> Connectionkeep-alive
> CookieJSESSIONID=2818D3E5D20A5B8A08173F854773A535;
> __utma=54525101.1533907930.1351347950.1353346652.1353348600.9;
> JSESSIONIDSSO=D2712DE9ED6AA32F7D68870679AAFB50;
> callBack="/idmanager2//jsp/user/home.jsp?formInstanceId="
> Hostlocal.texasweddingsltd.com
> Refererhttp://local.texasweddingsltd.com/manager/html?org.apache.catalina.filters.CSRF_NONCE=CA7898046139AE7E759206E8C71343BE
> User-AgentMozilla/5.0 (Windows NT 6.1; WOW64; rv:27.0) Gecko/20100101
> Firefox/27.0
> Request Headers From Upload Stream
> Content-Length0
> Content-Typeapplication/x-www-form-urlencoded

Hi Jerry,

I took a little time this morning to set up a similar environment:

OS:     Fedora 20 64 bit (latest updates)
HTTPD:  2.4.6-6
mod_jk: 1.2.37
JRE:    1.7.0_51 64 bit
Tomcat: 7.0.50
Tomcat: native connectors

I set up two virtual hosts, and used docBase to get both the ROOT and 
manager applications running under the virtual hosts.

I then pushed the manager application and some sample applications 
through Apache HTTPD using mod_jk.

As an aside, I'm not sure I would recommend running the manager 
application through Apache HTTPD. I can comment on that in a separate 
mail message if you'd like.

All worked as expected.

One of the things I noticed about your Firebug output above is the 
following line:

callBack="/idmanager2//jsp/user/home.jsp?formInstanceId="

What is this? I don't see it in my Firebug output.

Another thing that I noticed is that you're running the following Apache 
HTTPD:

ServerApache/2.0.59 (Win32) mod_jk/1.2.19 PHP/5.2.17

I know you've been on the upgrade wheel lately, but these are all very, 
very old.

There are known security issues with Apache HTTPD 2.0.x, PHP 5.2, and 
mod_jk 1.2.19. Apache 2.0.x is no longer supported as well.

If you're not using PHP in your environment, I would recommend just 
commenting out the loading of the PHP module. If you are, upgrading it 
may be a bit of a challenge since PHP web applications may or may not 
like the newer versions of PHP.

Anyway, I think what may be going on is that you're using the stock 
Apache Tomcat 7.0.50 for Windows, which comes with tcnative-1.dll.

Having this file in the CATALINA_HOME/bin directory causes the AJP 
connector to use the native APR version. The APR connector may not be 
compatible with your old mod_jk.

My first guess at a solution would be to rename tcnative-1.dll so that 
it won't load (maybe tcnative-1.dll.orig), restart Tomcat, and see if 
things work.

If that doesn't address your issues, then I am afraid it's time to 
upgrade your Apache HTTPD / mod_jk platform.

Jumping from 2.0 to 2.4 is a bit of a pain. I'd try Apache HTTPD 2.2 and 
the latest mod_jk first. The configuration file for Apache HTTPD 2.2 is 
reasonably similar to Apache HTTPD 2.0. Apache HTTPD 2.4 involves a fair 
number of changes.

I hope the easy fix works.

. . . . just my two cents.
/mde/

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


Mime
View raw message