Check the running jobs using AD Controller (adctrl).
If the running jobs are Java related and the number of workers is high (more than 20 or 30) then you might have hit a memory limit.
One way to fix that is to restart the adop session from scratch (after killing any hanging processes) and specify a lower number of workers:
restart=no abdandon=yes workers=16
To find, your patch is hung or not, you need to identify the current running jobs. Perform following steps
1. adctrl to find the status of jobs and find the running jobs and which worker is running it.....
2. Mostly it will be stuck on one Job, find the worker running it and open worker log file to find details....
3. Using ACTIVE DB sessions, try to link running job with database session and check if that DB session is doing anything or not
4. If no activities then you can kill the session and restart same job from adctrl
If you have no time for root cause, then you can stop the patch and restart as mentioned by Bashar.