About database's "closed connection"

i have stand a database called "TMIS",but now i can't start it ,after i put in the ID and the password,it always show me a message : "closed connection",i don't know what to do to help the "TMIS" start ,i tried many methods ,such as changing the listener.ora ,but it didn't help.
the service "TMIS" always showed the status "UNKOWN",I don't know the reasons to cause my database can't connection,here is my /etc/hosts and the listener.ora
#/etc/hosts
# Do not remove the following line, or various programs
# that require network functionality will fail.
127.0.0.1 localhost.localdomain localhost
#here 127.0.0.1, actually i change to my own ip address
#listener.ora
LISTENER =
(DESCRIPTION_LIST =
(DESCRIPTION =
(ADDRESS_LIST =
(ADDRESS = (PROTOCOL = IPC)(KEY = EXTPROC))
(ADDRESS_LIST =
(ADDRESS = (PROTOCOL = TCP)(HOST =localhost.localdomain)(PORT = 1521))
SID_LIST_LISTENER =
(SID_LIST =
(SID_DESC =
(SID_NAME = PLSExtProc)
(ORACLE_HOME = /opt/oracle/product/9.2.0)
(PROGRAM = extproc)
(SID_DESC =
(GLOBAL_DBNAME = TMIS)
(ORACLE_HOME = /opt/oracle/product/9.2.0)
(SID_NAME = TMIS)
###why there was another service called "PLSExtProc")
LSNRCTL> services
Connecting to (DESCRIPTION=(ADDRESS=(PROTOCOL=IPC)(KEY=EXTPROC)))
Services Summary...
Service "PLSExtProc" has 1 instance(s).
Instance "PLSExtProc", status UNKNOWN, has 1 handler(s) for this service...
Handler(s):
"DEDICATED" established:0 refused:0
LOCAL SERVER
Service "TMIS" has 1 instance(s).
Instance "TMIS", status UNKNOWN, has 1 handler(s) for this service...
Handler(s):
"DEDICATED" established:0 refused:0
LOCAL SERVER
please help me solve this question ,i'm confused by this problem.
thank you very very much!!!
my email address is [email protected],please connect with me !!

ORA-12705: Cannot access NLS data files or invalid environment specified
Cause: Either an attempt was made to issue an ALTER SESSION command with an invalid NLS parameter or value; or the environment variable(s) NLS_LANG, ORA_NLSxx, or ORACLE_HOME was incorrectly specified, therefore the NLS data files cannot be located.
Action: Check the syntax of the ALTER SESSION command and the NLS parameter, correct the syntax and retry the statement, or specify the correct directory path/values in the environment variables.
Set your NLS environment variable Correctly
SQL> show parameter nls
NAME TYPE VALUE
nls_calendar string
nls_comp string
nls_currency string
nls_date_format string
nls_date_language string
nls_dual_currency string
nls_iso_currency string
nls_language string AMERICAN
nls_length_semantics string BYTE
nls_nchar_conv_excp string FALSE
nls_numeric_characters string
NAME TYPE VALUE
nls_sort string
nls_territory string AMERICA
nls_time_format string
nls_time_tz_format string
nls_timestamp_format string
nls_timestamp_tz_format string
SQL>

Similar Messages

ORCL Failed to connect to database instance: Closed Connection.

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

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

Deploy form, question about database object or connection parameters

When form to be deployed to the dev/test/production environment, should it be compiled with that specific database connection username, password and sid? Another words, when I compile the database objects created for the compile is embedded in the .fmx file?
thanks for help

You won't need to compile your forms if the passwords of the target schema differs. It also doesn't matter on what platform/architecture the database server runs on. However it would matter how you created your schema objects. And of course it will matter if the platform your forms run on differ. The list of "what you need to do when you don't want to compile against the target database" is a long one.
Here is a short list of don'ts
- no +select * from [...]+ views
- no +select * from [...]+ in forms cursors and the like
- %TYPE is evil
- %ROWTYPE is much more evil
Those are just a few obvious things developers can mess up. Of course we all know that this sort of things are bad programming practice but they do happen. And as said: that's just the most obvious things. I work for a vendor where only the compiled files are shipped to the customer, and the road to this goal is a hard and bumpy one. If you don't want bad surprises in production I suggest you implement a fixed build process routine and a fixed upgrade process where you can ensure that the target database where the forms run against match exactly the development database you compile your forms from a logical point of view. The far easier exit is to just compile your forms on the target platform against the target database but I understand that this is not always possible.
cheers

"WARNING! Closed connections to peer [standby IP] database! Please restart peer node to bring databases in sync!!"

i have a two appliances of NAC Manager, i want to make a failover, but i only connect them with a crossover cable on eth1,
is it neccesary conect a serial cable?, because when i try to verify a failover they appear this:
“WARNING! Closed connections to peer [192.168.0.254] database! Please restart peer node to bring databases in sync!!” in each one

Hi. I had a lot of those messages. In my scenario the failover bundle works OK during certain time but ocassionally the hearbeat fails (never knew why) and the warning messages appeared. Since there's no sync anymore the config in both manager will be different, so the very first thing to do is to backup the configuration. Please notice if the current active NAM is the primary or the secondary NAM (it's necessary to know this information for the later steps).
Then you will have to stop both NAM (service perfigo stop)
Now there's an extra step only if the last active NAM was the secondary : you will have to restore the backup into the primary NAM (since this NAM will have an outdated configuration).
Now back to the regular steps. You must start both NAM . The primary NAM will be the new active , synchronization will take some minutes, after that the "warning" will be cleared.
Please rate if it helps.

Closing connection

Hello, I work with jdeveloper. I had 10.1.2 which used java version 1.4.2 and I used a simple connection class to call stored procedures in an Oracle db. I have jdeveloper 10.1.3 which uses java version 1.5.0 and the same class fails when I try to use ResultSets. I use to close the connection then return the resultset to whatever called it, now it tells me the connection is already closed when I try to access the resultset. I know this is why it's failing now, because it works if I don't close anything.
Can someone tell me how/why this has changed, and what I can do about it?
Thanks
Classes that use to work:
public class dbConn {
public dbConn() {
public static Connection getCon()
InitialContext ctx = null;
DataSource ds = null;
Connection conn = null;
try {
ctx = new InitialContext();
ds = (DataSource) ctx.lookup("jdbc/app1");
conn = ds.getConnection();
catch(Exception e){
System.out.println("Connection Error");
e.printStackTrace();
return conn;
public static void closeCon(CallableStatement proc, Connection conn)
try {
proc.close();
conn.close();
catch(SQLException e){
System.out.println("Error closing connections: "+e);
public static void main()
public static ResultSet GenResSet(String uname, String procName)
Connection conn = null;
CallableStatement proc = null;
ResultSet rs = null;
String callString = "{ call "+procName+"(?,?) }";
try {
conn = dbConn.getCon();
proc = conn.prepareCall(callString);
proc.registerOutParameter(1,OracleTypes.CURSOR);
proc.setString(2, uname);
proc.execute();
rs = (ResultSet)proc.getObject(1);
catch(SQLException e) {
System.out.println("sql error");
e.printStackTrace();
finally {
dbConn.closeCon(proc,conn);
return rs;
}

Ok thanks. So I can learn.. what exactly is my
misconception about how it works? My beginner view is
you stored a cursor set from a database query in a
result set then you could iterate through it. Why
does it have to be stored in a collection first? I
was closing the connection before I returned it, or
so I thought. It went through the finally code to
close everytime, but I could still use the results.
Maybe it wasn't closing them?That's exactly your misconception. After you close the connection, your ResultSet is not valid. In simple words, you need a live connection to fetch values from the ResultSet. In your method, you close the connection in the finally block and return the resultset. You will need to hold the results in something else, which would be some suitable collection.

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

SQLException: Closed Connection, SQL state [null]; error code [17002]

Hello All,
I am supporting a Java 5 project on Tomcat. We've used Spring and Stored Procedure in the project.
Recently we deployed our application in a GoLive environment and have started seeing Timeout errors in log files. After around two days we also have to restart Tomcat as users are no more able to login to access the application.
Same application runs fine without any timeout issues on another environment.
The only difference between two environments is that the Go-Live env has a firewall between Tomcat and Database and the other environment hosts both Tomcat and Database on same machine (i.e. no firewall).
For GoLive env the only port open on firewall for JDBC connection is 1521 and is used in the connection string url for obtaining the connections.
When there is a Timeout error, the N/w admin guy observed that the JDBC connection was not attempted on 1521 port, but on some random port which is not open on firewall, due to which the Database server logs also do not show entry for this connection attempt as it gets blocked by the firewall.
I am not sure why a randam port should be used to connect when a specific port is mentioned in the connection url? Also what can be making this port switching?
Application uses Apache DBCP with Spring to obtain connections.
Has anyone experienced similar errors?
Any suggestions/help on this issue is greatly appreciated!
Many Thanks,
CD
===============================
Error Log Extract:
Error while extracting database product name - falling back to empty error codes
org.springframework.jdbc.support.MetaDataAccessException: Error while extracting DatabaseMetaData; nested exception is java.sql.SQLException: Closed Connection
java.sql.SQLException: Closed Connection
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.PhysicalConnection.getMetaData(PhysicalConnection.java:1605)
at org.apache.commons.dbcp.DelegatingConnection.getMetaData(DelegatingConnection.java:247)
at org.apache.commons.dbcp.DelegatingConnection.getMetaData(DelegatingConnection.java:247)
at org.apache.commons.dbcp.PoolingDataSource$PoolGuardConnectionWrapper.getMetaData(PoolingDataSource.java:231)
at org.springframework.jdbc.support.JdbcUtils.extractDatabaseMetaData(JdbcUtils.java:172)
at org.springframework.jdbc.support.JdbcUtils.extractDatabaseMetaData(JdbcUtils.java:207)
at org.springframework.jdbc.support.SQLErrorCodesFactory.getErrorCodes(SQLErrorCodesFactory.java:187)
at org.springframework.jdbc.support.SQLErrorCodeSQLExceptionTranslator.setDataSource(SQLErrorCodeSQLExceptionTranslator.java:126)
at org.springframework.jdbc.support.SQLErrorCodeSQLExceptionTranslator.<init>(SQLErrorCodeSQLExceptionTranslator.java:92)
at org.springframework.jdbc.support.JdbcAccessor.getExceptionTranslator(JdbcAccessor.java:96)
at org.springframework.jdbc.core.JdbcTemplate.execute(JdbcTemplate.java:294)
at org.springframework.jdbc.core.JdbcTemplate.query(JdbcTemplate.java:348)
at org.springframework.jdbc.core.JdbcTemplate.query(JdbcTemplate.java:352)
at org.springframework.jdbc.core.JdbcTemplate.query(JdbcTemplate.java:356)
at com.o2.morse.dao.impl.sql.UserDaoImpl.batchLoad(UserDaoImpl.java:371)
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:585)
at org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:287)
at org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:181)
at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:148)
at org.springframework.transaction.interceptor.TransactionInterceptor.invoke(TransactionInterceptor.java:96)
at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:170)
at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:176)
at $Proxy3.batchLoad(Unknown Source)
at com.o2.morse.domain.User.doHousekeeping(User.java:667)
at com.o2.morse.domain.User$$FastClassByCGLIB$$372ff70b.invoke(<generated>)
at net.sf.cglib.proxy.MethodProxy.invoke(MethodProxy.java:149)
at org.springframework.aop.framework.Cglib2AopProxy$CglibMethodInvocation.invokeJoinpoint(Cglib2AopProxy.java:705)
at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:148)
at org.springframework.transaction.interceptor.TransactionInterceptor.invoke(TransactionInterceptor.java:96)
at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:170)
at org.springframework.aop.framework.Cglib2AopProxy$DynamicAdvisedInterceptor.intercept(Cglib2AopProxy.java:643)
at com.o2.morse.domain.User$$EnhancerByCGLIB$$d5ac966a.doHousekeeping(<generated>)
at com.o2.morse.scheduler.EndOfDay.run(EndOfDay.java:63)
at com.o2.morse.scheduler.EndOfDay$$FastClassByCGLIB$$3b2d4927.invoke(<generated>)
at net.sf.cglib.proxy.MethodProxy.invoke(MethodProxy.java:149)
at org.springframework.aop.framework.Cglib2AopProxy$CglibMethodInvocation.invokeJoinpoint(Cglib2AopProxy.java:705)
at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:148)
at org.springframework.transaction.interceptor.TransactionInterceptor.invoke(TransactionInterceptor.java:96)
at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:170)
at org.springframework.aop.framework.Cglib2AopProxy$DynamicAdvisedInterceptor.intercept(Cglib2AopProxy.java:643)
at com.o2.morse.scheduler.EndOfDay$$EnhancerByCGLIB$$488a9f86.run(<generated>)
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:585)
at org.springframework.util.MethodInvoker.invoke(MethodInvoker.java:248)
at org.springframework.scheduling.quartz.MethodInvokingJobDetailFactoryBean$MethodInvokingJob.executeInternal(MethodInvokingJobDetailFactoryBean.java:165)
at org.springframework.scheduling.quartz.QuartzJobBean.execute(QuartzJobBean.java:90)
at org.quartz.core.JobRunShell.run(JobRunShell.java:202)
at org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:525)
Could not close JDBC Connection
java.sql.SQLException: Already closed.
at org.apache.commons.dbcp.PoolableConnection.close(PoolableConnection.java:77)
at org.apache.commons.dbcp.PoolingDataSource$PoolGuardConnectionWrapper.close(PoolingDataSource.java:180)
at org.springframework.jdbc.datasource.DataSourceUtils.doReleaseConnection(DataSourceUtils.java:286)
at org.springframework.jdbc.datasource.DataSourceUtils.releaseConnection(DataSourceUtils.java:247)
at org.springframework.jdbc.datasource.DataSourceTransactionManager.doCleanupAfterCompletion(DataSourceTransactionManager.java:297)
at org.springframework.transaction.support.AbstractPlatformTransactionManager.cleanupAfterCompletion(AbstractPlatformTransactionManager.java:754)
at org.springframework.transaction.support.AbstractPlatformTransactionManager.processRollback(AbstractPlatformTransactionManager.java:615)
at org.springframework.transaction.support.AbstractPlatformTransactionManager.rollback(AbstractPlatformTransactionManager.java:560)
at org.springframework.transaction.interceptor.TransactionAspectSupport.doCloseTransactionAfterThrowing(TransactionAspectSupport.java:284)
at org.springframework.transaction.interceptor.TransactionInterceptor.invoke(TransactionInterceptor.java:100)
at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:170)
at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:176)
at $Proxy3.batchLoad(Unknown Source)
at com.o2.morse.domain.User.doHousekeeping(User.java:667)
at com.o2.morse.domain.User$$FastClassByCGLIB$$372ff70b.invoke(<generated>)
at net.sf.cglib.proxy.MethodProxy.invoke(MethodProxy.java:149)
at org.springframework.aop.framework.Cglib2AopProxy$CglibMethodInvocation.invokeJoinpoint(Cglib2AopProxy.java:705)
at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:148)
at org.springframework.transaction.interceptor.TransactionInterceptor.invoke(TransactionInterceptor.java:96)
at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:170)
at org.springframework.aop.framework.Cglib2AopProxy$DynamicAdvisedInterceptor.intercept(Cglib2AopProxy.java:643)
at com.o2.morse.domain.User$$EnhancerByCGLIB$$d5ac966a.doHousekeeping(<generated>)
at com.o2.morse.scheduler.EndOfDay.run(EndOfDay.java:63)
at com.o2.morse.scheduler.EndOfDay$$FastClassByCGLIB$$3b2d4927.invoke(<generated>)
at net.sf.cglib.proxy.MethodProxy.invoke(MethodProxy.java:149)
at org.springframework.aop.framework.Cglib2AopProxy$CglibMethodInvocation.invokeJoinpoint(Cglib2AopProxy.java:705)
at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:148)
at org.springframework.transaction.interceptor.TransactionInterceptor.invoke(TransactionInterceptor.java:96)
at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:170)
at org.springframework.aop.framework.Cglib2AopProxy$DynamicAdvisedInterceptor.intercept(Cglib2AopProxy.java:643)
at com.o2.morse.scheduler.EndOfDay$$EnhancerByCGLIB$$488a9f86.run(<generated>)
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:585)
at org.springframework.util.MethodInvoker.invoke(MethodInvoker.java:248)
at org.springframework.scheduling.quartz.MethodInvokingJobDetailFactoryBean$MethodInvokingJob.executeInternal(MethodInvokingJobDetailFactoryBean.java:165)
at org.springframework.scheduling.quartz.QuartzJobBean.execute(QuartzJobBean.java:90)
at org.quartz.core.JobRunShell.run(JobRunShell.java:202)
at org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:525)
Application exception overridden by rollback exception
org.springframework.jdbc.UncategorizedSQLException: StatementCallback; uncategorized SQLException for SQL [SELECT ID_USER_DETAILS, USERNAME, CREATED_ON, LAST_LOGIN FROM USER_DETAILS WHERE STATUS = 157 AND SUPERUSER <> 'Y']; SQL state [null]; error code [17002] ; Io exception: Connection timed out; nested exception is java.sql.SQLException: Io exception: Connection timed out
java.sql.SQLException: Io exception: Connection timed out
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:255)
at oracle.jdbc.driver.T4CStatement.executeForDescribe(T4CStatement.java:820)
at oracle.jdbc.driver.OracleStatement.executeMaybeDescribe(OracleStatement.java:1049)
at oracle.jdbc.driver.T4CStatement.executeMaybeDescribe(T4CStatement.java:845)
at oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleStatement.java:1154)
at oracle.jdbc.driver.OracleStatement.executeQuery(OracleStatement.java:1313)
at org.apache.commons.dbcp.DelegatingStatement.executeQuery(DelegatingStatement.java:205)
at org.apache.commons.dbcp.DelegatingStatement.executeQuery(DelegatingStatement.java:205)
at org.springframework.jdbc.core.JdbcTemplate$1QueryStatementCallback.doInStatement(JdbcTemplate.java:333)
at org.springframework.jdbc.core.JdbcTemplate.execute(JdbcTemplate.java:282)
at org.springframework.jdbc.core.JdbcTemplate.query(JdbcTemplate.java:348)
at org.springframework.jdbc.core.JdbcTemplate.query(JdbcTemplate.java:352)
at org.springframework.jdbc.core.JdbcTemplate.query(JdbcTemplate.java:356)
at com.o2.morse.dao.impl.sql.UserDaoImpl.batchLoad(UserDaoImpl.java:371)
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:585)
at org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:287)
at org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:181)
at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:148)
at org.springframework.transaction.interceptor.TransactionInterceptor.invoke(TransactionInterceptor.java:96)
at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:170)
at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:176)
at $Proxy3.batchLoad(Unknown Source)
at com.o2.morse.domain.User.doHousekeeping(User.java:667)
at com.o2.morse.domain.User$$FastClassByCGLIB$$372ff70b.invoke(<generated>)
at net.sf.cglib.proxy.MethodProxy.invoke(MethodProxy.java:149)
at org.springframework.aop.framework.Cglib2AopProxy$CglibMethodInvocation.invokeJoinpoint(Cglib2AopProxy.java:705)
at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:148)
at org.springframework.transaction.interceptor.TransactionInterceptor.invoke(TransactionInterceptor.java:96)
at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:170)
at org.springframework.aop.framework.Cglib2AopProxy$DynamicAdvisedInterceptor.intercept(Cglib2AopProxy.java:643)
at com.o2.morse.domain.User$$EnhancerByCGLIB$$d5ac966a.doHousekeeping(<generated>)
at com.o2.morse.scheduler.EndOfDay.run(EndOfDay.java:63)
at com.o2.morse.scheduler.EndOfDay$$FastClassByCGLIB$$3b2d4927.invoke(<generated>)
at net.sf.cglib.proxy.MethodProxy.invoke(MethodProxy.java:149)
at org.springframework.aop.framework.Cglib2AopProxy$CglibMethodInvocation.invokeJoinpoint(Cglib2AopProxy.java:705)
at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:148)
at org.springframework.transaction.interceptor.TransactionInterceptor.invoke(TransactionInterceptor.java:96)
at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:170)
at org.springframework.aop.framework.Cglib2AopProxy$DynamicAdvisedInterceptor.intercept(Cglib2AopProxy.java:643)
at com.o2.morse.scheduler.EndOfDay$$EnhancerByCGLIB$$488a9f86.run(<generated>)
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:585)
at org.springframework.util.MethodInvoker.invoke(MethodInvoker.java:248)
at org.springframework.scheduling.quartz.MethodInvokingJobDetailFactoryBean$MethodInvokingJob.executeInternal(MethodInvokingJobDetailFactoryBean.java:165)
at org.springframework.scheduling.quartz.QuartzJobBean.execute(QuartzJobBean.java:90)
at org.quartz.core.JobRunShell.run(JobRunShell.java:202)
at org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:525)
Batch Job Failed: org.springframework.transaction.TransactionSystemException: Could not roll back JDBC transaction; nested exception is java.sql.SQLException: Closed Connection

