Re: java.sql.SQLException: After clearParameters() has been called, all

Hi,
If you are looking for a patch to a specific issue I suggest contacting support,
quoting any case or change request reference you may have regarding the issue.
Kind Regards,
Richard Wallace
Senior Developer Relations Engineer
BEA Support.
x. wang <[email protected]> wrote:
I have the same problem. I'm using weblogic 5.10, sp10. The problem
happens on both NT4.0, Linux, and Solaris 8. Can you please send me
the patch file?
Many thanks,
xinmin

Similar Messages

SQLException: After clearParameters() has been called, all parameters must be reset before executing

Hi,
I am running: Weblogic 6.1, SP2
Driver : weblogic.jdbc.oci.Driver
Reason for not using the "thin" driver, which works, is limit
on size of Clob
Previous references to this problem in this newsgroup indicate driver problems
with older versions of WL.. I am using the latest..
The SQLException I get is "After clearParameters() has been called, all parameters
must be reset before executing". This happens the second time the code below is
excuted ( ok the first time )
"clearParameters()" is never called explicitly in my code.
The exception occurs on the "spFunc.execute();" statement at the very end of this
code:
// OBS:connection, conn_, is opened from a connection pool
before this code is called and cloesed afterwards.
conn_.setAutoCommit(false);
// ============== Initializing clob ==================
SerialStatement stmt = (SerialStatement)conn_.createStatement();
stmt.execute("INSERT INTO lc_clob_temp VALUES (1, EMPTY_CLOB())");
// OBS: using a prepared statement here will result in SerialClob
// exception when using setClob in the prepared statement
below
// This is probably a bug ( worked in WL 5.1 ). We had this
as a support case 270952 with WebLogic.
stmt.execute("SELECT * FROM lc_clob_temp WHERE id = 1");
ResultSet crs = stmt.getResultSet();
weblogic.jdbc.rmi.SerialClob xmlClob = null;
while ( crs.next() ) {
xmlClob=(weblogic.jdbc.rmi.SerialClob)crs.getClob("newclob");
// Call Oracle's stored procedure for calling Oracle XSU.
SerialCallableStatement spFunc =
(SerialCallableStatement)conn_.prepareCall(
"declare " +
"insCtx sys.DBMS_XMLSave.ctxType; " +
"begin " +
"insCtx := sys.DBMS_XMLSave.newContext(?); " +
"sys.DBMS_XMLSave.setBatchSize(insCtx,0);" + "sys.DBMS_XMLSave.setCommitBatch(insCtx,
0);" +
"? := sys.DBMS_XMLSave.insertXML(insCtx,?); " +
"sys.DBMS_XMLSave.closeContext(insCtx); " +
"end;"
spFunc.setString(1, viewName );
spFunc.registerOutParameter (2, Types.NUMERIC);
Writer outstream = xmlClob.getCharacterOutputStream();
outstream.write(xml.toString());
outstream.flush();
outstream.close();
spFunc.setClob( 3, xmlClob);
spFunc.execute();
spFunc.close();

Hi,
I am running: Weblogic 6.1, SP2
Driver : weblogic.jdbc.oci.Driver
Reason for not using the "thin" driver, which works, is limit
on size of Clob
Previous references to this problem in this newsgroup indicate driver problems
with older versions of WL.. I am using the latest..
The SQLException I get is "After clearParameters() has been called, all parameters
must be reset before executing". This happens the second time the code below is
excuted ( ok the first time )
"clearParameters()" is never called explicitly in my code.
The exception occurs on the "spFunc.execute();" statement at the very end of this
code:
// OBS:connection, conn_, is opened from a connection pool
before this code is called and cloesed afterwards.
conn_.setAutoCommit(false);
// ============== Initializing clob ==================
SerialStatement stmt = (SerialStatement)conn_.createStatement();
stmt.execute("INSERT INTO lc_clob_temp VALUES (1, EMPTY_CLOB())");
// OBS: using a prepared statement here will result in SerialClob
// exception when using setClob in the prepared statement
below
// This is probably a bug ( worked in WL 5.1 ). We had this
as a support case 270952 with WebLogic.
stmt.execute("SELECT * FROM lc_clob_temp WHERE id = 1");
ResultSet crs = stmt.getResultSet();
weblogic.jdbc.rmi.SerialClob xmlClob = null;
while ( crs.next() ) {
xmlClob=(weblogic.jdbc.rmi.SerialClob)crs.getClob("newclob");
// Call Oracle's stored procedure for calling Oracle XSU.
SerialCallableStatement spFunc =
(SerialCallableStatement)conn_.prepareCall(
"declare " +
"insCtx sys.DBMS_XMLSave.ctxType; " +
"begin " +
"insCtx := sys.DBMS_XMLSave.newContext(?); " +
"sys.DBMS_XMLSave.setBatchSize(insCtx,0);" + "sys.DBMS_XMLSave.setCommitBatch(insCtx,
0);" +
"? := sys.DBMS_XMLSave.insertXML(insCtx,?); " +
"sys.DBMS_XMLSave.closeContext(insCtx); " +
"end;"
spFunc.setString(1, viewName );
spFunc.registerOutParameter (2, Types.NUMERIC);
Writer outstream = xmlClob.getCharacterOutputStream();
outstream.write(xml.toString());
outstream.flush();
outstream.close();
spFunc.setClob( 3, xmlClob);
spFunc.execute();
spFunc.close();

Exception java.sql.SQLException: This Connection has either timed out

I am using JRUN 4 & SQL Server 2000
and Driver is Type 4 SQL Server 2000.
Type 4 driver : com.microsoft.jdbc.sqlserver.SQLServerDriver
I am able to connect & fire the query but while insertion record it gives me this error.
Exception java.sql.SQLException: This Connection has either timed out
or been closed, and it has returned to its pool. You must re-acquire the Connect
ion.
java.sql.SQLException: This Connection has either timed out or been closed, and
it has returned to its pool. You must re-acquire the Connection.
at jrun.sql.JRunConnectionHandle.assertConnectionExists(JRunConnectionHa
ndle.java:50)
at jrun.sql.JRunConnectionHandle.rollback(JRunConnectionHandle.java:107)
at krisolshipping.common.LMaintain.postData(LMaintain.java:563)
at krisolshipping.securities.SUser.doPost(SUser.java:186)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at jrun.servlet.ServletInvoker.invoke(ServletInvoker.java:91)
at jrun.servlet.JRunInvokerChain.invokeNext(JRunInvokerChain.java:42)
at jrun.servlet.JRunRequestDispatcher.invoke(JRunRequestDispatcher.java:
226)
at jrun.servlet.ServletEngineService.dispatch(ServletEngineService.java:
527)
at jrun.servlet.http.WebService.invokeRunnable(WebService.java:172)
at jrunx.scheduler.ThreadPool$ThreadThrottle.invokeRunnable(ThreadPool.j
ava:451)
Krisol 03 Exception java.sql.SQLException: This Connection has either timed out
or been closed, and it has returned to its pool. at jrunx.scheduler.Worke
rThread.run(WorkerThread.java:66)
You must re-acquire the Connection.
java.sql.SQLException: This Connection has either timed out or been closed, and
it has returned to its pool. You must re-acquire the Connection.

Did you by any chance close the connection?
The following appendix in the connection URL is recommended for M$ SQL:
jdbc:microsoft:sqlserver://mssql:1433;SelectMethod=Cursor

Set Cursor.vi fails after it has been called for 30 different panel refs in LV 7.1.1

Make sure both attached files (Run LabVIEW_Cursor_TestCase.vi, SimpleVI.vi) are in the same folder. Run LabVIEW_Cursor_TestCase.vi notice that the -3 error code is returned from "Set Cursor.vi" after it has been called with 30 different panel refs. If "Set Cursor.vi" is replaced with "Set Busy.vi" the same error occurs.Is there a workaround for this problem other that setting the cursor image manually in user32.dll? I must be able to open more than 30 panels and set them all to busy. In the test case I used a single VI, simply to demonstrate the error.
Message Edited by Jerred on 05-04-2007 10:06 AM
Attachments:
LabVIEW_Cursor_TestCase.vi ‏68 KB
SimpleVI.vi ‏13 KB

This bug is fixed in LabVIEW 8.0 and later. Unfortunately, I know of no workaround in LabVIEW 7.x. When I encountered this bug in one of my UIs in LabVIEW 7.x, my "fix" was simply to ignore the error outputs from the cursor VIs, and to live with the fact that I had no custom cursors after 30 windows had been opened.
-D
Darren Nattinger, CLA
LabVIEW Artisan and Nugget Penman

Java.sql.SQLException: Invalid argument(s) in call: setRowBufferAt

I have created a custom tag that does inserts. While it works on most every other table that I have dealt with, I keep getting this error for a particular table. I have created another table on an entirely different database, but get the same error.
Is anyone familiar with this error? I'm running Oracle 8.1.7.0.0
Thanks in advance,
Jim

Bug 1548205 Fixed: 9011
JDBC
Inserting into an empty Updateable Resultset causes an
SQLException:
java.sql.SQLException: Invalid argument(s) in call: setRowBufferAt

A way to set a flag in java layer when native method has been called?

Hi,
I'm calling a native method from the java layer through to a native c function. Is there a way I can set a flag in the java layer when this native method has been called?
Thanks!

1. Create a wrapper method. The wrapper method is the only exposed method. It calls the native method. It sets the flag.
2. Set the flag in the native method itself.
3. You might be able to use the debugging API to do this however it is going to require quite a bit of work. And it injects itself at runtime.
Is there a reason for this request? There might be other solutions if a general problem was posed.

Java? Stopping after criteria has been met?

Hi, I have this piece of code I have written;
num2 = Integer.parseInt(JOptionPane.showInputDialog("Enter second number"));
if (num1<0){
negative = ("You have entered a negative number!");
JOptionPane.showMessageDialog (null, negative);
num3 = Integer.parseInt(JOptionPane.showInputDialog("Enter third number"));
if (num1<0){
negative = ("You have entered a negative number!");
JOptionPane.showMessageDialog (null, negative);
if ((num1 == num2) && (num1 == num3))
result = ("Your triangle is equalateral, all sides are the same length!");
JOptionPane.showMessageDialog (null, result);
Everytime the user enters a negative number a message pops up saying "You have entered a negative number" BUT then it goes onto the second string and then third string.
I have 3 strings, e.g.
String 1 -> User enters 10
String 2 -> User enters -19 = You have entered a negative number
String 3 -> User enters 99
How can I get the program to stop after the "You have entered a negative number message? Thanx.

Hi,
How can I get the program to stop after the "You have entered a negative number message?{code}
If you want to terminate the currently running jvm use
{code}
System.exit(0);
{code}
Thanks

Unjnown java.sql.SQLException... :-|

Hello !
Does anybody help me to understand this exception ?
java.sql.SQLException: Connection.close() has already been called. Invalid operation in this state.
at com.mysql.jdbc.Connection.getMutex(Connection.java:2101)
at com.mysql.jdbc.PreparedStatement.executeQuery(PreparedStatement.java:1539)
Thanks
Ludovic

Connection.close() has already been called. Invalid operation in this state.
What more can be said? I guess the excepiton trace contains the line where you want to work with the connection after close.
Mike

Java.sql.SQLException: Statement cache size has not been set

All,
I am trying to create a light weight SQL Layer.It uses JDBC to connect to the database via weblogic. When my application tries to connect to the database using JDBC alone (outside of weblogic) everything works fine. But when the application tries to go via weblogic I am able to run the Statement objects successfully but when I try to run PreparedStatements I get the following error:
java.sql.SQLException: Statement cache size has not been set
at weblogic.rjvm.BasicOutboundRequest.sendReceive(BasicOutboundRequest.java:108)
at weblogic.rmi.internal.BasicRemoteRef.invoke(BasicRemoteRef.java:138)
at weblogic.jdbc.rmi.internal.ConnectionImpl_weblogic_jdbc_wrapper_PoolConnection_oracle_jdbc_driver_OracleConnection_812_WLStub.prepareStatement(Unknown Source)
i have checked the StatementCacheSize and it is 10. Is there any other setting that needs to be implemented for this to work? Has anybody seen this error before? Any help will be greatly appreciated.
Thanks.

Pooja Bamba wrote:
I just noticed that I did not copy the jdbc log fully earlier. Here is the log:
JDBC log stream started at Thu Jun 02 14:57:56 EDT 2005
DriverManager.initialize: jdbc.drivers = null
JDBC DriverManager initialized
registerDriver: driver[className=oracle.jdbc.driver.OracleDriver,oracle.jdbc.driver.OracleDriver@12e0e2f]
DriverManager.getDriver("jdbc:oracle:oci:@devatl")
trying driver[className=oracle.jdbc.driver.OracleDriver,oracle.jdbc.driver.OracleDriver@12e0e2f]
getDriver returning driver[className=oracle.jdbc.driver.OracleDriver,oracle.jdbc.driver.OracleDriver@12e0e2f]
Oracle Jdbc tracing is not avaliable in a non-debug zip/jar file
DriverManager.getDriver("jdbc:oracle:oci:@devatl")
trying driver[className=oracle.jdbc.driver.OracleDriver,oracle.jdbc.driver.OracleDriver@12e0e2f]
getDriver returning driver[className=oracle.jdbc.driver.OracleDriver,oracle.jdbc.driver.OracleDriver@12e0e2f]
DriverManager.getDriver("jdbc:oracle:oci:@devatl")
trying driver[className=oracle.jdbc.driver.OracleDriver,oracle.jdbc.driver.OracleDriver@12e0e2f]
getDriver returning driver[className=oracle.jdbc.driver.OracleDriver,oracle.jdbc.driver.OracleDriver@12e0e2f]
DriverManager.getDriver("jdbc:oracle:oci:@devatl")
trying driver[className=oracle.jdbc.driver.OracleDriver,oracle.jdbc.driver.OracleDriver@12e0e2f]
getDriver returning driver[className=oracle.jdbc.driver.OracleDriver,oracle.jdbc.driver.OracleDriver@12e0e2f]
DriverManager.getDriver("jdbc:oracle:oci:@devatl")
trying driver[className=oracle.jdbc.driver.OracleDriver,oracle.jdbc.driver.OracleDriver@12e0e2f]
getDriver returning driver[className=oracle.jdbc.driver.OracleDriver,oracle.jdbc.driver.OracleDriver@12e0e2f]
registerDriver: driver[className=weblogic.jdbc.jts.Driver,weblogic.jdbc.jts.Driver@c0a150]
registerDriver: driver[className=weblogic.jdbc.pool.Driver,weblogic.jdbc.pool.Driver@17dff15]
SQLException: SQLState(null) vendor code(17095)
java.sql.SQLException: Statement cache size has not been set
     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)Hi. Ok. This is an Oracle driver bug/problem. Please show me the pool's definition
in the config.xml file. I'll bet you're defining the pool in an unusual way. Typically
we don't want any driver-level pooling to be involved. It is superfluous to the functionality
we provide, and can also conflict.
Joe
     at oracle.jdbc.driver.OracleConnection.prepareCallWithKey(OracleConnection.java:1037)
     at weblogic.jdbc.wrapper.PoolConnection_oracle_jdbc_driver_OracleConnection.prepareCallWithKey(Unknown Source)
     at weblogic.jdbc.rmi.internal.ConnectionImpl_weblogic_jdbc_wrapper_PoolConnection_oracle_jdbc_driver_OracleConnection.prepareCallWithKey(Unknown Source)
     at weblogic.jdbc.rmi.internal.ConnectionImpl_weblogic_jdbc_wrapper_PoolConnection_oracle_jdbc_driver_OracleConnection_WLSkel.invoke(Unknown Source)
     at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:477)
     at weblogic.rmi.internal.BasicServerRef$1.run(BasicServerRef.java:420)
     at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:353)
     at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:144)
     at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:415)
     at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:30)
     at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197)
     at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:170)
