AppD Archive

13:48:18,315 ERROR [AD Thread Pool-Global0] DBAgentPollingForUpdate:34

CommunityUser
Splunk Employee
Splunk Employee

Why am I just now getting this Error with my DB-Agent.  it was working fine on Sat and I came in this Monday morning and I get this :

13:48:08,233 ERROR [AD Thread Pool-Global0] DBAgentPollingForUpdate:34 - Error reading response from Controller
com.singularity.ee.rest.ResponseReadException: java.io.StreamCorruptedException: invalid stream header: 3C726573
at com.singularity.ee.rest.controller.request.ABinaryControllerRequest.<init>(ABinaryControllerRequest.java:61)
at com.singularity.ee.rest.controller.request.AgentPollingConfigurationRequest.<init>(AgentPollingConfigurationRequest.java:24)
at com.singularity.ee.rest.controller.request.DBMonitorConfigRequest.<init>(DBMonitorConfigRequest.java:30)
at com.singularity.ee.agent.dbagent.config.channel.DBAgentPollingForUpdate.getConfigurationResponse(DBAgentPollingForUpdate.java:29)
at com.singularity.ee.agent.configuration.channel.PollingForUpdate.pollForConfigUpdate(PollingForUpdate.java:96)
at com.singularity.ee.agent.configuration.channel.PollingForUpdate.nextTransition(PollingForUpdate.java:40)
at com.singularity.ee.agent.configuration.channel.AgentConfigurationChannel.refreshConfiguration(AgentConfigurationChannel.java:48)
at com.singularity.ee.agent.configuration.channel.AgentConfigurationRefreshTask.run(AgentConfigurationRefreshTask.java:32)
at com.singularity.ee.util.javaspecific.scheduler.AgentScheduledExecutorServiceImpl$SafeRunnable.run(AgentScheduledExecutorServiceImpl.java:107)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
at com.singularity.ee.util.javaspecific.scheduler.ADFutureTask$Sync.innerRunAndReset(ADFutureTask.java:335)
at com.singularity.ee.util.javaspecific.scheduler.ADFutureTask.runAndReset(ADFutureTask.java:152)
at com.singularity.ee.util.javaspecific.scheduler.ADScheduledThreadPoolExecutor$ADScheduledFutureTask.access$101(ADScheduledThreadPoolExecutor.java:117)
at com.singularity.ee.util.javaspecific.scheduler.ADScheduledThreadPoolExecutor$ADScheduledFutureTask.runPeriodic(ADScheduledThreadPoolExecutor.java:204)
at com.singularity.ee.util.javaspecific.scheduler.ADScheduledThreadPoolExecutor$ADScheduledFutureTask.run(ADScheduledThreadPoolExecutor.java:234)
at com.singularity.ee.util.javaspecific.scheduler.ADThreadPoolExecutor$Worker.runTask(ADThreadPoolExecutor.java:694)
at com.singularity.ee.util.javaspecific.scheduler.ADThreadPoolExecutor$Worker.run(ADThreadPoolExecutor.java:726)
at java.lang.Thread.run(Thread.java:745)
Caused by: java.io.StreamCorruptedException: invalid stream header: 3C726573
at java.io.ObjectInputStream.readStreamHeader(ObjectInputStream.java:804)
at java.io.ObjectInputStream.<init>(ObjectInputStream.java:299)
at com.singularity.ee.util.serialize.JavaSerializer.unmarshalObject(JavaSerializer.java:40)
at com.singularity.ee.rest.controller.request.ABinaryControllerRequest.constructPaylodFromInputTracked(ABinaryControllerRequest.java:131)
at com.singularity.ee.rest.controller.request.ABinaryControllerRequest.constructPaylodFromInput(ABinaryControllerRequest.java:123)
at com.singularity.ee.rest.controller.request.ABinaryControllerRequest.<init>(ABinaryControllerRequest.java:56)
... 17 more

Tags (1)
0 Karma

Arun_Dasetty
Super Champion

Hi Glenn, 

 

      It could be the case that recently some agent/machine agent have started such that host id conflict (host name) have resulted, Can you restart db agent as following and see how it goes with error?

 

shell> java -Dappdynamics.agent.uniqueHostId=My_Database_Agent Host_1 -jar /path/to/<dbAgent_dir>/db-agent.jar

0 Karma
Get Updates on the Splunk Community!

Index This | What’s a riddle wrapped in an enigma?

September 2025 Edition Hayyy Splunk Education Enthusiasts and the Eternally Curious!  We’re back with this ...

BORE at .conf25

Boss Of Regular Expression (BORE) was an interactive session run again this year at .conf25 by the brilliant ...

OpenTelemetry for Legacy Apps? Yes, You Can!

This article is a follow-up to my previous article posted on the OpenTelemetry Blog, "Your Critical Legacy App ...