Jump to content
We've recently updated our Privacy Statement, available here ×

Jasperserver stops working 502 Bad Gateway


nicknxswart.nl

Recommended Posts

When I check the error log I see:

2021-09-16 09:38:22,406 ERROR SecureExceptionHandlerImpl,pool-5-thread-289:116 - There was an error on the server. Try again or contact site administrators. (Error UID: daf28a1e-52a0-4d29-863b-4566a0d7cf3a)

2021-09-16 09:40:03,990 ERROR SecureExceptionHandlerImpl,pool-5-thread-290:116 - There was an error on the server. Try again or contact site administrators. (Error UID: 35507256-efeb-419b-b3ad-26167210cba8)

2021-09-16 09:41:57,231 ERROR SecureExceptionHandlerImpl,pool-5-thread-292:116 - There was an error on the server. Try again or contact site administrators. (Error UID: 1cd808fa-df3f-42b2-b92b-92dbd0b0123f)

After that jasperserver stops working and when I go to the url I know see: 502 Bad Gateway

Any idea what could cause this crash or how I could find out?

Link to comment
Share on other sites

  • Replies 1
  • Created
  • Last Reply

Top Posters In This Topic

Top Posters In This Topic

These errors provide generic messages so not much can be deduced out of them. The "502 bad gateway" error usually relates to a proxy or load balancer that perhaps failed a redirect request. The first thing to check is whether the app server (commonly Tomcat server) starts up fine without errors and whether you can log in directly to the JR Server using its native ports of 8080 (default). You can also use the browser's dev console (F12) to trace the requests or inspect the http access log.

 

 

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

×
×
  • Create New...