AppD Archive

ClassCastException in Agent Log

CommunityUser
Splunk Employee
Splunk Employee

Hi,

I got an ClassCastException in the log file of the agent. I append this part of the log. It is weird ClassCastException:

java.lang.ClassCastException: java.lang.Integer cannot be cast to java.lang.Long

The error in front of the Exception is also very weird:

ERROR MySQLSessionGrabber - An exception occurred when getting MySQL DB session id.

There is no MySQL DB in the whole environment. So why does the agent try to get an MySQL DB session id?

Regards,

Thomas

0 Karma

Arun_Dasetty
Super Champion

Hi Thomas,

The error raised as part of agent logging and instrumentation of SQL backend exit calls and SQL queries as part of BT detecion, We have known bug around the error and is fixed already in 4.0.3 agent version, We request you to upgrade agent to 4.0.3 or latest 4.0.x agent version and that should resolve the error post agent ugprade and jvm restart.

Hope that information helps.

Regards,

Arun

0 Karma
Get Updates on the Splunk Community!

Update Your SOAR Apps for Python 3.13: What Community Developers Need to Know

To Community SOAR App Developers - we're reaching out with an important update regarding Python 3.9's ...

October Community Champions: A Shoutout to Our Contributors!

As October comes to a close, we want to take a moment to celebrate the people who make the Splunk Community ...

Automatic Discovery Part 2: Setup and Best Practices

In Part 1 of this series, we covered what Automatic Discovery is and why it’s critical for observability at ...