On Fri, 30 May 2014, Marvin Addison wrote:
I think the
underlying problem in the code is that @Transaction annotations were
placed at the wrong layer, on the methods in class
CentralAuthenticationServiceImpl.
+1
Your analysis and solution are probably the best evidence we have for
that claim. I recall having made a similar suggestion in the past, but
I didn't have a sound argument at the time. I believe your problem and
solution provide the evidence we need to move forward with a fix in
the next release of CAS. I would appreciate your filing a Jira issue
to make the change you suggested and citing this thread as a
reference.
Thanks for your persistence working through this issue and sharing the
result. Hopefully it will lead to a fix for this long-standing issue.
My testing hasn't indicated any problems with my workaround (transactions
only on the delete() and save() methods). Do you think that is a safe
workaround for this issue? At least in my simple configuration, I can't
see a reason to have transactions on anything else.
I really need this workaround because I have some maintenance to perform
on our MySQL server. If that is going to cause a CAS outage, then the
impact of the MySQL maintenance will be much larger!
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
