Abandoned connections

Hi,
I am trying to find a way of detecting and closing abandoned database connections, i.e., connections not closed by the applications. The thing is that some applications which run in my app server leave open connections, and apart from telling them to solve the problem, i would like to have some way of detecting these connections and closing them.
I don't see how can i do this, because the pool is implemented by the app server, and i haven't read anything about this in the documentation.
Any help would be greatly apreciated.
Thanks
Juan

let me put it other way. does anyone of you still uses
dbcp with removeAbandoned set to true in production?We have a system where we did want to handle this, because we give the "users" the abiity to script the system, and one of the scripting functions is to get a connection to the database and perform arbitrary queries.
So I did want to take care of "leaked" (abandoned) connections. However, I found out that the DBCP abandoned-connection support was a little too crude (very little control over the reaping of connections), so I ended up rolling my own layer on top of DBCP to do what I wanted, and stopped using their support. Quite fortunately, too, since 1.1 then went and deprecated it anyway.
Moral: don't depend on their abandoned-connection "support". If you have a system where connections can legitimately (i.e. not a bug in your code) be "abandoned" (say, due to user action or inaction, etc.), then roll your own connection-reaping support.
Otherwise, use this feature only in testing, and only to detect the situation, not to correct it.

Similar Messages

Orphaned/Abandoned connections

I have a roaming/managed environment, with 10.4.11 clients and user profiles living on a 10.4.11 server.
A handful of users are having problems disconnecting from the server on logout. That is, they logout successfully, but the AFP service holds onto the connection as though the user were still logged in and connected.
These users seem to be encountering this problem with specific machines and not with others, although hardware profiles are identical (eMac, 1 GHz).
Any help would be greatly appreciated.

let me put it other way. does anyone of you still uses
dbcp with removeAbandoned set to true in production?We have a system where we did want to handle this, because we give the "users" the abiity to script the system, and one of the scripting functions is to get a connection to the database and perform arbitrary queries.
So I did want to take care of "leaked" (abandoned) connections. However, I found out that the DBCP abandoned-connection support was a little too crude (very little control over the reaping of connections), so I ended up rolling my own layer on top of DBCP to do what I wanted, and stopped using their support. Quite fortunately, too, since 1.1 then went and deprecated it anyway.
Moral: don't depend on their abandoned-connection "support". If you have a system where connections can legitimately (i.e. not a bug in your code) be "abandoned" (say, due to user action or inaction, etc.), then roll your own connection-reaping support.
Otherwise, use this feature only in testing, and only to detect the situation, not to correct it.

Option of auto reclaiming 'abandoned' connection in DB conn pool

Hi, All,
It seems that by default DB conn pool implementation in Web AS 6.40 Java has the freature of automatically reclaiming 'abondoned' database connection when it detects a connection has been idle for a period of time. I wonder whether this feature is configurable because I want to turn it off. In some cases the JDBC connection got from pool needs to keep open all the time, so are the statement or preparedstmt.
Thanks in advance
John

Hi John
You can try increasing the max-pool size and if you observe any improvement.
Ignore the below if you already know how to tune the DB connections.
Change the max-pool-size to a higher number in domain.xml for creator domain.
<jdbc-connection-pool connection-validation-method="auto-commit" datasource-classname="com.pointbase.xa.xaDataSource" fail-all-connections="false" idle-timeout-in-seconds="300" is-connection-validation-required="false" is-isolation-level-guaranteed="true" max-pool-size="32" max-wait-time-in-millis="60000" name="PointBasePool" pool-resize-quantity="2" res-type="javax.sql.XADataSource" steady-pool-size="8">
<property name="DatabaseName" value="jdbc:pointbase:server://localhost:9092/sun-appserv-samples"/>
<property name="Password" value="pbPublic"/>
<property name="User" value="pbPublic"/>
</jdbc-connection-pool>
Thanks
Srinivas
Creator Suppot

Accidentally abandoned and not closed connections

Tome cat datasource can close abandoned connections. can weblogic data source implement
this? If not how can webligic connection pool deal with these accidentally abandoned
and not closed connections?

