Database connection closing in JSF

This is regarding Database connection closing in JSF.
in servlets we have destroy method where we will be closing the database connections, similarly in JSF where should we close the database connections? is it taken care by the framework?
is there a way where we could capture the end of session and then close the database connection?
I am creating database connection in backing bean as I am not supposed to create a pool of connection objects(I am using tomcat 5.5)
Thanks in advance for any suggestions about this.

k_srinivas wrote:
This is regarding Database connection closing in JSF.OK.
in servlets we have destroy method where we will be closing the database connectionsThis is at its own already a very bad practice. All database resources like Connection, Statement and ResultSet must be acquired and closed in the shortest possible scope. You should never keep them open as an instance variable and for sure not in a servlet (which lives as long as the application lives). If you keep a connection open that long, it will timeout sooner or later and your application will crash.
, similarly in JSF where should we close the database connections? is it taken care by the framework?
is there a way where we could capture the end of session and then close the database connection?No, just acquire and close the resources in the shortest possible scope. To improve performance, introduce connection pooling. But this doesn't mean that you can write the JDBC code the other way. You still need to acquire and close the resources quickly. The connection pooling implementation will worry about actually closing the connection or releasing the connection to the pool.
I am creating database connection in backing bean as I am not supposed to create a pool of connection objects(I am using tomcat 5.5)
Thanks in advance for any suggestions about this.This makes no sense. Just make use of Tomcat's own connection pooling facility.
For more about doing the database access logic the proper way, you may find this tutorial useful: [http://balusc.blogspot.com/2008/07/dao-tutorial-data-layer.html].

Similar Messages

[Bug] Or feature? Database connection closed if given a name after first op

I am not sure if this is a bug or a feature.
oracle.javatools.db.Database db = oracle.javatools.db.DatabaseFactory.findOrCreateDatabase("sample", conn);
If I supply a name for the database as the above line using "sample", the database connection is closed after the first op, i.e., you can call
db.listObjects once, but the second time, it will fail with StackOverFlowException. But the culprit is the database connection is closed after the first op.
However, if I don't give it a name, using null,
oracle.javatools.db.Database db = oracle.javatools.db.DatabaseFactory.findOrCreateDatabase(null, conn);
There's no problem at all.
Is this a bug or a feature?
If a feature, the JavaDoc made it worse, by using the following example:
http://www.oracle.com/technology/products/jdev/esdk/api1013/oracle/javatools/db/DatabaseFactory.html
The DatabaseFactory should be used over the DBObjectProviderFactory when a Database specifically is required, and the name and Connection of that Database are available.
e.g.
java.sql.Connection conn = // the Connection to the db
DatabaseFactory.findOrCreateDatabase( "ora10g", conn );
The example sure sounds like a name is mandatory. Or perhaps the name is not some random name, but TNSName? If so, the Doc should certainly mention that.

I am not sure if this is a bug or a feature.
oracle.javatools.db.Database db = oracle.javatools.db.DatabaseFactory.findOrCreateDatabase("sample", conn);
If I supply a name for the database as the above line using "sample", the database connection is closed after the first op, i.e., you can call
db.listObjects once, but the second time, it will fail with StackOverFlowException. But the culprit is the database connection is closed after the first op.
However, if I don't give it a name, using null,
oracle.javatools.db.Database db = oracle.javatools.db.DatabaseFactory.findOrCreateDatabase(null, conn);
There's no problem at all.
Is this a bug or a feature?
If a feature, the JavaDoc made it worse, by using the following example:
http://www.oracle.com/technology/products/jdev/esdk/api1013/oracle/javatools/db/DatabaseFactory.html
The DatabaseFactory should be used over the DBObjectProviderFactory when a Database specifically is required, and the name and Connection of that Database are available.
e.g.
java.sql.Connection conn = // the Connection to the db
DatabaseFactory.findOrCreateDatabase( "ora10g", conn );
The example sure sounds like a name is mandatory. Or perhaps the name is not some random name, but TNSName? If so, the Doc should certainly mention that.

When are database connections closed?

Hello.
This post is related to the post that I made the earlier today. If I am using an external connection pool with TopLink at what point is a connection returned to the pool? If I have a ClientSession does it happen when I call release? Similarly, does it happen for a UnitOfWork when commit() is called? Or, is the connection returned to the pool via the finalize() method of ClientSession/UnitOfWork?
More information on this subject will be greatly appreciated.
Thanks,
Katie

Thanks for your reply.
We are pretty stuck because our application's external connection pool (via a WebSphere DataSource) is set to use a maximum of 10 connections, and all of the connections are used up when there is only one user on the system. Therefore we get an exception from WebSphere when we try to do an operation against the database when all of the connections are in use. We aren't spawning threads or anything. Our application does one query at a time.
It sounds like we are not responsible for releasing connections, so I guess that is not the problem. Is there anything that we could be doing that would cause us to use all of the connections? We could just allocate more connections, but it seems like we will probably just run in to the same problem later when there are more users of the system. I'd rather attack the problem at its core so that we have something that is scalable. Also, our application had been working fine for several months and now this problem has cropped up.
Thanks for all of your help.
Katie Kelly

Database connection not closing on time out

Hi All,
Not sure if this is the right place for this question but..
I've moved my app (built using jdev10.1.2., adf bc's and jsp's) to an app server. For some reason, the database connection is not closing. I have 46 connections to the database and I''m the only one with the URL, not good.
So can anyone shed any light on this? I thought it should disconnect after a time out but its not.
Any ideas would be gratfully received.
Thanks in advance

or try this one..
Go to the bottom of the tutorial, you will find the configuration...
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/bc9baf90-0201-0010-479a-b49b25598ebf

Closed database connection in olap worksheet

i have installed analytic workspace manager after applying the pathches ,i tried to log in analytic workspace manager and connect to olap worksheet it gives
me an error as "closed database connection" .My patch
installation was successful and it did not give me any error and my database is also working properly.could anyone help me out with this problem.

I had the same problem. Follow this link for the solution
Re: Cannot connect to AWM

Database Connections Not Closing

I'm using iBatis for PostgreSQL database access and frequently have problems with connections not being closed. Here is a copy of my sqlMapConfig file:
============================
<?xml version="1.0" encoding="UTF-8" ?>
<!DOCTYPE sqlMapConfig
PUBLIC "-//iBATIS.com//DTD SQL Map Config 2.0//EN"
"http://www.ibatis.com/dtd/sql-map-config-2.dtd">
<sqlMapConfig>
<properties resource="ibatis.properties" />
<settings
lazyLoadingEnabled="true"
cacheModelsEnabled="true"
enhancementEnabled="false"
useStatementNamespaces="false"
/>
<transactionManager type="JDBC" commitRequired="true">
<dataSource type="DBCP">
<property name="driverClassName" value="${driver}" />
<property name="url" value="${url}" />
<property name="username" value="${username}" />
<property name="password" value="${password}" />
<property name="maxActive" value="10"/>
<property name="maxIdle" value="5"/>
<property name="maxWait" value="5000"/>
<property name="logAbandoned" value="true"/>
<property name="removeAbandoned" value="true"/>
<property name="removeAbandonedTimeout" value="1"/>
<property name="Driver.logUnclosedConnections" value="true"/>
</dataSource>
</transactionManager>
<sqlMap resource="job-sqlMap.xml" />
</sqlMapConfig>
============================
Due to the logAbandoned and removeAbandoned settings, I get a report in my log file whenever there is a connection that was not properly closed. Here is one of those log entries:
23:22:51.483 (10) Finalizing a Connection that was never closed:
java.lang.Throwable: Connection was created at this point:
at org.postgresql.jdbc2.AbstractJdbc2Connection.<init>(AbstractJdbc2Connection.java:175)
at org.postgresql.jdbc3.AbstractJdbc3Connection.<init>(AbstractJdbc3Connection.java:30)
at org.postgresql.jdbc3.Jdbc3Connection.<init>(Jdbc3Connection.java:24)
at org.postgresql.Driver.makeConnection(Driver.java:393)
at org.postgresql.Driver.connect(Driver.java:267)
at org.apache.commons.dbcp.DriverConnectionFactory.createConnection(DriverConnectionFactory.java:38)
at org.apache.commons.dbcp.PoolableConnectionFactory.makeObject(PoolableConnectionFactory.java:294)
at org.apache.commons.pool.impl.GenericObjectPool.borrowObject(GenericObjectPool.java:1148)
at org.apache.commons.dbcp.AbandonedObjectPool.borrowObject(AbandonedObjectPool.java:84)
at org.apache.commons.dbcp.PoolingDataSource.getConnection(PoolingDataSource.java:96)
at org.apache.commons.dbcp.BasicDataSource.getConnection(BasicDataSource.java:880)
at com.ibatis.sqlmap.engine.transaction.jdbc.JdbcTransaction.init(JdbcTransaction.java:48)
at com.ibatis.sqlmap.engine.transaction.jdbc.JdbcTransaction.getConnection(JdbcTransaction.java:89)
at com.ibatis.sqlmap.engine.mapping.statement.MappedStatement.executeQueryForList(MappedStatement.java:139)
at com.ibatis.sqlmap.engine.impl.SqlMapExecutorDelegate.queryForList(SqlMapExecutorDelegate.java:567)
at com.ibatis.sqlmap.engine.impl.SqlMapExecutorDelegate.queryForList(SqlMapExecutorDelegate.java:541)
at com.ibatis.sqlmap.engine.impl.SqlMapSessionImpl.queryForList(SqlMapSessionImpl.java:118)
at com.ibatis.sqlmap.engine.impl.SqlMapClientImpl.queryForList(SqlMapClientImpl.java:94)
at edu.calpoly.lib.multimedia.big.db.AutomaticPeriodUpdateIBatisImplDBHandler.getGamesWithAutomaticUpdatePolicy(AutomaticPeriodUpdateIBatisImplDBHandler.java:154)
at edu.calpoly.lib.multimedia.big.game.AutoUpdateThread.run(AutoUpdateThread.java:155)
The file: AutomaticPeriodUpdateIBatisImplDBHandler.java contains an iBatis call on line # 154:
--> list = sqlMap.queryForList("getGamesWithAutoPolicy", null);
from the map file:
<select id="getGamesWithAutoPolicy" resultClass="java.util.HashMap">
<![CDATA[
SELECT gameid, policy
FROM update_policy
]]>
</select>
Here is the code for the entire method that uses this transaction:
============================
public List getGamesWithAutomaticUpdatePolicy() throws BIGDatabaseFacadeException
List list = new ArrayList();
try
sqlMap.startTransaction();
list = sqlMap.queryForList("getGamesWithAutoPolicy", null);
sqlMap.commitTransaction();
catch(SQLException sqle)
throw new BIGDatabaseFacadeException(sqle);
finally
try
sqlMap.endTransaction();
catch(SQLException sqle)
throw new BIGDatabaseFacadeException(sqle);
return list;
============================
I know that this should be handled as an automatic transaction, but I tried adding the start, commit and end transaction commands in my desperate attempt to fix this problem (but it still didn't help).
Here is my code for creation of sqlMap -
--> sqlMap = SqlMapClientBuilder.buildSqlMapClient(Resources.getResourceAsReader("sqlMaps.xml"));
Except for the fact that occasionally connections are not closed, overall my database access using iBatis works very well.
In the course of trying to fix this problem I've worked to update all my lib files to the latest versions, and here is current status:
My iBatis lib file: ibatis-2.3.4.726.jar
My JDBC driver: postgresql-8.4-701.jdbc3.jar
Required commons files:
commons-dbcp-1.2.2.jar
commons-pool-1.5.3.jar
Note that I tried adding --> commitRequired="true" to the transactionManager in sqlMaps.xml, hoping it might help, but no joy.
Please help me figure out why my database connections often do not close. Thank you very much!

I'm sorry, but I don't understand what you mean by "close the session." I believe iBatis is supposed to take care of all that automatically. My understanding is that all the user does is create the sqlMapClient and then use it along with various map files to query and update the database. iBatis does the rest.

ORCL Failed to connect to database instance: Closed Connection.

Hi all,
i am getting ORCL Failed to connect to database instance: Closed Connection, on my work environment but when i look into the database it is ok more over this ticket is generated from GridControl , i checked in trace-file but i haven't got any clue what to do in this case please any one help me on this why it is giving this kind of error
(ORCL Failed to connect to database instance: Closed Connection.)
Thanks
venkat
Edited by: madala03 on Apr 10, 2013 3:32 AM

Hi ,
thanks for the reply i checked in listener log , havent got any connection errors but in sqlnet.log
i got this
VERSION INFORMATION:
TNS for Linux: Version 10.2.0.4.0 - Production
TCP/IP NT Protocol Adapter for Linux: Version 10.2.0.4.0 - Production
Time: 10-JAN-2011 12:08:29
Tracing not turned on.
Tns error struct:
ns main err code: 12564
TNS-12564: TNS:connection refused
ns secondary err code: 0
nt main err code: 0
nt secondary err code: 0
nt OS err code: 0

Closing the database connection after report in a server application

I searched these forums and the internet for a definitive answer on asking the Crystal SDK for java to close the jdbc connection after it has generated a report. We have been using the Crystal Report SDK to generate reports within our JEE application, built upon the Spring framework, for the past two years. It works well, especially if you prepare views in the database for your reports.
From what I can tell once you have used ReportClientDocument to create your report you all the close() method to release resources associated with report generation, but this does not close the jdbc database connection.
Further research states that if you are using the CrystalReportViewer you can call the dispose method to close the database connection. We are not using JSP nor this class, so that does us little good.
Finally I found a post that one could call ((AdvancedReportDocument)reportClientDocument.getReportSource()).dispose(). This doesn't drop the connection either.
Each report actually opens 3 connections according to SQL Server. Each report will reuse the connections it has open, so for 50 reports, theoretically, we could have up to 150 connections. We explained to our client those connections remain inactive, however this is unacceptable to our client as they would like to minimize the number of connections left open to their database.
If anyone can post any further information on this issue, it is much appreciated.

Yes, another team member found the issue. Quite embarrassing really I didn't see it. I was looking for the answer within Crystal's libraries. It had nothing to do with Crystal.
The developer who wrote the helper code for using Crystal first opened a connection to the datasource for the live production database and read that connection information for the report. Next he set that connection information in the report template's PropertyBag, then ran the report. The developer however forgot to close the connection he used to look up the connection info, leaving a memory leak and using up all the connections.
I'm glad you inquired. I forgot to post the resolution here.

Database connection not closed in Destroy() method of servlet

Hi,
I have a problem with my deployed web application. At first, I thought Glassfish was messing up on me, and after checking the log I could see plenty of null pointer exceptions being thrown at lines in my code where I generate prepared statements from my connection object. I have been initialising my connection in the Init() method of all my classes, and equally, I've been closing it in Destroy(). I can only imagine that destroy() isn't being called - since the log clearly shows "connection success" messages but not "connection closed" messages. I am connecting to the servlets via a J2ME app on my mobile phone. Does connecting in this way somehow not invoke the destroy method when the servlets work is complete? Am I going to need to move all my connection initilisation and closing into the necessary doGet/doPost methods of each of my servlets?
Chris

You shouldn't be keeping the connection that long open. It's a bad design. It will timeout sooner or later and your complete application will crash. Always acquire and close the connection in the shortest possible scope, preferably just in the same method block where you process the query and/or results. If you want to improve performance while connecting, consider using a connection pool.
Back to the actual problem: a servlet is created only once during application's lifetime and not during every request as you appears to think.
You may find this tutorial useful to read on about using the DAO pattern in JSP/Servlet.
[http://balusc.blogspot.com/2008/07/dao-tutorial-use-in-jspservlet.html]

How to correct close database connection after report generation

Hello
I have problem a with alive database connection after report creation and report closing. How to properly to close connection to database?
Best regards
Edited by: punkers84 on Jun 17, 2011 10:38 AM

that's what I am doing... after viewing the report, I call the close method on the window closing event of the container window. but the connection is still open. I had a lot of other issues with my jdbc driver but after downgrading to an older version those issues are resolved.Only this one is still there! Is there any other way to close the connection (like using dbcontroller or etc.)?

MySQL Database Connection (two databases at the same time)

I have never had to open more than one MySQL database from within the same website before, but I do now. The website I have is designed where all the content comes from within the main database. I am building an Inventory system that I want within it's own database, in the event I would ever need to move the application to another server or something, I don't want this data residing in the main database.
Currently, I open the database connection from within a file called "common.php" that resides in a directory called "lib" that can be accessed from the root directory. Below is the proposed code that would be placed within the "common.php" file:
// Define Database Variables
$dbserver = "127.0.0.1";
$dbuser = array('clevelan_user1', 'clevelan_user2');
$dbpass = array('P@ssw0rd', 'P@ssw0rd2');
$dbname = array('clevelan_database1', 'clevelan_database2');
// Start Session
session_start();
// Connect to Databases
connectdb($dbserver, $dbuser[0], $dbpass[0], $dbname[0]);
connectdb2($dbserver, $dbuser[1], $dbpass[1], $dbname[1]);
// Database 1 Connection
function connectdb($dbserver, $dbuser, $dbpass, $dbname) {
// connects to db
global $connection;
$connection = @mysql_connect($dbserver, $dbuser, $dbpass) or die ("could not connect to server");
$db = @mysql_select_db($dbname, $connection) or die ("could not select databsase");
return $connection;
// Database 2 Connection
function connectdb2($dbserver, $dbuser, $dbpass, $dbname) {
// connects to db
global $connection2;
$connection2 = @mysql_connect($dbserver, $dbuser, $dbpass) or die ("could not connect to server");
$db2 = @mysql_select_db($dbname, $connection2) or die ("could not select databsase");
return $connection2;
//End of Code Within the "common.php"
From within any page of the website, I want to access both connections by placing an include at the top of each page:
include_once("lib/common.php");
Currently, when I run the code above, any page within the website (the home page) provides error messages with regards to database connectivity (the pages are looking for there content from within the second database. It's as if the second database is the only database seen by the website.
I need help figuring out how I can have two MySQL databases open at the same time (the second database will only be open for short periods of time and then closed). But the main database is always open.

Create one project using one copy of the exact tables.
create 2 different sessions.xml files each pointing to the same project. Set the login information in the sessions.xml files.
That should work fine.
Peter

Database connection remains open after close being called

I am using oracle OC4J as my application server. I am not using connection pool and I am using non-pooled datasource to get connection. The database connection is made at runtime and then closed. I want to test if the users' connection sessions have been killed after they logout the application. But when I checked the table v$session in the database, it shows one connection remaining. I checked my program, the close method has been called. Does anybody know the solution?

Hi Chen,
This is just a suggestion for something to try -- only if you haven't
already tried it, that is!
Try running OC4J in "debug" mode. Here are details on how to do that:
http://kb.atlassian.com/content/atlassian/howto/orionproperties.jsp
Hope this helps you!
Good Luck,
Avi.

ME SDK:DB connection closed automatically

I designed a collaboration directive triggered by a web service using the SDK (ME 5.2.3).
Basically, this directive perform a select to get the material inventory, and then loop into the result to create one entry in a queue by material (those entries will be processed later)... So doing some insert in the database.
What I do, I open a DB connection, then loop to do my inserts...
Problem is that if this loop take too much time, the connection seems to be automatically closed, I got this in the log :
Connection object com.sap.sql.jdbc.vendor.VendorConnectionHandle@43c6ce53 has already been closed...
Do you know if there is a parameter we could extend (I guess the connection time-out is set to 60 seconds), or should I handle this in my code ?
Here is a summary of my code :
try {
connection = SystemBase.createDefaultSystemBase().getDBConnection();
for (int i = 0; i < inputInformation.size(); i++) {
 row = inputInformation.extractRow(i);
 statement.execute(insertQuery);
} catch (SQLException e) {
if (Utils.isTraceEnabled(Utils.COLLABORATION)) {
 e.printStackTrace();
returnData.put("EXCEPTION", e.toString());
returnData.put("SUCCESS", "false");
returnData.put("ERROR_MESSAGE", e.getMessage());
return returnData;
} finally {
SystemBase.closeDBConnection(connection, statement);
Thanks

As a rule timeouts should not be handled in the code. Reaching a timeout value should serve as an indication of a failure in the system that should never happen under normal circumstances.
This problem could be related to database connection timeout. This one must be set on the database side and it must fit your business needs. This parameter is vendor specific. Additionally, such exceptions could be caused by network issues, usage of firewall and antivirus software, etc.
Regards

Too many inactive database connections (c#, webapp, Oracle)

 I have a web application that uses the CrystalDecisions.Web.CrystalReportViewer to display my reports. The application opens a connection to an Oracle database with SetDatabaseLogon(). I have not yet implemented anything to free the connections when they're not needed anymore. I read in the Crystal help that the best place to call ReportDocument.Close() is in the Page_Unload method.The problem is that my reports have dynamic cascading parameters that make the page reload (ie Page_Unload -> Page_Load) several times. I can eventually call ReportDocument.Close() in a Global.asax method, like Session_End(), but I'm not sure it is optimal, as my report object is not known in this scope and I have extra code to write to handle this. Is there a better way to manage database connection ? Can anyone provide a working sample ?thanks 

I'm not aware of a better way. Your connections are definately being held up because you are not closing the Report. Possibly you could put a conditional ReportDocument.close() call in your unload method. You would need to check to make sure that the document was available and that you weren't loading parameters. I'm sure that this would work. Rob Horne<a href="/blog/10">Rob's blog - http://diamond.businessobjects.com/blog/10</a>

Oracle 11g database Connection & Response are very slow

I have an ORACLE 11g R2 on lRed Hat Enterprise Linux Server release 5.3 (Tikanga).
initially it was working fine.
Now a days while attempting to connect into the database from network using @service_name
it takes a lot of time to establish the connection and even it gets connected the query response time is very high.
on the other hand if I connect from the native database machine's terminal without @service_name it works fine & the response time is convincing. But even from the native database machine's terminal with @service_name it is giving me the same pain.
can any body help me how to fix this.
Thanks in advance..
Arkesh

thanks for the reply & Query
Alert Log entry do look like this
ORACLE_BASE from environment = /u01/app/oracle
Thu Apr 22 07:29:10 2010
ALTER DATABASE MOUNT
Successful mount of redo thread 1, with mount id 4283520006
Database mounted in Exclusive Mode
Lost write protection disabled
Completed: ALTER DATABASE MOUNT
Thu Apr 22 07:29:15 2010
ALTER DATABASE OPEN
Beginning crash recovery of 1 threads
parallel recovery started with 7 processes
Started redo scan
Completed redo scan
read 15 KB redo, 23 data blocks need recovery
Started redo application at
Thread 1: logseq 449, block 8217
Recovery of Online Redo Log: Thread 1 Group 2 Seq 449 Reading mem 0
Mem# 0: /u01/app/oracle/oradata/ultimus/redo02.log
Completed redo application of 0.01MB
Completed crash recovery at
Thread 1: logseq 449, block 8248, scn 10502937
23 data blocks read, 23 data blocks written, 15 redo k-bytes read
Thread 1 advanced to log sequence 450 (thread open)
Thread 1 opened at log sequence 450
Current log# 3 seq# 450 mem# 0: /u01/app/oracle/oradata/ultimus/redo03.log
Successful open of redo thread 1
MTTR advisory is disabled because FAST_START_MTTR_TARGET is not set
SMON: enabling cache recovery
Successfully onlined Undo Tablespace 2.
Verifying file header compatibility for 11g tablespace encryption..
Verifying 11g file header compatibility for tablespace encryption completed
SMON: enabling tx recovery
Database Characterset is WE8MSWIN1252
No Resource Manager plan active
replication_dependency_tracking turned off (no async multimaster replication found)
Starting background process QMNC
Thu Apr 22 07:29:18 2010
QMNC started with pid=27, OS id=3611
Completed: ALTER DATABASE OPEN
Thu Apr 22 07:29:20 2010
db_recovery_file_dest_size of 10240 MB is 0.00% used. This is a
user-specified limit on the amount of space that will be used by this
database for recovery-related files, and does not reflect the amount of
space available in the underlying filesystem or ASM diskgroup.
Thu Apr 22 07:29:20 2010
Starting background process CJQ0
Thu Apr 22 07:29:20 2010
CJQ0 started with pid=28, OS id=3817
Thu Apr 22 07:34:18 2010
Starting background process SMCO
Thu Apr 22 07:34:18 2010
SMCO started with pid=19, OS id=3861
Thu Apr 22 07:59:23 2010
Thread 1 advanced to log sequence 451 (LGWR switch)
Current log# 1 seq# 451 mem# 0: /u01/app/oracle/oradata/ultimus/redo01.log
Thu Apr 22 10:09:23 2010
DM00 started with pid=34, OS id=6272, job ULTIMUS.SYS_EXPORT_SCHEMA_01
Thu Apr 22 10:09:25 2010
DW00 started with pid=35, OS id=6274, wid=1, job ULTIMUS.SYS_EXPORT_SCHEMA_01
Thu Apr 22 10:11:20 2010
Thread 1 cannot allocate new log, sequence 452
Private strand flush not complete
Current log# 1 seq# 451 mem# 0: /u01/app/oracle/oradata/ultimus/redo01.log
Thread 1 advanced to log sequence 452 (LGWR switch)
Current log# 2 seq# 452 mem# 0: /u01/app/oracle/oradata/ultimus/redo02.log
Thu Apr 22 10:13:28 2010
DM00 started with pid=45, OS id=6395, job ULTIMUSISL.SYS_EXPORT_SCHEMA_01
Thu Apr 22 10:13:29 2010
DW00 started with pid=46, OS id=6397, wid=1, job ULTIMUSISL.SYS_EXPORT_SCHEMA_01
Thu Apr 22 10:14:29 2010
Thread 1 cannot allocate new log, sequence 453
Private strand flush not complete
Current log# 2 seq# 452 mem# 0: /u01/app/oracle/oradata/ultimus/redo02.log
Thread 1 advanced to log sequence 453 (LGWR switch)
Current log# 3 seq# 453 mem# 0: /u01/app/oracle/oradata/ultimus/redo03.log
Thu Apr 22 10:15:40 2010
DM00 started with pid=43, OS id=6432, job IULTIMUS.SYS_EXPORT_SCHEMA_01
Thu Apr 22 10:15:41 2010
DW00 started with pid=45, OS id=6434, wid=1, job IULTIMUS.SYS_EXPORT_SCHEMA_01
Thu Apr 22 10:16:38 2010
DM00 started with pid=45, OS id=6450, job ULTIMUSEXT.SYS_EXPORT_SCHEMA_01
Thu Apr 22 10:16:38 2010
DW00 started with pid=46, OS id=6452, wid=1, job ULTIMUSEXT.SYS_EXPORT_SCHEMA_01
Thu Apr 22 10:26:18 2010
Fatal NI connect error 12537, connecting to:
(LOCAL=NO)
VERSION INFORMATION:
     TNS for Linux: Version 11.2.0.1.0 - Production
     Oracle Bequeath NT Protocol Adapter for Linux: Version 11.2.0.1.0 - Production
     TCP/IP NT Protocol Adapter for Linux: Version 11.2.0.1.0 - Production
Time: 22-APR-2010 10:26:18
Tracing not turned on.
Tns error struct:
ns main err code: 12537
TNS-12537: TNS:connection closed
ns secondary err code: 12560
nt main err code: 0
nt secondary err code: 0
nt OS err code: 0
opiodr aborting process unknown ospid (6587) as a result of ORA-609

Database connection closing in JSF

Similar Messages

Maybe you are looking for