Shut Down Of OC4J Container ist blocked

Question

Hi,
i'vi got a problem with the new 10g iAS and if anybody's encountered the same or does know a solution, please let me know.
The problem is:
I'm not able to stop the OC4J container in the iAS cleanly.
The reason is:
There are two timers (java.util.Timer) running. These timers are cleanup timers, which run always throughout the application at intervalls (scheduleAtFixedRate). If i dont start the timers, the container will stop right away, without any error. If the timers are running the container is waiting for them to cancel and shutting down hardly after a timeout.
I didn't have this problem with 9i and i dont have it in the embedded OC4J of the JDeveloper.
Is there any workaround? How could i latch into the shutdown process, to cancel the timers myself?
Best regards,
Mirko

Answer 1

The OC4J script is not the cause of this -- if the message is shown "shutting down OC4J' then the call has been made to OC4J and its in the process of shutting down.
If you execute "set verbose=on" before executing oc4j.cmd, then you'll see the command that oc4j uses when -shutdown is performed is exactly that command you suggest:
oc4j -shutdown -port 23791 -password welcome1Executing: D:\java\jdk150_11\bin\java -jar "d:\java\oc4j-10133-prod\j2ee\home\admin.jar" ormi://localhost:23791 oc4jadmin welcome1 -shutdown
But as you are suggesting there are manual ways to shutdown OC4J that are equally valid to use; it's a matter of choice.
What you could try is using the -force extra switch with the -shutdown command to force it to shutdown:
java -jar admin.jar ormi://localhost:23791 oc4jadmin welcome1 -shutdown force
If that fails, ctrl+c the process. It doesn't do any damage to it.
A thread-dump (ctrl+break) on the hung process can help to identify any deadlock issues.
oc4j.cmd is limited certainly, but it provides a simpler entry point IMHO for new users. And we still fully support/endorse the direct startup path using the runnable JAR file.
-steve-