Java.sql.SQLException:The trans ... no longer active - status: 'Unknown'

Oracle DBA team received a stack trace from our developers about an error generated by a JAVA appilcation using a WebLogic 8.1 application server and a Oracle 9.2.0.8 (RAC) database server with a Linux 2.4 OS. No database errors were logged into the database alert or listener logs, and no trace files were generated by database server on the same day. Developers are still looking for a cause.
Here is the info provided to us by the developers:
Nested StackTrace:
java.sql.SQLException:The transaction is no longer active - status: 'Unknown'. No further JDBC access is allowed within this transaction.
     weblogic.jdbc.wrapper.JTSConnection.checkIfRolledBack(JTSConnection.java:219)
     weblogic.jdbc.wrapper.JTSConnection.checkConnection(JTSConnection.java:228)
     weblogic.jdbc.wrapper.ResultSet.getMetaData(ResultSet.java:184)
     us.tx.state.rrc.common.util.QueryUtils.getSimpleResults(QueryUtils.java:455)
     us.tx.state.rrc.common.util.QueryUtils.executeSimplePS(QueryUtils.java:373)
     us.tx.state.rrc.pr.events.valueobject.BaseLeaseEvent.loadEventData(BaseLeaseEvent.java:182)
     us.tx.state.rrc.pr.events.valueobject.BaseLeaseEvent.loadEvents(BaseLeaseEvent.java:194)
     us.tx.state.rrc.pr.events.valueobject.BaseLeaseEvent.getEvents(BaseLeaseEvent.java:161)
     us.tx.state.rrc.pr.events.PREventManager.getLeaseComingleEvents(PREventManager.java:104)
     us.tx.state.rrc.pr.events.PREventManager.getAllEvents(PREventManager.java:81)
     us.tx.state.rrc.pr.events.process.AutoResolveProcess.createTrxs(AutoResolveProcess.java:80)
     us.tx.state.rrc.process.ejb.session.ProcessManagerSessionBean.initProcess(ProcessManagerSessionBean.java:427)
Application reportedly ran okay when resubmitted later on the same day without any other changes to the environment except a RMAN hot full backup finished before the second run. Developers have been unable to reproduce application error. Any ideas on where the developers should look for a more definitive definition of application errors?

That message is a WLS-resident event. It means that the WLS-managed transaction
for which the thread/JDBC connection was operating, has already finished, whether by
having completed normally or having been rolled back.

Similar Messages

Java.sql.SQLException: The url cannot be null" faultCode="Server.Processing

Hi Everyone i am getting the following exception while envoking a java method from the flex using blazeds. Any help would be highly appreciated.
Fault faultString="com.Employee.Employeedetails.connection.DAOException : java.sql.SQLException: The url cannot be null" faultCode="Server.Processing" faultDetail="null"]

Hi Everyone i am getting the following exception while envoking a java method from the flex using blazeds. Any help would be highly appreciated.
Fault faultString="com.Employee.Employeedetails.connection.DAOException : java.sql.SQLException: The url cannot be null" faultCode="Server.Processing" faultDetail="null"]

"java.sql.SQLException: The url cannot be null"

Hi,
I started to use the torque in my last project but when I try to insert new data to the db(i am using MySQL) I get the following error "java.sql.SQLException: The url cannot be null".
Is that error familiar to anybody ?
Regards
RCY

