Idle time Closed Connection

Hi,
The following is the exception that i get when i use hibernate 3.0 to connect to Oracle 10G using the ojdbc14.jar.
i get this error when i run my eclipse plugin based application on windows vista. This happens when i keep the system idle for prolonged hours apprx 8 hours or more. But the same is not reproduced when i keep it idle on the windows xp system.
The Oracle server is present on another system which is a windows XP system but not on the same system where iam running the appliation.
So i need to know whether it is the Vista problem or the hibernate problem.
org.hibernate.TransactionException: JDBC rollback failed
at org.hibernate.transaction.JDBCTransaction.rollback(JDBCTransaction.java:170)
at <exceptions trace from the code>
Caused by: 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:1439)
at org.hibernate.transaction.JDBCTransaction.rollbackAndResetAutoCommit(JDBCTransaction.java:183)
at org.hibernate.transaction.JDBCTransaction.rollback(JDBCTransaction.java:162)
... 9 more
Thanks
Jagadish Suri

I think you need to do a firmware upgrade on your Router. Go to website linksysbycisco.com/downloads.........insert model no of your router in serach tab......select proper version of your router........download the firmware file......save that file on desktop..
Follow these steps to upgrade the firmware on the device : -
Open an Internet Explorer browser page on a computer hard wired to the router...
In the address bar type - 192.168.1.1...Leave the Username blank & in Password use admin in lower case...
Click on the 'Administration' tab- Then click on the 'Firmware Upgrade' sub tab- Here click on 'Browse' and browse the .bin firmware file and click on "Upgrade"...
Wait for few seconds until it shows that "Upgrade is successful" After the firmware upgrade, click on "Reboot" and you will be returned back to the same page OR it will say "Page cannot be displayed".
Now reset your router :
Press and hold the reset button for 30 seconds...Release the reset button...Unplug the power cable from your router, wait for 30 seconds and re-connect the power cable...Now re-configure your router...

Similar Messages

Oracle Idle Time errors

Any suggestions on how I can avoid "ORA-02396: exceeded maximum idle time, please connect again" errors?
Getting rid of the idle time restriction on the database is not an option, so I was looking for a parameter to tweak so Pages recovers better from Oracle idle timeouts.
What's happening are javascript errors and other errors in the logs when there is a timeout.

You may have issues that are not linked to timeout. Please check your database instance alert log:
$ oerr ora 3113
03113, 00000, "end-of-file on communication channel"
// *Cause: The connection between Client and Server process was broken.
// *Action: There was a communication error that requires further investigation.
//          First, check for network problems and review the SQL*Net setup.
//          Also, look in the alert.log file for any errors. Finally, test to
//          see whether the server process is dead and whether a trace file
//          was generated at failure time.

RCA Connection Pool idle Time-Out takes no effect !

My question description goes here.
According to JCA specification, I developed my 'ManagedConnectionImpl' class from the interface 'ManagedConnection'. I realize the 'destroy()' function to send out logout request to the EIS.
Then I deployed the connector in Sun Java System Application Server, I noticed there are two parameters in Connection Pool part, they are:
1. Idle Timeout. It said it's the maximum time that a connection can remain idle in the pool. I assume the connection will be removed after the specific time expired and before it's removed it will call the recallable function, 'destroy()', in my concrete class, 'ManagedConnectionImpl'.
2. Pool Resize Quantity. it said it's number of connections to be removed when pool idle time expired.
I am weird about it. I think EIS had itself session control strategy, if the specific session time-out expired, it will invalidate this session. So I think we will set 'Idle Timeout' in application server to be shorter than the EIS session time-out. If the 'Idle Timeout' in application server expired, it should remove all connections inside otherwise maybe the connection with invalid session will exist! (the background knowledge is our system will return back soap fault when it meets invalid session, so the invalid connections will not be removed by switching on your configuration item, 'On Any Failure')
So I set "inital and minimum pool size" to 8, "maximum pool size" to 32 and "Pool Resize Quantity" to 32. (I expect AS to remove all when pool idle time expired)
After deploying, I send out requests at the first round and wait for the time expired but I can't see the desired logout requests from pool automatically even one. Firstly I guess if my recallable function definition is wrong but when I shut down the Application Server, the desired logout requests are sent out from pool automatically. So I think my recallable function definition is workable.
What's your comments on it?
P.S.
I am using Sun Java System Application Server 8.1.
Thanks in advance!
BRs
/Leo