zorro wrote:
connection is retrived by this function.
public Connection createConnection()throws Exception{
try{
InitialContext ictx=new InitialContext();
DataSource ds=(DataSource)ictx.lookup("jdbc/Oracle");
return ds.getConnection();
catch(NamingException e){
logger.error("failed to get connection:"+e);
return null;
And most of us use it in the way as follow. But I am not sure that there is no
connection leak in the code of the other programmers. If connection leak steadily
and seldom occur, what will happan when the weblogic server works for a long time?
I know that tomcat datasource handal the connection leak very well.The code below is correct. As soon as GC finds an abandoned connection, it will
be closed and returned to the pool. You can also turn on leak checking, which will
print out where the leaked connection was reserved, to help you find the code tp fix.
Joe
>
>
Connection conn=null;
try{
conn=createConnection();
catch(Exception e ){
finally{
try{
if(conn!=null)conn.close();
catch(Exception e ){}

Listener EA2: database connection pool and connection revalidation

Hi all,
As one can expect from early adopter release there could be some bugs but I can't find any references in forum to my situation:
* My 11g XE database and listener are starting as windows services when server boots operating system (Windows Server 2003 R2).
* I configured my web server (unsupported Jetty 9.0.0.M1) to start as windows service when operating system starts.
* Apex Listener 2.0.0.268.17.05 configured to connect with XE using JDBC thin driver with default settings (initial pool size 3, max statements 10, min connections 1, max connections 10, inactivity timeout 1800, abandoned connection timeout 900)
* Because web server starts a bit faster than Oracle database when apex connects first time it gets "ORA-12528, TNS:listener: all appropriate instances are blocking new connections" (could be that database still starting but already registered service with listener)
* From listener.log file I can see that all further connections made from Apex listener succeeds
* When I try to open any apex page with browser I am getting 404 error and apex listener logs error (*time is 2 days after system startup*):
2012-11-30 3:56:02 PM oracle.dbtools.common.config.db.DatabaseConfig badConfiguration
SEVERE: The pool named: apex is not correctly configured, error: Listener refused the connection with the following error:
ORA-12528, TNS:listener: all appropriate instances are blocking new connections
ConnectionPoolException [error=BAD_CONFIGURATION]
     at oracle.dbtools.common.jdbc.ConnectionPoolException.badConfiguration(ConnectionPoolException.java:62)
     at oracle.dbtools.common.config.db.DatabaseConfig.badConfiguration(DatabaseConfig.java:146)
     at oracle.dbtools.common.config.db.DatabaseConfig.createPool(DatabaseConfig.java:168)
     at oracle.dbtools.common.config.db.DatabaseConfig.getConnection(DatabaseConfig.java:68)
     at oracle.dbtools.common.jdbc.ora.OraPrincipal.connection(OraPrincipal.java:25)
     at oracle.dbtools.apex.ModApexContext.getConnection(ModApexContext.java:320)
     at oracle.dbtools.apex.Procedure.getProcedure(Procedure.java:166)
     at oracle.dbtools.apex.OWA.validateProcedure(OWA.java:384)
     at oracle.dbtools.apex.security.Security.isValidRequest(Security.java:171)
     at oracle.dbtools.apex.ModApex.validateRequest(ModApex.java:233)
     at oracle.dbtools.apex.ModApex.doGet(ModApex.java:79)
     at oracle.dbtools.apex.ModApex.service(ModApex.java:263)
     at oracle.dbtools.rt.web.HttpEndpointBase.modApex(HttpEndpointBase.java:288)
     at oracle.dbtools.rt.web.HttpEndpointBase.service(HttpEndpointBase.java:127)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:848)
     at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:665)
     <... Jetty web server stack ...>
     at java.lang.Thread.run(Unknown Source)
2012-11-30 3:56:02 PM oracle.dbtools.rt.web.HttpEndpointBase modApex
* Oracle listener log for same time (no errors here):
30-NOV-2012 15:56:01 * (CONNECT_DATA=(CID=(PROGRAM=JDBC Thin Client)(HOST=__jdbc__)(USER=SYSTEM))(SERVICE_NAME=xe)(CID=(PROGRAM=JDBC Thin Client)(HOST=__jdbc__)(USER=SYSTEM))) * (ADDRESS=(PROTOCOL=tcp)(HOST=127.0.0.1)(PORT=1078)) * establish * xe * 0
30-NOV-2012 15:56:01 * (CONNECT_DATA=(CID=(PROGRAM=JDBC Thin Client)(HOST=__jdbc__)(USER=SYSTEM))(SERVICE_NAME=xe)(CID=(PROGRAM=JDBC Thin Client)(HOST=__jdbc__)(USER=SYSTEM))) * (ADDRESS=(PROTOCOL=tcp)(HOST=127.0.0.1)(PORT=1079)) * establish * xe * 0
30-NOV-2012 15:56:01 * (CONNECT_DATA=(CID=(PROGRAM=JDBC Thin Client)(HOST=__jdbc__)(USER=SYSTEM))(SERVICE_NAME=xe)(CID=(PROGRAM=JDBC Thin Client)(HOST=__jdbc__)(USER=SYSTEM))) * (ADDRESS=(PROTOCOL=tcp)(HOST=127.0.0.1)(PORT=1080)) * establish * xe * 0
30-NOV-2012 15:56:01 * (CONNECT_DATA=(CID=(PROGRAM=JDBC Thin Client)(HOST=__jdbc__)(USER=SYSTEM))(SERVICE_NAME=xe)(CID=(PROGRAM=JDBC Thin Client)(HOST=__jdbc__)(USER=SYSTEM))) * (ADDRESS=(PROTOCOL=tcp)(HOST=127.0.0.1)(PORT=1081)) * establish * xe * 0
* For some reason apex listener keeps first connection status and won't try to establish new connection if first attempt finished with ORA-12528
* The same scenario is valid when at time of web server start oracle database/listener is not available - even if database and listener starts and apex successfully establishes further connections all apex pages gets 404 error
* If I restart web server windows service (while oracle db and listener still running) browser opens apex pages without errors and apex listener does not log any errors
* I know that I can avoid this error delaying start of web server windows service but it would be nice to have production release 2.x without such bugs

Hi,
Is there any way to use the connection pool or Datasource while connecting to database?If I am using a stateless sesssion bean and using a Data Access layer which just creates a database session to write the persistence toplink objects how I can make use of application server connection pool?Hi Vinod,
Yes, TopLink allows you to use the app server's connection pooling and transaction services. Chapter 2 of the Oracle9iAS TopLink Foundation Library Guide provides details as do the TopLink examples. The easiest way to set this up is by using the sessions.xml file. The sample XML below is from the file <toplink903>\examples\ias\examples\ejb\sessionbean\sessions.xml. Here we are adding the datasource defined in OC4J and specifying that we are using the OC4J transaction controller also.
<login>
<user-name>sa</user-name>
<password></password>
<datasource>java:comp/env/jdbc/ejbJTSDataSource</datasource>
<uses-external-transaction-controller>true</uses-external-transaction-controller>
<uses-external-connection-pool>true</uses-external-connection-pool>
</login>
<external-transaction-controller-class>oracle.toplink.jts.oracle9i.Oracle9iJTSExternalTransactionController</external-transaction-controller-class>
When using this approach you need to change your TopLink code slightly in the EJB methods:
a. Acquire the ACTIVE unit of work from the server
session (again, see the EmployeeSessionEJB code
example) with something like:
UnitOfWork uow = clientSession.getActiveUnitOfWork();
b. Calls to uow.commit() can be ommitted or commented out
because the EJB will handle this. Note that of course
the methods you create in the EJB that are using this
approach must have TX Required (default).
Hope this helps.
Pete

Connection error while defining a IT resource for SQLServer

Hello,
I am new to the OIM. I am trying to provision users to a SQLServer database. I installed the DBConnector successfully, but while defining a ITResource (of type 'DBUM ITResource definition') for SQLServer from Web UI, I am getting this error.
Test connectivity is not supported for the IT resource type DBUM ITResource definition
Click Back to correct the connection parameters and re-test connection or click Continue to create the IT Resource anyway
Here are the parameters I am providing. I am sure I am entering the correct uid and pwd for the database.
Abandoned connection timeout :900
Admin ID : testUser
Admin Password : testPassword
Configuration : Lookup.DBUM.MSSQL.Configuration
Connection pooling supported : False
Connection Properties :
Connection Retries : 2
Connection Timeout : 1000
Connection wait timeout : 60
Database Driver : com.microsoft.sqlserver.jdbc.SQLServerDriver
Database Name : testDatabase
Inactive connection timeout : 300
Initial pool size : 3
isSecure : No
JDBC URL : jdbc:sqlserver://SQLServerHost;database=testDatabase
Max pool size : 30
Min pool size : 2
Native connection pool class definition :
Pool excluded fields : Configuration Lookup
Pool preference : Default
ResourceConnection class definition : oracle.iam.connectors.dbum.common.db.util.DBUMResourceConnectionImpl
Retry Interval : 1000
Target supports only one connection : False
Timeout check interval : 30
Validate connection on borrow : true
Thanks!
Kabi

Hi,
I setup the trace of com.waveset.adapter.ScriptedConnection.
the log message is following, what's reason of prblem? please help.
20070723 16:16:47.937 httpWorkerThread-8080-4(0x01341244) ScriptedConnectionPool#getConnection() Entry no args
20070723 16:16:47.937 httpWorkerThread-8080-4(0x01341244) ScriptedConnectionPool#getConnection() Exit void
20070723 16:16:47.938 httpWorkerThread-8080-4(0x01341244) TelnetConnection#connect() Entry no args
20070723 16:16:47.938 httpWorkerThread-8080-4(0x01341244) TelnetConnection#connect() Exit void
20070723 16:16:47.938 httpWorkerThread-8080-4(0x01341244) ScriptedConnection#runScript(Script) Entry no args
20070723 16:16:47.938 httpWorkerThread-8080-4(0x01341244) ScriptedConnection#processWaitFor() Entry no args
20070723 16:16:47.939 httpWorkerThread-8080-4(0x01341244) ScriptedConnection#refreshUnprocessedInput(int, int, String, boolean) Entry no args
20070723 16:17:57.990 httpWorkerThread-8080-4(0x01341244) ScriptedConnection#processWaitFor() Info Script failed waiting for "LOGIN:" with the following unprocessed text: ""

Anyone connected an Apple ADC CRT to Powerbook DVI, how??

I have my older 17" Apple Studio Display ADC CRT which I would like to use at home for extra screen space with my Titanium Powerbook which has a DVI port.
I bought the DVI to ADC adapter but have found out it ONLY works on the ADC LCDs and NOT CRTs. Crazy. So what connects these two together. I have seen many others in the Apple Display Forums with the same frustration but no solutions.
What gives? Apple abandoned connecting two of their own products which did overlap in time when sold.
Anyone else trying to do the same or are successfuly using these together?

I know your post is a bit old, but I'll contribute what I know anyway - You cannot use a DVI-ADC adapter with the ADC CRT because it is an analog display, and DVI by definition requires a digital signal. Therefore, neither the Apple adapter nor any other adapter can convert the signal from the CRT. It's outside of Apple's control. All of the LCD displays that are ADC use a digital signal, so they work just fine.
Apple only ever manufactured the one 17-inch ADC CRT, and only for about six months, so they're not affecting too many people... Unfortunately, you're one of them - and I have a beautiful, retired 17-inch CRT that I can't use with my PowerBook (Aluminum).
I got a 20-inch Cinema, and I love it.

Oracle error: java.sql.sqlrecoverableException: Closed Connection

need help on this closed connection
getting oracle error: java.sql.sqlrecoverableException: Closed Connection when running a java application using tomcat api to oracle 11g database EE 11.2.0.3.0 on windows 2008 R2
The process is reading data from an Oracle database using user_sdo_geom_metadata , memory allocated to DB is 5GB, java pool size 1G allocated , below is the code which gets data from Oracle
<NamedDataSourceDefinition:NamedDataSourceDefinition xmlns:NamedDataSourceDefinition="http://www.mapinfo.com/mxp" xmlns="http://www.mapinfo.com/mxp" xmlns:gml="http://www.opengis.net/gml"xmlns:ns2="http://www.mapinfo.com/midev/service/common/v1" xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:v1="http://www.mapinfo.com/midev/service/namedresource/v1"version="MXP_WorkSpace_1_5">
<ConnectionSet/>
<DataSourceDefinitionSet>
<DBDataSourceDefinition id="TXLANDMARKS">
<DataSourceName>txlandmarks</DataSourceName>
<ConnectionMember>
<InlineDBConnection dbType="oracle">
<JDBCDriverParameters>
<JDBCUrl>jdbc:oracle:thin:@NOIORAENT2K8-64:1521:FMETEST</JDBCUrl>
<DriverPropertySet>
<Property name="user" value="NOIDADATADEV"/>
<Property name="password" value="mndata"/>
</DriverPropertySet>
</JDBCDriverParameters>
</InlineDBConnection>
</ConnectionMember>
<DBTable owner="NOIDADATADEV" useQuotes="true">TXLANDMARKS</DBTable>
</DBDataSourceDefinition>
</DataSourceDefinitionSet>
<DataSourceRef ref="TXLANDMARKS"/>
</NamedDataSourceDefinition:NamedDataSourceDefinition>
Both the machines can ping to each other successfully, no firewall exists between them, these are connection setting been used in pooling-datasource-factory.properties
poolingDataSourceFactoryClass=com.mapinfo.midev.dbms.jdbc.TomcatDataSourceFactory
# what follows are properties specific to com.mapinfo.midev.dbms.jdbc.TomcatDataSourceFactory
# defaultAutoCommit - the default auto commit state of the connection. if
# not set the assumes the driver default
# defaultAutoCommit =
# (int) The maximum number of active connections that can be allocated from # this pool at the same time. The default value is 20
maxActive = 10
# (int) The maximum number of connections that should be kept in the pool at # all times. Default value is maxActive. Idle connections are checked # periodically (if enabled) and connections that been idle for longer than
# minEvictableIdleTimeMillis will be released.
maxIdle = 10
# (int) The minimum number of established connections that should be kept in the pool at all times. The connection pool can shrink below this number if # validation queries fail. Default value is 10
minIdle = 5
# (int)The initial number of connections that are created when the pool is # started. Default value is 10
initialSize = 5
# (int) The maximum number of milliseconds that the pool will wait (when # there are no available connections) for a connection to be returned before # throwing an exception. Default value is 30000 (30 seconds)
# maxWaitMillis = 30000
# (int) The number of milliseconds to sleep between runs of the idle # connection validation/cleaner thread. This value should not be set under 1
# second. It dictates how often we check for idle, abandoned connections,
# and how often we validate idle connections. The default value is 5000
# (5 seconds).
# timeBetweenEvictionRunsMillis = 5000
# (int) The minimum amount of time an object may sit idle in the pool before
# it is eligible for eviction. The default value is 60000 (60 seconds).
# minEvictableIdleTimeMillis = 60000
# (boolean) Flag to remove abandoned connections if they exceed the
# removeAbandonedTimout. If set to true a connection is considered abandoned
# and eligible for removal if it has been in use longer than the
# removeAbandonedTimeout Setting this to true can recover db connections
# from applications that fail to close a connection. See also
# logAbandoned The default value is false.
# removeAbandoned = false
# (int) Timeout in seconds before an abandoned(in use) connection can be
# removed. The default value is 60 (60 seconds). The value should be set to
# the longest running query your applications might have.
# removeAbandonedTimeout = 60
# (boolean) Flag to log stack traces for application code which abandoned a
# Connection. Logging of abandoned Connections adds overhead for every
# Connection borrow because a stack trace has to be generated. The default
# value is false.
# logAbandoned = false
# (long) Time in milliseconds to keep this connection. When a connection is
# returned to the pool, the pool will check to see if the now
# - time-when-connected > maxAge has been reached, and if so, it closes the
# connection rather than returning it to the pool. The default value is 0,
# which implies that connections will be left open and no age check will be
# done upon returning the connection to the pool.
# maxAgeMillis = 0

Hi,
I understand that you have raised a SR for this issue which is being worked upon by our team.
Additionally, please note that the "Closed connection" error typically happens because a timeout parameter of some sort timed out the connection. This could be a parameter specified in your datasource, in your application code, or network (such as a firewall).
You may also want to -
1. check your database to be sure it is not timing out connections.
2. Make sure your network is running efficiently and that it can provide fast connections,
3. Check your Java Virtual Machine (JVM) Code Cache For Oracle Enterprise Data Quality for any memory related issues
Thanks,
Shwet

OAS 10.1 3.1 0 OC4J JDBC Connection/Timeout settings

I am fairly new to OAS, and am trying to resolve a intermitent issue,
I have an OAS 10.1.3.1.0 with a deployed EAR file I was provided by a supplier containing mainly PL/SQL based logic, which configured the OAS to ask a middle tier for a an external to pass data to it via Stored Procedure and then usiing the deployed package connect to an external Oracle DB and insert the data.
Oas is running on a Windows 2003 platform that has no problems or connectivity problems, how ever intermittenlt the OAS stops uploading data to the external Oracle DB. Some custom external logging details this as a communication at the time it occurs, how ever there are no comms issues. A quick restart of the OAS windows service resolves the issue.
Apart from upgrading OAS to patch set 5, the only other thing I considered could be causing the issue is how OAS is handling the session timeout or connection pool.
I can see the following settings for the JDBC connection I am using, I wondered if anyone could advise anything that could be changed? I am not sure the implications on setting the validate connection to True and also not sure why maximum number of connections is set to -1?
Connections
Initial size of Connection Cache
Minimum Number of Connections
Maximum Number of Connections
Connection Retry Interval (seconds)
Maximum Connection Attempts
Maximum Number of Statements Cached
Lower Threshold Limit On Pool (%)
Defaults to 20% of max connections.
Validate Connection FalseTrue
Timeouts
Inactivity Timeout (seconds)
Time that an unused connection is inactive before it is removed from the pool.
Wait For Used Connection Timeout (seconds)
Maximum time to wait for a used connection to be released.
Max Active Time for a Used Connection (seconds)
Maximum time a used connection may be active.
Abandoned Connection Timeout (seconds)
Enforce Timeout Limits Interval (seconds)
Any help would be appreciated

Hi,
Along with Priya's suggestions, please refer the link below for the details on the parameters.
http://download.oracle.com/docs/cd/B32110_01/web.1013/b28958/datasrc.htm#CHDCFCHB
Hope this will help understand all the parameters.
Also refer,
What Should Be My Maximum Connection Pool Size? [ID 1061155.1]
http://www.oracle.com/technology/tech/java/sqlj_jdbc/htdocs/jdbc_faq.html
Regards,
Mithun

Connection Pool hangs

Hello,
We have a strange problem with Oracle Connetion pool on IAS 10.1.3.1.0.
Sometimes (for example once a week, sometimes one a month) connection pool hangs. Enterprise Manager / Connection pool monitor page shows information about threads waiting for connection (see below) and users are unable to work with application.
Connections In Use                1
Free Connections                13
Total Connections in Pool           14
Threads Waiting for Connections      534
WebApp installed on IAS is a simple Toplink based application. There are no strange messages in error logs, so why connection pool is unable to assign free connection to user ?
Thanks in advance
Tom
Edited by: olos on Sep 30, 2008 8:57 PM

Hello,
Thanks for response. I will try if it is possible to test connection from AS control during next connection pool crash. BTW we must check if this situation is not caused by operation system (Linux) swapping process.
Regards
Tom
My datasources file is:
<?xml version = '1.0' encoding = 'UTF-8'?>
<data-sources xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:noNamespaceSchemaLocation="http://xmlns.oracle.com/oracleas/schema/data-sources-10_1.xsd"
schema-major-version="10" schema-minor-versio
n="1">
<managed-data-source connection-pool-name="Example Connection Pool"
jndi-name="jdbc/OracleDS" name="OracleDS"/>
<managed-data-source connection-pool-name="Bufor List Connection Pool"
jndi-name="jdbc/BuforListDS" name="Bufor List Data Source"/>
<connection-pool name="Example Connection Pool">
<connection-factory
factory-class="oracle.jdbc.pool.OracleDataSource" user="scott"
password="tiger" url="jdbc:oracle:thin:@//localhost:1521/ORCL"/>
</connection-pool>
<connection-pool name="PRD Connection Pool"
abandoned-connection-timeout="120" connection-retry-interval="3"
max-connect-attempts="5" max-connections="200" min-connections="3"
property-check-interv
al="600">
<connection-factory
factory-class="oracle.jdbc.pool.OracleDataSource" user="user"
password="password"
url="jdbc:oracle:thin:@(DESCRIPTION=(ADDRESS_LIST=(LOAD_BALANCE=on)(ADDRESS=(PROTOCOL=tcp)(HOST
=host01)(PORT=1521))(ADDRESS=(PROTOCOL=tcp)(HOST=host02)(PORT=1521)))(CONNECT_DATA=(SERVICE_NAME=SN.DOMENA.PL)))"/>
</connection-pool>
</data-sources>

What happends if I dont close the connection

Hi,
I would like to know what happends if I dont close the connection after processing. we wont get any compile time & run time error if you dont close the connection. But why we used to close the connetion. Any specific reason for this. Please let me know.
Regards,
Satish

What happens if you don't close a connection? It depends on how many connections you open and how long your program keeps running.
Let's start with the case of a standalone program that runs for a little while then exits.
While the program is running, the operating system maintains a network connection to the database server for each open database connection; there are system limits on the number of open network connections, although this is usually a very high number. Also, every open connection to a database uses resources of the database; many databases have limits on the number of connections they can have open at once. Some database products or configurations (Oracle in "dedicated" mode) will also start a seperate process on the server for each open connection; too many open connections and these processes start swapping out to disk, too many more and the server runs out of memory.
When the program exits, the operating system will close any open network connections; the database server will also recognize that the network connections are closed. If the database supports transactions and the connection was in a transactional mode and there were uncommitted transactions, then the uncommitted transactions will be rolled back. Ultimately, all the database resources get released (assuming there are no bugs in the database program).
Thus, a program that runs for a few minutes, commits all its transactions and exits without closing connections doesn't do major harm; the operating systems of both the client and the database server clean up the network connection and the database itself cleans up the database connection. It's all designed this way because programs sometimes crash; you can't have a system/database that breaks when that occurs... However, this cleanup is not always absolutely immediate on program exit; it usually takes a short time, seconds to minutes, for everything to clean up. Therefore, if the same programs is run over and over real fast, it becomes possible to exhaust a resource, such as memory or network connections. For a quick little test program that's run once and that's it, no problem...
Now for a long running prgram, such as a web application that will run for days or months...
As I've alluded to above, each database connection uses system resources, both on the client machine and on the database server. When a connection is maintained open, those resources are tied up; there's always a limit on the total number of connections that can be supported, although with the right software, hardware and database configurations that limit can be a huge number, tens of thousands. For other systems, it might be a low number, hundreds or less. Whatever it is, the program could potentially reach that limit and cause something to fail. If it doesn't reach that limit (or cause another program to push past the limit) then there's no problem (other than a potential performance impact).
Now within a Java program, the JDBC standard requires that when an open database connection object is garbage collected, the connection is first closed. Assuming your driver conforms to the standard in this regard, and assuming no resource limit gets exceeded, then a long running program could open and abandon connections and let the garbage collector close and clean up. However, garbage collection is unpredictable, and connections are often sufficiently long lived that they get moved out of the "Eden" memory space and into the space of long-lived objects. These objects are only garbage collected when a "full" garbage collection takes place; a "partial" collection only examines the "Eden" space. Thus, depending on the applications load and memory usage and connection usage pattern and garbage collection configuration, an abandonded connection might not be garbage collected for hours or even days, greately increasing the chances that you run out of resources.
In other words, not closing your connections in a long running program is a really really bad idea.

Closed Connection Issues

We're having some issues with closed connection errors. Basically, if a user is idle long enough, if he clicks a button, then the results won't show and a closed connection error will be thrown. Frequently the user will have to re-enter information or it leads to some bad results. These tend to happen with views in particular.
So, any ideas? I'm new to JDeveloper and Oracle, so I'm not quite sure where to start or information I should provide. Our pages are running off of one virtual machine with the Oracle database on another virtual machine, both on the same physical machine.
A couple questions:
1) Does this have anything to do with Session timeout? We have ours set to 60 minutes. When I set it to 1 minute, it'll redirect to the login page at 1 minute. Odd... I just tested by idling on a page for 90 minutes, no redirect, no error thrown...
2) We have validate-connection set to true, but do not have validate-connection-query set. Is there a default value or will this stop the verification?
Thank you very much.
Here's our datasource information:
<data-sources xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="http://xmlns.oracle.com/oracleas/schema/data-sources-10_1.xsd" xmlns="http://xmlns.oracle.com/oracleas/schema">
<connection-pool name="jdev-connection-pool-DBSVR" disable-server-connection-pooling="false" validate-connection="true" abandoned-connection-timeout="60">
<connection-factory factory-class="oracle.jdbc.pool.OracleDataSource" user="user" password="" url="jdbc:oracle:thin:@192.168.130.23:1521:web"/>
</connection-pool>
<managed-data-source name="jdev-connection-managed-DBSVR" jndi-name="jdbc/DBSVRDS" connection-pool-name="jdev-connection-pool-DBSVR"/>
<native-data-source name="jdev-connection-native-STRATDBSVR" jndi-name="jdbc/STRATDBSVRCoreDS" url="jdbc:oracle:thin:@192.168.130.23:1521:web" user="user" password="" data-source-class="oracle.jdbc.pool.OracleDataSource"/>
</data-sources>
Session timeout:
<session-config>
<session-timeout>60</session-timeout>
</session-config>
Here's an example of the error:
INFO: Fatal error code : '17,008' detected handling SQLException : 'java.sql.SQLException: Closed Connection'.
12/01/09 14:40:27 java.lang.NullPointerException
12/01/09 14:40:27      at oracle.oc4j.sql.proxy.StatementBCELProxy.oc4j_releaseToCache(StatementBCELProxy.java:67)
12/01/09 14:40:27      at oracle.oc4j.sql.proxy.StatementBCELProxy.oc4j_releaseTarget(StatementBCELProxy.java:79)
12/01/09 14:40:27      at oracle.oc4j.sql.proxy.SQLBCELProxy.oc4j_close(SQLBCELProxy.java:95)
12/01/09 14:40:27      at oracle.oc4j.sql.proxy.StatementBCELProxy.close(StatementBCELProxy.java:92)
12/01/09 14:40:27      at oracle.jbo.server.DBTransactionImpl.closeStatement(DBTransactionImpl.java:4202)
12/01/09 14:40:27      at oracle.jbo.server.ViewObjectImpl.closeFreedStatements(ViewObjectImpl.java:8466)
12/01/09 14:40:27      at oracle.jbo.server.ViewObjectImpl.closeStatements(ViewObjectImpl.java:8451)
12/01/09 14:40:27      at oracle.jbo.server.DBTransactionImpl.closeStatements(DBTransactionImpl.java:4370)
12/01/09 14:40:27      at oracle.jbo.server.DBTransactionImpl.closeTransaction(DBTransactionImpl.java:1542)
12/01/09 14:40:27      at oracle.jbo.server.DBTransactionImpl.disconnect(DBTransactionImpl.java:4730)
12/01/09 14:40:27      at oracle.jbo.server.DBTransactionImpl2.disconnect(DBTransactionImpl2.java:310)
12/01/09 14:40:27      at oracle.jbo.server.DBTransactionImpl2.reconnect(DBTransactionImpl2.java:329)
12/01/09 14:40:27      at oracle.jbo.common.ampool.DefaultConnectionStrategy.reconnect(DefaultConnectionStrategy.java:239)
12/01/09 14:40:27      at oracle.jbo.server.ApplicationPoolMessageHandler.doPoolReconnect(ApplicationPoolMessageHandler.java:487)
12/01/09 14:40:27      at oracle.jbo.server.ApplicationPoolMessageHandler.doPoolMessage(ApplicationPoolMessageHandler.java:323)
12/01/09 14:40:27      at oracle.jbo.server.ApplicationModuleImpl.doPoolMessage(ApplicationModuleImpl.java:7777)
12/01/09 14:40:27      at oracle.jbo.common.ampool.ApplicationPoolImpl.sendPoolMessage(ApplicationPoolImpl.java:4074)
12/01/09 14:40:27      at oracle.jbo.common.ampool.ApplicationPoolImpl.manageReferencingState(ApplicationPoolImpl.java:1239)
12/01/09 14:40:27      at oracle.jbo.common.ampool.ApplicationPoolImpl.finalizeResource(ApplicationPoolImpl.java:1156)
12/01/09 14:40:27      at oracle.jbo.pool.ResourcePool.removeResourceInternal(ResourcePool.java:749)
12/01/09 14:40:27      at oracle.jbo.pool.ResourcePool.setState(ResourcePool.java:1004)
12/01/09 14:40:27      at oracle.jbo.pool.ResourcePool.gc(ResourcePool.java:1423)
12/01/09 14:40:27      at oracle.jbo.pool.ResourcePool.wakeup(ResourcePool.java:774)
12/01/09 14:40:27      at oracle.jbo.pool.ResourcePool.wakeup(ResourcePool.java:779)
12/01/09 14:40:27      at oracle.jbo.pool.ResourcePoolMonitor.run(ResourcePoolMonitor.java:98)
12/01/09 14:40:27      at java.util.TimerThread.mainLoop(Timer.java:512)
12/01/09 14:40:27      at java.util.TimerThread.run(Timer.java:462)
Exception breakpoint occurred at line 311 of ReleasableResourcePooledExecutor.java.
java.lang.UnsupportedOperationException:
Edited by: 908629 on Jan 17, 2012 2:18 PM

