Terminating the Embedded OC4J Process

JDeveloper provides an embedded OC4J server in JDeveloper is automatically started when you run or debug an EJB, servlet, or JSP project. Since this server is run directly on your local machine, you do not require a remote OC4J connection to an OC4J instance.

Once the embedded OC4J server has started, the Embedded OC4J Server process appears in the Run Manager tab from the Navigator. You can access the Run Manager by choosing View | Run Manager from the main menu.

Ways to shutdown the running embedded OC4J Server:

Choose Run | Terminate - Embedded OC4J Server from the main menu.
OR
Right-click Embedded OC4J Server in the Run Manager and choose Terminate from the context menu.
OR
Choose File | Exit to exit JDeveloper. You are prompted to terminate the embedded OC4J server process.

Depending on the selection made on the Global - Shutdown page of the Embedded OC4J Server Preferences dialog, JDeveloper will attempt to shut down OC4J either forcefully or gracefully. To configure the preferences for shutting down the embedded OC4J server, see Setting Preferences for the Embedded OC4J Server.

If OC4J does not respond when shutting down gracefully

Make sure to allow OC4J adequate time to shut down and check the Log window for status information about the shutdown. Reasons that OC4J does not shut down after the initial request may include:

Server configuration was changed while server was still running
Administrative shutdown command was sent to a port that was not the RMI port of the server, so the server never received the shutdown request.
The RMI port of the server is unavailable, which may happen if the server was launched when there was a port conflict trying to bind the RMI port, so the server never received the shutdown request.
A web browser using "keep alive" tokens is maintaining a connection to OC4J. If this is the case, close the browser window that is using those "keep alive" tokens.
A client to an EJB is still connected or the connection is hung.
A database connection used by an EJB, servlet, JSP, or XSQL page is still open and for some reason cannot be closed.

In these situations, you may need to shut down the OC4J server forcefully by doing the following:

Choose Run | Terminate - Embedded OC4J Server again from the main menu. When the embedded server starts up the next time, you will see a message in the Log window indicating that OC4J is attempting to recover from abrupt termination or a crash. This is the normal OC4J startup process after it has been forcefully terminated.