Submit a ticketCall us

AnnouncementsAre You “Flying Blind?”

When it comes to your complex IT infrastructure, you want to ensure you have a good grasp of what’s going on to avoid any fire drills that result from guesswork. Read our white paper to learn how proactively monitoring your IT environment can help your organization while giving you peace of mind.

Get your free white paper.

Home > Success Center > Web Help Desk (WHD) > WHD - Knowledgebase Articles > Java.exe*32 CPU Utilization at 100 on the WHD server

Java.exe*32 CPU Utilization at 100 on the WHD server

Table of contents

Overview

This article provides steps on how to fix when Java.exe*32 CPU Utilization spikes to 100% rendering WHD unusable.

Environment

WHD version 12.3

Steps

1. Run the query below to check for looping ticket:
SELECT F.JOB_TICKET_ID AS FIRST_TICKET_ID,F.MERGED_PARENT_TICKET_ID AS FIRST_TICKET_PARENT_ID,S.JOB_TICKET_ID AS SECOND_TICKET_ID, S.MERGED_PARENT_TICKET_ID AS SECOND_PARENT_ID, HE.ENTRY_TEXT, HE.ENTRY_DATE FROM JOB_TICKET as F JOIN JOB_TICKET as S ON S.MERGED_PARENT_TICKET_ID=F.JOB_TICKET_ID AND F.MERGED_PARENT_TICKET_ID = S.JOB_TICKET_ID JOIN HISTORY_ENTRY AS HE on F.JOB_TICKET_ID = HE.JOB_TICKET_ID WHERE HE.ENTRY_TEXT LIKE 'Merged in%' ORDER BY HE.ENTRY_DATE DESC;

 

If ticket(s) are found..the following query must be executed in order to break the loop behavior:
UPDATE JOB_TICKET SET MERGED_PARENT_TICKET_ID = NULL WHERE JOB_TICKET_ID = <parentID>

 

2. Log in to the mailbox associated with WHD.

3. Move emails from Inbox to Temp folder.

4. Start Web Help Desk.

 

Last modified

Tags

Classifications

Public