Thank you. However, a new error has arisen.
I set session-timeout to 120 (should be minutes) and abandon-timeout to 0 (which should disable it) and I get an error exactly on the hour, regardless of what the abandon-timeout or session-timeout were.
Is there are particular I should be checking on the Oracle database side?
oracle.jbo.NotConnectedException: JBO-25200: Application module is not connected to a database
     at oracle.jbo.server.DefaultTxnHandlerImpl.handleRollback(DefaultTxnHandlerImpl.java:149)
     at oracle.jbo.server.DBTransactionImpl.doRollback(DBTransactionImpl.java:4443)
     at oracle.jbo.server.DBTransactionImpl.rollback(DBTransactionImpl.java:2327)
     at oracle.stratis.SystemAdmin.threads.ImportExportThread.loadMHIF(ImportExportThread.java:262)
     at oracle.stratis.SystemAdmin.threads.ImportExportThread.run(ImportExportThread.java:67)
     at java.lang.Thread.run(Thread.java:662)

Apex Listener config recommendations

Our DBA is installing Apex Listener 1.1.2.131.15.23 for the first time, and had a question regarding some setup. Right now it's just a stand alone copy. In the JDBC Settings, what are your recommendations for the following settings?
Initial Pool Size: 3
Maximum Statements: 10
Minimum Connections: 1
Inactivity Timeout: 1800 seconds
Maximum Connections: 10
Abandoned Connection Timeout: 900 seconds
If there is some recommended reading on how to determine the best way to set this up, that would be great.

