I am just not seeing where this process is being generated from. The easiest "fix" for this is to stop Confluence, upgrade to the latest Java version (after checking it is valid for Confluence 7.14.2) by triggering the upgrade, or just waiting until it kicks in on-schedule, and then starting Confluence after it finishes. (On linux boxes, it is similar, but you have to do quite a bit of config to allow it to run the upgrade without asking the humans, and it tends to complain that Confluence is running as well) They can be configured to ask first, but it depends on which one it is. If this is a Windows machine, that would make sense - the standard installs of most Javas will, by default, install a small service that checks for new versions of Java and upgrades them automatically. This will interfere with anything using the Java install it is trying to update (and the update can thrash a machine sometimes, so that might be the cause of the 100% CPU) Javaupdate suggests you've got something on the computer that is trying to upgrade Java when it detects a new release. It was active for approximately milliseconds. Īt .threads.ThreadPoolExecutor$n(ThreadPoolExecutor.java:659)Īt .threads.TaskThread$n(TaskThread.java:61)Ģ 09:09:36.785 WARNUNG .StuckThreadDetectionValve.notifyStuckThreadCompleted Thread (id=) was previously reported to be stuck but has completed. There is/are thread(s) in total that are monitored by this Valve and may be stuck.Īt .io.SessionInputBufferImpl.streamRead(SessionInputBufferImpl.java:137) Is there any solution out there for this issue?Īt the event i've got the following in the catalina*.logĢ 09:09:16.774 WARNUNG .StuckThreadDetectionValve.notifyStuckThreadDetected Thread (id=) has been active for milliseconds (since ) to serve the same request for and may be stuck (configured threshold for this StuckThreadDetectionValve is seconds). Problem is, my colegue trying to attach an excel document and uploads a new version with goedit and the process "openJDK Plattform binary" starting to rise up to 100%, the upload is canceled and this process still takes about 90-100% for a while. first time it apears with confluence server 7.16.x, now we have 7.18.3 and it still the same. I have to kill the process JavaUpate to return Confluence to its operating status. Update: If the server is rebooted, the problem starts all over again. Can anyone tell me where next to look? Is there an old program that was not removed during the update that should have been? Do I need to update one of the configuration files? I am not sure what is forcing JavaUpdate to start or keep restarting after the process is terminated. I am now waiting to see if this happens again. So I again killed the process, stopped and started confluence again and it comes right back.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |