# com.lmax.disruptor.IgnoreExceptionHandler - Exception processing

**URL:** <https://discuss.elastic.co/t/com-lmax-disruptor-ignoreexceptionhandler-exception-processing/368022>\
**Category:** APM\
**Tags:** java\
**Created:** [September 30, 2024, 1:48pm UTC](https://discuss.elastic.co/t/com-lmax-disruptor-ignoreexceptionhandler-exception-processing/368022 "2024-09-30T13:48:19Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![murat3](https://avatars.discourse-cdn.com/v4/letter/m/e274bd/32.png) [@murat3](https://discuss.elastic.co/u/murat3)\
**Post date:** [September 30, 2024, 1:48pm UTC](https://discuss.elastic.co/t/com-lmax-disruptor-ignoreexceptionhandler-exception-processing/368022/1 "2024-09-30T13:48:19Z")

</div>

APM Agent 1.51  
Elastic Stack 8.11.4  
Java 8  
Weblogic 12.2

We are using the APM Java agent and attaching it programatically using "ElasticApmAttacher.attach()".

It is running more then a year now but the last months we are experiencing problems.  
Java Agent is not able to send data to Elasticsearch. The following exception is found thousands of times in the weblogic log:

[elastic-apm-server-reporter] INFO com.lmax.disruptor.IgnoreExceptionHandler - Exception processing: 112600405 Type: null java.lang.NullPointerException: null

After restart of the weblogic server the proces continues but very soon (sometimes a couple of hours sometimes a couple of days later) the same issue appears with the same error log.

I could not find any clues searching the internet.

Any ideas? Where to start to analyse this problem?

Best regards,

Murat

---

<div class="post-metadata">

**Author:** ![Sylvain\_Juge](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/sylvain_juge/32/55521_2.png) [@Sylvain\_Juge](https://discuss.elastic.co/u/Sylvain_Juge)\
**Post date:** [September 30, 2024, 3:52pm UTC](https://discuss.elastic.co/t/com-lmax-disruptor-ignoreexceptionhandler-exception-processing/368022/2 "2024-09-30T15:52:47Z")

</div>

Hi,

Thanks for reporting this issue.

Could you provide a copy of the whole stack trace please ? Sent is as DM if needed.

Do you have an estimate of the frequency this issue is happening ? is that one or twice per month or more weekly/daily ?

---

<div class="post-metadata">

**Author:** ![murat3](https://avatars.discourse-cdn.com/v4/letter/m/e274bd/32.png) [@murat3](https://discuss.elastic.co/u/murat3)\
**Post date:** [September 30, 2024, 8:52pm UTC](https://discuss.elastic.co/t/com-lmax-disruptor-ignoreexceptionhandler-exception-processing/368022/3 "2024-09-30T20:52:50Z")

</div>

Thanks for the quick reply!

I don't have a stack trace yet. Not showing up in the weblogic logs.  
But I have requested the Elasticsearch logs from the operators. This could take a couple of days unfortunately.

Should I also have the Kibana logs?

It started to happen more frequently the last 3 months. Last time, this happened within hours after restarting weblogic.  
A couple of months ago it worked for some weeks after a restart.

When it happens it is constantly throwing this error thousands of times per day.

---

<div class="post-metadata">

**Author:** ![Sylvain\_Juge](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/sylvain_juge/32/55521_2.png) [@Sylvain\_Juge](https://discuss.elastic.co/u/Sylvain_Juge)\
**Post date:** [October 1, 2024, 7:50am UTC](https://discuss.elastic.co/t/com-lmax-disruptor-ignoreexceptionhandler-exception-processing/368022/4 "2024-10-01T07:50:08Z")

</div>

The Elasticsearch and Kibana logs are not relevant here, what you need to provide is the elastic apm agent logs.

A common procedure to capture those in a separate file is [available here](https://www.elastic.co/guide/en/apm/agent/java/current/trouble-shooting.html#trouble-shooting-logging-procedure).

Given you are deploying on Weblogic, does it means one webapp deployed on the server deploys the agent through runtime attach with the API, and then it instruments the whole service ?

As an alternative, trying to use the more simple `-javaagent` setup method could likely help you achieve better stability. While we haven't changed this part recently it might still have a few corner cases.

---

<div class="post-metadata">

**Author:** ![murat3](https://avatars.discourse-cdn.com/v4/letter/m/e274bd/32.png) [@murat3](https://discuss.elastic.co/u/murat3)\
**Post date:** [October 1, 2024, 3:13pm UTC](https://discuss.elastic.co/t/com-lmax-disruptor-ignoreexceptionhandler-exception-processing/368022/5 "2024-10-01T15:13:02Z")

</div>

Okay understood.

I will configure APM via properties to log to a file and will set the log\_level to debug for a short time at runtime in production.

Thank you!

Kind regards,  
Murat