SQLException: SQLState(null) vendor code(17095)

Java.sql.SQLException: Connection has already been created in this tx context for pool named adrxSYBDEV07

I keep getting the following error when I try to use 2 different java.sql.Connections
from 2 different database connection pools in my message ejb. The message ejb
uses container managed transaction. The 2 connection pools point to different
Sybase Servers.
Any help will be much appreciated !!!
java.sql.SQLException: Connection has already been created in this tx context
for pool named adrxSYBDEV07. Illegal attempt to create connection from another
pool: Sybbev07Pool JDBCUtil > getConnection()

Hi Eddie,
"Eddie Baue" <[email protected]> wrote in message
news:3ddbf74f$[email protected]..
I keep getting the following error when I try to use 2 differentjava.sql.Connections
from 2 different database connection pools in my message ejb. The messageejb
uses container managed transaction. The 2 connection pools point todifferent
Sybase Servers.In order to access more then one database base within
a TX you need to have TXDataSources backed by XA
connection pools...
Regards,
Slava Imeshev

Java.sql.SQLException: The TCP/IP connection to the host has failed.

Hello. I hope you had a happy new year! Now its back to work.
I am having a problem connecting to a remote SQL Server DB. I am using NetBeans 5.5 and the latest J2EE. I am able to see the tables in the IDE and bind objects to data. But when I run it it gets this:
java.sql.SQLException: Error in allocating a connection. Cause: Connection could not be allocated because: The TCP/IP connection to the host has failed. java.net.ConnectException: Connection refused: no further information
at com.sun.gjc.spi.DataSource.getConnection(DataSource.java:100)
at com.sun.sql.rowset.internal.CachedRowSetXReader.connect(CachedRowSetXReader.java:344)
at com.sun.sql.rowset.internal.CachedRowSetXReader.readData(CachedRowSetXReader.java:126)
at com.sun.sql.rowset.CachedRowSetXImpl.execute(CachedRowSetXImpl.java:968)
at com.sun.sql.rowset.CachedRowSetXImpl.execute(CachedRowSetXImpl.java:1428)
I checked the SQL Server Configuration manager on that machine and TCP/IP connections are allowed. What else could be wrong?
Thank You.

