Just to provide a little more info, it does lock up and continuously error on that record in 4.0, fixed in 4.1. You can see that fix here: https://github.com/Jasig/uPortal/commit/e21c18f1038ceea2083c44076aaf0ea7221750b8. We just made the change to master since it involved a DB change.
- Tim ________________________________ From: bounce-35646735-70367...@lists.wisc.edu <bounce-35646735-70367...@lists.wisc.edu> on behalf of James Wennmacher <jwennmac...@unicon.net> Sent: Monday, July 7, 2014 1:48 PM To: uportal-dev@lists.ja-sig.org Subject: Re:[uportal-dev] https://issues.jasig.org/browse/UP-3899 Opening up to a broader discussion among uportal-dev because it begs more wisdom than I have. :-) Though a rare operational error, it causes event aggregation to fail. I'm not sure if it skips the bad record(s) or just locks up and continuously fails on that record. What is the downside of incorporating the change into uPortal 4.0? Does something special have to occur to update the database? I believe the user would need to run an additional ant command to update the database and I'm not familiar with whether we have to do something special to get it so ant knows how to update the DB. Of course we'd have to make note that a database update is needed in the patch release notes. Thoughts from others on whether to incorporate this into 4.0 and effort required? James Wennmacher - Unicon 480.558.2420 On 07/07/2014 11:29 AM, Tim Levett wrote: Hi James, I did not apply it to 4.0 because it is a database change which is kind of frowned upon I thought. An easy fix is to update the old record in UP_AGGR_PORTLET_MAPPING so that the new record can be inserted. - Tim ________________________________ From: James Wennmacher <jwennmac...@unicon.net><mailto:jwennmac...@unicon.net> Sent: Monday, July 7, 2014 11:54 AM To: Tim Levett Cc: Andrew Petro Subject: https://issues.jasig.org/browse/UP-3899 Hi Tim. Did you have a chance to look into adding https://issues.jasig.org/browse/UP-3899 to uPortal 4.0.x? The change looks straight forward and useful. What I'm not sure about is if anything special needs to occur related to updating the database schema. -- James Wennmacher - Unicon 480.558.2420 -- You are currently subscribed to uportal-dev@lists.ja-sig.org as: tim.lev...@wisc.edu To unsubscribe, change settings or access archives, see http://www.ja-sig.org/wiki/display/JSG/uportal-dev -- You are currently subscribed to uportal-dev@lists.ja-sig.org as: arch...@mail-archive.com To unsubscribe, change settings or access archives, see http://www.ja-sig.org/wiki/display/JSG/uportal-dev
