Weblogic Manage Server Health Status Changed to Critical Due to Stuck Thread in "PDF Content Publisher" (Doc ID 2626343.1)

Last updated on MAY 12, 2022

Applies to:

Symptoms

Web logic server goes in Critical health status.After checking the stuck thread the below error is coming.

ERROR
-----------------------
at com.ofss.digx.appx.writer.content.PDFContentPublisher.publish(PDFContentPublisher.java:132)
  
  at com.ofss.digx.appx.writer.DownloadFileWriter.writeTo(DownloadFileWriter.java:151)
  
  at com.ofss.digx.appx.writer.DownloadFileWriter.writeTo(DownloadFileWriter.java:44)
  
  at org.glassfish.jersey.message.internal.WriterInterceptorExecutor$TerminalWriterInterceptor.invokeWriteTo(WriterInterceptorExecutor.java:265)
  
  at org.glassfish.jersey.message.internal.WriterInterceptorExecutor$TerminalWriterInterceptor.aroundWriteTo(WriterInterceptorExecutor.java:250)
  
  at org.glassfish.jersey.message.internal.WriterInterceptorExecutor.proceed(WriterInterceptorExecutor.java:162)

STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. Login to weblogic
2. User can see the status as critical in weblogic admin server


BUSINESS IMPACT
-----------------------
The issue has the following business impact:
Due to this issue, users cannot download the statement.

Changes

 None

Cause

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.