...
[18:11:05 CDT(-0500)] <dmccallum54> thx
[18:12:18 CDT(-0500)] <JasonElwood> Has anybody noticed a slower response within your local SSP this week? It is noticeably slower since Monday.
[18:14:25 CDT(-0500)] <dmccallum54> during app load or everywhere?
[18:14:42 CDT(-0500)] <JasonElwood> pretty much everywhere
[18:15:07 CDT(-0500)] <JasonElwood> except Manage Users
[18:16:22 CDT(-0500)] <dmccallum54> a change went in on tuesday that keeps database connections open slightly longer
[18:16:56 CDT(-0500)] <dmccallum54> did CI slow down too?
[18:17:46 CDT(-0500)] <dmccallum54> not that it has all the 1.2 changes, of course
[18:17:51 CDT(-0500)] <JasonElwood> I really haven't used CI much because it's been flaky
[18:18:06 CDT(-0500)] <dmccallum54> heh
[18:18:27 CDT(-0500)] <JasonElwood> I haven't spent the time to figure it out pushing towards the release. It will take some time to get some useful external data in there
[18:51:20 CDT(-0500)] <js70> The SSP-688 error showcases that reports are not part of the ext.js app. just a jsp page that submits.
[18:52:18 CDT(-0500)] <JasonElwood> so is there any way to catch the timeout like the ext.js does?
[18:52:41 CDT(-0500)] <dmccallum54> yes
[18:53:42 CDT(-0500)] <JasonElwood> and reasonably easy and quick
[18:53:57 CDT(-0500)] <dmccallum54> you get a 403 in this case i think
[18:56:25 CDT(-0500)] <dmccallum54> would have to either… change all the forms to ajax submits or modify the error page that generates the 403 json to "do something else".
[18:56:41 CDT(-0500)] <dmccallum54> the latter is pretty squishy and isn't really going to be pleasant
[18:57:26 CDT(-0500)] <dmccallum54> for the user i mean
[18:59:44 CDT(-0500)] <dmccallum54> there are jquery plugins for the former (http://www.malsup.com/jquery/form/)
[19:00:14 CDT(-0500)] <dmccallum54> not sure how well that's going to work with our PDF responses
[19:01:45 CDT(-0500)] <dmccallum54> might have to monkey with the headers being set server side
[19:02:16 CDT(-0500)] <dmccallum54> so anyway… maybe an hour or so to see if it's even feasible
[19:03:32 CDT(-0500)] <dmccallum54> "it" being submitting forms via ajax, correctly offering to download resulting PDFs, handling error codes gracefully, and special handling for 403 to offer to redirect to login
[19:09:27 CDT(-0500)] <js70> we don' have a 403 jsp page, I'm pretty sure its bringing back the 500. not a big deal but we need to create the 403 as well.
[19:10:56 CDT(-0500)] <dmccallum54> think it might not be using any of the jsp pages
[19:11:06 CDT(-0500)] <dmccallum54> @PreAuthorize(Permission.PERMIT_ALL)
[19:11:06 CDT(-0500)] <dmccallum54> @ExceptionHandler(AccessDeniedException.class)
[19:11:06 CDT(-0500)] <dmccallum54> @ResponseStatus(HttpStatus.FORBIDDEN)
[19:11:06 CDT(-0500)] <dmccallum54> public @ResponseBody
[19:11:06 CDT(-0500)] <dmccallum54> ServiceResponse handleAccessDenied(final AccessDeniedException e) {
[19:11:06 CDT(-0500)] <dmccallum54> getLogger().error(ERROR_PREFIX, e);
[19:11:06 CDT(-0500)] <dmccallum54> return new ServiceResponse(false, e.getMessage());
[19:11:07 CDT(-0500)] <dmccallum54> }
[19:11:34 CDT(-0500)] <js70> k
[19:12:00 CDT(-0500)] <js70> makes sense
[19:12:48 CDT(-0500)] <dmccallum54> trying to use a page seems a little weird in this case, esp if we're going to try to pretty it up
[19:13:23 CDT(-0500)] <dmccallum54> b/c again you're hitting an API and it's barfing. it's not a web page that's barfing where it would make sense to send you to a nice pretty 'sorry about that' page
[19:13:31 CDT(-0500)] <js70> yeah, I like your jquery form suggestion. if it works should be fairly simple to implement.
[19:18:01 CDT(-0500)] <dmccallum54> isn't that always the story 
[19:18:44 CDT(-0500)] <dmccallum54> alright. i gotta run. daycare pickup calls again.