I have had following test to ensure I sent out notification to listener.
[#|2005-08-23T16:14:25.061+0800|INFO|sun-appserver-pe8.1_01|javax.enterprise.system.stream.out|_ThreadID=12;|
It's in managed env!|#]
[#|2005-08-23T16:14:25.062+0800|INFO|sun-appserver-pe8.1_01|javax.enterprise.system.stream.out|_ThreadID=12;|
enter matchManagedConnections() !|#]
[#|2005-08-23T16:14:25.062+0800|INFO|sun-appserver-pe8.1_01|javax.enterprise.system.stream.out|_ThreadID=12;|
try to find a matching and existing one, reuse it!|#]
[#|2005-08-23T16:14:25.062+0800|INFO|sun-appserver-pe8.1_01|javax.enterprise.system.stream.out|_ThreadID=12;|
Found a matching and existing one, reuse it!|#]
[#|2005-08-23T16:14:25.495+0800|INFO|sun-appserver-pe8.1_01|javax.enterprise.system.stream.out|_ThreadID=12;|
tearDown() is called, the application-level connection is released!|#]
[#|2005-08-23T16:14:25.496+0800|INFO|sun-appserver-pe8.1_01|javax.enterprise.system.stream.out|_ThreadID=12;|
enter calling close() of managed connection.|#]
[#|2005-08-23T16:14:25.496+0800|INFO|sun-appserver-pe8.1_01|javax.enterprise.system.stream.out|_ThreadID=12;|
Start calling close() of managed connection.|#]
[#|2005-08-23T16:14:25.496+0800|INFO|sun-appserver-pe8.1_01|javax.enterprise.system.stream.out|_ThreadID=12;|
start to notify the listener the completeness of connection.|#]
[#|2005-08-23T16:14:25.496+0800|INFO|sun-appserver-pe8.1_01|javax.enterprise.system.stream.out|_ThreadID=12;|
notify the listener the completeness of connection successfully.|#]
Whether it's related with the initial and minimum number parameter? Although I found it will not be created during AS start-up and will be created at the first request.
Whether it shall be kept to meet the minimum requirement? I have failed to set it to 0.

WLS 8.1 SP5 Message bridge doesn't refresh connection after idle time out

Hi,
I am seeing in the log after enabling the debug flags that message bridge intermittently stops refreshing the connection without logging further info and causing a production failure.Bridge is forwarding the message from WLS 8.1..5 DQ to the remote MQ 6.0 queue.
Below is the snippet which doesn't come in the log which suggests that bridge stops refreshing the connection.
<BEA-200027> <Bridge "CASLDNSenderBridge" works in asynchronous mode and has not received messages for the predefined maximum idle time. The connections to the adapters will be interrupted and reestablished.>
The above message does appear everytime but intermittently it stops and the messages put after this leading to the exceptions.The bridge has been configured in asynchronous mode and the idle time out is configured as 60 secs.
Can somebody please let me know if there is any known issue with 8.1 SP5 where message bridge stops refreshing connection intermittently or how to debug this further.

I would normally suggest raising the issue with support, but I recall hearing that 8.1 is nearing the end of its support cycle, so I'm not sure that's an option for you. Other options:
- try upgrading to a newer SP, or better yet, a new version of WebLogic
- try changing to synchronous forwarding
- examine thread dumps from when the bridge appears to be stalled
- post the exception that bridge is throwing when it tries to connect
- try patching MQ (the problem could be on the MQ side, and perhaps an older version of the bridge may not be fully capable of handling all of MQs minor quirks)
- write a program to (A) detect inactivity on the src destination, and (B) somehow restart the bridge and/or all of WL when this occurs
Tom

CLOSED: MAPVIEWER LONG PREPARATION TIME AFTER LONG IDLE TIME

SR # 6896831.994
Customer: NEDGRAPHICS BV
Mapviewer Release: 9.0.4
This issue was posted to the Field Service Forum. They responded with
For Map, we do create the datasource and related maps, themes, styles to be used for Map. The exeuction part is done by Mapviewer and we don't have much control on the mapviewer code on performance tuning point of view.
Please post this question in mapviewer forum
Issue:
After MapViewer being idle for some time (+/- 60 minutes) it takes a long time to generate the first map image --> 5 minutes.
In the MapViewer logfile with log-level=finest, I see that there is a very long preparation time.
After producing the first map image the next (same!) image is produced very fast.
What could be the reason?
What does MapViewer do during "preparation"?
Customer statement:
I am a very experienced Oracle specialist and a very experienced MapViewer developer.
Could you please pass on my request to the MapViewer developers?
I have to know what is going on during preparation time.
Is there a possibility to get more detailed logging of the preparation time?
SEE log file at:
http://workbench.oraclecorp.com/cgi-bin/tools/its_reltar?tar=6896831.994
FILE: mapviewer_37.log
Additional customer info.
UPDATE from customer
================
The first time after long idle time it takes between 100 and 300 seconds.
After that it takes less than 2 seconds.
Can it be a dabase connection issue?
Will it make a difference if I use a database connection via data-sources.xml
instead of a direct data-source in mapviewerConfig.xml?
This is what I mean :
Method 1:
<map_data_source name="NBG"
jdbc_host="plutonium"
jdbc_sid="ods"
jdbc_port="1521"
jdbc_user="nbgex"
jdbc_password="ELvaJ7axzKQl0aKtjikuKT7JUFTjukU3"
jdbc_mode="thin"
number_of_mappers="3"
/>
Method 2:
<map_data_source name="NBG"
container_ds="jdbc/NBG"
number_of_mappers="3"
/>
data-sources.xml:
<data-source
class="oracle.jdbc.pool.OracleDataSource"
name="NBG"
location="jdbc/OracleCache"
ejb-location="jdbc/NBG"
xa-location="jdbc/xa/OracleXADS"
connection-driver="oracle.jdbc.driver.OracleDriver"
username="nbgex"
password="nbgex
url="jdbc:oracle:thin:@plutonium:1521:ods"
inactivity-timeout="30">
<property name="connectionCacheName" value="ICC"/>
<property name="connectionCachingEnabled" value="true"/>
<property name="fastConnectionFailoverEnabled" value="true"/>
</data-source>
Thanks
Message was edited by:
user639281

RESPONSE from customer
====================
The database is restarted once a day in the morning. That could explain the problems in the morning. But there are also problems during day time after some hours of idle time when the database in not restarted.
After testing we noticed that we don't have the problem if we use database connection through OC4J (data-sources.xml).
If we use that method every database connection is cleaned up if it is not used for 15 seconds or so.
If we use the other method (database connection in mapviewerconfig.xml) then the database connection is open for a long time and then we have the problem with the long preparation time.
This problem only occurs in a DMZ environment. MapViewer is installed on a DMZ server and connects through the firewall with a intranet database.
Is it possible that the firewall software prevents communication of an open database connection after a long period of idle time?
Thanls.

WRT300N V1.1 - Firmw v1.51.2 - Problems to get wireless connection after long idle time

Hello,
I have a WRT300N, v1.1 with latest firmware available (v1.51.2).
I've been experiencing a strange problem:
1. After long idle time (router is on, no devices are using it wirelessly), no device can get a wireless connection;
2. I have tried using different OSes (Windows XP SP2, Windows Vista, and Symbian OS);
3. Wireline connection to a FE port works (if I plug a device using the cable, I can get an IP address and navigate to the internet).
4. If power reset it (WRT300N), I can get wireless connections working again.
Is this a known issue?
Thanks, Gustavo

Well as you are able to go online from your Hardwired Computer, then i think you need to make some changes on the Wireless Part of your Router. Follow this settings on your Router, i think this might solve the problem.
Open an Internet Explorer browser page on your wired computer(desktop).In the address bar type - 192.168.1.1 and press Enter...Leave Username blank & in Password use admin in lower case...
For Wireless Settings, please do the following : -
Click on the Wireless tab
- Here select manual configuration...Wireless Network mode should be mixed...
- Provide a unique name in the Wireless Network Name (SSID) box in order to differentiate your network from your neighbours network...
- Set the Radio Band to Wide-40MHz and change the Wide channel to 9 and Standard Channel to 11-2.462GHz...Wireless SSID broadcast should be Enabled and then click on save settings...
Please make a note of Wireless Network Name (SSID) as this is the Network Identifier...
For Wireless Security : -
Click on the Sub tab under Wireless > Wireless Security...
Change the Wireless security mode to WPA, For Encryption, select AES...For Passphrase input your desired WPA Key. For example , MySecretKey , This will serve as your network key whenever you connect to your wireless network. Do NOT give this key to anyone.
NOTE : Passphrase should be more that 8 characters...
Click on Advanced Wireless Settings
Change the Beacon Interval to 50 >>Change the Fragmentation Threshold to 2304 Change the RTS Threshold to 2307 >>Click on "Save Settings"...
Now see if you can locate your Wireless Network and attempt to connect...

Jdbc connection lost after idle time

Dear users,
i'm using the oracle 10g database. Now i found out that several programs (SQuirreL, QuantumDB,...) which use the ojdbc14 driver are losing connection to the database after about one hour idle time, but it is not set in db configuration to disconnect (eg parameter idle_time is not set). What could be the cause of this? Is this a error of jdbc (the java exception is something like socket lost) or is it a missconfiguration of the db?
Thx for help.

With a simple java program that makes a select on a database table over jdbc after one Hour idle_time this exception happens: (the program is started local on the database server so no firewall or router is between)
java.sql.SQLException: No more data to read from socket
at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:112)
at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:146)
at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:208)
at oracle.jdbc.driver.T4CMAREngine.unmarshalUB1(T4CMAREngine.java:1118)
at oracle.jdbc.driver.T4CMAREngine.unmarshalSB1(T4CMAREngine.java:1070)
at oracle.jdbc.driver.T4C8Oall.receive(T4C8Oall.java:478)
at oracle.jdbc.driver.T4CStatement.doOall8(T4CStatement.java:207)
at oracle.jdbc.driver.T4CStatement.executeForDescribe(T4CStatement.java:790)
at oracle.jdbc.driver.OracleStatement.executeMaybeDescribe(OracleStatement.java:1039)
at oracle.jdbc.driver.T4CStatement.executeMaybeDescribe(T4CStatement.java:830)
at oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleStatement.java:1132)
at oracle.jdbc.driver.OracleStatement.executeQuery(OracleStatement.java:1272)
at test$1.run(test.java:24)
at test.main(test.java:55)

Weblogic server closed connection after idle timeout

I have the Weblogic webserver set up to automatically come on at 0600 each morning. This morning I received the following error message and the server was displaying an Error 503--Service Unavailable message:
Here is the output form the log file:" Does anyone have any idea as to why the idle timeout closed the connectino to the server. This has never happened before?
<Dec 9, 2009 6:05:21 AM CET> <Notice> <WebLogicServer> <BEA-000331> <Started Web
Logic Admin Server "AdminServer" for domain "WUIMMS" running in Development Mode
>
<Dec 9, 2009 6:05:21 AM CET> <Notice> <WebLogicServer> <BEA-000365> <Server stat
e changed to RUNNING>
<Dec 9, 2009 6:05:21 AM CET> <Notice> <WebLogicServer> <BEA-000360> <Server star
ted in RUNNING mode>
<Dec 9, 2009 7:08:02 AM CET> <Warning> <Socket> <BEA-000449> <Closing socket as
no data read from it during the configured idle timeout of 25 secs>
<Dec 9, 2009 7:10:17 AM CET> <Warning> <Socket> <BEA-000449> <Closing socket as
no data read from it during the configured idle timeout of 25 secs>
<Dec 9, 2009 7:10:22 AM CET> <Warning> <Socket> <BEA-000449> <Closing socket as
no data read from it during the configured idle timeout of 25 secs>
<Dec 9, 2009 7:11:12 AM CET> <Warning> <Socket> <BEA-000449> <Closing socket as
no data read from it during the configured idle timeout of 25 secs>
<Dec 9, 2009 7:12:12 AM CET> <Warning> <Socket> <BEA-000449> <Closing socket as
no data read from it during the configured idle timeout of 25 secs>
<Dec 9, 2009 7:13:32 AM CET> <Warning> <Socket> <BEA-000449> <Closing socket as
no data read from it during the configured idle timeout of 25 secs>
<Dec 9, 2009 7:17:12 AM CET> <Warning> <Socket> <BEA-000449> <Closing socket as
no data read from it during the configured idle timeout of 25 secs>
<Dec 9, 2009 7:18:02 AM CET> <Warning> <Socket> <BEA-000449> <Closing socket as
no data read from it during the configured idle timeout of 25 secs>

192.168.250.145 is the local machine's IP ( "Powered-On Machine"),
my convert setting likes follows,
Source Type : Powered-On Machine / This Local Machine
Location for the Virtual machine : D:\VM_PC
attached log file is my latest Try today.

JDBC initialize failed due to long idling time

Hi gurus
Anyone having similar problem and would like to share their solution for the problem stated below.
Normally the integration for IDOC-XI-JDBC scenarios is working fine, but when the R3 halt sending IDOC to XI, the JDBC connection to MS SQL 2000 server failed to process and initialise due to long idling time. Currently the temporary solution is to go to XI change the Integration Directory : Communication Channel for the JDBC - Activate - Clear Cache. Then go to R3, retrigger the IDOC again. And the above problem will be resolved. But after a while (long idling time again), this problem arise once again.
2008-10-21 15:18:45     Success     Message successfully received by messaging system. Profile: XI URL: http://locahost:50600/MessagingSystem/receive/AFW/XI Credential (User): PIISUSER
2008-10-21 15:18:45     Success     Using connection JDBC_http://sap.com/xi/XI/System. Trying to put the message into the receive queue.
2008-10-21 15:18:45     Success     Message successfully put into the queue.
2008-10-21 15:18:45     Success     The message was successfully retrieved from the receive queue.
2008-10-21 15:18:45     Success     The message status set to DLNG.
2008-10-21 15:18:45     Success     Delivering to channel: CC_IDOC_TO_DBMS_ESMS_588
2008-10-21 15:18:45     Success     MP: Entering module processor
2008-10-21 15:18:45     Success     MP: Processing local module localejbs/CallSapAdapter
2008-10-21 15:18:45     Success     Receiver JDBC adapter: processing started; QoS required: ExactlyOnce
2008-10-21 15:18:45     Error     JDBC adapter receiver channel CC_IDOC_TO_DBMS_ESMS_588 not initialized. Unable to proceed due to null
2008-10-21 15:18:46     Error     MP: Exception caught with cause com.sap.aii.af.ra.ms.api.RecoverableException: JDBC Adapter configuration not initialized: null
2008-10-21 15:18:46     Error     Exception caught by adapter framework: JDBC Adapter configuration not initialized: null
2008-10-21 15:18:46     Error     Delivery of the message to the application using connection JDBC_http://sap.com/xi/XI/System failed, due to: com.sap.aii.af.ra.ms.api.RecoverableException: JDBC Adapter configuration not initialized: null.
2008-10-21 15:18:46     Success     The message status set to WAIT.
2008-10-21 15:18:46     Success     The asynchronous message was successfully scheduled to be delivered at Tue Oct 21 15:23:46 GMT+08:00 2008.
2008-10-21 15:23:46     Success     The message status set to TBDL.
2008-10-21 15:23:46     Success     Retrying to deliver message to the application. Retry: 1
2008-10-21 15:23:46     Success     The message was successfully retrieved from the receive queue.
2008-10-21 15:23:46     Success     The message status set to DLNG.
2008-10-21 15:23:46     Success     Delivering to channel: CC_IDOC_TO_DBMS_ESMS_588
2008-10-21 15:23:46     Success     MP: Entering module processor
2008-10-21 15:23:46     Success     MP: Processing local module localejbs/CallSapAdapter
2008-10-21 15:23:46     Success     Receiver JDBC adapter: processing started; QoS required: ExactlyOnce
2008-10-21 15:23:46     Error     JDBC adapter receiver channel CC_IDOC_TO_DBMS_ESMS_588 not initialized. Unable to proceed due to null
2008-10-21 15:23:46     Error     MP: Exception caught with cause com.sap.aii.af.ra.ms.api.RecoverableException: JDBC Adapter configuration not initialized: null
2008-10-21 15:23:46     Error     Exception caught by adapter framework: JDBC Adapter configuration not initialized: null
2008-10-21 15:23:46     Error     Delivery of the message to the application using connection JDBC_http://sap.com/xi/XI/System failed, due to: com.sap.aii.af.ra.ms.api.RecoverableException: JDBC Adapter configuration not initialized: null.
2008-10-21 15:23:46     Success     The message status set to WAIT.
2008-10-21 15:23:46     Success     The asynchronous message was successfully scheduled to be delivered at Tue Oct 21 15:28:46 GMT+08:00 2008.
2008-10-21 15:28:46     Success     The message status set to TBDL.
Edited by: Malcolm Pang on Oct 23, 2008 11:08 AM

In the JDBC adapter , select option Disconnect From Database after Each message processing.
This will solve the process as your JDBC Database seems to be closing the connection after a particular idle time.
Regards
Bhavesh

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

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)

Just closing connection enough?

Hi friends..This is my first post...I am a newbie Java Developer..Okay Here goes
I have just made a LAN based Java application using Swing,JDBC with backend as MS-Access..The backend is on a shared network drive..
The application is distributed as jar files on the LAN PCs..
Everywhere I have connected to the database I have just closed the connection explicitly like this
con.close();
I do not close the associated resultset and statement explicitly
The specification says associated statements and resultsets close when you close
the connection,even if you don't explicitly close them
Also I am not using connection pool..its simple basic connection using DriverManager
Class.forName("sun.jdbc.odbc.JdbcOdbcDriver");
String url = "jdbcdbcSN name";
String user = "";
String pw = "";
con = DriverManager.getConnection(url, user, pw);
Statement stmt = con.createStatement();
String select = "" ;
ResultSet rows = stmt.executeQuery(select);
Till now no performance problems..over 4K records have been added..
JVM is not exiting or anything..
On the net everyone says to explicitly close everything..but I did not know that
earlier..
My question is
Is closing just the connection enough..?
Is there any way I can check whether statements and resultsets have been implicitly closed?
Later on will it cause any performance problems or anything...?
Shud I change my code and add rs.close() and stmt.close() everywhere..?
If specification says everything closes on
closing connection why do ppl insist on closing everything explicitly..?
Or is this driver dependent..don't the drivers go through the specification..
My driver is the Sun JDBC ODBC bridge.....
There would be 8-10 users maximum at a time using the application concurrently...
Any help would be appreciated..Thanks in advance..

@jschell
Thanks for your help
I was running a few more tests..can you please explain the the following code...
Code
import java.sql.*;
import java.io.*;
class gc5test
public static void main(String args[])
Connection con = null;
long memoryBeforeSelects;
long memoryAfterSelects;
long memoryAfterConnectionClose;
try
PrintWriter pw= new PrintWriter("c:\\log1.txt");
Class.forName("sun.jdbc.odbc.JdbcOdbcDriver");
String url = "jdbc:odbc:pravahcon";
String user = "admin";
String pass = "ash123";
for(int i=1;i<=20;i++)
pw.println("Connection No"+i);
memoryBeforeSelects = Runtime.getRuntime().freeMemory();
pw.println("Free Memory before making connection " + memoryBeforeSelects / 1024 + " kB");
con = DriverManager.getConnection(url, user, pass);
Statement stmt = con.createStatement();
String select = "SELECT * FROM Users" ;
ResultSet rows = stmt.executeQuery(select);
memoryAfterSelects = Runtime.getRuntime().freeMemory();
pw.println("Free Memory after making connection " + memoryAfterSelects / 1024 + " kB");
rows.close();
stmt.close();
con.close();
memoryAfterConnectionClose = Runtime.getRuntime().freeMemory();
pw.println("Free Memory after closing connection " + memoryAfterConnectionClose / 1024 + " kB");
pw.close();
catch (ClassNotFoundException f)
System.out.println(f.getMessage());
System.exit(0);
catch (SQLException g)
System.out.println(g.getMessage());
System.exit(0);
catch (Exception e)
System.out.println(e.getMessage());
System.exit(0);
Output
Connection No1
Free Memory before making connection 4729 kB
Free Memory after making connection 4675 kB
Free Memory after closing connection 4675 kB
Connection No2
Free Memory before making connection 4675 kB
Free Memory after making connection 4638 kB
Free Memory after closing connection 4620 kB
Connection No3
Free Memory before making connection 4620 kB
Free Memory after making connection 4584 kB
Free Memory after closing connection 4584 kB
Connection No4
Free Memory before making connection 4584 kB
Free Memory after making connection 4548 kB
Free Memory after closing connection 4529 kB
Connection No5
Free Memory before making connection 4529 kB
Free Memory after making connection 4493 kB
Free Memory after closing connection 4493 kB
Connection No6
Free Memory before making connection 4493 kB
Free Memory after making connection 4457 kB
Free Memory after closing connection 4457 kB
Connection No7
Free Memory before making connection 4439 kB
Free Memory after making connection 4403 kB
Free Memory after closing connection 4403 kB
Connection No8
Free Memory before making connection 4403 kB
Free Memory after making connection 4367 kB
Free Memory after closing connection 4367 kB
Connection No9
Free Memory before making connection 4349 kB
Free Memory after making connection 4313 kB
Free Memory after closing connection 4313 kB
Connection No10
Free Memory before making connection 4313 kB
Free Memory after making connection 4277 kB
Free Memory after closing connection 4277 kB
Connection No11
Free Memory before making connection 4259 kB
Free Memory after making connection 4223 kB
Free Memory after closing connection 4223 kB
Connection No12
Free Memory before making connection 4223 kB
Free Memory after making connection 4187 kB
Free Memory after closing connection 4169 kB
Connection No13
Free Memory before making connection 4169 kB
Free Memory after making connection 4817 kB
Free Memory after closing connection 4800 kB
Connection No14
Free Memory before making connection 4800 kB
Free Memory after making connection 4766 kB
Free Memory after closing connection 4766 kB
Connection No15
Free Memory before making connection 4766 kB
Free Memory after making connection 4714 kB
Free Memory after closing connection 4714 kB
Connection No16
Free Memory before making connection 4714 kB
Free Memory after making connection 4678 kB
Free Memory after closing connection 4678 kB
Connection No17
Free Memory before making connection 4678 kB
Free Memory after making connection 4627 kB
Free Memory after closing connection 4627 kB
Connection No18
Free Memory before making connection 4627 kB
Free Memory after making connection 4592 kB
Free Memory after closing connection 4575 kB
Connection No19
Free Memory before making connection 4575 kB
Free Memory after making connection 4540 kB
Free Memory after closing connection 4540 kB
Connection No20
Free Memory before making connection 4540 kB
Free Memory after making connection 4489 kB
Free Memory after closing connection 4489 kB
The memory is not being freed immediately after closing connection explicitly in first 12 iterations..
In the first 12 iterations memory after making connection and memory after closing
connection are the same/or very less difference...
Only in the 13th iteration the memory increases from 4169 to 4817..
Why is this happening..?
I am closing everything explicitly..
Shouldn't the memory be reclaimed immediately..?
Insted it is happening later on..
Am I missing something here..?

Closing connections question

Hi, My application seems to be running out of memory despite closing the resultsets and connections used.
I have a DBHelper class (DBHelper.java) with the following 2 methods:
public Connection getConn(){
// setups a JDBC connection and returns it
// Close all connections
public void cleanUp(){
try{
if(this.conn != null && !this.conn.isClosed()){
this.production_Conn.close();
catch(SQLException e){
System.out.println(e.getMessage());
So let's say if I have another class, e.g. Class A, that creates a Connection object using DBHelper.getConn() method, will calling DBHelper.cleanUp() be sufficient to close the connection? Or do i have to clear the reference object used inside Class A as well?
Regards

First off, are you sure you're out of memory is related to not closing connections? Mostly connections and ResultSets don't use that much memory so you usually run into database problems (too many open connections, too many sessions, etc.) before the Java app runs out of memory. Is it possible the leak is elsewhere?
If you're sure its connection related maybe a problem with the helper class? Does getConn() create a new connection every time its called? If so, it looks like cleanUp() only closes the most recently opened connection - but without seeing the whole class I can't be sure.
For example, the following would leave an open connection - though if the app is no longer referencing it, it should get garbage collected and closed eventually (though relying on this is bad form).
class Bad {
   Connection con;
   public Connection getConn()
         con = // create connection
         return con;
   public void cleanUp()
         con.close();
   public static void main( String[] args )
         Bad b = new Bad();
         b.getConn();
         b.getConn();
         b.cleanUp();
}- Jemiah

Java.sql.SQLException: can't create statement from closed connection

java.sql.SQLException: can't create statement from closed connection.
at com.caucho.sql.QPooledConnectionImpl.prepareStatement(QPooledConnecti onImpl.java:411)
I am getting this error with my JSP's, i am running on Resin on Win2k, and MySql as backend.
Has anyone else also faced this issue ?
Looking for someone to help me to solve this issue.
rc

Looking for someone to help me to solve this issue.Maybe you are closing the connections. You might want to verify that you are not doing that. Or if you are that that is the correct way to return the connection to the pool.
Or you could have stale connections. Some databases will time out connections if the connection is no used in a while. (This is a good thing.) But this means connection pools must do something with connections that are not used for a while. The pools usually have a configuration option(s) which allows you to set up a keep alive message which keeps the database from closing the connection.

CF 6.1 - JRUN Closed Connection/Server errors occurring on a daily basis

We seem to be having issues with Jrun Closed Connection/Server errors occuring on a daily basis now. The server will stop responding to requests until the ColdFusion service is restarted.
We're using CF 6.1, the following error message is from the log files and seems to be Java/JVM related but I was hesitant to make any changes to the JVM parameters.
Any suggestions on how to resolve this daily issue of restarting CF service? Other than upgrading to more recent version of CF which we'll be doing later this year.
Thanks,
Dave
>>>>>>>>>>>>
An unexpected exception has been detected in native code outside the VM.
Unexpected Signal : EXCEPTION_ACCESS_VIOLATION (0xc0000005) occurred at PC=0x77FCAFF8
Function=[Unknown.]
Library=C:\WINNT\system32\ntdll.dll
NOTE: We are unable to locate the function name symbol for the error
      just occurred. Please refer to release documentation for possible
      reason and solutions.
Current Java thread:
          at java.io.WinNTFileSystem.list(Native Method)
          at java.io.File.list(File.java:915)
          at coldfusion.mail.MailSpooler.refreshSpoolFiles(MailSpooler.java:1484)
          at coldfusion.mail.MailSpooler.run(MailSpooler.java:897)
          at coldfusion.scheduling.ThreadPool.run(ThreadPool.java:201)
          at coldfusion.scheduling.WorkerThread.run(WorkerThread.java:70)
Dynamic libraries:
0x00400000 - 0x0040F000           C:\CFusionMX\runtime\bin\jrun.exe
0x77F80000 - 0x77FFC000           C:\WINNT\system32\ntdll.dll
0x7C570000 - 0x7C624000           C:\WINNT\system32\KERNEL32.dll
0x7C2D0000 - 0x7C335000           C:\WINNT\system32\ADVAPI32.dll
0x77D30000 - 0x77D9F000           C:\WINNT\system32\RPCRT4.dll
0x78000000 - 0x78045000           C:\WINNT\system32\MSVCRT.dll
0x08000000 - 0x082A7000           C:\CFusionMX\runtime\jre\bin\server\jvm.dll
0x77E10000 - 0x77E6F000           C:\WINNT\system32\USER32.dll
0x77F40000 - 0x77F7D000           C:\WINNT\system32\GDI32.dll
0x77570000 - 0x775A0000           C:\WINNT\system32\WINMM.dll
0x10000000 - 0x10007000           C:\CFusionMX\runtime\jre\bin\hpi.dll
0x00770000 - 0x0077E000           C:\CFusionMX\runtime\jre\bin\verify.dll
0x00780000 - 0x00798000           C:\CFusionMX\runtime\jre\bin\java.dll
0x007A0000 - 0x007AD000           C:\CFusionMX\runtime\jre\bin\zip.dll
0x39A70000 - 0x39A7F000           C:\CFusionMX\runtime\jre\bin\net.dll
0x75030000 - 0x75044000           C:\WINNT\system32\WS2_32.dll
0x75020000 - 0x75028000           C:\WINNT\system32\WS2HELP.DLL
0x782C0000 - 0x782CC000           C:\WINNT\System32\rnr20.dll
0x77980000 - 0x779A5000           C:\WINNT\system32\DNSAPI.DLL
0x75050000 - 0x75058000           C:\WINNT\system32\WSOCK32.dll
0x77340000 - 0x77353000           C:\WINNT\system32\iphlpapi.dll
0x77520000 - 0x77525000           C:\WINNT\system32\ICMP.dll
0x77320000 - 0x77337000           C:\WINNT\system32\MPRAPI.dll
0x75150000 - 0x75160000           C:\WINNT\system32\SAMLIB.DLL
0x7CDC0000 - 0x7CE10000           C:\WINNT\system32\NETAPI32.DLL
0x7C340000 - 0x7C34E000           C:\WINNT\system32\Secur32.dll
0x77BF0000 - 0x77C01000           C:\WINNT\system32\NTDSAPI.dll
0x77950000 - 0x7797B000           C:\WINNT\system32\WLDAP32.DLL
0x751C0000 - 0x751C6000           C:\WINNT\system32\NETRAP.dll
0x7CE20000 - 0x7CF0F000           C:\WINNT\system32\OLE32.DLL
0x779B0000 - 0x77A4C000           C:\WINNT\system32\OLEAUT32.DLL
0x773B0000 - 0x773DF000           C:\WINNT\system32\ACTIVEDS.DLL
0x77380000 - 0x773A3000           C:\WINNT\system32\ADSLDPC.DLL
0x77830000 - 0x7783E000           C:\WINNT\system32\RTUTILS.DLL
0x77880000 - 0x7790E000           C:\WINNT\system32\SETUPAPI.DLL
0x7C0F0000 - 0x7C154000           C:\WINNT\system32\USERENV.DLL
0x774E0000 - 0x77514000           C:\WINNT\system32\RASAPI32.dll
0x774C0000 - 0x774D1000           C:\WINNT\system32\rasman.dll
0x77530000 - 0x77552000           C:\WINNT\system32\TAPI32.dll
0x71710000 - 0x71794000           C:\WINNT\system32\COMCTL32.DLL
0x70A70000 - 0x70AD6000           C:\WINNT\system32\SHLWAPI.DLL
0x77360000 - 0x77379000           C:\WINNT\system32\DHCPCSVC.DLL
0x777E0000 - 0x777E8000           C:\WINNT\System32\winrnr.dll
0x777F0000 - 0x777F5000           C:\WINNT\system32\rasadhlp.dll
0x39FB0000 - 0x39FBC000           C:\CFusionMX\runtime\bin\portscan.dll
0x74FD0000 - 0x74FED000           C:\WINNT\system32\msafd.dll
0x75010000 - 0x75017000           C:\WINNT\System32\wshtcpip.dll
0x3AAC0000 - 0x3AAC5000           C:\CFusionMX\runtime\jre\bin\rmi.dll
0x3B9D0000 - 0x3B9D6000           C:\CFusionMX\runtime\jre\bin\ioser12.dll
0x3BBE0000 - 0x3BC60000           C:\CFusionMX\lib\izmjniado.dll
0x3C270000 - 0x3C278000           C:\CFusionMX\lib\CFXNeo.dll
0x780A0000 - 0x780B2000           C:\WINNT\system32\MSVCIRT.dll
0x780C0000 - 0x78121000           C:\WINNT\system32\MSVCP60.dll
0x3C280000 - 0x3C28B000           C:\CFusionMX\lib\cfregistry.dll
0x3C3A0000 - 0x3C3A8000           C:\CFusionMX\lib\PerfmonClient.dll
0x3C5C0000 - 0x3C5CC000           C:\CFusionMX\lib\cfindex.dll
0x3C5D0000 - 0x3C7C2000           C:\CFusionMX\lib\vdk200.dll
0x3C7D0000 - 0x3C805000           C:\CFusionMX\lib\LIBALLRSEI.dll
0x7CA00000 - 0x7CA23000           C:\WINNT\system32\rsaenh.dll
0x7C740000 - 0x7C7CC000           C:\WINNT\system32\CRYPT32.dll
0x77430000 - 0x77441000           C:\WINNT\system32\MSASN1.dll
0x3EE10000 - 0x3EE3E000           C:\CFusion\CustomTags\GetUserGroups.dll
0x77800000 - 0x7781E000           C:\WINNT\system32\WINSPOOL.DRV
0x76620000 - 0x76631000           C:\WINNT\system32\MPR.DLL
0x7CF30000 - 0x7D176000           C:\WINNT\system32\SHELL32.dll
0x3F650000 - 0x3F75A000           C:\CFusionMX\runtime\jre\bin\awt.dll
0x75E60000 - 0x75E7A000           C:\WINNT\system32\IMM32.dll
0x3F760000 - 0x3F7B0000           C:\CFusionMX\runtime\jre\bin\fontmanager.dll
0x72800000 - 0x72846000           C:\WINNT\system32\ddraw.dll
0x728A0000 - 0x728A6000           C:\WINNT\system32\DCIMAN32.dll
0x72CF0000 - 0x72D84000           C:\WINNT\system32\D3DIM700.DLL
0x690A0000 - 0x690AB000           C:\WINNT\system32\PSAPI.DLL
Heap at VM Abort:
Heap
PSYoungGen      total 5824K, used 1523K [0x10010000, 0x10800000, 0x138f0000)
eden space 3520K, 26% used [0x10010000,0x100fa4e0,0x10380000)
from space 2304K, 25% used [0x105c0000,0x106528b0,0x10800000)
to   space 2304K, 0% used [0x10380000,0x10380000,0x105c0000)
PSOldGen        total 29824K, used 22612K [0x138f0000, 0x15610000, 0x30010000)
object space 29824K, 75% used [0x138f0000,0x14f051e0,0x15610000)
PSPermGen       total 20736K, used 20580K [0x30010000, 0x31450000, 0x38010000)
object space 20736K, 99% used [0x30010000,0x314293b0,0x31450000)
Local Time = Fri Dec 13 13:50:53 2013
Elapsed Time = 19424
# The exception above was detected in native code outside the VM
# Java VM: Java HotSpot(TM) Server VM (1.4.2-b28 mixed mode)
space 3520K, 26% used space 2304K, 25% used space 2304K, 0% used space 29824K, 75% used space 20736K, 99% used# An error report file has been saved as hs_err_pid2920.log.
# Please refer to the file for further information.

CF6, Java 1.4.2 and Windows NT - have not seen those for a long time myself.
Perhaps this is the issue from error report:
PSPermGen       total 20736K, used 20580K
object space 20736K, 99% used
I guess Java non heap space Permanent Generation is full the next object trying to load into that space can’t fit, plus all the objects in there are referenced so no objects can be removed so free space can’t be made available. One would need to do some work with Java logging and know what JVM.CONFIG looks like to know if that guess is accurate.
You could try increase that parameter 10Mb or so and see what happens? In JVM.CONFIG, JVM args, -XX:MaxPermSize=NNm where NN = numbers.
Needless to say you are running a lot of end of life product and should plan to migrate to something more current.
HTH, Carl.

Idle time Closed Connection

Similar Messages

Maybe you are looking for