I am using latest Jrockit 16)5, ojdbc6_g.jar,spring.jar Weblogic 10.3 and Oracle 10G 10.2.4 .. whatever but always get "Closed Connection"
java.lang.Throwable: Closed Connection
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.PhysicalConnection.createStatement(PhysicalConnection.java:750)
at oracle.jdbc.OracleConnectionWrapper.createStatement(OracleConnectionWrapper.java:183)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:27)
at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:7053)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:3902)
at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2773)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:224)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:183)

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.

Using database link to connect to two databases

Hi guys,
Here's my question. I need to give a contractor Select rights on tables located in two schemas located on two different servers. One server is dev and one is prod. Let's say we have schema user: EMPLOYEE on dev and schema user: DEPARTMENT on prod. The outside contractor needs select rights on all tables in DEPARTMENT schema but only needs select on a few tables ( 4 to be exact) from EMPLOYEE schema.
My initial train of thougth is: CREATE a user named: TEST (random name of course, just used for an example) for contractor on prod. Give user TEST select rights on all tables in DEPARTMENT schema.
Create database link to dev server so user TEST can access EMPLOYEE schema.
How do i go about limiting the user TEST via the database link to only view the 4 tables from EMPLOYEE instead of all teh tables?
Should I also consider doing this scenario in reverse? Creating user TEST on dev, giving TEST rights to the 4 tables in EMPLOYEE, then creating the database link to connect to department schema on prod database??
Any help will be appreciated. Thanks in advance.

