Hi,
one of my TSplus servers has a serious problem with the process HTML5service.exe (OpenJDK platform binary). It consumes 30-50 % of CPU.
Is there any known reason for this?
There are only 3 users on this server and no one is connected via Browser (all via RDP).
TSplus version is 14.30.11.23.
regards
Michael
HTML5service.exe consumes 30-50% of CPU
HTML5service.exe consumes 30-50% of CPU
Last edited by bzdega on Tue Dec 22, 2020 3:21 pm, edited 1 time in total.
Re: HTML5service.exe consumes 30-50% of CPU
After updating to 14.40.12.18 the problem first seems to be gone. But after my (3) users logged on, the HTML5service.exe starts consuming a lot CPU power.
Also the AdminTool says, that the webserver is not running, but this is not true.
So again my question: what can cause this behavior of HTML5service.exe?
Michael
Also the AdminTool says, that the webserver is not running, but this is not true.
So again my question: what can cause this behavior of HTML5service.exe?
Michael
Re: HTML5service.exe consumes 30-50% of CPU
Hello bzdega,
there is no way to guess except to get access to problematic system for few days and debug it until catching the state when this cpu load occurs since not reproducible on my systems. Can we arrange it?
You can always send me sensitive data per email to find in my profile.
there is no way to guess except to get access to problematic system for few days and debug it until catching the state when this cpu load occurs since not reproducible on my systems. Can we arrange it?
You can always send me sensitive data per email to find in my profile.
TSplus HTML5 and Java web engineer
Re: HTML5service.exe consumes 30-50% of CPU
Hi,
the CPU load occurs, when HTML5service.exe is running. Stopping this process immedeatly stops the heavy CPUload.
Because the users are only connecting via RDP, stopping the process is no problem. But this is no solution.
I send you a login to this system.
regards,
Michael
the CPU load occurs, when HTML5service.exe is running. Stopping this process immedeatly stops the heavy CPUload.
Because the users are only connecting via RDP, stopping the process is no problem. But this is no solution.
I send you a login to this system.
regards,
Michael