threadcount | Messaging analytics | Analytics library

Try running your test as:

maven-failsafe-plugin has no notion of "packages". The notion of "suites" is related to junit4 Suite.

To solve my problem above, I did the following:

In each "features.area" I created a "TestSuiteStub":

If you are on a recent version of Cucumber (> 5.0) the syntax is cucumber.filter.tags=@Smoke-Login.

Try to provide the full path to your AllTestsRelease.xml file, e.g. src/test/java/testSuites/AllTestsRelease.xml

My question is : how to manage the resources? for example, first step 4 tasks will be executed using 4 core and 4 arrayList. Then whenever a core is available, the 5th task will be executed along with available arrayList. How to do that in Java? please give me reference or source code.

AFAIK, natively, Java does not have features to explicitly map a given thread to a given core (i.e., thread affinity). You can do it via explicit system calls such as in Linux OS using the taskset command. But this would require you to do a lot of working, and possibility lose portability in the way.

You would be better off using higher-level Java abstracts (e.g., ExecutorService) to deal with those low levels details for you. Send the tasks to a Thread Pool using the ExecutorService let the pool and ultimately the OS Threads scheduler deal with the mapping between threads/task.

Btw even using Java Thread Pools, there is no guarantee that the threads will be nicely mapped to separate cores.

Other languages, such as C/C++ might provide you with libraries that allow you to explicitly map cores to threads, for instance using OpenMP thread affinity features.

Based on your comment :

If I only send the tasks to a Thread Pool without managing the arrayList, it will consume a lot of memory. Suppose 1 have 100 tasks then it will need 100 arrayLists.. I want to reduce the memory consumption by using only 4 arrayList to be reused whenever a task is completed.

It sounds to me that you want to implement the producer-consumer pattern. One thread will be responsible for adding work to the Queue (i.e., ArrayLists) will the other threads request that work from the Queue and consume it.

Found the problem with our application and writing here whoever passes by this issue. At least it may give some ideas where to look.

Findings:

• Quartz .Net does not any relation with the issue.
• Our logger enricher was trying to query the service name for each log.
• This action was causing service.exe to respond and thus the reason for the high CPU.

I have tried a couple of windows profiler but unfortunately, none of them provided enough or easy to understand information. Finally, tried dotTrace which showed me the hot spot in the application, and after that making a correlation between my application and services.exe was easy.

Personal learning:

• I was trying to make a correlation between my application and services.exe which there had to be one. But my mistake was to focus on Quartz .Net and how manages threads on the operating system.
• Even though the issue was different, pursuing to make a correlation was the key point for me. No fire, no smoke.

Thanks.

As per the doc Understand metrics: Thread Count --> The number of threads currently active in the app process. It should include the azure webjob's thread count. But as per my testing, the doc seems incorrect.

You can give it a try by going to the kudu site to check the thread count for each webjobs.

Steps: Go to azure portal -> your azure web app -> Advanced Tools -> click the go button:

Then in the kudu site -> click the Process explorer tab, then check the thread_count column for threads of your webjob:

In general, such exception happens when you have two versions of the same class in the classpath. Some of the reasons that may happens are:

1. Your dependencies include two version of google-api-client. I don't see any direct dependency so It could be a transitive dependency. You can run mvn dependency:tree and look for google-api-client dependencies and exclude one of the jars
2. You are packing a provided dependency. It could be that app engine already include such jar with HttpTransport, if you also include this HttpTransport class into your artefact it will create problems. To fix this identify which dependency contains HttpTransport class and in your pom.xml add provided to it
3. This class is included in the classpath from some old jar in some generated repository. If this is the case all you have to do is reset your environment. Clone the repository again and re-init app engine

Issue was with values in the df with space. Once we removed the space in the values Bokeh was able to plot without any issues.