OracleJSP: An error occurred. Consult your application/system administrator for support. Programmers should consider setting the init-param debug_mode

Yesterday i did a new installation of SOA Suite 10.1.3.1 and then upgraded it to 10.1.3.4

when i tried to log in to the bpel console i got the following 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.

Referring to some otn link i changed the global-web-applicaiton.xml file in following location

D:\product\10.1.3.1\OracleAS_2\j2ee\oc4j_soa\config

I changed my code as follows

<servlet>
<servlet-name>jsp</servlet-name>
<servlet-class>oracle.jsp.runtimev2.JspServlet</servlet-class>
<!-- you can set main_mode to "justrun" to speed up
JSP dispatching, if you don't need to recompile
your JSP anymore. You can always switch your
main_mode. Please see our doc for details -->
<!--
<init-param>
<param-name>main_mode</param-name>
<param-value>justrun</param-value>
</init-param>
-->
<load-on-startup>0</load-on-startup>
</servlet>




<servlet>
<servlet-name>jsp</servlet-name>
<servlet-class>oracle.jsp.runtimev2.JspServlet</servlet-class>
<init-param>
<param-name>debug_mode</param-name>
<param-value>true</param-value>
</init-param>
-->
<load-on-startup>0</load-on-startup>
</servlet>



Again when i tried to log in i got following error in console

Request URI:/BPELConsole/default/index.jsp

Exception:
OracleJSP:java.io.FileNotFoundException: D:\product\10.1.3.1\SOA\j2ee\oc4j_soa\applications\orabpel\console\default\index.jsp (The system cannot find the path specified)

OracleJSP:oracle.jsp.parse.JspParseException: /default/index.jsp: Line # 10, <%@include file="initI18n.jspf" %>
Error: Include file not found: /default/initI18n.jspf

then i did a lot of r & d but couldn't resolve the issue.

Esb console was working fine for me.

I dropped the schemas and recreated it again, and moved it to the required patch level.

But still i got the same issue.Finally i shutdown application server and database too

then restarted it and all of a sudden it started wokring for me.I have tried all the options earlier also except restarting the database so i believe if you get this issue do the following before taking any action

Stop soa suite
stop database
stop listener
start listener
start database
start soa suite.


Then check the console again.Remove the browser history because it always will point to domainPicker.jsp or use internet explorer to log in to console.