zephyr223 wrote:
Hi guys,
Here's my question. I need to give a contractor Select rights on tables located in two schemas located on two different servers. One server is dev and one is prod. Let's say we have schema user: EMPLOYEE on dev and schema user: DEPARTMENT on prod. The outside contractor needs select rights on all tables in DEPARTMENT schema but only needs select on a few tables ( 4 to be exact) from EMPLOYEE schema.
My initial train of thougth is: CREATE a user named: TEST (random name of course, just used for an example) for contractor on prod. Give user TEST select rights on all tables in DEPARTMENT schema.
Create database link to dev server so user TEST can access EMPLOYEE schema.
How do i go about limiting the user TEST via the database link to only view the 4 tables from EMPLOYEE instead of all teh tables? Only grant them access to those four tables from EMPLOYEE. You have to explicitly grant privileges anyways, and since there is no GRANT SELECT ON <SCHEMA> ability it should not be that difficult.
Should I also consider doing this scenario in reverse? Creating user TEST on dev, giving TEST rights to the 4 tables in EMPLOYEE, then creating the database link to connect to department schema on prod database?? Are you creating database links as the EMPLOYEE and DEPARTMENT users? If so, I would caution against that. Create a "current user" database link for TEST. I think you can manage privileges better that way.
HTH!
HTH!

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