"Connection refused" means that the client sends a packet saying "I would like to connect to port number NNNN please" to the server computer, and the server computer's OS sends the reply "there is no process listening to that port on the network interface you are using".
The database server is not running, or running but not listening to TCP/IP connections, or at a different port from what you think, or listening to only selected network interfaces (it is possible for a process to listen to a specific interface or a wildcard for all interfaces). A less likely scenario is that a firewall is sending the "connection refused" message.
First aid check list for "connection refused":
- Check host name in connect string.
- Check port number in connect string.
- Try numeric IP address of server host in connect string, in case name server is hosed.
- Are there any firewalls between client and server blocking the port.
- Check that the db server is running.
- Check that the db server is listening to the port. On the server, try: "telnet localhost the-port-number". Or "netstat -an", there should be a listening entry for the port. You need to configure the database to accept TCP connections; the server documentation or google should explain how.
- Try "telnet server-host-name the-port-number" from the client, to see if firewalls are blocking it.
- If "telnet" fails: try telnet with the numeric ip address.
- If "telnet" fails: does it fail immediately or after an obvious timeout? How long is the timeout?
- Does the server respond to "ping serverhost" or "telnet serverhost" or "ssh serverhost"?

Java.sql.SQLException: No operations allowed after connection closed

Hi all
I was trying the jakarta DBCP pool for managing my connections to Mysql(4.0.17-standard ). I let tomcat to manage the pool by specifying datasource in server.xml and web.xml. Everything works fine if there are only a few transactions. But when the number of queries increse, I get an exception like
java.sql.SQLException: No operations allowed after connection closed.
Connection was closed explicitly by the application at the following location:
** BEGIN NESTED EXCEPTION **
java.lang.Throwable
STACKTRACE:
java.lang.Throwable
        at com.mysql.jdbc.Connection.close(Connection.java:1061)
        at org.apache.commons.dbcp.PoolableConnection.reallyClose(PoolableConnec
tion.java:124)
        at org.apache.commons.dbcp.PoolableConnectionFactory.destroyObject(Poola
bleConnectionFactory.java:196)
        at org.apache.commons.pool.impl.GenericObjectPool.returnObject(Unknown S
ource)
        at org.apache.commons.dbcp.AbandonedObjectPool.returnObject(AbandonedObj
ectPool.java:140)
        at org.apache.commons.dbcp.PoolableConnection.close(PoolableConnection.j
ava:110)
......I then tried the Connecion Pool manually with DBCP to check it is a problm with tomcat or ont. Still the exception comes after a few transactions. I re-checked the code and I am closing all connections in finally block. I searched in net for a solution, but couldnt find any. Is that a problm with mysql? has anyone experienced it? Any help will be greatly appreciated
thanks
boolee

