• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Ron McLeod
  • Paul Clapham
  • Bear Bibeault
  • Junilu Lacar
Sheriffs:
  • Jeanne Boyarsky
  • Tim Cooke
  • Henry Wong
Saloon Keepers:
  • Tim Moores
  • Stephan van Hulst
  • Tim Holloway
  • salvin francis
  • Frits Walraven
Bartenders:
  • Scott Selikoff
  • Piet Souris
  • Carey Brown

IIS5/Tomcat 5.5/workers2.properties

 
Greenhorn
Posts: 9
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I have successfully redirected from IIS 5 to Tomcat 5.5 the /serlvet-examples webapp that comes with the Tomcat 5.5 distribution. I also have been able to successfully test my own servlets by calling them directly on port 8080. I have been unable, however, to redirect to these servlets in the same fashion as the sample servlets. When I view the uri runtime info via /jkstatus everything looks consistent so I suspect the workers2.properties file listed below.

----------------

#Look at
#http://jakarta.apache.org/tomcat/tomcat-4.1-doc/jk2/jk2/configwebcom.html
#for parameter description

[shm:]
info=Shared memory file. Required for multiprocess servers
file=D:\Apache Software Foundation\Tomcat 5.5\temp\jk2.shm
size=1048576

[channel.socket:localhost:8009]
info=Ajp13 worker, connects to tomcat instance using AJP 1.3 protocol
tomcatId=localhost:8009

# Map webapps to the Web server uri space
[uri:/contracts/*]
info=contracts
context=/contracts

[uri:/servlets-examples/*]
info=Servlet examples, map requests for all servlets to Tomcat.
context=/servlets-examples

[uri:/sample/*]
info=Sample Servlets
context=/sample

# define the worker
[status:status]

# Uri mapping
[uri:/jkstatus/*]
worker=status:status

--------------

Let me reiterate that everything works fine by calling port 8080. All servlets located in /servlets-examples work. A servlet in /sample works but a jsp file in that webapp throws a HTTP 500 - Internal server error as well as all of the servlets in the /contracts webapp.

Any ideas would be appreciated.
 
Would you turn that thing down? I'm controlling a mind here! Look ... look at the tiny ad ...
Thread Boost feature
https://coderanch.com/t/674455/Thread-Boost-feature
    Bookmark Topic Watch Topic
  • New Topic