Re: SOLVED [ANN] Apache Tomcat JK 1.2.26 Web Server Connector released

2008-01-30 Thread Haroon Rafique
On Today at 5:45pm, MT=>Mladen Turk <[EMAIL PROTECTED]> wrote:

MT> [..snip..]
MT> 
MT> Hmm, you might be hitting the point here. When tightening up the vhost 
MT> mappings we probably overlooked the SSL (or any other protocol) 
MT> scenario, where the actual vhost is the same, only the protocol is 
MT> different. However since the SSL is inside vhost and can have its own 
MT> native mappings it complies to the vhost concept. Anyhow, you made me 
MT> think that we should probably fine-tune our vhost separation beyond 
MT> actual Httpd vhost concept by checking the actual vhost name and 
MT> protocol. In case only the protocol is different we should treat them 
MT> as one regarding jk mounts thought.
MT> 
MT> Regards
MT> 

Thanks, Mladen,

Posted to dev list with new subject (now that I know what the problem is).

Cheers,
--
Haroon Rafique
<[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: SOLVED [ANN] Apache Tomcat JK 1.2.26 Web Server Connector released

2008-01-30 Thread Mladen Turk

Haroon Rafique wrote:


Your above question got me thinking and I said to myself, I don't harve any 
VirtualHosts. And then, I remembered SSL. In my config for apache 2.2.6, 
there is an include for conf/extra/httpd-ssl.conf and of course :443 is 
served via a VirtualHost.




Hmm, you might be hitting the point here.
When tightening up the vhost mappings we probably overlooked the
SSL (or any other protocol) scenario, where the actual vhost is
the same, only the protocol is different.
However since the SSL is inside vhost and can have its own
native mappings it complies to the vhost concept.
Anyhow, you made me think that we should probably fine-tune
our vhost separation beyond actual Httpd vhost concept
by checking the actual vhost name and protocol.
In case only the protocol is different we should treat them
as one regarding jk mounts thought.

Regards
--
(TM)

-
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: SOLVED [ANN] Apache Tomcat JK 1.2.26 Web Server Connector released

2008-01-30 Thread Haroon Rafique
On Yesterday at 11:58pm, RJ=>Rainer Jung <[EMAIL PROTECTED]> wrote:

RJ> 
RJ> [..snip..]
RJ> 
RJ> The ugly: stricter handling of JkMount/JkMountFile etc. with respect 
RJ> to virtual hosts. It should have behaved for a long time in the way, 
RJ> that mounts are not inherited between virtual hosts and also not from 
RJ> the global server to any virtual host.
RJ> 
RJ> The debug log statement you cite indicates, that there is no mount 
RJ> known in a virtal host you are using.
RJ> 
RJ> So first question: Do you have an VirualHost in your apache httpd
RJ> configuration?
RJ> 

Hi Rainer,

Thanks for your response.

Your above question got me thinking and I said to myself, I don't have any 
VirtualHosts. And then, I remembered SSL. In my config for apache 2.2.6, 
there is an include for conf/extra/httpd-ssl.conf and of course :443 is 
served via a VirtualHost.

RJ> 
RJ> If so: first find out, which VirtualHost handles your requests. This 
RJ> might be trivial, in some cases it is not trivial. If you are not 
RJ> sure, you can configure a different CustomLog in the global server and 
RJ> for wach VirtualHost and then check, in which CustomLog your request 
RJ> got logged.
RJ> 
RJ> Once you know, which VirtualHost handles your request, you can either:
RJ> 
RJ> - define all relevant JkMount/JkUnMount/JkMountfile in the VirtualHost
RJ> 
RJ> or
RJ> 
RJ> - define them globally and copy all of them into the VirtualHost by setting
RJ> "JkMountCopy On" inside the virtual host.
RJ> 
RJ> In case you have lots of VirtualHost and you want them all to share 
RJ> several JkMounts, put them into the global server and add "JkMountCopy 
RJ> all" to the global server.
RJ> 

If someone else is having the same problem, here's my solutions (for 
acrhiving purposes). I had an include in the main httpd.conf for 
conf/mod_jk.conf. I took the easy route and add JkMountCopy All to my 
conf/mod_jk.conf so that the SSL VirtualHost sees those mounts as well. I 
could have just as well used a JkMountCopy On inside the SSL VirtualHost 
only.

