Uploaded image for project: 'Confluence Data Center'
  1. Confluence Data Center
  2. CONFSERVER-100197

javax.servlet.ServletException: org.glassfish.jersey.server.internal.process.MappableException

XMLWordPrintable

    • 16
    • 5
    • We collect Confluence feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

      Problem

      In recent Confluence versions such as 9.2.x, we are seeing logs spammed with messages like below:

        2025-07-08 00:02:50,274 ERROR [http-nio2-8080-exec-41 url: /500page.jsp; user: PPothuga] [atlassian.confluence.status.SystemErrorInformationLogger] logException Unhandled exception, request unique ID: 6a3f786a-80e4-46a8-b615-96a4dc611171
 -- traceId: c09abe6d6ded8901
javax.servlet.ServletException: org.glassfish.jersey.server.internal.process.MappableException: javax.ws.rs.WebApplicationException: HTTP 410 Gone
    at org.glassfish.jersey.servlet.WebComponent.serviceImpl(WebComponent.java:410)
    at org.glassfish.jersey.servlet.WebComponent.service(WebComponent.java:346)
    at org.glassfish.jersey.servlet.ServletContainer.service(ServletContainer.java:359)

      08-Jul-2025 06:52:31.469 SEVERE [http-nio2-8080-exec-15 url: /rest/api/search; user: XXXX] org.glassfish.jersey.server.ServerRuntime$Responder.writeResponse An I/O error has occurred while writing a response message entity to the container output stream.
	org.glassfish.jersey.server.internal.process.MappableException: org.apache.catalina.connector.ClientAbortException: java.io.IOException: Broken pipe
		at org.glassfish.jersey.server.internal.MappableExceptionWrapperInterceptor.aroundWriteTo(MappableExceptionWrapperInterceptor.java:67)
		at org.glassfish.jersey.message.internal.WriterInterceptorExecutor.proceed(WriterInterceptorExecutor.java:139)
		at org.glassfish.jersey.message.internal.MessageBodyFactory.writeTo(MessageBodyFactory.java:1116)
		at org.glassfish.jersey.server.ServerRuntime$Responder.writeResponse(ServerRuntime.java:649)
		at org.glassfish.jersey.server.ServerRuntime$Responder.processResponse(ServerRuntime.java:380)
		at org.glassfish.jersey.server.ServerRuntime$Responder.process(ServerRuntime.java:370)
		at org.glassfish.jersey.server.ServerRuntime$1.run(ServerRuntime.java:259)
		at org.glassfish.jersey.internal.Errors$1.call(Errors.java:248)

      We believe these logs are related to client/server communication interruption in some fashion as noted in these discussions:

      https://community.openhab.org/t/error-jersey-server-serverruntime-responder-an-i-o-error-has-occurred-while-writing-a-response-message-entity-to-the-container-output-stream/43599

      https://community.atlassian.com/forums/Confluence-questions/Confluence-500-error-when-I-try-and-update-labels-via-requests/qaq-p/952443

      https://jira.atlassian.com/secure/CreateIssueDetails!init.jspa?pid=10470&issuetype=10000&summary=Errors+in+the+logs.&description=h3.+Problem%0A%0A%0Ah3.+Suggested+Solution%0A_%28Add+a+suggested+solution+once+one+has+been+determined%29_%0A%0Ah3.+Why+This+Is+Important%0A_%28Add+a+description+for+why+this+is+important%29_%0A%0Ah3.+Workaround%0A_%28Add+a+workaround%2C+if+available%29_

      Suggested Solution

      We would like to suggest reducing/suppressing these messages to DEBUG mode as these errors are very frequent and affects legitimate log events.

      Workaround

      NA

              Unassigned Unassigned
              sganeshan@atlassian.com Sathya Ganeshan
              Votes:
              3 Vote for this issue
              Watchers:
              6 Start watching this issue

                Created:
                Updated: