>>> Amos Shapira <[EMAIL PROTECTED]> 25-Jun-00 5:17:27 PM
>>>
>We want this test because we discovered by accident that
>our product will loop on 97% CPU when it tries to connect to
>a server and the server immieidetly shuts the connection down
>(familiar problem to anyone who ever writen some system-level
>server stuff, already fixed). Since our phylosophy is to turn
>each bug into a (automatic) test case we want to add this to
>our regression tests.
I see... I think you're wrong but I can see where you're coming
from.
>I'd suspect that a non-HTTP servlet might help to circumnavigate
>around the automatic handling of HTTP connections, but I don't
>see how can I setup such a servlet, if at all.
No. That's not possible. Servlets have no life of their own - a
container is everything to them.
There is only one non-HTTP implementation of the API that I am aware
of and that is the Apache James project (a Mail implementation using
Servlets). It wouldn't be of any use to you.
>Any ideas?
What you want to do MUST be performed by the container. You need to
get the source for a container and adapt it to shut the connection
down instead of responding (possibly on the basis of the requestpath
or something).
If I did want to do this I would get Jserv, Jigsaw or GNU-Paperclips
and alter the source code to do what I wanted.
You would need to run the container stand alone as anything hanging
off a webserver might be subject to the webserver responding for it.
I think this is the *only* way you're going to be able to do it.
(I still think you're crazy though /8-)
Nic
___________________________________________________________________________
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
