Deployment: Showing Full Error instead of 500 Internal Server Error

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.
 

Comments:

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

Posted by Will Senn on October 10, 2007 at 12:54 AM PDT #

but I use eclipse. how can I see the complete error message. plz let't me know....

Posted by Yang on October 27, 2010 at 05:52 PM PDT #

Hi Yang, The JDeveloper deployment option is probably just passing the setting on to the OC4J deploment process. So however you deploy to OC4J, there you must have a similar option available. You should be able to find it in the documentation of your deployment tool and/or the OC4J documentation. Hope this helps, Sandra

Posted by Sandra Muller on October 27, 2010 at 06:27 PM PDT #

Post a Comment:
  • HTML Syntax: NOT allowed
About

Java EE Consultants - JHeadstart, ADF, JSF

Search

Archives
« April 2014
SunMonTueWedThuFriSat
  
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
   
       
Today