« Deploying JHeadstart 10.1.3 applications to OC4J 10.1.3.2 | Main | Version Control for ADF-JHeadstart Applications »

Deployment: Showing Full Error instead of 500 Internal Server Error

By sandra.muller on August 8, 2007 1:52 AM

Cliff Cotino had a good tip on the JHeadstart Discussion Forum: how to show the complete error in case your deployed application shows only a 500 Internal Server Error.

Suppose your application runs fine in Embedded OC4J in JDeveloper, but when deployed on Standalone OC4J or Oracle Application Server shows this error:

500 Internal Server Error

Servlet
error: An exception occurred. The current application deployment
descriptors do not allow for including it in this response. Please
consult the application log for details.

If you want to know the complete error message and stack trace you must deploy the
application in "development" mode. To achieve this you must perform the following:

Suppose you have a JDeveloper Application Server connection named "ConnectionName".

  • Right-click the deployment profile and select "Deploy to ConnectionName"
  • In the "Configure Application" dialog box you have the option to edit certain deployment options.
  • Select the web-app on the left side of the screen. On the right side of the screen there is an option "development". Set the value to "true" and deploy your application.
Now when you access the application (page) in your browser you will see the complete error message.
 

AddThis Social Bookmark Button

Comments (1)

ConnectionName? That's pretty funny. How about SourceName or AppIdentifier or something? :) Good tip though. Thanks.

Posted by Will Senn | October 10, 2007 7:54 AM

Post a comment

(If you haven't left a comment here before, you may need to be approved by the site owner before your comment will appear. Until then, it won't appear on the entry. Thanks for waiting.)