Odd that Throwable is the exception logged. What does your finally block actually look like? As an experiment, what happens if you execute the following line of hypothetical code in your 'finally' block?
finally {
System.out.println(conn.getClass().getName());
}- Saish

Java.sql.SQLException: Cannot obtain connection after 3600 seconds. , Exception = Access not allowed

Using Weblogic Platform 7.0 (installed from platform700_win32.exe),
Running a BPM Doamin(WLIDomain with BPM only).
When I try to access my entity bean(CMP), the following exception is getting thrown.
I have seen a similar post in here, but the answer to that post, which says to
provide ACL. does not apply quite well my scenario.
To do this, I right clicked on the connection pool and selected define Ploicy..
It shows two options
RealmAdapterAuthorizer and DefaultAuthorizer; On DefaultAuthroizer i specified
role accessing the resource would be "everyone". - restarted the server - but
still the same error.
Please suggest a solution if any. Do i have to get some service pack for this?
TIA
Ranjith.

We have never seen a case yet where this was not a permissions problem.
Do you have a fileRealm.properties file as part of your configuration?
"Ranjith" <[email protected]> wrote in message
news:3f0fdeb3$[email protected]..
>
java.sql.SQLException: Cannot obtain connection after 3600 seconds. ,Exception
= Access not allowed
java.sql.SQLException: Cannot obtain connection after 3600 seconds. ,Exception
= Access not allowed
atweblogic.jdbc.jts.Connection.wrapAndThrowSQLException(Connection.java:701)
atweblogic.jdbc.jts.Connection.getOrCreateConnection(Connection.java:623)
atweblogic.jdbc.jts.Connection.prepareStatement(Connection.java:133)
atweblogic.jdbc.rmi.internal.ConnectionImpl.prepareStatement(ConnectionImpl.ja
va:139)
atweblogic.jdbc.rmi.SerialConnection.prepareStatement(SerialConnection.java:81
atservice.samplemgt.v1_0.ejb.entity.BanksampletypeCMP_ckv0ao__WebLogic_CMP_RDB
MS.ej
bFindAll(BanksampletypeCMP_ckv0ao__WebLogic_CMP_RDBMS.java:873)
at java.lang.reflect.Method.invoke(Native Method)
atweblogic.ejb20.cmp.rdbms.RDBMSPersistenceManager.collectionFinder(RDBMSPersi
stenceManager
java:300)
atweblogic.ejb20.manager.BaseEntityManager.collectionFinder(BaseEntityManager.
java:715)
atweblogic.ejb20.manager.BaseEntityManager.collectionFinder(BaseEntityManager.
java:688)
atweblogic.ejb20.internal.EntityEJBLocalHome.finder(EntityEJBLocalHome.java:47
6)
at ...

Cannot obtain connection after 30 seconds. : java.sql.SQLException: Data So

Hi Guys,
I need some help, I've already set up my datasource. It was working when i had only 1 EJB module.
But when i added another ejb module to be loaded. I started having this kind of problem:
##<Oct 11, 2007 9:07:17 AM GMT+08:00> <Error> <Deployer> <djao> <AdminServer> <[STANDBY] ExecuteThread: '2' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1192064837780> <BEA-149231> <Unable to set the activation state to true for the application 'Test.ear'.
weblogic.application.ModuleException: Exception activating module: EJBModule(MyEntityEJBs.jar)
Unable to deploy EJB: MyEntity from MyEntityEJBs.jar:
Cannot obtain connection after 30 seconds. : java.sql.SQLException: Data Source jdbc/DataSource does not exist.
     at weblogic.ejb.container.deployer.EJBModule.activate(EJBModule.java:422)
     at weblogic.application.internal.flow.ModuleListenerInvoker.activate(ModuleListenerInvoker.java:107)
     at weblogic.application.internal.flow.DeploymentCallbackFlow$2.next(DeploymentCallbackFlow.java:381)
     at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
     at weblogic.application.internal.flow.DeploymentCallbackFlow.activate(DeploymentCallbackFlow.java:71)
     at weblogic.application.internal.flow.DeploymentCallbackFlow.activate(DeploymentCallbackFlow.java:63)
     at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:641)
     at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
     at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:229)
     at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:154)
     at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:80)
     at weblogic.deploy.internal.targetserver.BasicDeployment.activate(BasicDeployment.java:181)
     at weblogic.deploy.internal.targetserver.BasicDeployment.activateFromServerLifecycle(BasicDeployment.java:352)
     at weblogic.management.deploy.internal.DeploymentAdapter$1.doActivate(DeploymentAdapter.java:52)
     at weblogic.management.deploy.internal.DeploymentAdapter.activate(DeploymentAdapter.java:186)
     at weblogic.management.deploy.internal.AppTransition$2.transitionApp(AppTransition.java:30)
     at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:233)
     at weblogic.management.deploy.internal.ConfiguredDeployments.activate(ConfiguredDeployments.java:169)
     at weblogic.management.deploy.internal.ConfiguredDeployments.deploy(ConfiguredDeployments.java:123)
     at weblogic.management.deploy.internal.DeploymentServerService.resume(DeploymentServerService.java:173)
     at weblogic.management.deploy.internal.DeploymentServerService.start(DeploymentServerService.java:89)
     at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
     at weblogic.work.ServerWorkManagerImpl$WorkAdapterImpl.run(ServerWorkManagerImpl.java:518)
     at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
     at weblogic.work.ExecuteThread.run(ExecuteThread.java:181)
