Bugs item #648344, was opened at 2002-12-04 11:52
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=376685&aid=648344&group_id=22866
Category: None
Group: None
Status: Open
Resolution: None
Priority: 5
Submitted By: Bruce Barrow (bruce_b)
Assigned to: Nobody/Anonymous (nobody)
Summary: open-cursors limit reached
Initial Comment:
First 'bug', so bear with me. Some description follows
the trace.
OS: Windows NT 4.0
JDK: 1.4
10:13:49,671 INFO [Server] JBoss Release: JBoss-
3.0.3 CVSTag=JBoss_3_0_3
10:13:49,718 INFO [Server] Home Dir: F:\jboss\jboss-
3.0.3
10:13:49,718 INFO [Server] Home URL:
file:/F:/jboss/jboss-3.0.3/
10:13:49,718 INFO [Server] Library URL:
file:/F:/jboss/jboss-3.0.3/lib/
10:13:49,718 INFO [Server] Patch URL: null
10:13:49,718 INFO [Server] Server Name: efc
10:13:49,718 INFO [Server] Server Home Dir:
F:\jboss\jboss-3.0.3\server\efc
10:13:49,718 INFO [Server] Server Home URL:
file:/F:/jboss/jboss-3.0.3/server/efc/
10:13:49,718 INFO [Server] Server Data Dir:
F:\jboss\jboss-3.0.3\server\efc\db
10:13:49,718 INFO [Server] Server Temp Dir:
F:\jboss\jboss-3.0.3\server\efc\tmp
10:13:49,750 INFO [Server] Server Config URL:
file:/F:/jboss/jboss-3.0.3/server/efc/conf/
10:13:49,750 INFO [Server] Server Library URL:
file:/F:/jboss/jboss-3.0.3/server/efc/lib/
10:13:49,750 INFO [Server] Root Deployemnt Filename:
jboss-service.xml
10:13:49,750 INFO [Server] Starting General Purpose
Architecture (GPA)...
10:13:50,218 INFO [ServerInfo] Java version:
1.4.0_02,Sun Microsystems Inc.
10:13:50,218 INFO [ServerInfo] Java VM: Java HotSpot
(TM) Client VM 1.4.0_02-b02,Sun Microsystems Inc.
10:13:50,218 INFO [ServerInfo] OS-System: Windows
NT 4.0,x86
10:13:50,312 INFO [ServiceController] Controller MBean
online
10:13:50,484 INFO [MainDeployer] Creating
10:13:50,546 INFO [MainDeployer] Created
10:13:50,546 INFO [MainDeployer] Starting
10:13:50,546 INFO [MainDeployer] Started
10:13:50,578 INFO [JARDeployer] Creating
10:13:50,578 INFO [JARDeployer] Created
10:13:50,578 INFO [JARDeployer] Starting
10:13:50,578 INFO [MainDeployer] Adding deployer:
org.jboss.deployment.JARDeployer@808199
10:13:50,578 INFO [JARDeployer] Started
10:13:50,609 INFO [SARDeployer] Creating
10:13:50,609 INFO [SARDeployer] Created
10:13:50,609 INFO [SARDeployer] Starting
10:13:50,609 INFO [MainDeployer] Adding deployer:
org.jboss.deployment.SARDeployer@66a22b
10:13:50,703 INFO [SARDeployer] Started
10:13:50,703 INFO [Server] Core system initialized
10:13:50,718 INFO [MainDeployer] Starting deployment
of package: file:/F:/jboss/jboss-
3.0.3/server/efc/conf/jboss-servi
ce.xml
[...]
10:14:04,562 INFO [jbossweb] Starting Jetty/4.1
10:14:04,593 INFO [jbossweb] Started
org.mortbay.http.NCSARequestLog@8a8ce2
[...]
10:14:31,437 INFO [EjbModule] Started
10:14:31,437 INFO [EjbModule] Starting
10:14:31,484 INFO [EjbModule] Started
10:14:31,484 INFO [MainDeployer] Deployed package:
file:/F:/jboss/jboss-3.0.3/server/efc/deploy/efc.ear
10:14:31,484 INFO [URLDeploymentScanner] Started
10:14:31,500 INFO [MainDeployer] Deployed package:
file:/F:/jboss/jboss-3.0.3/server/efc/conf/jboss-service.xml
10:14:31,500 INFO [Server] JBoss (MX MicroKernel)
[3.0.3 Date:200209301503] Started in 0m:41s:750ms
10:42:25,890 INFO [STDOUT]
CPCBean.registerUserSession
10:42:25,906 INFO [STDOUT]
CPCBean.registerUserSession: Registering
userSession, key="edgar_j:Product Tester [-38522377
2]"
[...]
11:08:20,468 ERROR [STDERR]
{className="WorkspaceDAOOracle"
methodName="readRow"
componentSequenceNumber=203003 severity
=13 errorType=0 errorMessage="An SQL Exception
occurred while trying to execute statement SELECT
<cols_list> FROM <table> WHERE <where> .
The error was 72000
" dynamicContent={" SELECT <cols> FROM
<table> WHERE <etc...> ", "72000
"} nestedException.message="ORA-01000: maximum
open cursors exceeded
" nestedException.stackTrace="java.sql.SQLException:
ORA-01000: maximum open cursors exceeded
Initially, the open_cursors parameter on the database
was set to 250. This was raised to 500, but this was just
putting off the problem - not resolving it.
Querying the database shows that some sessions have
over 250 cursors - these should really expire or be aged
out. Is this a known issue?
Connecting to the JBoss server takes one or two
seconds, because of the work required to determine
access rights, therefore sessions are left connected.
The number of cursors used therefore increases quickly.
Is there a way of configuring JBoss to release cursors
more quickly?
Thanks in advance,
Bruce
----------------------------------------------------------------------
>Comment By: Bruce Barrow (bruce_b)
Date: 2002-12-19 11:34
Message:
Logged In: YES
user_id=661946
UPDATE:
We found (okay, so I didn't!) a statement in the
initialisation/connection opening section which was setting
the date format. This statement was NOT being closed.
This was done by one of our colleagues (long-since left). I
don't say this to assign or shift blame in any way, but if other
people have this issue, might help them to think laterally to
find a similar cause.
The statement in question was to set the date format for each
connection. This statement was causing the whole problem -
after the initialisation was finished, the reference to this
stateemnt was lost and it could not be closed. Once this
statement was correctly closed at the end of initialisation, the
cursors count stayed low.
Am I 'allowed' to close this bug...is there a procedure that
should be followed?
Regards,
Bruce
----------------------------------------------------------------------
Comment By: Igor Fedorenko (igorfie)
Date: 2002-12-11 16:35
Message:
Logged In: YES
user_id=232950
Can you provide simple example that demonstrates the
problem? Something like a stateless bean talking oracle and
a client of that bean.
----------------------------------------------------------------------
Comment By: Bruce Barrow (bruce_b)
Date: 2002-12-11 15:56
Message:
Logged In: YES
user_id=661946
I can confirm we are closing all resources in finally blocks, so
I guess we think it is a bug.
Please let me know what more information I can supply to
help you investigate.
Thanks, Bruce
----------------------------------------------------------------------
Comment By: David Jencks (d_jencks)
Date: 2002-12-09 05:48
Message:
Logged In: YES
user_id=60525
JBoss doesn't try to close result sets, statements, or connections for
you. You are responsible for closing all of these in finally blocks after
you are done with them.
It would be possible, using the jdbc-jca wrappers, to close result sets
and statements when a connection is closed or when they become
unreachable: something of this nature may be implemented in jboss 4.
We can't close connection handles for you due to some slightly silly
requirements of the jca spec.
Please indicate if you are already closing all resources in finally blocks:
if you are, this might be a bug, if not it is a feature request.
----------------------------------------------------------------------
Comment By: Bruce Barrow (bruce_b)
Date: 2002-12-05 16:46
Message:
Logged In: YES
user_id=661946
Follow-up on this:
This might not be popular, but we also support BEA with our
development, and WebLogic releases the cursors......I guess
JBoss is more concerned about interacting with open source
databases...?
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=376685&aid=648344&group_id=22866
-------------------------------------------------------
This SF.NET email is sponsored by: Geek Gift Procrastinating?
Get the perfect geek gift now! Before the Holidays pass you by.
T H I N K G E E K . C O M http://www.thinkgeek.com/sf/
_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