Hi,
Sorry for the lack of info.
1) This is my Torque.properties :
# T O R Q U E P R O P E R T I E S
#Torque has the ability to use multiple databases. This property
#specifies which database is to be used as the default
torque.database.default=rcy
# Torque has the ability to deal with multiple database systems.
# This property specifies the database adapter to use.
torque.database.rcy.adapter=mysql
#torque.database.jd.rcy=mysql
# The factory class that will be used to provide database connections.
torque.dsfactory.rcy.factory=org.apache.torque.dsfactory.SharedPoolDataSourceFactory
#torque.dsfactory.rcy.factory=org.apache.torque.dsfactory.TorqueDataSourceFactory
# The JDBC database driver to use when connecting to your database.
torque.dsfactory.rcy.connection.driver org.gjt.mm.mysql.Driver
# The URL that will be used to access your database. Torque's generated
# object model will perform all database operations using this URL.
# This value should reflect the database name specified in your database schema file
#torque.dsfactory.rcy.connection.url jdbc\:mysql\://localhost\:3306/rcy
torque.dsfactory.rcy.connection.url jdbc\:mysql\://127.0.0.1\:3306/rcy
#torque.dsfactory.rcy.connection.user user
#torque.dsfactory.rcy.connection.password password
torque.dsfactory.rcy.connection.user chen
torque.dsfactory.rcy.connection.password 1qazI created the db with torque and then copied the file(Torque.properties ) to my project.
2) This is my build.properties file :
# T O R Q U E C O N F I G U R A T I O N F I L E
# This file contains the most commonly used properties. For a
# a complete list of build properties, please refer to:
#   http://jakarta.apache.org/turbine/torque/properties-reference.xml
# P R O J E C T
# This is the name of your Torque project. Your non-Java generated
# files will be named using the project name selected below. If your
# project=killerapp then you will have a generated:
#   killerapp-schema.sql
# The custom is then to also rename your project XML schema from
# project-schema.xml to killerapp-schema.xml. This is required
# for a few targets such as datasql, datadump, and datadtd.
torque.project = rcy
# T A R G E T D A T A B A S E
# This is the target database, only considered when generating
# the SQL for your Torque project. Your possible choices are:
#   axion, cloudscape, db2, db2400, hypersonic, interbase, mssql,
#   mysql, oracle, postgresql, sapdb, sybase
torque.database = mysql
# O B J E C T M O D E L I N F O R M A T I O N
# These settings will allow you to customize the way your
# Peer-based object model is created.
# addGetByNameMethod
#   If true, Torque adds methods to get database fields by name/position.
# addIntakeRetrievable
#   If true, the data objects will implement Intake's Retrievable
#   interface
# addSaveMethod
#   If true, Torque adds tracking code to determine how to save objects.
# addTimeStamp
#   If true, Torque true puts time stamps in generated om files.
# basePrefix
#   A string to pre-pend to the file names of base data and peer objects.
# complexObjectModel
#   If true, Torque generates data objects with collection support and
#   methods to easily retreive foreign key relationships.
# targetPackage
#   Sets the Java package the om files will generated to, e.g.
#   "com.company.project.om".
# useClasspath
#   If true, Torque will not look in the <code>templatePath</code> directory,
#   for templates, but instead load them from the classpath, allowing you to
#   use Torque without extracted it from the jar.
# useManagers
#   If true, Torque will generate Manager classes that use JCS for caching.
#   Still considered experimental.
torque.targetPackage = com.base
torque.addGetByNameMethod = true
torque.addIntakeRetrievable = false
torque.addSaveMethod = true
torque.addTimeStamp = true
torque.basePrefix = Base
torque.complexObjectModel = true
torque.useClasspath = false
torque.useManagers = false
# D A T A B A S E S E T T I N G S
# JDBC connection settings. This is used by the JDBCToXML task that
# will create an XML database schema from JDBC metadata. These
# settings are also used by the SQL Ant task to initialize your
# Torque system with the generated SQL.
# sameJavaName
#   If true, the JDBC task will set the javaName attribute for the tables
#   and columns to be the same as SQL name.
torque.database.createUrl = jdbc:mysql://127.0.0.1/mysql
torque.database.buildUrl = jdbc:mysql://127.0.0.1/rcy
torque.database.url = jdbc:mysql://127.0.0.1/rcy
torque.database.driver = org.gjt.mm.mysql.Driver
torque.database.user = chen
torque.database.password = 1qaz
torque.database.host = 127.0.0.1
torque.sameJavaName = falseI hope that will help you to help me :)
Thank's

SQLException: Transaction is no longer active (status = Committed).

