Hi Rajneesh
I recently got rid of JWS 2.0 after a few years of poor reliabilty, in
favour Apache/JServ, but we did experience exactly the what you are
experiencing.
The termination of the webservice was caused by three things.
1) more than one or two unhandled exceptions on or servlet. Add some
logging to your servlets and set your logging in the Admin tool to log
errors to a largefile size and increase the buffer.
2) Run JWS 2.0 0n JDK 1.2.2 or above not the 1.1.7b it ships with, it has
memory leaks that kill the webpage service over time, and slows it own
little by little. It is interestng to run a test on your server at
startup and then let it run a few days (if you can keep it runing that
long) and then test it again.. dismall
3) NT Sevice Pack 5 alowing the JREW to dominate the CPU hence starving
the network. This was pretty intermittant but wa a problem. Service pack 6
+resolved this issue.
Also in Web Service Manage, Service tuning, double all the defaults for
even a low traffic site.
We gave up on JWS after Sun got into b4d with Netscape since there is no
clear path to follow at this stage. Apache and JServ are unbelivebly more
reliabe than JWS.. We stil hae one site on JWS 2.0 nd the others on
apache. The serive intervals on JWS are about 10times that of Apache,
simply no comparison.
Well I hope that gives you some help.
Chris
On Wed, 7 Jun 2000 19:21:39 +0530, Rajneesh Garg wrote:
>Hi there,
>
>We are working on an online web application using JWS 2.0 with SQL
>Server 7 as database for Windows NT 4. Here, while working we are
>encountering some strange behavior from the JWS.
>
> * Sometimes, it just terminates the web service on its own. We have
> tried to find out the cause, but have not succeeded yet. What could
>
> be the possible cause for it? I dont think it is because of
> overcrowd of users, because we are only 5 persons working on it.
> * Second problem relates to session time-out. We have not changed the
>
> session time-out interval (i.e. the time out is 30 mins, by
> default). However, if user is inactive for some time (< 30 mins),
> some times, it throws the user out of session. What could be the
> reason behind such inconsistent behavior? Should we explicitly set
> the time-out interval? Is there any other way to avoid it?
> * I have read somewhere that we should not use Web Server for
> deployment of our web applications, and instead use an application
> server, that has a Web Server in it. Is it really so? How it
> affects the application, in terms of performance and otherwise?
>
>I hope someone have encountered/knows about such probs. Any pointers
>will me highly appreciated.
>
>Rajneesh Garg
>
>Keep Smiling. It does improve your face value :-)
>
>___________________________________________________________________________
>To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
>of the message "signoff SERVLET-INTEREST".
>
>Archives: http://archives.java.sun.com/archives/servlet-interest.html
>Resources: http://java.sun.com/products/servlet/external-resources.html
>LISTSERV Help: http://www.lsoft.com/manuals/user/user.html
>
___________________________________________________________________________
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff SERVLET-INTEREST".
Archives: http://archives.java.sun.com/archives/servlet-interest.html
Resources: http://java.sun.com/products/servlet/external-resources.html
LISTSERV Help: http://www.lsoft.com/manuals/user/user.html