Cannot obtain connection after 30 seconds. : java.sql.SQLException: Data Source jdbc/DataSource does not exist. NestedException Message is :Cannot obtain connection after 30 seconds. : java.sql.SQLException: Data Source jdbc/DataSource does not exist.
     at weblogic.ejb.container.cmp11.rdbms.PersistenceManagerImpl.verifyDatabaseType(PersistenceManagerImpl.java:251)
     at weblogic.ejb.container.cmp11.rdbms.PersistenceManagerImpl.setup(PersistenceManagerImpl.java:148)
     at weblogic.ejb.container.manager.BaseEntityManager.setupPM(BaseEntityManager.java:295)
     at weblogic.ejb.container.manager.BaseEntityManager.setup(BaseEntityManager.java:244)
     at weblogic.ejb.container.manager.DBManager.setup(DBManager.java:172)
     at weblogic.ejb.container.deployer.ClientDrivenBeanInfoImpl.activate(ClientDrivenBeanInfoImpl.java:1379)
     at weblogic.ejb.container.deployer.EntityBeanInfoImpl.activate(EntityBeanInfoImpl.java:232)
     at weblogic.ejb.container.deployer.EJBDeployer.activate(EJBDeployer.java:1270)
     at weblogic.ejb.container.deployer.EJBModule.activate(EJBModule.java:405)
     at weblogic.application.internal.flow.ModuleListenerInvoker.activate(ModuleListenerInvoker.java:107)
     at weblogic.application.internal.flow.DeploymentCallbackFlow$2.next(DeploymentCallbackFlow.java:381)
     at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
     at weblogic.application.internal.flow.DeploymentCallbackFlow.activate(DeploymentCallbackFlow.java:71)
     at weblogic.application.internal.flow.DeploymentCallbackFlow.activate(DeploymentCallbackFlow.java:63)
     at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:641)
     at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
     at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:229)
     at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:154)
     at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:80)
     at weblogic.deploy.internal.targetserver.BasicDeployment.activate(BasicDeployment.java:181)
     at weblogic.deploy.internal.targetserver.BasicDeployment.activateFromServerLifecycle(BasicDeployment.java:352)
     at weblogic.management.deploy.internal.DeploymentAdapter$1.doActivate(DeploymentAdapter.java:52)
     at weblogic.management.deploy.internal.DeploymentAdapter.activate(DeploymentAdapter.java:186)
     at weblogic.management.deploy.internal.AppTransition$2.transitionApp(AppTransition.java:30)
     at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:233)
     at weblogic.management.deploy.internal.ConfiguredDeployments.activate(ConfiguredDeployments.java:169)
     at weblogic.management.deploy.internal.ConfiguredDeployments.deploy(ConfiguredDeployments.java:123)
     at weblogic.management.deploy.internal.DeploymentServerService.resume(DeploymentServerService.java:173)
     at weblogic.management.deploy.internal.DeploymentServerService.start(DeploymentServerService.java:89)
     at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
     at weblogic.work.ServerWorkManagerImpl$WorkAdapterImpl.run(ServerWorkManagerImpl.java:518)
     at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
     at weblogic.work.ExecuteThread.run(ExecuteThread.java:181)
