Actually, that error is generally related to IIS trying to start up when Apache Http server is running on the same port...make sure Apache http server is STOPPED and than Tomcat is not set up to be listening on port 80...
Rick Bullotta CTO Lighthammer Software (http://www.lighthammer.com) -----Original Message----- From: Johannes Fiala [mailto:[EMAIL PROTECTED] Sent: Monday, March 10, 2003 2:24 PM To: Tomcat Users List Cc: [EMAIL PROTECTED] Subject: RE: Tomcat 4.1.18 - IIS 5.0 plugin - jk2.properties + workers2.properties Hi Rick, I tried both fixes, but they failed. I also tried different releases (2.0.1, 2.0.2), but none worked. It also doesn't log properly, just fails when I look into the event viewer Event Type: Error Event Source: W3SVC Event Category: None Event ID: 115 Date: 10.03.2003 Time: 20:17:27 User: N/A Computer: DEVELOPER1 Description: The service could not bind instance 1. The data is the error code. For additional information specific to this message please visit the Microsoft Online Support site located at: http://www.microsoft.com/contentredirect.asp. Data: 0000: 40 27 00 00 @'.. I cannot fully understand why jk 1.x works so smoothly, but 2.0.2 simply doesn't work out. Do you know any location where I can find more info about this error? Maybe I need a patch for IIS to fix this?? I've spent lots of hours trying to get this work, but troubleshooting this IIS connector is much harder than programming Java :) thx a lot for your input! johannes Rick Bullotta <[EMAIL PROTECTED]> 09.03.2003 15:34 Please respond to [EMAIL PROTECTED] To Tomcat Users List <[EMAIL PROTECTED]> cc Subject RE: Tomcat 4.1.18 - IIS 5.0 plugin - jk2.properties + workers2.properties Here are a few differences between your configuration and mine: 1) My workers2.properties uses [shm:] instead of [shm]. 2) I found that the 2.0.2 jk2 ISAPI redirector dll does not like forward slash path syntax on Windows (for your SHM file). Try \\. ---- Tomcat Users List <[EMAIL PROTECTED]> wrote: > hi there, > > here are the properties files I currently use (a merge of Mark's + Rick's > configuration files): > > ========================= > jk2.properties > ========================= > ## THIS FILE MAY BE OVERRIDEN AT RUNTIME. MAKE SURE TOMCAT IS STOPED > ## WHEN YOU EDIT THE FILE. > > ## COMMENTS WILL BE _LOST_ > > ## DOCUMENTATION OF THE FORMAT IN JkMain javadoc. > > # Set the desired handler list > # handler.list=apr,request,channelJni > # > # Override the default port for the socketChannel > # channelSocket.port=8019 > # Default: > # channelUnix.file=${jkHome}/work/jk2.socket > # Just to check if the the config is working > # shm.file=${jkHome}/work/jk2.shm > > # In order to enable jni use any channelJni directive > # channelJni.disabled = 0 > # And one of the following directives: > > # apr.jniModeSo=/opt/apache2/modules/mod_jk2.so > > # If set to inprocess the mod_jk2 will Register natives itself # This > will enable the starting of the Tomcat from mod_jk2 # > apr.jniModeSo=inprocess > > # > # Socket configuration > # > handler.list=request,container,channelSocket > #apr > > # > # apr configuration > # jk2.properties file in C:\Tomcat\conf > # > #apr.NativeSo=${jkHome}\\bin\\Win32\\jkjni.dll > #apr.jniModeSo=${jkHome}\\bin\\Win32\\jkjni.dll > > # > # socket configuration > # > channelSocket.port=8009 > channelSocket.address=127.0.0.1 > channelSocket.maxPort=port+10 > > ========================= > workers2.properties > ========================= > # workers2.properties file in C:\Apache2\conf > # only at beginning. In production uncomment it out > # [logger.apache2] > # level=DEBUG > > [shm] > file=f:/tomcat-4.1.18/shm.file > size=1048576 > > # Example socket channel, override port and host. > [channel.socket:localhost:8009] port=8009 > host=127.0.0.1 > > # define the worker > [ajp13:localhost:8009] > channel=channel.socket:localhost:8009 > > # Uri mapping > [uri:/examples/*] > worker=ajp13:localhost:8009 > > [uri:/wartung/*] > worker=ajp13:localhost:8009 > > [uri:/SignonClient/*] > worker=ajp13:localhost:8009 > > thx > Johannes --------------------------------------------------------------------- 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]
