Servlets for IIS

[krishnaraj]

Hi friends,
I am using IIS web server. I use the plugin JRUN for running the servlets using the IIS. I was able to configure JRUN successfully and I tested the same using the sample servlets like SnoopServlet and HelloWorldServlet. Now, I have written a servlet and i have placed the class file under .\Inetpub\wwwroot. When i tried to run this servlet, I get a '500 Internal Server Error'. Can anybody help me how to solve this problem ? or Where could I have gone wrong ?
For your information, I have tested the same using Domino Server and it is working fine.
Thanx & Regards
Krish..

[Jan Meeuwesen]

Hi there,

I think you should place the HTML which calls the servlet in the wwroot and the class files in the servlets directory. You can set the servlet directory by running the servletrunner with the parameter '-d' (which sets the default servlet directory).

Greets,
Jan Meeuwesen
( If this answer is of any value to you, rate it! (bottom right in your browser under this text) )

[krishnaraj]

Hi Jan,
I have placed the HTML files in \inetpub\wwwroot... i don't understand what u mean by " running the servletrunner with the parameter '-d' (which sets the default servlet directory)". Kindly elaborate.
Thanx
Krish..

[Jan Meeuwesen]

Hi,

I'm sorry I wasn't very clear to you.
The Jrun plugin is for running servlets, I assume? Well then can you tell this plugin where the default directory is for your servlets? Or maybe it's default location is the scripts directory of IIS (have you tried this?). I suggest that you read the avaible readme files, for more information on this plugin.

Good luck,
Jan Meeuwesen.

[125]

You have to configer the JRun so that it's property files contains the proper path to your servelts directory. If I remember that correctly, you can specify your path from "alias" tab of jse screen (could be wrong, I did that a while ago, but it worked). Check out the user menu from their web site. The instructions are pretty decent...

But I do have problems with JRun from time to time. Seems to me it tends to have conflicts with some other software, and once it scrowed, its pretty hard to be removed completly. I don't know if there is some other options out there for IIS, and also free?

[krishnaraj]

Hi,
I think there is no problem with the configuration of JRUN right now, as I am able to browse http://IPaddress/servlet/SnoopServlet and all the other sample servlets. But, i do have some problem running the servlets that i have created.
Here it goes. I placed all the class files in the /Jrun/servlets directory. I am now able to browse. But as soon as the web server receives a such a request, it throws Dr. Watson for Windows NT for javaw.exe and the JRUN service imediately stops.
I believe JRUN can be configured in 2 ways - NT service mode and application mode. I tried removing the NT service mode using the wizard available. Though the JRUN service was not to be seen in the list of NT services, still there is no change in DR. Watson problem.
Can you help me how to proceed ?
When you say "it tends to have conflicts with some other software, and once it scrowed, its pretty hard to be removed completly", does it mean that JRUN unreliable for IIS ?
Krish..

[krishnaraj]

Hi,
Yes, JRUN is the only plugin available (known to me) for running servlets in IIS. Even while installation of JRUN, a dll is placed in the inetpub\scripts directory.
According to JRUN's documentation, the mapping of /servlet/classname is done by the JRUN itself and the class files need not be physically placed in the \jrun\servlet directory. But, since this didn't work (i placed all the files in \inetpub\wwwroot and got a 500 Internal Server Error), i tried by placing all the class files in the \jrun\servlet directory and tried. This worked fine but everytime, the server receives a request from the browser, Dr. Watson for Windows NT comes and crashes the javaw.exe (which is installed during Jrun installation). I hope i am clear.
Krishnaraj

Where do you put your applets? Make sure the applets you created are in the same directory as those working samples are and try it. If that works, it means that the applet directory configueration is causing the problem -- you need to point your JRUN's path to your applet's directory. If it still doesn't work, it could be the applet itself that cause the problem. Try a real simple one as the first step.

Good luck.

Lifeng