On Fri, 15 Mar 2013, Marvin Addison wrote:
The error trace in the browser leads me to believe it has something to do
with creating a TGT:
...
But my tickets are stored in memcache, not MySQL...
Are you using Inspektr for auditing and logging to database? If yes
that would explain the involvement of database. You could use the
Slf4jLoggingAuditTrailManager to confirm this theory; if you switch
and the problem disappears, that would be confirmation.
I'm already using Slf4jLoggingAuditTrailManager.
All signs indicate a networking issue, though what exactly I can't say.
I ran a packet capture of the traffic between the CAS server and the MySQL
server while I submitted a login request to CAS. This was done under
normal conditions, not while iptables is rejecting the traffic.
The packet capture showed this series of MySQL queries:
SET autocommit=0
commit
SET autocommit=1
SET autocommit=0
commit
SET autocommit=1
Once again, this is my dataSource bean:
<bean id="dataSource" class="com.mchange.v2.c3p0.ComboPooledDataSource"
p:driverClass="com.mysql.jdbc.Driver"
p:jdbcUrl="jdbc:mysql://<redacted>.oregonstate.edu:3306/cas?autoReconnect=true"
p:user="cas"
p:password="<redacted>"
p:initialPoolSize="5"
p:minPoolSize="5"
p:maxPoolSize="10"
/>
Perhaps there is some behavior around autocommit that is biting me?
Thanks,
Andy
--
You are currently subscribed to [email protected] as:
[email protected]
To unsubscribe, change settings or access archives, see
http://www.ja-sig.org/wiki/display/JSG/cas-user
