Solution for always outputting quartz debugging information during openmeetings source code debugging

When openmeetings uses the source code for debugging, the console always outputs the following Z debugging information:

 

[Debug] [DefaultQuartzScheduler_Worker-1] org. hibernate. JDBC. connectionmanager-opening JDBC connection
[Debug] [DefaultQuartzScheduler_Worker-1] org. hibernate. transaction. jdbctransaction-current autocommit status: false
[Debug] [DefaultQuartzScheduler_Worker-1] org. hibernate. JDBC. abstractbatcher-about to open preparedstatement (Open preparedstatements: 0, globally: 0)
[Debug] [DefaultQuartzScheduler_Worker-1] Org. hibernate. SQL-select recording0 _. recording_id as recording1_29 _, recording0 _. comment_field as comment2_29 _, recording0 _. name as name29 _, recording0 _. rooms as rooms29 _, recording0 _. starttime as starttime29 _, recording0 _. updatetime as updatetime29 _, recording0 _. deleted as deleted29 _, recording0 _. duration as duration29 _, recording0 _. xmlstring as xmlstrin G29 _, recording0 _. Same as container _, recording0 _. recordedby as container _, recording0 _. whiteboardconverted as container _ from recording recording0 _ Where recording0 _. whiteboardconverted =? And recording0 _. Deleted <>?
[Debug] [DefaultQuartzScheduler_Worker-1] org. hibernate. JDBC. abstractbatcher-about to open resultset (Open resultsets: 0, globally: 0)

 

The method to remove isrunning = false is the last sentence of whiteboardconvertionjobmanager. getinstance (). initjobs;

Try {
If (! Isrunning ){
Isrunning = true;

......

Isrunning = false;

}

 

Although I don't know why I need to set it to true first and then to false, it may be to view debugging information. It is best to add it back when the development ends.