JDBC Wait timeout in WL 7.0

Hi All,
We are using the JDBC connection pool in the application and I have
coinfigured the max connections as 100. Its been observed that, when
the 101st user request for the connection, pool throws
ResourceException immediately without waiting any time. Is it possible
to coinfigure pool in WL 7.0 with wait timeout? if possible how?
Thank you all,
Santhosh.

Joseph Weinstein" <[email protected]> wrote in message
news:[email protected]..
Currently there is no way to make the pool waiting. But you can
easily fix the problem by increasing size of the connection
pool.So if he increases to 200, and his 201st user logs in and gets the same
problem?Aparently, if you can not set up a pool to satisfy all requests,
there is a problem with code/design. We can hardly fight
programming/design mistakes except may be giving good
advices.
The fundamental problem is that the design of his application is retaining
a pooled JDBC connection indefinitely, spanning multiple interactionsbetween
a given user and the server. If this is necessary the customer must either
have a pool with as many connections as he will have concurrent users,I meant exactly that.
or he should write his application to use direct non-pooled connectionswhich
he gets from the DBMS driver.Than application will get screwed up using direct driver calls.
As for me, it doesn' t make big difference. At least using
pool helped to identify the fact of the problem presence
quickly.
< Ideally, the customer can design the application
like EJBs or good servlets, that get a connection, use it, and return itto the pool,
all with a single user-server message/response.Sure.
Regards,
Slava Imeshev

Similar Messages

Finding the lock wait timeout in Oracle 11g

Want to know how to find the lock wait timeout set on Oracle 11g

Hi,
To find number of seconds a distributed transaction waits for a lock:
SELECT *
FROM v$parameter
WHERE NAME = 'distributed_lock_timeout';To find all parameter's related to lock you can use something like this:
SELECT *
FROM v$parameter
WHERE NAME like '%lock%';Thanks,
Shankar

Error 131 Transaction rolled back by lock wait timeout

Hello all,
I was trying to run apriori, and then HANA writer in my database.
Apriori executes directly, and then I configure and try to execute HANA Writer. But it keeps executing for more than half an hour, and then gives the following error: Error 131 Transaction rolled back by lock wait timeout. Lock timeout occurs while waiting TABLE_LOCK of mode EXCLUSIVE.
Bimal suggested me to reduce the data to be analysed, so then I reduced it to a pretty small part and executed again.
It gave me the same error after more than 30 minutes waiting executing.
after having this error, I tried just execute apriori, but with a filter of 5 transactions and than it worked. After that I tried to visualize the results, and got the following error:
It means that my HANA memory is full?
I got the view from HANA:
Regards!
Error 131 Transaction rolled back by lock wait timeout

Hi Jurgen,
I'm a developper for PAL from Shanghai team.
Could you please provide some details information about this case:
- How many records did you use ?
- What’s the value of “MIN_SUPPORT” and “MIN_CONFIDENCE” did you use ?
The algorithm of apriori will consume much memory when the input data is very large and min_support is low.
So I suggest you set “MIN_SUPPORT” and “MIN_CONFIDENCE” as 0.9 firstly, check if it can output result.
Thanks,
Peng

Lock wait timeout: Could not commit JPA transaction

We are using MySQL v5.1.67 under Solaris (SmartOS) in a zone. We are using Java EE and Jetty as our servlet container (Hibernate, Ehcache). Sometimes we get: "Could not commit JPA transaction; nested exception is javax.persistence.RollbackException: Error while commiting the transaction" and then "Lock wait timeout exceeded; try restarting transaction". We have the database as one file instead of one file per table. The file is large about 20 GB. There are millions of rows in many tables. One table has 30 million rows. Some table has varchar(255)s. Some others have texts. It seems like cells in the database has been broken. Because if you try to update the same entry in the DB you get a "Lock wait timeout exceeded; try restarting transaction", just by issuing a MySQL query. The problem persists until you restart the DB server. Sometimes they start appearing again after a while. Now they seem to come more and more often. There are a lot of threads in the Java EE .war application. We send more and more JMS messages. There is also PHP-code accessing the database. How do we stop this problem from occuring?

