PC SOFT

GRUPOS DE DISCUSSÃO PROFISSIONAL
WINDEVWEBDEV e WINDEV Mobile

Inicio → WINDEV 2024 → error too many visitors
error too many visitors
Iniciado por guest, abr., 14 2014 1:26 PM - 16 respostas
Publicado em abril, 14 2014 - 1:26 PM
Sometimes when I want open my CMS www.kb-actief.be or www.kba-tv.be there is an error too many connections. More than 10.

I use the wepserver from Webdev and everything is set to more than 100 users.

The error is produced by IIS. I can not find a setting in IIS. Someone an idea what is going on.

Thanks

Willy.
Publicado em abril, 14 2014 - 1:47 PM
Hi Willy

the fact that you mention 10 users make me ask you this:

Are you sure that you installed the FULL ($$$) version of the wbedev server and not the free one, which is limited to 10 concurrent users?

Best regards
Publicado em abril, 14 2014 - 1:51 PM
Maybe a bit offtopic, but this makes me wonder (i never used WebDev). What is a user. Because HTTP is stateless this is not easy to define.

My guess would be: request from different sources (internet IP's) within a given timeframe.
Publicado em abril, 14 2014 - 3:47 PM
Hi Pim,

An active WebDev session is counted as a user.

To run dynamic serverside WB pages/sites you need a WebDev application server to run on your webserver and if you count on more then 10 concurrent 'users' this server cost you about 300,- euro's.
Publicado em abril, 14 2014 - 3:53 PM
Thanks for the replay Peter. Feels a bit like that i am hijacking the topic (sorry for that).

Is there any control about the length of the session? This could help to stretch the limit a bit ;) (If i would write a API in this could i set the timeout to 60 seconds or less. Or is there a under limit/special impact when doing this?)
Publicado em abril, 14 2014 - 4:00 PM
Hi Pim

The answer is different depending on the type of site:
- in classic mode, webdev keeps a session open in memory for each user (and the URL indicates the session number)... Number of sessions in memory=number of users... If you reduce the time out to 60 seconds and a user stays on a page for more than that (very easy), he will be DISCONNECTED... So, not a good idea.
- in awp mode, there is no session kept on the server, so the time out doesn't apply. so number of users = number of requests done at any given time. As one browser session can generate multiple request at the same time using ajax, by example, you can reach the 10 users limit with just ONE physical user.
- in php mode, I have no clue, as I managed till now to always avoid it, for tons of reasons.

Best regards
Publicado em abril, 14 2014 - 4:13 PM
Fabrice thanks for the replay, bottom line: U need a payed license for every production site server :D.

What happens when the user get's disconnected. I can image that when a user loses it's session but for a lot of sites the user would not even see that (assuming the user is not logged in). And even that u could faked by setting a cookie. (just wondering :D).
Publicado em abril, 14 2014 - 5:10 PM
I have already installed the application server. With the local taxes it was about €400. So that is the one mentioned here.

But when I look at the about button I can see no difference with the other (test)server with the 10 connections version of the application server.

Now at this moment there are 17 connections.

Often I see that an IP adress that is several times in the connection list.

I use a function "maintain session" to avoid that users are canceled. That works fine

It is a website with a timer. Every screen is a predefined number of seconds in the picture. Then the next screen is his predefined seconds in the picture.

I hope this extra information will define the problem more detailed.

Thanks
Willy Hermans
Publicado em abril, 14 2014 - 5:10 PM
Hi Pim

yes, if you need to manage a lot of user on a dedicated server. otherwise, you can get a webdev hosting (shared) for a few euros/month.

When a use is disconnected, newt time he tries to do anything server side, he gets a nice and shiny error page stating that his sessions was disconnected, has to restart a session, and redo everything from scratch. Basically the same thing that if a windev program crashed.

in awp mode, of course, no such problem,

Best regards
Publicado em abril, 14 2014 - 7:29 PM
Hi Willy

could you paste here the EXACT error message that you are getting ? It will probably tell us more than you think.

On another hand if you do have 17 connections, it's not coming from the free version limit, that's for sure.

An IP several times in the connection list can be perfectly normal (several users at the same place, or simply several sessions in the same browser, or user quit, then came back and created a new session, etc...)
Publicado em abril, 14 2014 - 11:17 PM
The error screen is in Dutch. I think most of us does not understand it.
But maybe the HTTP 403.9 could mean something.
Is it possible that the cause is a time out. The upload speed is only 8 mbit.

Thanks,
Willy

De pagina kan niet worden weergegeven
Er zijn op dit moment te veel aanvragen voor toegang tot de website.
Ga als volgt te werk:
•Klik op de knop Vernieuwen of probeer het later opnieuw.
•Open de 213.219.133.230 introductiepagina en kijk of er koppelingen zijn naar de gewenste informatie.
HTTP 403.9 - Toegang verboden: Te veel gebruikers
Internet Information Services
Technische informatie (voor ondersteuningsmedewerkers)
•Achtergrondinformatie:
Deze fout kan optreden als de webserver bezet is en de aanvraag niet kan worden verwerkt omdat er te veel verkeer is.
•Meer informatie:
Ondersteuning van Microsoft
Publicado em abril, 14 2014 - 11:50 PM
Willy,

The page u pasted is the default error page of IE when u get a errorcode on http (it does differ a small bit depending on the http code returned).

The HTTP code 403.9 is the code for too many users. See: http://en.wikipedia.org/wiki/HTTP_403. So my guess is u do not have the payed version active.

Pim
Publicado em abril, 15 2014 - 10:13 AM
what windows are you using ?
Publicado em abril, 15 2014 - 10:29 AM
It is a testserver with Win XP 32 bit

The definitive version is not decided. Maybe I will use the cloud from PC Soft. I am waiting for the pricing. Otherwise it will become a VPS. And then I presume it will be the latest Windows.

Greetings,
Willy
Publicado em abril, 15 2014 - 10:35 AM
Willy,

It's a problem with IIS, not WebDev.
http://support.microsoft.com/kb/262635
Publicado em abril, 15 2014 - 10:39 AM
Oeps,

I was not aware of the limits.

I still have an W2003 server in the box. I will try this for testing.

Thanks,
Willy
Publicado em abril, 15 2014 - 12:21 PM
If the problem is only wtih the web engine, you can try to stop the IIS on the xp machine, install apache on it and run your app based on apache instead of IIS.