May I know, what might be causing this issue. Every time collector is running, it goes to WAITING state ad takes longer time to complete collection (~1hr).
Version : 6.9.1.91521 P04
May I know, what might be causing this issue. Every time collector is running, it goes to WAITING state ad takes longer time to complete collection (~1hr).
Version : 6.9.1.91521 P04
Happened again this week end.
One collector gets a stack trace and the collection is stuck in Waiting which means all following collections are just queued.
We will upgrade to P04 and hopefully it will solve this. (at least the growing queue)
Hi Markus,
We are also facing the same issue with collector stuck in Waiting, have you tested with P04, whether it is resolved ?
regards,
William
It is not resolved in 7.0.2 P04
This has been running for 82 hours in our test environment.
We restarted acm and database and the status shows failed for In-progress tasks.
But once we start collection again the same issue occurs ; the Account collection stucks in waiting.
Have you restarted and tested again?
Yes, that is usually the way we get it running again. This time though, this happened:
My previous response was in the test environment, Friday night it happened in our production environment.
Since we haven't got it back up running in test, we are hesitant to restart the production environment...
If your production is stuck, could you check if there is a *.data file under:
/home/oracle/wildfly-8.2.0.Final/standalone/tmp/vfs/deployment/deployment<....>/aveksa.war-<...>/WEB-INF/LocalAgent/collected_data
and is that file growing in size?
If you can't find the right folder, looked for a directory called "collected_data"
thanks for the advice. We manage to solved it by remove the "hanging" collector & application.
Then we recreate the application & collector, to perform a fresh start on collection.
I have the exact same issue, running 7.0.2 P03
This morning one of the entitlement collectors got stuck with a stacktrace as in your picture and all other collectors are queued.
It also happened on Friday evening and all collectors where queued till Monday morning when we got back to work.
Which means that we had around 80 different jobs in the work queue. It is interesting that it just adds to the queue, even if it is a collection already in the queue...