I don't think it's threads deadlocking. I've seen this problem many times before and I've always been able to fix it by restarting the MySQL-server. Then it executes normally day after day. Then something special happens and then it fails every day until I restart mysql. I've also encountered the same problem using the test database I have on my local machine. Only one job executes, the one I'm testing. First it works every run. Something special happens usually triggered by errant code. I fix the error. The job continues to fail with the same message "Could not commit JPA transaction; nested exception is javax.persistence.RollbackException: Error while commiting the transaction". If try to do a simple UPDATE SQL query accessing exactly the row that's been corrupted, I get a lock wait timeout. But if I restart the database it starts working again. The update works and the Java job works both locally and on the server. But now a special job has experienced more severe problems of this nature. I restart mysql and the job works when triggered manually but not when triggered chronologically on schedule. Actually all failed first and then a few worked but most failed. It's the same job executing multiple times.

IPCC Express-record call after waiting timeout end e-mail

I have IPCC Express 3.5.2. I have successfully created a script that enables recording a message when either a wait timeout occurs and then the user selects to leave a message. There is a maximum time limit on the recording. As long as the user stays online long enough during the recording fort he max timer to expire I can save the file and send out an e-,mail with this attached.
My question is how do detect hang-up then save the file and send the e-mail when a caller hangs up before the max time out has expired?

You need to use the On Exception GoTo and Clear Exception steps.
An Example:
Start
...logic...
On Exception (contactInactiveException) GoTo RecordingException
Recording
--Successful
----Label: Recording Exception
----Clear Exception: RecordingException
----....email/otherlogic...
End
The On Exception Goto watches for the caller hanging up. If they do, it moves the script to the label instead of going to the end. You must have the Clear Exception step to then clear the exception and move on.

Uncaught Exception: Application Registry Wait Timeout Error Messages - BB 8703e

Ok, I hope someone here can help me a bit more then US Cellular has done so far for this never ending problem.
This whole problem started after I updated my BB device software and installed face book application over the weekend. Since then my BB will not receive any data signal, however I can make phone calls still after confirming many Uncaught Exception: Application Registry Wait Timeout Error Messages. Until they start coming up again.
Here are some steps I have already tried to correct this problem
Remove Battery, then reboot
Load up Blackberry Manager to restore setting -- BB Manager doesn't even seem to see it anymore when I connect it.
US Cellular has already tried reloading the BB device software again
Has anyone ever ran into this or a similar problem like this one and figured out a solution to it?
If yes Please let me know. I don't want to end up carrying around some basic cellphone again. I am already addicted to my crackberry.
TIA
Solved!
Go to Solution.

Greetings, and welcome to the BlackBerry.com Support Forums.
What is the signal indicator you get from your device?
I am trying to recall the 8703 settings, look at Options or Tools > to Mobile Network. What are you settings there?
1. If any post helps you please click the below the post(s) that helped you.
2. Please resolve your thread by marking the post "Solution?" which solved it for you!
3. Install free BlackBerry Protect today for backups of contacts and data.
4. Guide to Unlocking your BlackBerry & Unlock Codes
Join our BBM Channels (Beta)
BlackBerry Support Forums Channel
PIN: C0001B7B4 Display/Scan Bar Code
Knowledge Base Updates
PIN: C0005A9AA Display/Scan Bar Code

OAS 10.1 3.1 0 OC4J JDBC Connection/Timeout settings