Web Service exception: Closed Connection

I build a J2EE 1.3 Web Service using JDeveloper 10.1.3 by generating it from a PL/SQL procedure. It works fine on the embedded server and even on the standalone OC4J. When I deploy it on an OAS 10.1.3 it works fine initially but the day after I start to receive the following SOAP message:
<?xml version="1.0" encoding="UTF-8" ?>
- <SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
- <SOAP-ENV:Body>
- <SOAP-ENV:Fault>
<faultcode>SOAP-ENV:Server.Exception:</faultcode>
<faultstring>java.sql.SQLException: java.sql.SQLException: Closed Connection</faultstring>
<faultactor>/login/LoginTesthire</faultactor>
</SOAP-ENV:Fault>
</SOAP-ENV:Body>
</SOAP-ENV:Envelope>

When I program a non-web application I use the following code to connect to and query a SQL Server database (I have omitted the try -catch sections):
Class.forName("com.microsoft.sqlserver.jdbc.SQLServerDriver");
String url = "jdbc:sqlserver://localhost:2766;databaseName=Cosmotim;IntegratedSecurity=true";
Connection conn = DriverManager.getConnection(url);
Statement s1=conn.createStatement();
String select="SELECT * FROM [Table name]";
ResultSet DBSet=s1.executeQuery(select1);But when I use the same code in a Web Service method with return type String and I try to deploy the Web service (to Java System Application Server PE 9 with NetBeans) I get many error messages and I can't deploy the service.
I cannot understand why I can't deploy this WS but I can deploy other Web Services which do not use database connectivity.

