Blog dedicated to Oracle Applications (E-Business Suite) Technology; covers Apps Architecture, Administration and third party bolt-ons to Apps

Thursday, March 18, 2010

JSP Error Exception: java.sql.SQLException: Closed Connection

Manoj called me today about this issue. After clone, when application username (SYSADMIN) and password was keyed in by him and he reached the URL

http://justanexample.com/OA_HTML/fndvald.jsp

The following error was shown:

JSP Error

Exception:

java.sql.SQLException: Closed Connection

jserv.log showed:

java.sql.SQLException: Closed Connection
at oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java:134)
at oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java:179)
at oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java:269)
at oracle.jdbc.driver.OracleConnection.rollback(OracleConnection.java:1459)
at _oa__html._fndvald._jspService(_fndvald.java:121)
at oracle.jsp.runtime.HttpJsp.service(HttpJsp.java:119)
at oracle.jsp.app.JspApplication.dispatchRequest(JspApplication.java:417)
at oracle.jsp.JspServlet.doDispatch(JspServlet.java:267)
at oracle.jsp.JspServlet.internalService(JspServlet.java:186)
at oracle.jsp.JspServlet.service(JspServlet.java:156)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:588)
at org.apache.jserv.JServConnection.processRequest(JServConnection.java:456)
at org.apache.jserv.JServConnection.run(JServConnection.java:294)
at java.lang.Thread.run(Thread.java:619)

I checked the Database alert log and found that everytime we tried to log in the following error was logged in the DB alert log:

Errors in file /justanexample/dbdata/admin/udump/justanexample_ora_27477.trc:
ORA-07445: exception encountered: core dump [00000001025F3090] [SIGSEGV] [Address not mapped to object] [0x100C100010000] [] []

The trace file showed more details:

ksedmp: internal or fatal error
ORA-07445: exception encountered: core dump [00000001025F3090] [SIGSEGV] [Address not mapped to object] [0x100C100010000] [] []
Current SQL statement for this session:
alter session set max_dump_file_size=unlimited
----- PL/SQL Call Stack -----
object line object
handle number name
441590590 428 package body APPS.FND_TRACE
441e4f050 350 package body APPS.FND_AOLJ_UTIL
441e4f050 236 package body APPS.FND_AOLJ_UTIL
43e89dd08 1 anonymous block

Manoj bounced the database once and these errors stopped coming in alert log. We were able to login to the applications without issues.

Thursday, March 4, 2010

'Io exception: NL Exception was generated' running IRCA

Shahed pinged me about this during SOA installation:

$ sh irca.sh
Integration Repository Creation Assistant (IRCA) 10.1.3.1.0
(c) Copyright 2006 Oracle Corporation. All rights reserved.

Enter database "host port serviceName" [localhost 1521 orcl]: justanexample 1521 soa11g
Enter sys password:
Running IRCA for all product(s):
connection="justanexample 1521 soa11g", , orabpelUser=ORABPEL, esbUser=ORAESB, orawsmUser=ORAWSM

ERROR: Failed to establish database connection due to the following error:
ORA-01017: invalid username/password; logon denied

Please check your connection parameters and try again.

I tried it and got different result:

$ sh irca.sh
Integration Repository Creation Assistant (IRCA) 10.1.3.1.0
(c) Copyright 2006 Oracle Corporation. All rights reserved.

Enter database "host port serviceName" [localhost 1521 orcl]: "justanexample 1521 soa11g"
Enter sys password:
Running IRCA for all product(s):
connection=""justanexample 1521 soa11g"", , orabpelUser=ORABPEL, esbUser=ORAESB, orawsmUser=ORAWSM

ERROR: Failed to establish database connection due to the following error:
Io exception: NL Exception was generated
Please check your connection parameters and try again.

A search on My Oracle Support showed up Article [ID 580448.1]

Cause

A valid connection 'as sysdba' could not be established to the Oracle RDBMS instance.

Testing a connection from a JDeveloper client to the target RDBMS shows that a SYSTEM schema can
create a connection, but SYS is also unable to create a regular rdbms connection. Therefore
JDeveloper is having the same problem making a 'SYS as sysdba' connection over jdbc thin.

Solution

Create a password file and ensure that your RDBMS allows remote connections as sysdba.

Issue was resolved after creating passwordfile by running orapwd :
Usage: orapwd file= password= entries= force= ignorecase= nosysdba=