top of page
  • valitilvinisump

How I Solved the Problem of Automatically Killing Hanging Programs During Startup And Shutdown



Spring Boot configure this shutdown hook automatically since version 2.3 (see jihor's answer). You may need to register some @PreDestroy methods that will be executed during the graceful shutdown (see Michal's answer).


Previously, I wrote the Ultimate Troubleshooting Guide for Windows 7 Homegroup Issues, which a lot of people found useful. Today, I am going to write up a ultimate troubleshooting guide for Windows 7 hanging issues. This includes Windows 7 hanging on startup/boot, hanging when logging off, hanging when shutting down, hanging when installing programs, etc.




How To Automatically Kill Hanging Programs During Startup And Shutdown




To monitor a program it first needs to be running as Restarter selects the executable from a list of opened processes, then you can choose the monitor interval (default is 60 seconds), whether to restart the process, kill an unresponsive process, play a warning sound and run an external script (reboot and send email VBS scripts are included). Supplying a working directory and startup arguments are optional extras. Restarter has a Create shortcut button which will add a desktop shortcut to allow launching the selected application and then monitor it automatically.


In this DocumentGoalSolution Cause 1 : Log transport issues. Solution 1: Please use cksum command to verify the size of password file on the primary and the standby sites, and make sure SEC_CASE_SENSITIVE_LOGON is set to false for 11g or above databases. Cause 2 : Firewall caused partial archive log transferred. Solution 2: Please make sure the following firewall features are disabled. Cause 3 : ARC process on the primary that is responsible for the heartbeat sticks on the network due to bug 6113783 Solution 3: The bug 6113783 was fixed in 11.2.0.2. You could workaround the issue by killing the arch processes on the primary database. Cause 4. The standby recovery asked for old sequence # that had been applied to the standby. Solution 4 : Apply the fix of bug 6029179 or kill the heartbeat arch process of each primary instance if the primary is a RAC database. Cause 5 Recover from the wrong location. Solution 5 Specify standby_archive_dest the same location as log_archive_dest_1 on the physical standby. Use from 'location' attribute in the manual recovery clause. Cause 6: All standby redo log files are active on the standby database. Solution 6: Please make sure you have enough space in the archive location. log_archive_dest_1 is defined with proper valid_for values and db_unique_name. standby_archive_dest is specified properly. Cause 7 : Partial archive log file is applied on the standby database. Solution 7 Use RMAN incremental backup method to roll forward your physical standby database. Cause 8 : The archive log files were transferred to the standby manually, not through data guard log transport service. Solution 8 Register those archive log files or use manual recovery. Cause 9 : The archive log files are deleted from the primary before they are shipped and applied to the standby. Solution 9 Restore archive log files from backup, register them and use managed recovery to recover them; or use manual recovery without registering them. Cause 10 : New datafiles are added to the primary, but they are not added to the standby automatically. Solution 10 Add the new datafiles to the standby database manually. Cause 11 : MRP can stall after control file contention at the standby. Solution 11 This is fixed in 10.2.0.4. The workaround is to restart the standby. Cause 12 : Cancelling managed recovery hangs. Solution 12 Let's shutdown abort the standby, startup mount, then have a clean shutdown, check if there are server processes left over for the standby instance.References My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.


I have had this issue now for 2+ years and only way I have been able to solve it is via a full host restart after shutting down each working v-machine (rdp and shutdown). The v-machine process that hangs (always either during proper restart/startup) does not want to get killed any which way I try. Have tried right click run as admin to launch task manager and process explorer and then try to kill the process - the problem process does not die. Tried killing a working v-machine and that closed shop and died in no time. Nothing in event log stands out.


Does your Windows PC keep freezing or locking up? Whether your computer is frozen right now, hangs at startup or shutdown, or freezes at random, there are easy ways to narrow down the cause and fix the problem permanently. This wikiHow article will cover several simple troubleshooting tricks that are sure to help you resolve issues with freezing and hanging on Windows 10, 11, and 8.1.


2ff7e9595c


1 view0 comments

Recent Posts

See All

Commenti


bottom of page