I am fairly new to OAS, and am trying to resolve a intermitent issue,
I have an OAS 10.1.3.1.0 with a deployed EAR file I was provided by a supplier containing mainly PL/SQL based logic, which configured the OAS to ask a middle tier for a an external to pass data to it via Stored Procedure and then usiing the deployed package connect to an external Oracle DB and insert the data.
Oas is running on a Windows 2003 platform that has no problems or connectivity problems, how ever intermittenlt the OAS stops uploading data to the external Oracle DB. Some custom external logging details this as a communication at the time it occurs, how ever there are no comms issues. A quick restart of the OAS windows service resolves the issue.
Apart from upgrading OAS to patch set 5, the only other thing I considered could be causing the issue is how OAS is handling the session timeout or connection pool.
I can see the following settings for the JDBC connection I am using, I wondered if anyone could advise anything that could be changed? I am not sure the implications on setting the validate connection to True and also not sure why maximum number of connections is set to -1?
Connections
Initial size of Connection Cache
Minimum Number of Connections
Maximum Number of Connections
Connection Retry Interval (seconds)
Maximum Connection Attempts
Maximum Number of Statements Cached
Lower Threshold Limit On Pool (%)
Defaults to 20% of max connections.
Validate Connection FalseTrue
Timeouts
Inactivity Timeout (seconds)
Time that an unused connection is inactive before it is removed from the pool.
Wait For Used Connection Timeout (seconds)
Maximum time to wait for a used connection to be released.
Max Active Time for a Used Connection (seconds)
Maximum time a used connection may be active.
Abandoned Connection Timeout (seconds)
Enforce Timeout Limits Interval (seconds)
Any help would be appreciated

Hi,
Along with Priya's suggestions, please refer the link below for the details on the parameters.
http://download.oracle.com/docs/cd/B32110_01/web.1013/b28958/datasrc.htm#CHDCFCHB
Hope this will help understand all the parameters.
Also refer,
What Should Be My Maximum Connection Pool Size? [ID 1061155.1]
http://www.oracle.com/technology/tech/java/sqlj_jdbc/htdocs/jdbc_faq.html
Regards,
Mithun

Synchronous JDBC - message timeout

Hi,
I have a scenario RFC-XI-JDBC synch. I am getting a message timeout error while trying to post large data volume. Apparently the sync message is geting expired after timeout (default 180 sec).
I found SAP note 730870 (question 14) suggests to increase the property xiadapter.inbound.timeout.default. However, SAP note 791379 says you should never change this value.
Is anyone has chaged this value in oreder to optimize performance ? Pls suggest.
Also pls let me know if you have any other suggestion.

As per the documentation
http://help.sap.com/saphelp_nw04s/helpdata/en/29/22ee41c334c717e10000000a155106/frameset.htm
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/bd5950ff-0701-0010-a5bc-86d45fd52283
You should increase the timeout from 180000(default) to 240000.
or 240 sec.
please visit
Re: MessageExpired because of large amount of data

Timestem and jdbc Query Timeout

