Forum: Bug Report and Feature Requests

"Too Many Concurrent Accesses"

eg5305 🚫

I retired from managing a site that has very unpredictable load, and I still consult to them. I was wondering how SOL manages the Too Many Concurrent Accesses message.

I wanted to send a private note the Lazeez, but can't really figure out how, so perhaps I can ask here, and I'll be happy to get an answer either here or privately.

I need a method that will review back end services like database and offline cache, and flip a switch on the web servers to deny new sessions.

While I can probably come up with something on my own, I would be happy not to reinvent the wheel.

Lazeez? Can you reach out to me?

Thanks,
Ed Greenberg

Replies: jimq2 Gauthier Lazeez Jiddan (Webmaster)

jimq2 🚫

@eg5305

Upper right corner of the home page "Contact"

Gauthier 🚫

@eg5305

Too Many Concurrent Accesses

SOL implementation isn't a real concurrent access detection and prevention system.
You can trigger it only by loading multiple chapter list rapidly. My guess is that it's just a last request time saved in the server session. if not enough time has elapsed, it reply with a 503 thus bypassing mysql access and saving server resources. It only make sense if the limiting factor are database reads. With mySQL replicas, it shouldn't be the case.

I need a method that will review back end services like database and offline cache, and flip a switch on the web servers to deny new sessions.

That's a bit harsh, usually in constrained system, like sales tunnel you implement a queue and let the user know (count down) when it can attempt the purchase. That prevent a lot of user refreshing 503 pages which could be even more problematic.

Lazeez Jiddan (Webmaster)

@eg5305

I retired from managing a site that has very unpredictable load, and I still consult to them. I was wondering how SOL manages the Too Many Concurrent Accesses message.

it's fairly simple.

Whenever a reader accesses a story, the system sets a cached bit of info containing the reader's id, and the story's id for 15 seconds. It only allows accesses to this story while the cache is valid.

Every time there is a new story/chapter request, the delivery system checks for this cached data and if it exists, and the story id is different, then it throws the error, otherwise, it refreshes the cache and delivers the requested text.

It helps restrict automated downloads to one story at a time.

Replies: Dinsdale samuelmichaels spam.mc+a2

Dinsdale 🚫

@Lazeez Jiddan (Webmaster)

So if I accidentally click on the wrong story on my phone, then back out and get the correct one, I have to wait a few more seconds. Call it delayed gratification. The alternative approach is borrowed from a couple of Jay Cantrell stories - "I'm a lawyer, I want what I want when I want it".
Sometime I'll right-click on a few stories and open them in new tabs, typically when I've been away for a few days. Some of the tabs get that message so I refresh them when I get to that story.

samuelmichaels 🚫

@Lazeez Jiddan (Webmaster)

It helps restrict automated downloads to one story at a time.

A neat approach.

spam.mc+a2 🚫
Updated:

@Lazeez Jiddan (Webmaster)

I often accidentally trigger this on my android tablet when I have multiple tabs open looking at different stories. I think android kills off the browser process fairly often when it doesn't have focus. When I switch back to it, it reloads all the tabs in parallel and triggers the too many concurrent sessions alert. Please don't ban me!

Replies: Dinsdale

Dinsdale 🚫

@spam.mc+a2

I had it yesterday afternoon on my Android phone.
I read one chapter of story, backed out of it (and the index) and clicked on the index of the other story that interested me. It appears that the index is treated as a normal page of the story, so backing out made the index of story 1 current which meant it was 15 seconds before I got to the second index.
At least I knew exactly what was going on.

Replies: madnige

madnige 🚫

@Dinsdale

It appears that the index is treated as a normal page of the story

True that - which is why I try to use the [More Info] link, as that's a special page.

Reply to topic

Forum: Bug Report and Feature Requests

"Too Many Concurrent Accesses"

WARNING! ADULT CONTENT...