You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Using the Docker version of fcrepo-camel-toolbox (latest version) I got a 100% CPU usage for one of the container cores even when no update is present in the Fedora ActiveMQ queue.
Output of the htop command: 1842434 root 20 0 13,5g 729244 25604 S 100,0 2,2 162:10.88 java -jar /usr/local/fcrepo-camel-toolbox/driver.jar -c /config/toolbox-configuration.properties (CPU is at 100% for at least one of my 8 cores)
Is it possible to lower the polling frequency on the JMS queue using the configuration?
Is it in some way related to the Thread.onSpinWait() cycle in the Driver class?
Thanks Andrea
The text was updated successfully, but these errors were encountered:
If you have a recommendation, we will happily take it.
I'll add this to the list of things to have a look at. This app will need to change to be more spring-boot like with the latest Camel versions, but no one has been willing to take a look at that yet.
Using the Docker version of fcrepo-camel-toolbox (latest version) I got a 100% CPU usage for one of the container cores even when no update is present in the Fedora ActiveMQ queue.
My configuration of the toolbox is:
Output of the
htop
command:1842434 root 20 0 13,5g 729244 25604 S 100,0 2,2 162:10.88 java -jar /usr/local/fcrepo-camel-toolbox/driver.jar -c /config/toolbox-configuration.properties
(CPU is at 100% for at least one of my 8 cores)Is it possible to lower the polling frequency on the JMS queue using the configuration?
Is it in some way related to the Thread.onSpinWait() cycle in the Driver class?
Thanks Andrea
The text was updated successfully, but these errors were encountered: