After https://github.com/RedHatInsights/insights-java-client/pull/43 the fallback to using a file writer doesn't work anymore. The report service throws the following and ends
WARN [org.jboss.eap.insights.report] (ServerService Thread Pool -- 1) Scheduled send failed: com.redhat.insights.InsightsException: I4ASR0015: SSLContext creation error at com.redhat.insights.tls.PEMSupport.getBytesPossiblyPrivileged(PEMSupport.java:92) at com.redhat.insights.tls.PEMSupport.createTLSContext(PEMSupport.java:39) at org.jboss.eap.insights.report.ServerStatusReportService$1.get(ServerStatusReportService.java:115) at org.jboss.eap.insights.report.ServerStatusReportService$1.get(ServerStatusReportService.java:111) at org.jboss.eap.insights.report.InsightsApacheHttpClient.isReadyToSend(InsightsApacheHttpClient.java:172) at com.redhat.insights.http.InsightsMultiClient.isReadyToSend(InsightsMultiClient.java:57) at com.redhat.insights.InsightsReportController.lambda$generate$0(InsightsReportController.java:119) at org.jboss.eap.insights.report.JBossInsightsScheduler.lambda$scheduleAtFixedRate$0(JBossInsightsScheduler.java:59) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) at java.lang.Thread.run(Thread.java:748) at org.jboss.threads.JBossThread.run(JBossThread.java:513) Caused by: java.io.IOException: Cert helper binary: /opt/jboss-cert-helper does not exists. at com.redhat.insights.tls.CertHelper.readUsingHelper(CertHelper.java:26) at com.redhat.insights.tls.PEMSupport.getBytesPossiblyPrivileged(PEMSupport.java:90) ... 15 more
As a side-note, the fact that it produces a WARN in logs is also an issue.