I am using TopLink 9.0.3 with a set of stateless session beans running in Weblogic 6.1 hitting an Oracle 8.x database. I am using the recommended approach for using the external trancaction controller but I am seeing the following errors when calling a method on a session bean that persists an object:
UnitOfWork(2028166)--JTS#beforeCompletion()
UnitOfWork(2028166)--#executeQuery(DataReadQuery())
UnitOfWork(2028166)--SELECT SEQUENCE_NUMBER.NEXTVAL FROM DUAL
UnitOfWork(2028166)--#reconnecting to external connection pool
UnitOfWork(2028166)--EXCEPTION [TOPLINK-4002] (TopLink - 9.0.3 (Build 423)): oracle.toplink.exceptions.DatabaseException
EXCEPTION DESCRIPTION: java.sql.SQLException: The transaction is no longer active (status = Committed). No further JDBC access is allowed within this transaction.
INTERNAL EXCEPTION: java.sql.SQLException: The transaction is no longer active (status = Committed). No further JDBC access is allowed within this transaction.
Strangely enough, this session bean method call works the first time it's called but then fails when I call it the second time. It seems there may be some issue with the transaction listener:
--------------- nested within: ------------------
weblogic.transaction.RollbackException: Unexpected exception in beforeCompletion: sync=oracle.toplink.jts.wls.WebLogicSynchronizationListener@1609cc
EXCEPTION DESCRIPTION: java.sql.SQLException: The transaction is no longer active (status = Committed). No further JDBC access is allowed within this transaction.
INTERNAL EXCEPTION: java.sql.SQLException: The transaction is no longer active (status = Committed). No further JDBC access is allowed within this transaction.
ERROR CODE: 0 - with nested exception:
[EXCEPTION [TOPLINK-4002] (TopLink - 9.0.3 (Build 423)): oracle.toplink.exceptions.DatabaseException
EXCEPTION DESCRIPTION: java.sql.SQLException: The transaction is no longer active (status = Committed). No further JDBC access is allowed within this transaction.
INTERNAL EXCEPTION: java.sql.SQLException: The transaction is no longer active (status = Committed). No further JDBC access is allowed within this transaction.
It seems that TopLink is referencing then old transaction. Has anyone seen this issue? Any ideas?
Thanks,
Darcy Welsh.

Hello Darcy,
I'm not exactly sure what is happening and think that a lot more information would be required, so technical support might be your best bet.
My guess would be that your sessionbean method is hitting an exception in user code that is triggering the transaction to be marked for rollback, and thus not allow any SQL execution. Try putting a try/catch/debug statements in your sessionbean method to find out if any exception are occurring.
Otherwise more information such as,
- the complete exception stack trace
- how are you configuring your session, external connection pooling, which transaction controller, etc., does it work with normal connection pooling
- what exactly is the sessionbean doing
- when exactly does the problem occur, are there concurrent process, etc.

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: Byte array not long enough

using thin jdbc returned this exception seems to be connected to the length of the statment:
////////create a prepared statement////////
preUpdateStatement = dbConnection.prepareStatement(updateStatement.toString());
// build data output stream on byte array output stream
ByteArrayOutputStream byte_os = new ByteArrayOutputStream();
DataOutputStream data_os = new DataOutputStream(byte_os);
// write chars to data output stream
data_os.writeChars(((Element)m_values_vector.elementAt(i)).m_value);
// create input stream and pass it to prepared statement
ByteArrayInputStream byte_is = new ByteArrayInputStream(byte_os.toByteArray());
preStatement.setUnicodeStream(i+1, byte_is, byte_os.toByteArray().length);
// execute
preUpdateStatement.executeUpdate();
preUpdateStatement.close();
null

stack is:
java.sql.SQLException: Io exception: Char array not long enough: javaCharsToUtf8Bytes
at java.lang.Throwable.<init>(Compiled Code)
at java.lang.Exception.<init>(Compiled Code)
at java.sql.SQLException.<init>(Compiled Code)
at oracle.jdbc.dbaccess.DBError.throwSqlException(Compiled Code)
at oracle.jdbc.dbaccess.DBError.throwSqlException(Compiled Code)
at oracle.jdbc.dbaccess.DBError.throwSqlException(Compiled Code)
at oracle.jdbc.driver.OracleStatement.executeNonQuery(Compiled Code)
at oracle.jdbc.driver.OracleStatement.doExecuteOther(Compiled Code)
at oracle.jdbc.driver.OracleStatement.doExecuteWithBatch(Compiled Code)
at oracle.jdbc.driver.OracleStatement.doExecute(Compiled Code)
at oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(Compiled Code)
at oracle.jdbc.driver.OraclePreparedStatement.executeUpdate(Compiled Code)

The transaction is no longer active - status: 'Committed'.

Hello -
We are attempting to use a design where a connection will remain in use over multiple
transactions.
Is there any way to get weblogic to allow this?
We are currently experiencing the stack trace below, when a database read is
attempting to use the same connection as the previously committed tx.
Thanks for any advice.
Tyson
org.springframework.jdbc.UncategorizedSQLException: (HibernateAccessor): encountered
SQLException [The transaction is no longer active - status: 'Committed'. No further
JDBC access is allowed within this transaction.]; nested exception is java.sql.SQLException:
The transaction is no longer active - status: 'Committed'. No further JDBC access
is allowed within this transaction. java.sql.SQLException: The transaction is
no longer active - status: 'Committed'. No further JDBC access is allowed within
this transaction. at weblogic.jdbc.wrapper.JTSConnection.checkIfRolledBack(JTSConnection.java:118)
at weblogic.jdbc.wrapper.JTSConnection.checkConnection(JTSConnection.java:127)
at weblogic.jdbc.wrapper.Connection.prepareStatement(Connection.java:324) at weblogic.jdbc.wrapper.JTSConnection.prepareStatement(JTSConnection.java:426)
at com.benefitpoint.cmp.hibernate.AbstractDataManager$2.doInHibernate(AbstractDataManager.java:501)
at org.springframework.orm.hibernate.HibernateTemplate.execute(HibernateTemplate.java:150)
at com.benefitpoint.cmp.hibernate.AbstractDataManager.execRawSqlPreparedStatement(AbstractDataManager.java:568)
at

Tyson Norris wrote:
Hello -
We are attempting to use a design where a connection will remain in use over multiple
transactions.
Is there any way to get weblogic to allow this?No, at least not jts connections. Non-XA connections need our management to
ensure all the work gets committed or rolled back atomically. It doesn't
cost anything to always obtain jts connections in the context of the tx
they are needed.
Besides XA, you could get a plain non-transactional connection and do your
own jdbc commits/rollbacks...
Joe
>
We are currently experiencing the stack trace below, when a database read is
attempting to use the same connection as the previously committed tx.
Thanks for any advice.
Tyson
org.springframework.jdbc.UncategorizedSQLException: (HibernateAccessor): encountered
SQLException [The transaction is no longer active - status: 'Committed'. No further
JDBC access is allowed within this transaction.]; nested exception is java.sql.SQLException:
The transaction is no longer active - status: 'Committed'. No further JDBC access
is allowed within this transaction. java.sql.SQLException: The transaction is
no longer active - status: 'Committed'. No further JDBC access is allowed within
this transaction. at weblogic.jdbc.wrapper.JTSConnection.checkIfRolledBack(JTSConnection.java:118)
at weblogic.jdbc.wrapper.JTSConnection.checkConnection(JTSConnection.java:127)
at weblogic.jdbc.wrapper.Connection.prepareStatement(Connection.java:324) at weblogic.jdbc.wrapper.JTSConnection.prepareStatement(JTSConnection.java:426)
at com.benefitpoint.cmp.hibernate.AbstractDataManager$2.doInHibernate(AbstractDataManager.java:501)
at org.springframework.orm.hibernate.HibernateTemplate.execute(HibernateTemplate.java:150)
at com.benefitpoint.cmp.hibernate.AbstractDataManager.execRawSqlPreparedStatement(AbstractDataManager.java:568)
at

How to get rid of java.sql.SQLException?

I get a error message while executing the SQL statement select * from person where person_ID =? in a web application.
error
java.sql.SQLException: The requested parameter metadata is not available for the current statement.
Thanks in advance

i am using MySQL and NetBeans 5.5.1
when i am using the SQL statement which does not involve user input like
select * from travel
then there is no error and the program is working fine.
But when i use the statement like
select * from travel where = ?
the error is generated.
java.sql.SQLException: [DataDirect]The requested parameter metadata is not available for the current statement.
at com.ddtek.jdbc.base.BaseExceptions.createException(Unknown Source)
at com.ddtek.jdbc.base.BaseExceptions.getException(Unknown Source)
at com.ddtek.jdbc.base.BaseParameters.getParameterInfo(Unknown Source)
at com.ddtek.jdbc.base.BaseParameterMetaData.getParameterType(Unknown Source)
at org.netbeans.modules.sql.project.dbmodel.DBMetaData.getPrepStmtParameters(DBMetaData.java:1749)
at org.netbeans.modules.sql.project.dbmodel.DBMetaData.getPrepStmtMetaData(DBMetaData.java:698)
at org.netbeans.modules.sql.project.dbmodel.DBMetaData.getPrepStmtMetaData(DBMetaData.java:733)
at org.netbeans.modules.sql.project.anttasks.WSDLGenerator.generateInsertSchemaElements(WSDLGenerator.java:690)
at org.netbeans.modules.sql.project.anttasks.WSDLGenerator.modifyMessageTypes(WSDLGenerator.java:401)
at org.netbeans.modules.sql.project.anttasks.WSDLGenerator.modifyWSDL(WSDLGenerator.java:326)
at org.netbeans.modules.sql.project.anttasks.WSDLGenerator.generateWSDL(WSDLGenerator.java:294)
at org.netbeans.modules.sql.project.anttasks.GenerateWSDL.execute(GenerateWSDL.java:176)
at org. customer .tools.ant.UnknownElement.execute(UnknownElement.java:275)
at org. customer .tools.ant.Task.perform(Task.java:364)
at org. customer .tools.ant.Target.execute(Target.java:341)
at org. customer .tools.ant.Target.performTasks(Target.java:369)
at org. customer.tools.ant.Project.executeSortedTargets(Project.java:1216)
at org. customer .tools.ant.Project.executeTarget(Project.java:1185)
at org. customer .tools.ant.helper.DefaultExecutor.executeTargets(DefaultExecutor.java:40)
at org. customer .tools.ant.Project.executeTargets(Project.java:1068)
at org. customer .tools.ant.module.bridge.impl.BridgeImpl.run(BridgeImpl.java:240)
at org. customer .tools.ant.module.run.TargetExecutor.run(TargetExecutor.java:293)
at org.netbeans.core.execution.RunClassThread.run(RunClassThread.java:131)

JDBC Transaction is no longer active - status: 'Marked rollback'

I'm getting the folowing issue, we are not seeing this issue if we recycle the WLS
Using WLS V10.3.3
Can any one suggest on this issue, how to reslove this
85417.772: [Full GC [PSYoungGen: 117504K->0K(234880K)] [PSOldGen: 662564K->665699K(700416K)] 780068K->665699K(935296K) [PSPermGen: 133284K->132438K(225280K)], 30.2876423 secs] [Times: user=31.23 sys=0.68, real=30.32 secs]
java.sql.SQLException: The transaction is no longer active - status: 'Marked rollback. [Reason=weblogic.transaction.internal.TimedOutException: Transaction timed out after 39 seconds
BEA1-600C65F8B23E363DFDF0]'. No further JDBC access is allowed within this transaction.
at weblogic.jdbc.wrapper.JTSConnection.checkIfRolledBack(JTSConnection.java:193)
at weblogic.jdbc.wrapper.JTSConnection.checkConnection(JTSConnection.java:209)
at weblogic.jdbc.wrapper.ResultSet.preInvocationHandler(ResultSet.java:99)
at weblogic.jdbc.wrapper.ResultSet_oracle_jdbc_driver_OracleResultSetImpl.next(Unknown Source)
at com.vzw.pos.cmw.ejb.service.UserProfileService.getNewUserId(Unknown Source)
at com.vzw.pos.cmw.ejb.utils.CMWEjbUtil.createUserProfileVO(Unknown Source)
at com.vzw.pos.cmw.ejb.utils.CMWEjbUtil.createRosterVO(Unknown Source)
at com.vzw.pos.cmw.ejb.service.AdministrationBean.getRostersByUserId(Unknown Source)
at com.vzw.pos.cmw.ejb.service.Administration_ujnwz8_ELOImpl.__WL_invoke(Unknown Source)
at weblogic.ejb.container.internal.SessionLocalMethodInvoker.invoke(SessionLocalMethodInvoker.java:39)
at com.vzw.pos.cmw.ejb.service.Administration_ujnwz8_ELOImpl.getRostersByUserId(Unknown Source)
at com.vzw.pos.cmw.action.CMWTopFrameAction.setUserRoleInSession(Unknown Source)
at com.vzw.pos.cmw.action.CMWTopFrameAction.changeLocation(Unknown Source)
at sun.reflect.GeneratedMethodAccessor190.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.apache.struts.actions.DispatchAction.dispatchMethod(DispatchAction.java:280)
at org.apache.struts.actions.DispatchAction.execute(DispatchAction.java:216)
at org.apache.struts.action.RequestProcessor.processActionPerform(RequestProcessor.java:484)
at org.apache.struts.action.RequestProcessor.process(RequestProcessor.java:274)
at org.apache.struts.action.ActionServlet.process(ActionServlet.java:1482)
at org.apache.struts.action.ActionServlet.doPost(ActionServlet.java:525)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227)
at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125)
at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:300)
at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:26)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
at com.vzw.pos.cmw.filters.CMWFilter.doFilter(Unknown Source)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.wrapRun(WebAppServletContext.java:3710)
at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3676)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120)
at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2272)
at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2178)
at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1454)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:178)
<Aug 23, 2013 10:41:53 AM EDT> <Warning> <Socket> <BEA-000450> <Socket 298 internal data record unavailable (probable closure due idle timeout), event received -32>
<Aug 23, 2013 10:41:53 AM EDT> <Warning> <Socket> <BEA-000450> <Socket 286 internal data record unavailable (probable closure due idle timeout), event received -32>
<Aug 23, 2013 10:41:56 AM EDT> <Warning> <Socket> <BEA-000450> <Socket 299 internal data record unavailable (probable closure due idle timeout), event received -32>
<Aug 23, 2013 10:42:51 AM EDT> <Warning> <Socket> <BEA-000450> <Socket 286 internal data record unavailable (probable closure due idle timeout), event received -32>

