• Forums
    • Public Forums
      • Community Connect
      • Dynatrace
        • Dynatrace Open Q&A
      • Application Monitoring & UEM
        • AppMon & UEM Open Q&A
      • Network Application Monitoring
        • NAM Open Q&A
  • Home /
  • Public Forums /
  • Application Monitoring & UEM /
  • AppMon & UEM Open Q&A /
avatar image
Question by Jason p. · Mar 28, 2013 at 05:32 PM ·

purepath timeout due to long running background thread

We have a situation where a background thread is created using the java Timer API that waits 30 minutes then wakes up and clears a cache.

Purepaths that trigger creation of that thread are timing out.

We're looking for a way to tell Dynatrace to ignore this particular background thread.

We have tried putting exclude & global exclude method sensors on the method that creates the timer but that doesn't fix the problem.

What is the appropriate way of deal with this situation?

Comment

People who like this

0 Show 0
10 |2000000 characters needed characters left characters exceeded
  • Viewable by all users
  • Viewable by moderators
  • Viewable by moderators and the original poster
  • Advanced visibility
Toggle Comment visibility. Current Visibility: Viewable by all users

Up to 10 attachments (including images) can be used with a maximum of 50.0 MiB each and 250.0 MiB total.

7 Replies

  • Sort: 
  • Most voted
  • Newest
  • Oldest
avatar image

Answer by Christian S. · May 07, 2014 at 04:32 AM

hi Laurent,

right, you should do this exclusion of java.util.Timer$TimerImpl.run().

however, I'm wondering: I could not see this class in Sun/Oracle JVM 1.4-7 source code. and based on your session, you're working with IBM Java 6 VMs, right? so I guess this is something we should add to the default exclusions.

in the thread start tagging sensor you will see, that there is already a similar exclusion for java.util.Timer.run(). so this exclusion should basically be added here (you could just switch from "equals" to "starts").

please let me know if this worked for you, so we can discuss taking this into the product.

thx, Christian

Comment

People who like this

0 Show 0 · Share
10 |2000000 characters needed characters left characters exceeded
  • Viewable by all users
  • Viewable by moderators
  • Viewable by moderators and the original poster
  • Advanced visibility
Toggle Comment visibility. Current Visibility: Viewable by all users

Up to 10 attachments (including images) can be used with a maximum of 50.0 MiB each and 250.0 MiB total.

avatar image

Answer by Laurent I. · May 06, 2014 at 07:01 PM

Hi Christian,

 

you'll find attached a couple of pp exhibiting the aforementionned behaviour.

Argos_06mai.dts

Thanks for your insight.

NB: we'll try to exclude, as proposed by Jason, the "Timer.$TimerImpl.run()" method, but this will reduce further our visibility on this code execution... 

Regards

--

Laurent

Comment

People who like this

0 Show 0 · Share
10 |2000000 characters needed characters left characters exceeded
  • Viewable by all users
  • Viewable by moderators
  • Viewable by moderators and the original poster
  • Advanced visibility
Toggle Comment visibility. Current Visibility: Viewable by all users

Up to 10 attachments (including images) can be used with a maximum of 50.0 MiB each and 250.0 MiB total.

avatar image

Answer by Jason p. · May 06, 2014 at 01:30 AM

Yes, I believe we got rid of this problem by excluding that method from the Threading sensor. 

Lucky for us, we only had that one usage of Timer.run() so it didn't affect anything else.

Comment

People who like this

0 Show 0 · Share
10 |2000000 characters needed characters left characters exceeded
  • Viewable by all users
  • Viewable by moderators
  • Viewable by moderators and the original poster
  • Advanced visibility
Toggle Comment visibility. Current Visibility: Viewable by all users

Up to 10 attachments (including images) can be used with a maximum of 50.0 MiB each and 250.0 MiB total.

avatar image

Answer by Christian S. · May 06, 2014 at 01:27 AM

could you show us a PurePath or give an exact example of the behavior you see, please?

in most cases this can be solved by an exclusion rule in the threading sensors.

best, Christian

Comment

People who like this

0 Show 0 · Share
10 |2000000 characters needed characters left characters exceeded
  • Viewable by all users
  • Viewable by moderators
  • Viewable by moderators and the original poster
  • Advanced visibility
