|
Home > Archive > IIS Server > January 2005 > 403 Access Forbidden
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
403 Access Forbidden
|
|
| cipher 2005-01-29, 2:47 am |
| I have a .NET web service running on IIS. The client is a Java applet. The
client calls a method on the server every few seconds. When running the
client in IE 6, it gradually uses up all available IIS connections (limit is
set to 10, but have tried it at 40 with same results) resulting in a 403
Access Forbidden exception. When I run the client in appletviewer, it never
uses more than 1 connection and runs perfectly. Is there a way to limit the
number of connects IE 6 will use or some settings in IIS or the web service
that will control this? Thanks.
| |
| Kristofer Gafvert 2005-01-29, 2:47 am |
| Hello,
As far as i know IE uses only two connections because that is what the RFC
recommends. What is the substatus code of the 403 error message? Are you
sure it is 9 "Too many users"? (nothing in your post verifies that this is
the problem).
I am not however sure how a Java applet works. If you (the programmer of
the Java applet) is responsible for opening and closing connections, or if
IE manages this. A guess is that the Java applet controls this.
--
Regards,
Kristofer Gafvert
www.gafvert.info - My Articles and help
www.ilopia.com
cipher wrote:
> I have a .NET web service running on IIS. The client is a Java applet.
The
> client calls a method on the server every few seconds. When running the
> client in IE 6, it gradually uses up all available IIS connections
(limit is
> set to 10, but have tried it at 40 with same results) resulting in a 403
> Access Forbidden exception. When I run the client in appletviewer, it
never
> uses more than 1 connection and runs perfectly. Is there a way to limit
the
> number of connects IE 6 will use or some settings in IIS or the web
service
> that will control this? Thanks.
| |
| cipher 2005-01-29, 5:54 pm |
| The Java exception doesn't have a substatus code which is why it took so
long to discover the problem. It is the "Too many users" exception - I
varified this two ways. Watching the number of connections gradually climb
to the limit set in IIS and as soon as it tries to exceed this limit, the
exceptions start spewing in the Java console. After this happens, if I try
to connect to the server with another browser (different machine), it tells
me there are "too many users".
For a Java applet to use a .NET web service, all that needs to be done is
run a Java tool that generates stub objects from the web service's asmx file
(wsdl). Then instantiate an instance of the stub object and call it's
methods. I only create one instance of the stub object. It does not
appear to be a problem with the Java applet because as I stated in my
original post, this problem only happens when run in IE. Run the applet in
AppletViewer.exe and it only consumes 1 connection to IIS and runs
perfectly. If it was the applet causing the problem, it would manifest
itself regardless of host application.
"Kristofer Gafvert" <kgafvert@NEWSilopia.com> wrote in message
news:xn0dxtsmb78ga15018@news.microsoft.com...[vbcol=seagreen]
> Hello,
>
> As far as i know IE uses only two connections because that is what the RFC
> recommends. What is the substatus code of the 403 error message? Are you
> sure it is 9 "Too many users"? (nothing in your post verifies that this is
> the problem).
>
> I am not however sure how a Java applet works. If you (the programmer of
> the Java applet) is responsible for opening and closing connections, or if
> IE manages this. A guess is that the Java applet controls this.
>
>
> --
> Regards,
> Kristofer Gafvert
> www.gafvert.info - My Articles and help
> www.ilopia.com
>
>
> cipher wrote:
>
> The
> (limit is
403[vbcol=seagreen]
> never
> the
> service
|
|
|
|
|