Don’t Use OC4J Bundled with Oracle 10g

I couldn’t believe it when I saw it on this random forum post at Oracle’s own website but apparently you are not supposed to use the OC4J install that comes with Oracle for your own applications. It is meant only for internal settings!?

Please do not use the internal OC4J from the DB for your application. Please install a standalone OC4J instance which is available from OTN. You will not have the same functionality as you will with the standalone OC4J. That instance is used for internal settings (it is also used for the console), therefore please download an installation.

Is this why my “helloworld.jsp” page from Oracle themselves throws this error when placed in the default web app directory?

500 Internal Server Error

Servlet error: java.lang.ClassNotFoundException: _helloworld

I can only hope so. Next step, try installing a standalone version of OC4J and test using the same “helloworld.jsp” file. Why is this not CLEARLY stated in the documentation? The OC4J default install with Oracle includes a help file “OC4Jstandaloneguide.pdf” that doesn’t mention this anywhere! This could also explain why all the help I can find online references a default port of 8888 not the 1158 port that the Oracle Enterprise Manager is located on at “http://hostname:1158/em”.


I installed the OC4J standalone from Oracle available here by unzipping the downloaded file and setting the J2EE_HOME to the location of “<oc4j install dir>/j2ee/home”. It works, but it seems to really really slow down my machine after it is started. I need to look into this but at least I can view the test pages and my “helloworld.jsp” file works perfectly.

One thought on “Don’t Use OC4J Bundled with Oracle 10g

Leave a Reply

Your email address will not be published. Required fields are marked *

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>