You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tomcat.apache.org by Bob Bateman <bb...@bobbateman.com> on 2007/06/12 04:11:02 UTC

Issue with JK connector vs. IIS 6

Hi all,

I'm giving trouble bringing up an installation of Tomcat 5.5.23 via IIS 6
and the JK1 connector.  I have tracked the problem down to something about
the IIS 5.0 Isolation Mode.  If I enable Isolation Mode, all is well with my
config: the connector logs requests and mapping, requests are correctly
forwarded to Tomcat and serviced.  Unfortunately this is not a workable
solution because other apps on the server (ASP?) break under 5.0 mode, and
there doesn't seem to be a way to configure 5.0 mode on any scope less than
the entire server.  I need to find a way to make Tomcat work with IIS 6.

I've been through the whole same setup on WinXP/IIS5, and everything works
there, except of course there is no Isolation Mode.

Another wrinkle is that the entire setup is running on a VPS.  I'm finding
that tools like FileMon, ProcMon do not run either.  Could these be related?

I have tried:

	Running the connector in its own application pool, or not
	Running the application pool as various users; Local System, Network
Service, Local Service, IWAM_TEMPLATE, etc.
	Connector versions 1.2.19 and 1.2.23
	Connector config in Registry, properties file or both


I feel sure that the worker.properties, uriworkermap.properties and
isapi_redirect.properties, server.xml, IIS extensions and filters are
correct because the setup works in the compatibility mode.

I'm thinking this must be something related to specific user or permissions
config for the connector, Isolation mode config, or a VPS artifact.  I've
seen conflicting messages about whether JK1 really works with IIS6 with
Isolation Mode.  Is this a bug?

Thanks in advance,
-BB


	
	


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


RE: Issue with JK connector vs. IIS 6

Posted by Bob Bateman <bb...@bobbateman.com>.
A few more observations to add: when the problem occurs (not in Isolation
Mode) the connector shows as loaded OK (green up-arrow in IIS) but does not
generate any system event messages or isapi logfile messages.  I do see
messages in both places when running correctly in Isolation Mode.  On the
browser side you just get 404s.

I'm out of ideas about how to debug this any further.

-BB


-----Original Message-----
From: Bob Bateman [mailto:bb@bobbateman.com] 
Sent: Monday, June 11, 2007 7:11 PM
To: users@tomcat.apache.org
Subject: Issue with JK connector vs. IIS 6

Hi all,

I'm giving trouble bringing up an installation of Tomcat 5.5.23 via IIS 6
and the JK1 connector.  I have tracked the problem down to something about
the IIS 5.0 Isolation Mode.  If I enable Isolation Mode, all is well with my
config: the connector logs requests and mapping, requests are correctly
forwarded to Tomcat and serviced.  Unfortunately this is not a workable
solution because other apps on the server (ASP?) break under 5.0 mode, and
there doesn't seem to be a way to configure 5.0 mode on any scope less than
the entire server.  I need to find a way to make Tomcat work with IIS 6.

I've been through the whole same setup on WinXP/IIS5, and everything works
there, except of course there is no Isolation Mode.

Another wrinkle is that the entire setup is running on a VPS.  I'm finding
that tools like FileMon, ProcMon do not run either.  Could these be related?

I have tried:

	Running the connector in its own application pool, or not
	Running the application pool as various users; Local System, Network
Service, Local Service, IWAM_TEMPLATE, etc.
	Connector versions 1.2.19 and 1.2.23
	Connector config in Registry, properties file or both


I feel sure that the worker.properties, uriworkermap.properties and
isapi_redirect.properties, server.xml, IIS extensions and filters are
correct because the setup works in the compatibility mode.

I'm thinking this must be something related to specific user or permissions
config for the connector, Isolation mode config, or a VPS artifact.  I've
seen conflicting messages about whether JK1 really works with IIS6 with
Isolation Mode.  Is this a bug?

Thanks in advance,
-BB


	
	


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





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