SAP agent generates trace file when starting ' at java.base/java.io.Reader.<init>(Reader.java:167)'

book

Article ID: 211890

calendar_today

Updated On:

Products

CA Automic Workload Automation - Automation Engine

Issue/Introduction

SAP agent generates trace file when starting when using XI option:

20210203/142650.331 - 21     ----------------------- Stack Trace -----------------------
20210203/142650.332 - 21     java.lang.NullPointerException
 at java.base/java.io.Reader.<init>(Reader.java:167)
 at java.base/java.io.InputStreamReader.<init>(InputStreamReader.java:97)
 at com.uc4.ex.sap.SLDIntegration.readTemplate(SLDIntegration.java:150)
 at com.uc4.ex.sap.SLDIntegration.register(SLDIntegration.java:62)
 at com.uc4.ex.sap.SAPHost.setSldConnection(SAPHost.java:1179)
 at com.uc4.ex.sap.UCXJR3X.afterExecutorLogon(UCXJR3X.java:191)
 at com.uc4.ex.ExecutorLifecycle.logonCompleted(ExecutorLifecycle.java:494)
 at com.uc4.ex.MessageDispatcher$1.run(MessageDispatcher.java:374)
 at com.uc4.ex.ThreadPool$RunnableDecorator.run(ThreadPool.java:53)
 at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515)
 at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
 at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
 at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
 at java.base/java.lang.Thread.run(Thread.java:834)

Resolution

This trace can be disregarded. Jobs can still run after the trace is generated.

Workaround:
Remove login object defined on the agent object under System Landscape Directory.

Fix:
Defect fix is currently scheduled for 12.3.6. This is a tentative release and the date or version can change