hi all,
i have install timesten on one computer and configure there Query Timeout like This:
SQLQueryTimeout = 80
and i have JBoss Application Server on another computer and timesten client.
i've timesten-xa-ds.xml configuration file configured like this :
<set-tx-query-timeout>
<query-timeout>50000</query-timeout>
<set-tx-query-timeout>
and when i tryed to execute sql command i get an error:
14:19:13,342 WARN [JDBCExceptionReporter] SQL Error: 0, SQLState: S1000
14:19:13,344 ERROR [JDBCExceptionReporter] [TimesTen][TimesTen 6.0.4 CLIENT]Query Timeout must be numeric, greater than or equal to 0, and less than the Network Timeout
14:19:13,346 ERROR [STDERR] javax.persistence.PersistenceException: org.hibernate.exception.GenericJDBCException: could not execute query
14:19:13,346 ERROR [STDERR] at org.hibernate.ejb.AbstractEntityManagerImpl.throwPersistenceException(AbstractEntityManagerImpl.java:567)
14:19:13,346 ERROR [STDERR] at org.hibernate.ejb.QueryImpl.getResultList(QueryImpl.java:56)
14:19:13,347 ERROR [STDERR] at com.magti.businesslayer.ejb3Fasade.srvprov.MobileServiceFasadeBean.simChange(MobileServiceFasadeBean.java:1381)
can anybody help me ? :(

We are execute some tests and we got this mistake
java.sql.SQLException: [TimesTen][TimesTen 7.0.1.0.0 CLIENT]Query Timeout must be numeric; if the Network Timeout is non-zero, the Query Timeout must be greater than zero and less than the Network Timeout, else if the Network Timeout is zero, the Query Timeout must be greater than or equal to zero.
at com.timesten.jdbc.JdbcOdbc.createSQLException(JdbcOdbc.java:3186)
at com.timesten.jdbc.JdbcOdbc.standardError(JdbcOdbc.java:3320)
at com.timesten.jdbc.JdbcOdbc.standardError(JdbcOdbc.java:3285)
at com.timesten.jdbc.JdbcOdbc.SQLSetStmtOption(JdbcOdbc.java:2555)
at com.timesten.jdbc.JdbcOdbcStatement.setStmtOption(JdbcOdbcStatement.java:1889)
at com.timesten.jdbc.JdbcOdbcStatement.setQueryTimeout (JdbcOdbcStatement.java:714)
at org.hibernate.jdbc.AbstractBatcher.closeQueryStatement(AbstractBatcher.java:226)
at org.hibernate.jdbc.AbstractBatcher.closeQueryStatement(AbstractBatcher.java:162)
at org.hibernate.loader.Loader.doQuery(Loader.java:714)
at org.hibernate.loader.Loader.doQueryAndInitializeNonLazyCollections(Loader.java:224)
at org.hibernate.loader.Loader.loadCollection(Loader.java:1919)
at org.hibernate.loader.collection.CollectionLoader.initialize(CollectionLoader.java:71)
at org.hibernate.persister.collection.AbstractCollectionPersister.initialize(AbstractCollectionPersister.java:520)
at org.hibernate.event.def.DefaultInitializeCollectionEventListener.onInitializeCollection(DefaultInitializeCollectionEventListener.java:60)
at org.hibernate.impl.SessionImpl.initializeCollection(SessionImpl.java:1627)
at org.hibernate.collection.AbstractPersistentCollection.forceInitialization(AbstractPersistentCollection.java:454)
at org.hibernate.engine.StatefulPersistenceContext.initializeNonLazyCollections(StatefulPersistenceContext.java :827)
at org.hibernate.loader.Loader.doQueryAndInitializeNonLazyCollections(Loader.java:229)
at org.hibernate.loader.Loader.doList(Loader.java:2150)
at org.hibernate.loader.Loader.listIgnoreQueryCache (Loader.java:2029)
at org.hibernate.loader.Loader.list(Loader.java:2024)
at org.hibernate.loader.hql.QueryLoader.list(QueryLoader.java:369)
at org.hibernate.hql.ast.QueryTranslatorImpl.list(QueryTranslatorImpl.java :300)
at org.hibernate.engine.query.HQLQueryPlan.performList(HQLQueryPlan.java:146)
at org.hibernate.impl.SessionImpl.list(SessionImpl.java:1093)
at org.hibernate.impl.QueryImpl.list(QueryImpl.java:79)
at org.springframework.orm.hibernate3.HibernateTemplate$31.doInHibernate(HibernateTemplate.java:853)
at org.springframework.orm.hibernate3.HibernateTemplate.execute(HibernateTemplate.java:366)
at org.springframework.orm.hibernate3.HibernateTemplate.find (HibernateTemplate.java:844)
at org.springframework.orm.hibernate3.HibernateTemplate.find(HibernateTemplate.java:836)
at com.bursatec.bmv.selectividad.persistence.dao.impl.FedCenlacesDaoImpl.findEnlaces(FedCenlacesDaoImpl.java :119)
at com.bursatec.bmv.retransmision.middleware.service.impl.RetransmisorImpl.getEnlaces(RetransmisorImpl.java:229)
at com.bursatec.bmv.retransmision.middleware.service.impl.RetransmisorImpl.getInfoEnlace (RetransmisorImpl.java:242)
at com.bursatec.bmv.retransmision.middleware.service.impl.RetransmisorImpl.efectuarReTx(RetransmisorImpl.java:122)
at com.bursatec.bmv.retransmision.middleware.service.impl.RetransmisorImpl.atenderSolicitud (RetransmisorImpl.java:103)
at com.bursatec.bmv.retransmision.middleware.configura.SubscriptorListener.onMessage(SubscriptorListener.java:22)
at progress.message.jimpl.Session.deliver(Unknown Source)
at progress.message.jimpl.Session.run(Unknown Source)
at progress.message.jimpl.Session$SessionThread.run(Unknown Source)
I wish some one could help me
Thanks a lot.

Parameter for jdbc waiting time

I'm using wls5.1+sp10 on Solaris 8
I've configured 25 jdb connections in jdbc connection pool, but my
application will generate jdbc connection request more than that. All the
database calling are using CMP. I checked the document that we can configure
the waiting time for t3 driver. But I'm using Oracle OCI driver. Is there
any parameter I can tune to let the CMP to wait longer time to get the jdbc
connection? I found the default the value is 3 seconds which is too small
for me.
Thanks!

hi check the below link on JDBC adapter
http://help.sap.com/saphelp_nw70/helpdata/EN/96/791c42375d5033e10000000a155106/frameset.htm
https:/.../weblogs/sdn_weblogs_topics/pub/wlg/4183
recent enhancements to JDBC adapter
https:/.../weblogs/sdn_weblogs_topics/pub/wlg/1278
https:/.../weblogs/sdn_weblogs_topics/pub/wlg/4020
note:reward points if solution found helpfull.....
regards
chandrakanth.k

JDBC LDAP Timeout

While connecting to our LDAP source using packaged LDAP JDBC driver we receive a timeout error:
7000 : null : com.sunopsis.sql.k: Oracle Data Integrator TimeOut
Re-executing the job helps in most cases, but sometimes timeout problem persists. Any ideas on how can we increase the connection timeout ?
We are still on ODI 10.1.3.2.0
Connection details:
JDBC Driver: com.sunopsis.ldap.jdbc.driver.SnpsLdapDriver
JDBC URL: jdbc:snps:ldap?ldap_url=ldap://server:389/&ldap_password=ENCODEDPASSWORD&ldap_basedn=OU=one,OU=two,OU=three,OU=four,OU=five,DC=SIX,DC=COM&ab=\\fileserver\alias_ldap.txt

Go to odi studio menu-->odi--->user parameters
There you can find to increase the time out time
Oracle Data Integrator Timeout 1000 Timeout used by Oracle Data Integrator for the database connections.

AEX JDBC Synchronous Timeout

Hi everyone!
I have a synchronous scenario Proxy->JDBC On PI 7.4 Java Only.
I have imported this scenario from another server dual stack, there it works.
I following this thread
SOAP Receiver adapter on 7.4 AEX exeeds synchronous timeout
, but it´s not answered.
do i forgot something?

Hi guys,
I found a solution.
Applying the SAPnote 0001493502.
Our problem was the paralelism, this wasn´t set.

JDBC / JTA Timeouts : How to set a timeout on the fetching of a query ?

Hi !
I'm working on an Application running on Weblogic Server 11g. This app executes a query on an Oracle 11g database ...
The problem is that this query returns millions of records ... and the app fetches the results during tens of minutes.
We would like to set a timeout, wich will abandon the transaction, hang the database connection, destroy the socket ... or anything else ...
This timeout will prevent the thread to become in STUCK state and stucking the weblogic managed server.
Is this possible ?
Thank's for your answers.
Steve.
Edited by: 966918 on 10 avr. 2013 07:18

Abandon timeout will not help. That is only used if a database crashes during the second phase of commit. It specifies how long the transaction manager should keep trying to complete the transaction.
JTA timeout will only work if you are using XA datasources and two-phase commit transactions. When the timeout occurs, it guarantees that the transaction cannot be committed. Eventually, all of the participant resources will be notified and will not allow any more work to take place on the transaction. It does not stop the threads and the application must be written to handle exceptions appropriately.
Edited by: Steve Felts on Apr 17, 2013 8:32 AM

JDBC Tx timeout

Nedd help!
We are runing Weblogic6.1 with Oracle 8.
During our Tx transaction processes, flollowing SQL Error happens:
"[java.sql.SQLException: Transaction 14:7aaa0978f11df335 not active anymore. tx
status = Marked rollback. [Reason=weblogic.transaction.internal.TimedOutException:
Transaction timed out after 31 seconds
Name=[EJB com.processingnew.NewProcessBean.(java.util.Vector,com.eduction.pay.PayCalendar,long,boolean)],Xid=14:7aaa0978f11df335(5400402),Status=Active,numRepliesOwedMe=0,numRepliesOwedOthers=0,seconds
since begin=31,seconds left=30,ServerResourceInfo[weblogic.jdbc.jts.Connection]=(state=started,assigned=none),SCInfo[eductionprod+biz01]=(state=active),properties=({weblogic.transaction.name=[EJB
com.processingnew.NewProcessBean.process(java.util.Vector,com.eduction.pay.PayCalendar,long,boolean)],
weblogic.jdbc=t3://122.122.23.23:9001}),OwnerTransactionManager=ServerTM[ServerCoordinatorDescriptor=(CoordinatorURL=biz01+122.122.23.23:9001+eductionprod+,
Resources={})],CoordinatorURL=biz01+122.122.23.23:9001+eductionprod+)]]
But we know whole process runs much less than 30 seconds, only about 5 seconds,
it must be some bug errors.

