I wrote a custome application that will get invoked when I click the link in the SES search result page.
I could invoke the application. However, getting the following exception when I click one button in my application: 500 Internal Server Error
OracleJSP: An error occurred. Consult your application/system administrator for support. Programmers should consider setting the init-param debug_mode to "true" to see the complete exception message.
How can see the exceptions I am getting. I mean how can I set the init-param debug_mode to "true".
I tried a couple of things. First set a servelt init param in my web.xml called debug_mode to true. It did not work (got the same message about programmers should consider setting debug_mode to true). Then I tried to set it in the deployment plan for my ear as below (I got this from the .xsd of orion-web-app). This does not make a difference either.
I gave up trying to set this possibly mythical "debug" parameter, but found that all the error information you need is in the "application.log" file of your custom application.
For example if your application is called "ses_query" and is deployed to the standard SES OC4J location, then the file will be
Normally application.log is where I look for problems. However this time there's nothing in the application.log file.
I 'm trying a little experiment with how I build my .ear file. Usually I keep all the dependent jars of my webapp under WEB-INF/lib and then include the .war inside a .ear for command line deployment to Oracle application server (not OC4J standalone). Now I 'm trying place all my dependent library .jar files in the top directory of the .ear and then have a CLASSPATH entry in the .war's META-INF/MANIFEST.MF file to reference those jar files. This way multiple .war files inside my .ear then can reference a common set of jars without having to duplicate then under WEB-INF/lib of each war. Maven2 supports this type of packaging. In some forums this is called "skinny war" packaging.
With this "skinny war" packaging, my .ear file deploys without errors using admin_client.jar (command line deployment) to the Oracle app server. However when I access the JSF page in one of my apps from the browser, I see this OracleJSP error asking me to set the debug parameter. NOTHING in the application.log file.
On the application server host I don't have write permissions to all the application server directories (so I can set this debug param in soe global file) . I prefer being able to set this debug flag via my application's deployment plan file or web.xml.
I have a workaround by making all the .wars inside my .ear "fat" i.e. they will have their own copies of the jars instead of sharing. I guess I can try to setup a OAS shared library and accomplish this too but with the "skinny" war approach the .ear is self contained.
To clarify: Edit
In the section <servlet><servlet-name>jsp<...
Add an "init-param" section so it looks like this:
<!-- you can set main_mode to "justrun" to speed up
Then restart the midtier using "searchctl restart"
Don't leave this on for production - sometimes it can reveal database passwords!