optimize: Response header too large

Camunda 8 Topics
1

after save the new report, i can not access the web page. it show the HTTP ERROR 500.

I got the in logs:
09:47:23.146 [qtp945899637-21] WARN o.eclipse.jetty.server.HttpChannel - handleException /optimize/ org.eclipse.jetty.http.BadMessageException: 500: Response header too large

I NEED HELP!

2

Hey naikun,

have pointed the same error without any interaction. For me the problem with 500 was solved by deleting the cookie and authenticate again (works for 4 minutes untill token expiration)
Have opened an issue on the platform project optimize: BadMessageException: 500: Response header too large · Issue #560 · camunda/camunda-platform · GitHub maybe it helps you and the team somehow :slight_smile:

Regards
Andrej

1 Like
3

Hey there! Do you have any updates on this?
All my containers are healthy, but Optimize - in spite of being healthy - is not working. Sometimes when I open a fresh browser tab, it redirects me to the keycloak login page. But after login, it goes down.
The container logs say:

14:07:14.115 [qtp946833587-20] WARN  o.eclipse.jetty.server.HttpChannel - handleException / org.eclipse.jetty.http.BadMessageException: 500: Response header too large
14:07:14.436 [qtp946833587-22] WARN  o.eclipse.jetty.server.HttpChannel - handleException / org.eclipse.jetty.http.BadMessageException: 500: Response header too large
14:07:14.803 [qtp946833587-20] WARN  o.eclipse.jetty.server.HttpChannel - handleException / org.eclipse.jetty.http.BadMessageException: 500: Response header too large
14:07:18.142 [ZeebeImportScheduler-1] INFO  o.c.o.s.i.z.m.ZeebeProcessDefinitionImportMediator - Records of type PROCESS from partition 1 imported in page: 0
14:07:18.191 [ZeebeImportScheduler-1] INFO  o.c.o.s.i.z.m.ZeebeProcessInstanceImportMediator - Records of type PROCESS_INSTANCE from partition 1 imported in page: 0
14:07:18.250 [ZeebeImportScheduler-1] INFO  o.c.o.s.i.z.m.ZeebeVariableImportMediator - Records of type VARIABLE from partition 1 imported in page: 0
14:07:18.305 [ZeebeImportScheduler-1] INFO  o.c.o.s.i.z.m.ZeebeIncidentImportMediator - Records of type INCIDENT from partition 1 imported in page: 0
14:07:18.392 [ZeebeImportScheduler-1] WARN  o.c.o.s.i.z.f.AbstractZeebeRecordFetcher - No Zeebe index with alias zeebe-record-user-task found to
4

I have the same problem, did you find a permanent solution?

5

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.