Hi Jining,
Transaction timemout is calculated since the transaction
started. Is it possible that method NewProcessBean.process
is called within another transaction?
Regards,
Slava Imeshev
"Jining Qi" <[email protected]> wrote in message
news:3da72c75$[email protected]..
>
Nedd help!
We are runing Weblogic6.1 with Oracle 8.
During our Tx transaction processes, flollowing SQL Error happens:
"[java.sql.SQLException: Transaction 14:7aaa0978f11df335 not active
anymore. tx> status = Marked rollback.[Reason=weblogic.transaction.internal.TimedOutException:> Transaction timed out after 31 seconds> Name=[EJBcom.processingnew.NewProcessBean.(java.util.Vector,com.eduction.pay.PayCalendar,long,boolean),Xid=14:7aaa0978f11df335(5400402),Status=Active,numRepliesOwedMe=0,numRepliesOwedOthers=0,seconds
since begin=31,secondsleft=30,ServerResourceInfo[weblogic.jdbc.jts.Connection]=(state=started,assi
gned=none),SCInfo[eductionprod+biz01]=(state=active),properties=({weblogic.t
ransaction.name=[EJB
>
com.processingnew.NewProcessBean.process(java.util.Vector,com.eduction.pay.P
ayCalendar,long,boolean)],
>
weblogic.jdbc=t3://122.122.23.23:9001}),OwnerTransactionManager=ServerTM[Ser
verCoordinatorDescriptor=(CoordinatorURL=biz01+122.122.23.23:9001+eductionpr
od+,
Resources={})],CoordinatorURL=biz01+122.122.23.23:9001+eductionprod+)]]
But we know whole process runs much less than 30 seconds, only about 5seconds,
it must be some bug errors.

SQL message: transaction rolled back by lock wait timeout; SQL 131

Hi,
There is a table which already has about 77 lakh records. The modify on it gives the following error.
SQL error "SQL code: 131" occurred while accessing table "/PSMP/D_UACTID".
(runtime error DBSQL_SQL_ERROR)
(SQL statement:MODIFY /psmp/d_uactid FROM TABLE lt_uactid.)
Did anyone face this kind of an issue. If yes, kindly share the learning.
Thanks and Regards,
Madhura Lobo

Hi,
I have already given the modify query in the initial post above. Here is the table structure.
MANDT                     CLNT 3
CUST_ID                  CHAR 10
SYS_NUM                CHAR 18
CNTXT_ID                INT4 10
SAR_ID                     CHAR 30
UYEAR                      CHAR 4
UQUAR                      CHAR 1
CUST_NAME             CHAR 35
SYS_ID                      CHAR 3
SYS_NAME               CHAR 40
SAR_NAME               SSTRING 255
TOTAL_NR                INT4 10
USED_NR                  INT4 10
Once again the SQL statement: MODIFY /psmp/d_uactid FROM TABLE lt_uactid.
Regards,
Madhura Lobo

JDBC Wait timeout in WL 7.0

Similar Messages

Maybe you are looking for