Here is DS configuration
Initial Capacity:                  75
Maximum Capacity:                  75
Capacity Increment:                    1
Seconds to trust an idle pool connection:     10
Shrink Frequency:                    900
Enable Connection Leak Profiling:          False
Enable Connection Profiling:               False
Test Frequency:                         120 seconds
Test Connections on Reserve:               True
Connection Reserve Timeout:               10 seconds
Connection Creation Retry Frequency:         1
Inactive Connection Timeout:               60 second
Maximum Waiting for Connection:               2147483647
Statment Cache Type:     LRU
Statment Cache Size:     10
Connection Creation Relay Frequency:      1
Remove Infected Connections Enabled:      True
Wrap Data types:     True
Ignore In-use connections:     True

Java.sql.SQLException:ORA-01801:date format is too long for internal buffer

Hi,
I am getting the following exception when i trying to insert data in to a table through a stored procedure.
oracle.apps.fnd.framework.OAException: java.sql.SQLException: ORA-01801: date format is too long for internal buffer
when execute this stored procedure from ana anonymous block , it gets executed successfully, but i use a OracleCallableStatement to execute the procedure i am getting this error.
Please let me know how to resolve this error.
Is this error something to do with the Database Configuration ?
Thanks & Regards
Meenal

I don't know if this will help, but we were getting this error in several of the standard OA framework pages and after much pain and aggravation it was determined that visiting the Sourcing Home Page was changing the timezone. For most pages this just changed the timezone that dates were displayed in, but some had this ORA-01801 error and some others had an ORA-01830 error (date format picture ends before converting entire input string). Unfortunately, if you are not using Sourcing at your site, this probably won't help, but if you are, have a look at patch # 4519817.
Note that to get the same error, try the following query (I got this error in 9.2.0.5 and 10.1.0.3):
select to_date('10-Mar-2006', 'DD-Mon-YYYY________________________________________________HH24:MI:SS') from dual;
It appears that you can't have a date format that is longer than 68 characters.