Can anyone help me with this pls? Im sure that my datasource exist, I could even test the connection in the admin console.
Daniel

Are you sure you have your datasource in place? You can test connection pools, but not datasources.

Oracle error 1403:java.sql.SQLException: ORA-01403: no data found ORA-06512

My customer has an issue, and error message as below:
<PRE>Oracle error 1403: java.sql.SQLException: ORA-01403: no data found ORA-06512:
at line 1 has been detected in FND_SESSION_MANAGEMENT.CHECK_SESSION. Your
session is no longer valid.</PRE>
Servlet error: An exception occurred. The current application deployment descriptors do not allow for including it in this response. Please consult the application log for details.
And customer’s statement is: Upgrade from EBS 11.5.10 to 12.1.3. Login the EBS, open any forms and put it in idle. Then refresh the form, error happens
Then, I checked ISP, and found two notes:
Note 1284094.1: Web ADI Journal Upload Errors With ORA-01403 No Data Found ORA-06512 At Line Has Been Detected In FND_SESSION_MANAGEMENT.CHECK_SESSION.Your Session Is No Longer Valid (Doc ID 1284094.1)
Note 1319380.1: Webadi Gl Journal Posting Errors After Atg R12.1.3 (Doc ID 1319380.1)
But these two notes are both WebADI.
Following is the data collection from customer:
1. Run UNIX command to check .class file version:
strings $JAVA_TOP/oracle/apps/bne/utilities/BneViewerUtils.class | grep Header--> S$Header: BneViewerUtils.java 120.33.12010000.17 2010/11/21 22:19:58 amgonzal s$
2. Run SQL to check you patch level:
SELECT * FROM fnd_product_installations WHERE patch_level LIKE '%BNE%';--> R12.BNE.B.3
3. Run SQL to check patch '9940148' applied or not:
SELECT * FROM ad_bugs ad WHERE ad.bug_number = '9940148';--> No Rows returned
4. Run SQL to check patch '9785477' applied or not:
SELECT * FROM ad_bugs WHERE bug_number in ('9785477');-->
BUG_ID APPLICATION_SHORT_NAME BUG_NUMBER CREATION_DATE ARU_RELEASE_NAME CREATED_BY LAST_UPDATE_DATE LAST_UPDATED_BY TRACKABLE_ENTITY_ABBR BASELINE_NAME GENERIC_PATCH LANGUAGE
576982 11839583 2011/8/7 上午 08:20:36 R12 5 2011/8/7 上午 08:20:36 5 pjt B n US
516492 9785477 2011/6/12 上午 11:42:45 R12 5 2011/6/12 上午 11:42:45 5 bne B n US
546109 9785477 2011/6/12 下午 01:17:41 R12 5 2011/6/12 下午 01:17:41 5 bne B n ZHT
5. Run SQL to check the status of object ‘FND_SESSION_MANAGEMENT’
SELECT * FROM dba_objects do WHERE do.object_name = 'FND_SESSION_MANAGEMENT';-->
OWNER OBJECT_NAME SUBOBJECT_NAME OBJECT_ID DATA_OBJECT_ID OBJECT_TYPE CREATED LAST_DDL_TIME TIMESTAMP STATUS TEMPORARY GENERATED SECONDARY NAMESPACE EDITION_NAME
APPS FND_SESSION_MANAGEMENT 219425 PACKAGE 2004/10/30 下午 01:52:35 2011/8/7 上午 08:18:39 2011-08-07:08:18:26 VALID N N N 1
APPS FND_SESSION_MANAGEMENT 226815 PACKAGE BODY 2004/10/31 上午 01:05:40 2011/8/7 上午 08:18:54 2011-08-07:08:18:27 VALID N N N 2
So, my question is: Customer’s BneViewerUtils.java version is already 120.33.12010000.17, which greater than 120.33.12010000.14. Is there any others solutions for this issue? Does customer still need to apply patch '9940148' based on action plan of
Note 1284094.1: Web ADI Journal Upload Errors With ORA-01403 No Data Found ORA-06512 At Line Has Been Detected In FND_SESSION_MANAGEMENT.CHECK_SESSION.Your Session Is No Longer Valid?
Customer's EBS version is 12.1.3; OS is HP-UX PA-RISC (64-bit); DB is 11.2.0.2.
Thanks,
Jackie