Hello Rick,
it's hard to give you actual values. These settings concern, more or less, your load expectations. The numbers you need are
- average number of concurrent sessions (work load)
- maximum number of concurrent sessions (peek load)
Some settings might as well depend on your applications.
Recommended reading would be the Table A-1 of the Installation and Developers Guide, where the parameters you picked are described among other configuration parameters.
Just some thoughts on connection handling:
The APEX Listener uses a pool of connections to the database that is shared among all users. Usually it would be a waste of resources to have a dedicated connection for each application session, as there are usually times when there's no user activity, e.g. when a user is reading a report. So you want to make the pool size as small as possible without negative impact on your user experience. To achieve this, you may initialize your pool to be able to serve your average work load and allow it to grow to the expected peek. You may want to set the minimum number of connections below that value, so resource consumption is reduced in times of low charge.
The timeouts concern the reduction of the pool size due to reduced load (inactivity timeout - a connection isn't needed any more) or failures or unexpected long database reaction times (abandoned connection).
Statements caching can reduce database load and response times, but increases resource consumption of the Listener and may result in inacurate results if cached values are outdated.
If you have more practical questions on that topic, don't hesitate to ask.
-Udo

OIM-AD connector Issues in OIM 11g

Hi
We are trying to provision user from OIM 11G to AD using Administration Tab of Admin Console.
As part of ADITResource configuration , follwoing fields are included.In the Enterprise manager OIM server log, we are getting the below error message.
Error Message In Enterprise manager OIM server log -
Module     OIMCP.ADCS
Thread ID     [ACTIVE].ExecuteThread: '3' for queue: 'weblogic.kernel.Default (self-tuning)'
Message     com.thortech.xl.integration.ActiveDirectory.tcUtilADTasks : createUser : Wrong Value Specified in Root Context of IT ResourceOr Organization DN_
However, in Admin console Selfservice-->Task-->Provisioning -->Shows error as
Response:Connection Error encountered
Response Description:     Error encountered while connecting to target system
We have sucessfully tested the connection using Diagnoistic Dashboard (XIMDD) & Ldap Browser.
IT Resource Details-
Parameter                               Value
AD Sync installed (yes/no)                     no
ADAM LockoutThreshold Value                5
ADDisableAttr Lookup Definition                Lookup.ADProvisioning.DisableAttrLookup
ADGroup LookUp Definition                     Lookup.ADReconciliation.GroupLookup
Abandoned connection timeout                600
Admin FQDN                               cn=administrator,cn=Users,dc=example,dc=com
Admin Login                               administrator
Admin Password                          ********
Allow Password Provisioning                     yes
AtMap ADGroup                          AtMap.ADGroup
AtMap ADUser                               AtMap.AD
AtMap Group                               AtMap.ADGroup
Atmap ADOrg                               AtMap.ADOrg
Backup Server URL                          [NONE]
Connection pooling supported                false
Connection wait timeout                     100
Custom Attribute Name
CustomizedReconQuery
Inactive connection timeout                     600
Initial pool size                               1
Invert Display Name                          no
LDAP Connection Timeout                     30000
Last Modified Time Stamp                     0
Last Modified Time Stamp Group                0
Max pool size                               30
Min pool size                               2
Native connection pool class definition
OIM User UDF
Pool excluded fields
Pool preference                               Default
Port Number                               389
Remote Manager Prov Lookup                AtMap.AD.RemoteScriptlookUp
Remote Manager Prov Script Path
ResourceConnection class definition           com.thortech.xl.integration.ActiveDirectory.ADResourceConnectionImpl
Root Context                               dc=example,dc=com
SSL Port Number                          636
Server Address                               WIN-PEUB23TMMT4.example.com
Target Locale: Country                     US
Target Locale: Language                     en
Target Locale: TimeZone                     GMT
Target supports only one connection           false
Timeout check interval                     100
UPN Domain                               example.com
Use Disable Attr                          false
Use SSL                               false
Validate connection on borrow                true
isADAM                               no
isUserDeleteLeafNode                          no
For Organization we have selected ou=Test,dc=example,dc=com in our lookup defination
Please suggest....
Thanks

It's not Key, it's the Scheduled Task attribute "IT Resource Name"
Documentation: http://download.oracle.com/docs/cd/E11223_01/doc.910/e11197/using_conn.htm#CHDFBAAC
Here is the documentation on the lookup format: http://download.oracle.com/docs/cd/E11223_01/doc.910/e11197/intro.htm#CHDHCCJD
-Kevin

Cant provision user using AD connector (9.1.1.7.2) in OIM (11.1.1.5.0)

Hi all,
I get the following error in the server log when trying to provision a user from OIM to AD using the Administration tab of the Admin console:
createUser : Wrong Value Specified in Root Context of IT ResourceOr Organization DN
Any suggestions?
The ITResource information is as follows
ADAM LockoutThreshold Value          5
ADGroup LookUp Definition          Lookup.ADReconciliation.GroupLookup
Abandoned connection timeout          600
Admin FQDN                    cn=Administrator,cn=Users,dc=vc,dc=iam
Admin Password                    *********
Allow Password Provisioning          yes
AtMap ADGroup                    AtMap.ADGroup
AtMap ADUser                    AtMap.AD
Atmap ADOrg                    AtMap.ADOrg
Backup Server URL               [NONE]
Connection pooling supported          false
Connection wait timeout               60
Inactive connection timeout          600
Initial pool size               1
Invert Display Name               no
LDAP Connection Timeout               3000
Max pool size                    30
Min pool size                    2
Native connection pool class definition
Pool excluded fields
Pool preference                    Default
Port Number                    636
Remote Manager Prov Lookup          AtMap.AD.RemoteScriptlookUp
Remote Manager Prov Script Path
ResourceConnection class definition     com.thortech.xl.integration.ActiveDirectory.ADResourceConnectionImpl
Root Context                    dc=vc,dc=iam
Server Address                    zactn06101.vodacom.corp
Target Locale: TimeZone               GMT+02:00
Target supports only one connection     false
Timeout check interval               30
UPN Domain                    vc.iam
Use SSL                         yes
Validate connection on borrow          true
isADAM                         no
isUserDeleteLeafNode               no
The process form information is as follows
AD Server                    ADITResource
AD Remote Manager                ITResource
Password                    ********
User ID                         AAGASSI
User Principal Name               [email protected]
First Name                    Andre
Middle Name
Last Name                    Agassi
Common Name                    Andre Agassi
Full Name                    Andre Agassi
Password never expires               check box ticked
User must change password at next logon
Organization Name
Account is Locked out
Telephone Number
Account Expiration Date
E Mail
Post Office Box
City
State
Zip
Home Phone
Mobile
Pager
Fax
IP Phone
Title
Department
Company
Manager Name
Office
Country
Street
Terminal Profile Path
Terminal Home Directory
Terminal Allow Login
Redirection Mail ID

Hi guys.
Thanks for your prompt response. When I try to run the "AD Organization Recon" task, I get the error below. Any suggestions?
2012-05-08T11:22:12.869+02:00] [oim_server1] [NOTIFICATION] [IAM-5010000] [oracle.iam.reconciliation.impl] [tid: [ACTIVE].ExecuteThread: '3' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: oiminternal] [ecid: 0000JSfZ4m92rI05Vzk3yc1FeDWR000002,0] [APP: oim#11.1.1.3.0] Generic Information: {0}[[
oracle.iam.platform.utils.SuperRuntimeException: oracle.iam.platform.utils.SuperRuntimeException: java.sql.SQLSyntaxErrorException: ORA-00936: missing expression
at oracle.iam.reconciliation.impl.ActionEngine.processEvent(ActionEngine.java:239)
at oracle.iam.reconciliation.impl.BaseEntityTypeHandler.executeBatchPerEvent(BaseEntityTypeHandler.java:305)
at oracle.iam.reconciliation.impl.OrganizationHandler.executeBulkCUD(OrganizationHandler.java:118)
at oracle.iam.reconciliation.impl.BaseEntityTypeHandler.process(BaseEntityTypeHandler.java:42)
at oracle.iam.reconciliation.impl.ActionEngine.processBatch(ActionEngine.java:134)
at oracle.iam.reconciliation.impl.ActionEngine.execute(ActionEngine.java:92)
at oracle.iam.reconciliation.impl.ActionTask.execute(ActionTask.java:72)
at oracle.iam.platform.async.impl.TaskExecutor.executeUnmanagedTask(TaskExecutor.java:100)
at oracle.iam.platform.async.impl.TaskExecutor.execute(TaskExecutor.java:70)
at oracle.iam.platform.async.messaging.MessageReceiver.onMessage(MessageReceiver.java:68)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at com.bea.core.repackaged.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:310)
at com.bea.core.repackaged.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:182)
at com.bea.core.repackaged.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:149)
at com.bea.core.repackaged.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:89)
at com.bea.core.repackaged.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171)
at com.bea.core.repackaged.springframework.aop.support.DelegatingIntroductionInterceptor.doProceed(DelegatingIntroductionInterceptor.java:131)
at com.bea.core.repackaged.springframework.aop.support.DelegatingIntroductionInterceptor.invoke(DelegatingIntroductionInterceptor.java:119)
at com.bea.core.repackaged.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171)
at com.bea.core.repackaged.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:204)
at $Proxy343.onMessage(Unknown Source)
at weblogic.ejb.container.internal.MDListener.execute(MDListener.java:574)
at weblogic.ejb.container.internal.MDListener.transactionalOnMessage(MDListener.java:477)
at weblogic.ejb.container.internal.MDListener.onMessage(MDListener.java:379)
at weblogic.jms.client.JMSSession.onMessage(JMSSession.java:4659)
at weblogic.jms.client.JMSSession.execute(JMSSession.java:4345)
at weblogic.jms.client.JMSSession.executeMessage(JMSSession.java:3821)
at weblogic.jms.client.JMSSession.access$000(JMSSession.java:115)
at weblogic.jms.client.JMSSession$UseForRunnable.run(JMSSession.java:5170)
at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:178)
Caused by: oracle.iam.platform.utils.SuperRuntimeException: java.sql.SQLSyntaxErrorException: ORA-00936: missing expression
at oracle.iam.reconciliation.dao.ReconActionDao.executeOrgMatch(ReconActionDao.java:1370)
at oracle.iam.reconciliation.impl.OrganizationHandler.executeSingleEventMatch(OrganizationHandler.java:34)
at oracle.iam.reconciliation.impl.EntityTypeHandler.process(EntityTypeHandler.java:38)
at oracle.iam.reconciliation.impl.ActionEngine.processEvent(ActionEngine.java:209)
... 34 more
Caused by: java.sql.SQLSyntaxErrorException: ORA-00936: missing expression
at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:457)
at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:405)
at oracle.jdbc.driver.T4C8Oall.processError(T4C8Oall.java:889)
at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:476)
at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:204)
at oracle.jdbc.driver.T4C8Oall.doOALL(T4C8Oall.java:540)
at oracle.jdbc.driver.T4CStatement.doOall8(T4CStatement.java:202)
at oracle.jdbc.driver.T4CStatement.executeForRows(T4CStatement.java:1074)
at oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleStatement.java:1466)
at oracle.jdbc.driver.OracleStatement.executeInternal(OracleStatement.java:2224)
at oracle.jdbc.driver.OracleStatement.execute(OracleStatement.java:2168)
at oracle.jdbc.driver.OracleStatementWrapper.execute(OracleStatementWrapper.java:333)
at weblogic.jdbc.wrapper.Statement.execute(Statement.java:466)
at oracle.iam.reconciliation.dao.ReconActionDao.executeOrgMatch(ReconActionDao.java:1351)
... 37 more

Abandoned connections

Similar Messages

Maybe you are looking for