Hello again,
I can finally come up with a patch (attached) that solves the issue for
me. Anyone mind to point out potential concerns regarding the patch?
Explanation:
After some debugging-mess with printing the memory addresses, I noticed
that the workers grab a slot even if they did that before
Hi,
that bug is reported. https://issues.apache.org/bugzilla/show_bug.cgi?id=52402
There is no solution with vhosts yet.
Cheers
Mario
Hi Mario,
Thanks for the hint - this seems indeed to be a duplicate: Two creations
of 's96f9938e_mycluster' - second grab fails.
I will now monitor that.
Unfortunately, I'm not sure about the ap_proxy_share_balancer/_worker(),
attach(), and the reference by conf-id semantics. Wouldn't a simple
Hi together,
I'm trying to get my reverse-proxy running with the new httpd 2.4.1,
that aborts now with worker slotmem_grab failed.
When looking at mod_proxy_balancer:
It looks like each balancer creates the SHM for its number of workers (1
in my case) using its unique -sname. After that, each
