<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
Hi Scott<br>
<br>
thank you for your time. I understand that there's an ODBC resource
problem, and that the best option is not to use SP session at all
once the app has its session. But what about the shared shibd? What
I do not understand is that "<i>the remoting was not meant to work
across machines</i>". The Wiki recommends that many machines can
share a common shibd. What if I put a load balancer in front of two
shibd's and, if the active fails, the LB switches over to the
passive? I understand all sessions from the active shibd node will
be lost then, but I could live with that.<br>
<br>
Cheers,<br>
Martin<br>
<br>
<br>
<div class="moz-cite-prefix">Am 22.01.2014 15:49, schrieb Cantor,
Scott:<br>
</div>
<blockquote cite="mid:CF0543BE.480FD%25cantor.2@osu.edu" type="cite">
<pre wrap="">On 1/22/14, 4:30 AM, "Martin Haase" <a class="moz-txt-link-rfc2396E" href="mailto:Martin.Haase@DAASI.de"><Martin.Haase@DAASI.de></a> wrote:
</pre>
<blockquote type="cite">
<pre wrap="">
thanks for this one. No, we had not reported the bug yet to Ubuntu, but
looks like we're forced to now. The application (moodle) ist clustered
via some mySQL DBs and an haProxy on each machine. There's another
CGI-based application clustered via shared NFS. Both of them are
protected by the SP. As far as I can see, Apache worker is not an
option, it's PHP again, where worker is (at least used to be, we'd have
to check) not thread safe.
</pre>
</blockquote>
<pre wrap="">
That means it's likely to be your problem, not a bug. The stack trace
suggested a mutex exhaustion issue, so short of maybe increasing kernel
resource counts, you have to avoid the thread explosion. If you use PHP,
then you need to get it out of process to avoid their bugs.
</pre>
<blockquote type="cite">
<pre wrap="">What about the idea I mentioned, a failover via the TCPListener, do you
see this is an option?
</pre>
</blockquote>
<pre wrap="">
No. You will not find that it scales, the remoting was not meant to work
across machines. It slows applications with a lot of requests per page to
a crawl, a factor of 10 or more. Unless you don't use the SP session for
anything, which is the best choice actually. Use it to establish the app
session and then get it out of the way.
-- Scott
--
To unsubscribe from this list send an email to <a class="moz-txt-link-abbreviated" href="mailto:users-unsubscribe@shibboleth.net">users-unsubscribe@shibboleth.net</a>
</pre>
</blockquote>
<br>
<pre class="moz-signature" cols="72">--
Dr. Martin Haase, Solutions Engineer
DAASI International GmbH
Europaplatz 3
D-72072 Tübingen
Germany
phone: +49 7071 407109-6
fax: +49 7071 407109-9
email: <a class="moz-txt-link-abbreviated" href="mailto:martin.haase@daasi.de">martin.haase@daasi.de</a>
web: <a class="moz-txt-link-abbreviated" href="http://www.daasi.de">www.daasi.de</a>
Sitz der Gesellschaft: Tübingen
Registergericht: Amtsgericht Stuttgart, HRB 382175
Geschäftsleitung: Peter Gietz
</pre>
</body>
</html>