Toggle Comment visibility. Current Visibility: Viewable by all users

Up to 10 attachments (including images) can be used with a maximum of 50.0 MiB each and 250.0 MiB total.

avatar image

Answer by Laurent I. · May 06, 2014 at 01:09 AM

any update on this ?

I'm having this exact same case where a Timer.run() is invoked and the purepath times out on wait()...

Thanks

--

Laurent

Comment

People who like this

0 Show 0 · Share
10 |2000000 characters needed characters left characters exceeded
  • Viewable by all users
  • Viewable by moderators
  • Viewable by moderators and the original poster
  • Advanced visibility
Toggle Comment visibility. Current Visibility: Viewable by all users

Up to 10 attachments (including images) can be used with a maximum of 50.0 MiB each and 250.0 MiB total.

avatar image

Answer by Jason p. · Apr 09, 2013 at 06:53 PM

We are working through this with support.
I will post the results when we (hopefully) find a resolution.

Comment

People who like this

0 Show 0 · Share
10 |2000000 characters needed characters left characters exceeded
  • Viewable by all users
  • Viewable by moderators
  • Viewable by moderators and the original poster
  • Advanced visibility
Toggle Comment visibility. Current Visibility: Viewable by all users

Up to 10 attachments (including images) can be used with a maximum of 50.0 MiB each and 250.0 MiB total.

avatar image

Answer by Andreas G. · Apr 09, 2013 at 09:10 AM

I assume that you are interested in certain background threads but just not in those particulare ones - correct?

Right now you can only disable our Thread Tagging Sensor but that would mean that you do not get any threads tagged at all.
In your case I would rather suggest to not capture these PurePaths that start these backgroudn threads. If these threads are always triggered by specific web requests, e.g: "/someurl/urlthatstartsthread" - then you could modify your Servlet Sensor and exclude this URL from starting a PurePath.
In case your application is a non-web application you can exclude the "Entry Point" method of these PurePaths with a global exclude so that they dont start a PurePath anymore

Let me know if this works. otherwise - feel free to export some of these PurePAths and attach it to this post

Comment

People who like this

0 Show 0 · Share
10 |2000000 characters needed characters left characters exceeded
  • Viewable by all users
  • Viewable by moderators
  • Viewable by moderators and the original poster
  • Advanced visibility
Toggle Comment visibility. Current Visibility: Viewable by all users

Up to 10 attachments (including images) can be used with a maximum of 50.0 MiB each and 250.0 MiB total.

How to get started

First steps in the forum
Read Community User Guide
Best practices of using forum

NAM 2019 SP5 is available


Check the RHEL support added in the latest NAM service pack.

Learn more

LIVE WEBINAR

"Performance Clinic - Monitoring as a Self Service with Dynatrace"


JANUARY 15, 3:00 PM GMT / 10:00 AM ET

Register here

Follow this Question

Answers Answers and Comments

4 People are following this question.

avatar image avatar image avatar image avatar image

Forum Tags

dotnet mobile monitoring load iis 6.5 kubernetes mainframe rest api dashboard framework 7.0 appmon 7 health monitoring adk log monitoring services auto-detection uem webserver test automation license web performance monitoring ios nam probe collector migration mq web services knowledge sharing reports window java hybris javascript appmon sensors good to know extensions search 6.3+ server documentation easytravel web dashboard kibana system profile purelytics docker splunk 6.1 process groups account 7.2 rest dynatrace saas spa guardian appmon administration production user actions postgresql upgrade oneagent measures security Dynatrace Managed transactionflow technologies diagnostics user session monitoring unique users continuous delivery sharing configuration alerting NGINX splitting business transaction client 6.3 installation database scheduler apache mobileapp RUM php dashlet azure purepath agent 7.1 appmonsaas messagebroker nodejs 6.2 android sensor performance warehouse
  • Forums
  • Public Forums
    • Community Connect
    • Dynatrace
      • Dynatrace Open Q&A
    • Application Monitoring & UEM
      • AppMon & UEM Open Q&A
    • Network Application Monitoring
      • NAM Open Q&A