AppD Archive

unable to bci class

CommunityUser
Splunk Employee
Splunk Employee

Hello,

I get Agent Diagonistic events telling "unable to bci class com/ibm/jsse2/sca$a_$0 because of potential Classloader deadlock". 

How can I exlude this package from bci?

0 Karma

Arun_Dasetty
Super Champion

Hi,

We see such errors earlier but this error indicates that there is certain level of instrumentation failure on this JVM and hence we request you to add following two -D jvm args in addition to -javaagent entry on jvm startup script and restart the JVM 

-Dappdynamics.bciengine.class.verify=false

-Dappdynamics.bciengine.defer.risky.bci=false

We expect the above errors should not affect any app functionality let us know if you see such issues.

If issue still persists please send the logs folder archive under <appserveragent_install_dir>/logs path to assist you further.

Keep us posted how it goes.

The other option is to exclude manually from app-agent-config.xml at <agent_dir>/conf path by adding entry of package at section  looks similar to below, but above suggested jvm args should help in your case:

 <bci-processing-excludes>

<custom-exclude filter-type="CONTAINS" filter-value="org/pack1"/>

Regards,

Arun

0 Karma
Get Updates on the Splunk Community!

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 ...

UCC Framework: Discover Developer Toolkit for Building Technology Add-ons

The Next-Gen Toolkit for Splunk Technology Add-on Development The Universal Configuration Console (UCC) ...

.conf25 Community Recap

Hello Splunkers, And just like that, .conf25 is in the books! What an incredible few days — full of learning, ...