Java.sql.SQLException: ORA-20002: 3133: Activity instance 'HR_REVIEW_CHANGE

Hi,
We are on 11.5.10.2 and 9.2.0.8, getting below errors in SSHR any help in this regard would be appreciated. I found one note 472411.1 but its not helping much.
## Detail 0 ##
java.sql.SQLException: ORA-20002: 3133: Activity instance 'HR_REVIEW_CHANGES_JSP_FCT-1' is not a notified activity for item 'HRSSA/62479'.
ORA-06512: at "APPS.WF_ENGINE", line 5665
ORA-06512: at line 1
regards

Hi,
Did you verify the files version and see if you need to apply the patch? If the patch is already applied, I would suggest you log a SR.
Regards,
Hussein

Java.sql.SQLException: Connection to remote site no longer valid

Hi
Somebody can help me with this ?
java.sql.SQLException: Connection to remote site no longer valid
Sometimes this error message appears in the moment when the next code execute, the database is Informix 10
public BeanOutParametersSMS siantelSMS(BeanArgumentsSMS bean)
throws SQLException, NumberFormatException,
NullPointerException, Exception {
String sql = "execute procedure SP_SMS_MKT(?,?,?,?,?,?,?,?,?)";
CallableStatement cs = null;
ResultSet rs = null;
BeanOutParametersSMS out = new BeanOutParametersSMS();
String salesForce = "";
try {
cs = connection.prepareCall(sql);
s.setString(1, bean.getAction());
cs.setString(2, "R0" + bean.getRegion());
cs.setString(3,bean.getCveclientesms());
cs.setString(4,bean.getPuerto());
cs.setString(5,bean.getCveproducto());
if (cs.execute()) {
rs = cs.getResultSet();
if (rs.next()) {
out.setActionInvoked(rs.getString(1));
out.setCode(rs.getString(2));
out.setPuerto(rs.getString(3));
out.setCveproducto(rs.getString(4)); etc ....
note. The stored procedure connecting with two databases (informix 10 & informix 9)

Where do you close the connection and statement/result set?

Java.sql.SQLException: Listener refused the connection with the following error: ORA-12514, TNS:listener does not currently know of service requested in connect descriptor

Good Day,
I'm encountering this problem
     java.sql.SQLException: Listener refused the connection with the following error:
     ORA-12514, TNS:listener does not currently know of service requested in connect descriptor
here's the java code
Class.forName("oracle.jdbc.driver.OracleDriver").newInstance();
String url = "jdbc:oracle:thin:@//10.143.85.21/UCSL";
String userName = "mssoriano";
String passWord = "mssoriano_4319";
conn = DriverManager.getConnection(url, userName, passWord);
and here's my tnsnames.ora
UCSL =
(DESCRIPTION =
    (ADDRESS_LIST =
      (ADDRESS = (PROTOCOL = TCP)(HOST = 10.143.85.21)(PORT = 1521))
    (CONNECT_DATA =
      (SID = psusldb11)
Please do let me know if what may the cause of the problem and how to solve this. Thank you and God bless.

Hi,
see this example
Connect to Oracle DB via JDBC driver
Frank

What may be the cause of this error java.sql.SQLException: invalid sql type passed to callable statement in iplanet ussing JNDI

Hi,
The possibilities can be of various reasons, with the sql statements,
xml descriptors, data sources, improper drivers anything. To crack down
the solution, kindly let me know the error messages and what exactly are
you trying to accomplish.
Thanks & Regards
Raj
manimaran t wrote:
what may be the cause of this error java.sql.SQLException: invalid sql
type passed to callable statement in iplanet ussing JNDI
Try our New Web Based Forum at http://softwareforum.sun.com
Includes Access to our Product Knowledge Base!

Java.sql.SQLException in the Buss. Comp. Proj. WIZARD...why?

hi,
I'm getting a java.sql.SQLException in the Bussiness Component Project Wizard. I made the connection using "Oracle JDBC Thin" and the connection works fine, then I click next to give the package name and when I click next again, I get the java.sql.SQLException runtime error and I don't see the user scott for which I created and tested the connection in the schema combo box of the next page in the "Buss Comp. Proj. WIZARD" wizard nor do I see any tables.
I also tried it with jdk1.3 support and it didn't work. jdk1.3 was installed succefully in jdeveloper because you can see in the about dialog box.
can someone please shed some light here. Whats weirder is that I'm following the same exampe in chapter 1 of the JDeveloper3 Handbook and thats about 40 dolloars down the drain.
My OS is Windows2000 server, I'm using JDeveloper 3.2
thanks.
ayman.

Yes, well it says something exremly scary. :)
It give the following :
java.lang.NullPointerException
     void oracle.jbo.dt.ui.pkg.PKTableOptionPanel.populateUserCombo()
     void oracle.jbo.dt.ui.pkg.PKTableOptionPanel.enter()
     void oracle.jbo.dt.ui.pkg.PKEntityPanel.enter(oracle.jbo.dt.objects.JboNamedObject)
     void oracle.jbo.dt.ui.main.dlg.DtuWizard.newPageSelected(oracle.jbo.dt.ui.main.dlg.DtuWizardPanel)
     void oracle.jbo.dt.ui.pkg.PKWizard.newPageSelected(oracle.jbo.dt.ui.main.dlg.DtuWizardPanel)
     void oracle.jbo.dt.ui.main.dlg.DtuWizard.stateChanged(javax.swing.event.ChangeEvent)
     void javax.swing.JTabbedPane.fireStateChanged()
     void javax.swing.JTabbedPane$ModelListener.stateChanged(javax.swing.event.ChangeEvent)
     void javax.swing.DefaultSingleSelectionModel.fireStateChanged()
     void javax.swing.DefaultSingleSelectionModel.setSelectedIndex(int)
     void javax.swing.JTabbedPane.setSelectedIndex(int)
     void javax.swing.plaf.basic.BasicTabbedPaneUI$MouseHandler.mousePressed(java.awt.event.MouseEvent)
     void java.awt.Component.processMouseEvent(java.awt.event.MouseEvent)
     void java.awt.Component.processEvent(java.awt.AWTEvent)
     void java.awt.Container.processEvent(java.awt.AWTEvent)
     void java.awt.Component.dispatchEventImpl(java.awt.AWTEvent)
     void java.awt.Container.dispatchEventImpl(java.awt.AWTEvent)
     void java.awt.Component.dispatchEvent(java.awt.AWTEvent)
     void java.awt.LightweightDispatcher.retargetMouseEvent(java.awt.Component, int, java.awt.event.MouseEvent)
     boolean java.awt.LightweightDispatcher.processMouseEvent(java.awt.event.MouseEvent)
     boolean java.awt.LightweightDispatcher.dispatchEvent(java.awt.AWTEvent)
     void java.awt.Container.dispatchEventImpl(java.awt.AWTEvent)
     void java.awt.Window.dispatchEventImpl(java.awt.AWTEvent)
     void java.awt.Component.dispatchEvent(java.awt.AWTEvent)
     void java.awt.EventQueue.dispatchEvent(java.awt.AWTEvent)
     boolean java.awt.EventDispatchThread.pumpOneEventForHierarchy(java.awt.Component)
     void java.awt.EventDispatchThread.pumpEventsForHierarchy(java.awt.Conditional, java.awt.Component)
     void java.awt.EventDispatchThread.pumpEvents(java.awt.Conditional)
     void java.awt.EventDispatchThread.run()

Java.sql.SQLException:The trans ... no longer active - status: 'Unknown'

Similar Messages

Maybe you are looking for