Jump to content

ives.stoddard

Members
  • Posts

    3
  • Joined

  • Last visited

ives.stoddard's Achievements

Newbie

Newbie (1/14)

  • Week One Done
  • One Month Later
  • One Year In
  • First Post Rare

Recent Badges

0

Reputation

  1. Hello Erez. Were you ever able to find a solution for this? I'm trying to do something similar (update datasource credentials programmatically for password rotation.
  2. We can run and connect to Tomcat's JMX port (8999) without issue. We can't seem to connect to the default 10990 for JasperServer however. We see the port is running, but no combinations of config allow us to connect jconsole to jasperserver on port 10990. We're on 611, but switching versions of documentation on this site is a pain. Docs from 550 seem to be similar: https://community.jaspersoft.com/wiki/jconsole-and-jasperreports-server https://community.jaspersoft.com/documentation/jasperreports-server-administration-guide/v550/exposing-diagnostics-through https://community.jaspersoft.com/documentation/jasperreports-server-administration-guide/v550/real-time-diagnostics https://community.jaspersoft.com/wiki/video-troubleshooting-jconsole-connections-jmx
  3. @ssturdivant: wouldn't this mean nobody, other than the report requestor, can check report status via the API? We have a problem where large reports are crashing jasper. Trying to sort out the best way to monitor long-running requests. On jasper 6.1, I can query the current reports via "/jasperserver-pro/rest_v2/reports" or "/jasperserver-pro/rest_v2/reportExecution". Both return the same information, an array of currently running reports with both report id & report uri. When making a follow-up call (keeping jsessionid), I also get HTTP 204 / "No Content". What would be the preferred method for a sensu monitor to obtain report details for a running report, so it could be correlated with date/time started, execution duration, etc.?
×
×
  • Create New...