RJ> 
RJ> I hope that is understandable?
RJ> 

Thanks again for your help.

RJ> Regards,
RJ> 
RJ> Rainer
RJ> 

Cheers,
--
Haroon Rafique
<[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: [ANN] Apache Tomcat JK 1.2.26 Web Server Connector released

2008-01-29 Thread Rainer Jung

Hi Haroon,

the change in the status worker display that you noticed is not directly 
related to your problem, only so far, as we changed a couple of things 
around the mount tables.


The good: more information in the status worker.

The ugly: stricter handling of JkMount/JkMountFile etc. with respect to 
virtual hosts. It should have behaved for a long time in the way, that 
mounts are not inherited between virtual hosts and also not from the 
global server to any virtual host.


The debug log statement you cite indicates, that there is no mount known 
in a virtal host you are using.


So first question: Do you have an VirualHost in your apache httpd 
configuration?


If so: first find out, which VirtualHost handles your requests. This 
might be trivial, in some cases it is not trivial. If you are not sure, 
you can configure a different CustomLog in the global server and for 
wach VirtualHost and then check, in which CustomLog your request got logged.


Once you know, which VirtualHost handles your request, you can either:

- define all relevant JkMount/JkUnMount/JkMountfile in the VirtualHost

or

- define them globally and copy all of them into the VirtualHost by 
setting "JkMountCopy On" inside the virtual host.


In case you have lots of VirtualHost and you want them all to share 
several JkMounts, put them into the global server and add "JkMountCopy 
all" to the global server.


I hope that is understandable?

Regards,

Rainer

Haroon Rafique schrieb:

On Dec 24 at 4:36pm, RJ=>Rainer Jung <[EMAIL PROTECTED]> wrote:

RJ> The Apache Tomcat team is pleased to announce the immediate availability
RJ> of version 1.2.26 of the Apache Tomcat Connectors.
RJ> 
RJ> [..snip..]


So, JK 1.2.26 has been out for over a month and I finally got around to 
upgrading from 1.2.25 and without changing my mod_jk.conf or 
workers.properties the connector seems to stop working. In debug mode, I 
get the following with 1.2.26:


jk_translate::mod_jk.c (3033): missing uri map for haroon.sis.utoronto.ca:/rxp/

With 1.2.26 the Jk Status Manager reports:

Server  URI Match Type  Source
haroon.sis.utoronto.ca  /rxp/*  WildcharJkMount

With 1.2.25:

Match Type  Uri Source
Wildchar/rxp/*  JkMount

Obviously the difference is due to this:

	* JKStatus: Enhance URI to worker map listing for Apache httpd. We 
  now list maps for all virtual servers and not only the one, in 
  which JKStatus itself was called. (rjung)


Anyone care to share their war stories with 1.2.26?

Here's my configuration files:

workers.properties
==
# basic worker list
worker.list=local,status

# Define a worker using ajp13
worker.local.port=8009
worker.local.host=localhost
worker.local.type=ajp13

worker.status.type=status

mod_jk.conf
===
# Load mod_jk module
LoadModule jk_module modules/mod_jk.so

# Where to find workers.properties
JkWorkersFile conf/workers.properties

# Where to put jk logs
JkLogFile logs/mod_jk.log

# Set the jk log level
JkLogLevel error

JkShmFile logs/mod_jk.shm

JkMount /rxp/* local
JkMount /jkstatus status


The same setup works flawlessly with 1.2.25. Spent the last few hours on 
this and was getting no where.


Thanks in advance,
--
Haroon Rafique
<[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: [ANN] Apache Tomcat JK 1.2.26 Web Server Connector released

2008-01-29 Thread Haroon Rafique
On Dec 24 at 4:36pm, RJ=>Rainer Jung <[EMAIL PROTECTED]> wrote:

RJ> The Apache Tomcat team is pleased to announce the immediate availability
RJ> of version 1.2.26 of the Apache Tomcat Connectors.
RJ> 
RJ> [..snip..]

So, JK 1.2.26 has been out for over a month and I finally got around to 
upgrading from 1.2.25 and without changing my mod_jk.conf or 
workers.properties the connector seems to stop working. In debug mode, I 
get the following with 1.2.26:

jk_translate::mod_jk.c (3033): missing uri map for haroon.sis.utoronto.ca:/rxp/

With 1.2.26 the Jk Status Manager reports:

Server  URI Match Type  Source
haroon.sis.utoronto.ca  /rxp/*  WildcharJkMount

With 1.2.25:

Match Type  Uri Source
Wildchar/rxp/*  JkMount

Obviously the difference is due to this:

* JKStatus: Enhance URI to worker map listing for Apache httpd. We 
  now list maps for all virtual servers and not only the one, in 
  which JKStatus itself was called. (rjung)

Anyone care to share their war stories with 1.2.26?

Here's my configuration files:

workers.properties
==
# basic worker list
worker.list=local,status

# Define a worker using ajp13
worker.local.port=8009
worker.local.host=localhost
worker.local.type=ajp13

worker.status.type=status

mod_jk.conf
===
# Load mod_jk module
LoadModule jk_module modules/mod_jk.so

# Where to find workers.properties
JkWorkersFile conf/workers.properties

# Where to put jk logs
JkLogFile logs/mod_jk.log

# Set the jk log level
JkLogLevel error

JkShmFile logs/mod_jk.shm

JkMount /rxp/* local
JkMount /jkstatus status


The same setup works flawlessly with 1.2.25. Spent the last few hours on 
this and was getting no where.

Thanks in advance,
--
Haroon Rafique
<[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: [ANN] Apache Tomcat JK 1.2.26 Web Server Connector released

2008-01-02 Thread Tim Whittington
Binary builds of 1.2.26 for various platforms are available now from
http://sourceforge.net/projects/timsjk/
These include builds of a patched IIS 5/6 ISAPI Redirector that support
HTTP 1.1 chunked encoding (and thus keep-alives on dynamic content).

cheers
tim


-Original Message-
From: Rainer Jung [mailto:[EMAIL PROTECTED] 
Sent: Tuesday, 25 December 2007 4:36 a.m.
To: users@tomcat.apache.org; [EMAIL PROTECTED]; [EMAIL PROTECTED];
[EMAIL PROTECTED]
Subject: [ANN] Apache Tomcat JK 1.2.26 Web Server Connector released

The Apache Tomcat team is pleased to announce the immediate availability
of version 1.2.26 of the Apache Tomcat Connectors.

It contains connectors, which allow a web server such as Apache HTTPD,
Microsoft IIS and Sun Web Server to act as a front end to the Tomcat web
application server.

This version contains a few enhancements and fixes a number of minor bugs
of the previous versions.

See http://tomcat.apache.org/connectors-doc/miscellaneous/changelog.html
for a complete list of changes.

Source distribtions can be downloaded from an Apache Software Foundation
mirror at:

http://tomcat.apache.org/download-connectors.cgi

Binary distributions for a number of different operating systems and web
servers can be downloaded from an Apache Software Foundation mirror at:

http://tomcat.apache.org/download-connectors.cgi

Syncing the release to the download mirrors might take up to 48 hours.

Documentation for using Apache Tomcat Connectors can be found at:

http://tomcat.apache.org/connectors-doc/

Thank you,

-- The Apache Tomcat Team

P.S.: Merry Christmas!



-
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]



[ANN] Apache Tomcat JK 1.2.26 Web Server Connector released

2007-12-24 Thread Rainer Jung
The Apache Tomcat team is pleased to announce the immediate availability
of version 1.2.26 of the Apache Tomcat Connectors.

It contains connectors, which allow a web server such as Apache HTTPD,
Microsoft IIS and Sun Web Server to act as a front end to the Tomcat web
application server.

This version contains a few enhancements and fixes a number of minor
bugs of the previous versions.

See http://tomcat.apache.org/connectors-doc/miscellaneous/changelog.html
for a complete list of changes.

Source distribtions can be downloaded from an Apache Software Foundation
mirror at:

http://tomcat.apache.org/download-connectors.cgi

Binary distributions for a number of different operating systems and
web servers can be downloaded from an Apache Software Foundation mirror at:

http://tomcat.apache.org/download-connectors.cgi

Syncing the release to the download mirrors might take up to 48 hours.

Documentation for using Apache Tomcat Connectors can be found at:

http://tomcat.apache.org/connectors-doc/

Thank you,

-- The Apache Tomcat Team

P.S.: Merry Christmas!



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