And customer’s statement is: Upgrade from EBS 11.5.10 to 12.1.3. Login the EBS, open any forms and put it in idle. Then refresh the form, error happens
Idle for how long? Is the issue with all sessions?
Please see these docs/links
User Sessions Get Timed Out Before Idle Time Parameter Values Are Reached [ID 1306678.1]
https://forums.oracle.com/forums/search.jspa?threadID=&q=Timeout+AND+R12&objID=c3&dateRange=all&userID=&numResults=15&rankBy=10001
Then, I checked ISP, and found two notes:
Note 1284094.1: Web ADI Journal Upload Errors With ORA-01403 No Data Found ORA-06512 At Line Has Been Detected In FND_SESSION_MANAGEMENT.CHECK_SESSION.Your Session Is No Longer Valid (Doc ID 1284094.1)
Note 1319380.1: Webadi Gl Journal Posting Errors After Atg R12.1.3 (Doc ID 1319380.1)
But these two notes are both WebADI.Can you find any details about the error in Apache log files and in the application.log file?
Any errors in the database log file?
So, my question is: Customer’s BneViewerUtils.java version is already 120.33.12010000.17, which greater than 120.33.12010000.14. Is there any others solutions for this issue? No.
Does customer still need to apply patch '9940148' based on action plan ofIf the issue not with Web ADI, then ignore this patch. However, if you use Web ADI you could query AD_BUGS table and verify if you have the patch applied.
Note 1284094.1: Web ADI Journal Upload Errors With ORA-01403 No Data Found ORA-06512 At Line Has Been Detected In FND_SESSION_MANAGEMENT.CHECK_SESSION.Your Session Is No Longer Valid?
Customer's EBS version is 12.1.3; OS is HP-UX PA-RISC (64-bit); DB is 11.2.0.2.If you could not find any details in the logs, please enable debug as per (R12, 12.1 - How To Enable and Collect Debug for HTTP, OC4J and OPMN [ID 422419.1]).
Thanks,
Hussein

Re: java.sql.SQLException: After clearParameters() has been called, all

Similar Messages

Maybe you are looking for