Java.sql.SQLException: Closed Connection from Custom Identity Service

Hi,
Here is an issue I am trying to resolve:
Platform: Oracle BPEL 10.1.2
OS: Red Hat Enterprise Linux ES release 4 (Nahant Update 4)
Please note that the whole thing has been working in other same type of installations (e.g. RedHat, Windows, Developer BPEL on Windows & Linux) but this seems to be something special on this server. Any help will be appreciated:
This actually work for sometime (2-3 hours) and then suddenly stops working even if we don't do any transaction on it.
Thanks,
Bipul Dutta.
Error stack:
09/08/17 12:45:25 CustomIdentityService::authenticateUser():: begin
############# inside authenticateUser
09/08/17 12:45:25 CustomIdentityService::user authenticated
############# inside getUser()
09/08/17 12:45:25 java.sql.SQLException: Closed Connection
09/08/17 12:45:25      at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:137)
09/08/17 12:45:25      at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:174)
09/08/17 12:45:25      at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:239)
09/08/17 12:45:25      at oracle.jdbc.driver.PhysicalConnection.prepareStatement(PhysicalConnection.java:930)
09/08/17 12:45:25      at oracle.jdbc.driver.PhysicalConnection.prepareStatement(PhysicalConnection.java:826)
09/08/17 12:45:25      at oracle.tip.pc.services.identity.FAMDBProvider.getUser(FAMDBProvider.java:418)
09/08/17 12:45:25      at oracle.tip.pc.services.identity.FAMCustomIdentityService.lookupUser(FAMCustomIdentityService.java:101)
09/08/17 12:45:25      at oracle.tip.pc.services.hw.worklist.WorklistService.authenticateUser(WorklistService.java:333)
09/08/17 12:45:25      at com.famis.web.service.core.humanworkflow.service.AbstractTaskWebService.getBpelContext(AbstractTaskWebService.java:20)
09/08/17 12:45:25      at com.famis.web.service.core.humanworkflow.service.GetTasksWebServiceImpl.process(GetTasksWebServiceImpl.java:51)
09/08/17 12:45:25      at com.famis.web.service.core.humanworkflow.service.TaskWebServiceImpl.process(TaskWebServiceImpl.java:68)
09/08/17 12:45:25      at sun.reflect.GeneratedMethodAccessor9.invoke(Unknown Source)
09/08/17 12:45:25      at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
09/08/17 12:45:25      at java.lang.reflect.Method.invoke(Method.java:324)
09/08/17 12:45:25      at org.apache.axis.providers.java.MsgProvider.processMessage(MsgProvider.java:141)
09/08/17 12:45:25      at org.apache.axis.providers.java.JavaProvider.invoke(JavaProvider.java:323)
09/08/17 12:45:25      at org.apache.axis.strategies.InvocationStrategy.visit(InvocationStrategy.java:32)
09/08/17 12:45:25      at org.apache.axis.SimpleChain.doVisiting(SimpleChain.java:118)
09/08/17 12:45:25      at org.apache.axis.SimpleChain.invoke(SimpleChain.java:83)
09/08/17 12:45:25      at org.apache.axis.handlers.soap.SOAPService.invoke(SOAPService.java:454)
09/08/17 12:45:25      at org.apache.axis.server.AxisServer.invoke(AxisServer.java:281)
09/08/17 12:45:25      at org.apache.axis.transport.http.AxisServlet.doPost(AxisServlet.java:699)
09/08/17 12:45:25      at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
09/08/17 12:45:25      at org.apache.axis.transport.http.AxisServletBase.service(AxisServletBase.java:327)
09/08/17 12:45:25      at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
09/08/17 12:45:25      at com.evermind.server.http.ServletRequestDispatcher.invoke(ServletRequestDispatcher.java:835)
09/08/17 12:45:25      at com.evermind.server.http.ServletRequestDispatcher.forwardInternal(ServletRequestDispatcher.java:341)
09/08/17 12:45:25      at com.evermind.server.http.HttpRequestHandler.processRequest(HttpRequestHandler.java:816)
09/08/17 12:45:25      at com.evermind.server.http.AJPRequestHandler.run(AJPRequestHandler.java:231)
09/08/17 12:45:25      at com.evermind.server.http.AJPRequestHandler.run(AJPRequestHandler.java:136)
09/08/17 12:45:25      at com.evermind.util.ReleasableResourcePooledExecutor$MyWorker.run(ReleasableResourcePooledExecutor.java:192)
09/08/17 12:45:25      at java.lang.Thread.run(Thread.java:534)
<2009-08-17 12:45:25,877> <ERROR> <tmobilet.collaxa.cube.services> <PCException::<init>> User is not found.
<2009-08-17 12:45:25,877> <ERROR> <tmobilet.collaxa.cube.services> <PCException::<init>> User "BSAUNDE4" is not found in realm "tmobilet".
<2009-08-17 12:45:25,877> <ERROR> <tmobilet.collaxa.cube.services> <PCException::<init>> Check the error stack and fix the cause of the error. Contact
Edited by: user11798418 on Aug 17, 2009 10:30 AM

