DAT Solutions Internal

Back
Aug 6, 2026 7:22 AM PDT

CarrierWatch — All BIPD Reports Returning HTTP 500 (Internal Server Error)

Updates

  • Aug 6, 2026 9:47 AM PDT

    All BIPD-related admin reports in CarrierWatch (Cancelled BIPD, No BIPD, Bad BIPD Policy) are returning HTTP 500 errors due to a JSP compilation failure on the CarrierWatch Tomcat application. The Reporter class cannot be resolved at runtime, causing the /reports/cancelledBipd.jsp (and likely related BIPD report pages) to fail to render. This prevents admin and operations staff from running insurance compliance reports used to identify and remove carriers with inactive or cancelled BIPD insurance policiess Commit 9d8ce6b6 (CSB-2863 treg logging, PR #1254) deleted treg/src/java/com/tcore/treg/Reporter.java from the source tree. Nine BIPD report JSPs continued to reference new Reporter() via import com.tcore.treg.*. Because JSP scriptlets compile lazily at first HTTP request rather than at build time, the Java-only CI compile remained green and the missing class was not detected until the report pages were accessed in production, resulting in HTTP 500 errors across all affected BIPD report endpoints.

    Resolution:
    Reporter.java was restored from the pre-deletion commit (9d8ce6b6^) and its internal logging dependency was migrated from the deleted com.tcore.log.Logger to slf4j/lombok. The restored file was reintroduced to the source tree, a hotfix jar was produced, and the patch was hot-deployed to the CarrierWatch Tomcat (treg) host without a full stack redeployment. All affected BIPD report pages were verified as operational following the patch.

    What Changed:

    Restored Reporter.java to the treg/src/java/com/tcore/treg/ source tree
    Migrated logging from com.tcore.log.Logger → slf4j/lombok

    A PIR will be documented and action items will be assigned.

    Resolved
  • Aug 6, 2026 7:22 AM PDT (2 hours and 25 minutes earlier)

    All BIPD-related admin reports in CarrierWatch (Cancelled BIPD, No BIPD, Bad BIPD Policy) are returning HTTP 500 errors due to a JSP compilation failure on the CarrierWatch Tomcat application. The Reporter class cannot be resolved at runtime, causing the /reports/cancelledBipd.jsp (and likely related BIPD report pages) to fail to render. This prevents admin and operations staff from running insurance compliance reports used to identify and remove carriers with inactive or cancelled BIPD insurance policiess The CarrierWatch Tomcat application experienced a JSP compilation failure that caused all BIPD-related admin report pages to return HTTP 500 errors. The Reporter class was unresolved at runtime, preventing the affected report endpoints from rendering. The CSB team identified the missing class, produced a targeted hotfix jar with the corrected build, and hot-deployed the patch to the CarrierWatch treg host without requiring a full redeployment. Behavior was verified post-patch to confirm the BIPD reports were restored

    Monitoring