Fail to add new schedule via the reports admin under control panel.

• Type: Bug
• Status: Closed
• Resolution: Fixed
• Affects Version/s: 6.1.30 EE GA3, 6.2.0 CE M5
• Fix Version/s: 6.1.30 EE GA3, 6.2.0 CE M6
• Component/s: Business Productivity, Business Productivity > Reporting > API, Business Productivity > Reporting > Jasper
• Labels:
  • QA-R
  • QA-TP
• Environment:
  Hide

  Tomcat 7.0 + MySQL 5. Portal 6.1.x.EE GIT ID: 9300078d3cc684e4d96a87967da62bb1e84b4270. ; Plugin 6.1.x EE GIT ID: 8082260527cb80b751bb99f89530c793369a5fc4. ; Tomcat 7.0 + MySQL 5. Portal 6.2.x GIT ID: 4474b0e18f4469cae06b12cf8615f46a01a407e7. ; Plugin 6.2.x EE GIT ID: 09a370c07c2543489d1475f30574e075d05fd720.

  Show

  Tomcat 7.0 + MySQL 5. Portal 6.1.x.EE GIT ID: 9300078d3cc684e4d96a87967da62bb1e84b4270. Plugin 6.1.x EE GIT ID: 8082260527cb80b751bb99f89530c793369a5fc4. Tomcat 7.0 + MySQL 5. Portal 6.2.x GIT ID: 4474b0e18f4469cae06b12cf8615f46a01a407e7. Plugin 6.2.x EE GIT ID: 09a370c07c2543489d1475f30574e075d05fd720.
• Branch Version/s:
  6.1.x
• Backported to Branch:
  Committed
• Story Points: 8
• Fix Priority: 4
• Git Pull Request: https://github.com/brianchandotcom/liferay-plugins-ee/pull/1929

Steps to reproduce:

1. Start Liferay bundle.
2. Make the reports-portlet war file.
3. Deploy the war file to Liferay. This also need the jasperreports-web war file.
4. Go to Site Administration > Reports Admin (in 6.1 and previous Control Panel -> Reports Admin)
5. Go to the tab called: Definitions and add a new report definition.
6. Click the Action button after the new added report definition.
7. Click Add Schedule.

Expected result:
Add Schedule can be clicked without any stacktrace.
Actual result:
A stacktrace like the attach file show on the console when clicking at Add Schedule with a reminder said:"Reports Admin is temporarily unavailable. ".