>
I have my application jar on the server, and launch this JFrame application from the browser. ><zen question>
Which particular 'the browser'? What version of what browser running on what OS?
</zen question>
The reason I ask is that it is up to the browser to call an applet's stop()/destroy() methods and if they do not do so - there is almost nothing we as developers can do about it.
If you need such reliable shut down behaviour, it would be best to launch the applet or frame using Java Web Start.

Got "closed connection" via OEM 10.1.0.2.0

Hello,
please help.....
I installed OEM version 10.1.0.2.0 on windows 2000 PC. All the database instances are displayed under Network Navigator. when i log on to the database either as normal / sysoper /sysdba, I got "closed connection" error right after clicked OK on the login window.
can anyone give me suggestion/ references to this issue?
many thanks.

Check firewall configurations on the PC to see if it is blocking the Listener port 1521. Also check the setting of SQLNET.AUTHENTICATION_SERVICES = in $ORAACLE_HOME/network/admin/sqlnet.ora

Java.sql.SQLException: Closed Connection error when invoking web service

Hi
I've assembled a simple web service for an Oracle PL/SQL package and deployed it on a Standalone OC4J, when I come to invoke it on the Oracle Enterprise Manager screen I'm getting the following returned within the envelope body:
<env:Body>
<env:Fault>
<faultcode>env:Server</faultcode>
<faultstring>Internal Server Error (serialization error: java.sql.SQLException: java.sql.SQLException: Closed Connection)</faultstring>
</env:Fault>
</env:Body>
The function that is called within the database returns a user defined object that consists of a RAW value and an XMLTYPE. The function takes a string as a parameter, when I enter a string that I know will not return an object there is no error in the envelope body, only when there is an object to return does the error appear.
Anyone have any suggestion as to why this is?

I'm no further forward with this: has anyone assembled, deployed and invoked a web service that returns a XMLTYPE?? I know this should be possible but I think there's maybe some manual intervention required with the classes created with webservicesassembler: I'd really appreciate it if anyone with any experience of this kind of thing could help me think this through.

About database's "closed connection"

Similar Messages

Maybe you are looking for