-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Well, the crashes are still occuring. I have set up a workaround for our
other SSL issues, and this bug is still around.
Any other suggestions on what to check?
Jeff
Jeff Chapin wrote:
We are still deploying and moving towards launch. At the
Hi Corey,
That is exactly how we do it. Terminate SSL at the F5.
A couple of things to be aware of.
If you are planning on issuing ProxyTickets each or the cas servers behind
the F5 will need to have ssl enabled because they will be calling back into
the cas client ofer https.
If you
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I have rolled an instance of CAS 3.3.5 into a test instance. We have
started to tie a few apps to this instance, and CAS has begun randomly
crashing, sometimes as often as several times a day, and not always when
under load much load. As little as one
A first glance, it looks like something to do with SSL perhaps. Are you
using Tomcat? Are you offloading SSL or is you container handling it?
On Thu, Apr 1, 2010 at 7:57 AM, Jeff Chapin jeff.cha...@uni.edu wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I have rolled an instance of
As far as having the F5 front the CAS servers (assuming a CAS cluster of
2 in your stack?) and perform the SSL termination, I gather that this is
a common way to offer the CAS service.
As CAS newbies, we are just building out our CAS deployment here, with
an SSL-offload configuration with our
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
We are still deploying and moving towards launch. At the moment we do
*not* have a cluster running. That is slated for phase 2 of the process,
and is the first feature to be added once the single node install is
working correctly.
I have redeployed,
