We have several reports running in production and a user recently reported that the drill down reports are now hanging in Internet Explorer.
Upon further investigation, I was able to reproduce, and found that it is the .../reportExecution/.../status call that is causing the issue. Running the same report in Chrome & Firefox, this call takes < 40 ms. In IE (9, 10, 11) this call takes almost 60 seconds.
Has anyone else experienced this problem lately?
Details: Jasper Pro version 6.1.1 with Visualize.js, running within an AngularJS application
| URL | Protocol | Method | Result | Type | Received | Taken | Initiator | Wait | Start | Request | Response | Cache read |
| /jasperserver-pro2/rest_v2/reportExecutions | HTTPS | POST | 200 | application/json | 342 B | 312 ms | XMLHttpRequest | 2949 | 109 | 0 | 203 | 0 |
| /jasperserver-pro2/rest_v2/reportExecutions/4d5.../exports | HTTPS | POST | 200 | application/json | 213 B | 47 ms | XMLHttpRequest | 3261 | 0 | 0 | 47 | 0 |
| /jasperserver-pro2/rest_v2/reportExecutions/4d5.../exports/c2.../outputResource | HTTPS | GET | 200 | text/html | 0.76 MB | 3.01 s | XMLHttpRequest | 3308 | 0 | 2995 | 15 | 0 |
| /jasperserver-pro2/getReportComponents.html | HTTPS | POST | 200 | application/json | 15.32 KB | 0.70 s | XMLHttpRequest | 6568 | 0 | 0 | 468 | 234 |
| /jasperserver-pro2/rest_v2/reportExecutions/4d5.../status | HTTPS | GET | 200 | application/status+json | 238 B | 58.43 s | XMLHttpRequest | 8549 | 0 | 58438 | 0 | 0 |
| /jasperserver-pro2/rest_v2/reportExecutions/4d5… | HTTPS | GET | 200 | application/json | 0.51 KB | 156 ms | XMLHttpRequest | 66987 | 78 | 78 | 0 | 0 |
1 Answer:
Solved the problem thanks to a user from another thread: http://community.jaspersoft.com/questions/988721/visualizejs-610-report-...
The solution was to disable the jiveUI features (sorting, filtering, etc.) from the table in the drill down.
_reportService.report({
resource: uri,
container: containerId,
defaultJiveUi: { enabled: false },
runImmediately: false,
events: {
changeTotalPages: function(totalPages) {
EventService.pub("PAGE_COUNT_CHANGED", {pageCount: totalPages, container: containerId});
}
},
linkOptions: {
events: {
"click": function(evt, link){
_fireReportClickEvent(evt, link);
}
}
},
error: function (err) {
_handleError("An error occurred while attempting to load the list of reports. " + err.message, err);
}
});
