JDBC Maximum Waiting Time

What is maximum waiting time parameter in jdbc connecton?
Is it like when a client accesses the database if there is not connection available the client waits the certain period of time until someone releases the resource?

Hi Skip Ford,
Follow these links
http://www.java2s.com/Code/Java/Database-SQL-JDBC/GetdatefromOracle.htm
http://ramblingabout.wordpress.com/2007/01/26/remember-date-time-timestamp/
http://www.oracle.com/technology/tech/java/sqlj_jdbc/htdocs/jdbc_faq.htm
Regards,
Santosh.

Similar Messages

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

Java.sql.SQLException: No available resource. Wait-time expired.

Hi all,
The application platform is SunONE Application Server 7, and the database is ORACLE 9i. My Website application will raise the SQLException once a few days' running. Everything will be ok once the Application server has been restarted. The detail about the Exception is :
[12/Aug/2003:10:41:03] WARNING (25931): CORE3283: stderr: java.sql.SQLException: No available resource. Wait-time expired.
[12/Aug/2003:10:41:03] WARNING (25931): CORE3283: stderr:      at com.sun.enterprise.resource.JdbcDataSource.internalGetConnection(JdbcDataSource.java:251)
[12/Aug/2003:10:41:03] WARNING (25931): CORE3283: stderr:      at com.sun.enterprise.resource.JdbcDataSource.getConnection(JdbcDataSource.java:98)
[12/Aug/2003:10:41:03] WARNING (25931): CORE3283: stderr:      at com.tsp.gdgpo.ejbm.util.EnvUtil.getDSConnection(EnvUtil.java:72)
[12/Aug/2003:10:41:03] WARNING (25931): CORE3283: stderr:      at com.tsp.gdgpo.ejbm.util.DirectDSUtil.getObjectsFromDS(DirectDSUtil.java:103)
[12/Aug/2003:10:41:03] WARNING (25931): CORE3283: stderr:      at com.tsp.gdgpo.ejbm.jcsms.dam.JcsmsDDSA.getSpecialistByPage(JcsmsDDSA.java:388)
[12/Aug/2003:10:41:03] WARNING (25931): CORE3283: stderr:      at com.tsp.gdgpo.ejbm.jcsms.sessionbeans.SpecialManagerEJBBean.listSpecialist(SpecialManagerEJBBean.java:1941)
[12/Aug/2003:10:41:03] WARNING (25931): CORE3283: stderr:      at com.tsp.gdgpo.ejbm.jcsms.sessionbeans.SpecialManagerEJBBean_EJBObjectImpl.listSpecialist(SpecialManagerEJBBean_EJBObjectImpl.java:702)
[12/Aug/2003:10:41:03] WARNING (25931): CORE3283: stderr:      at com.tsp.gdgpo.ejbm.jcsms.sessionbeans._SpecialManagerEJBBean_EJBObjectImpl_Tie._invoke(Unknown Source)thanks for any help
Niu

Ther is a related Bug i n Oracle: Bug No. 4420032
PROBLEM STATEMENT: ------------------
The Oracle client file ojdbc_14.jar is not handling exceptions correctly. The connection pool slowly runs out of connections and hits the oracle db limit of max_sessions. Increasing the db max_sessions does not help as the number of sessions continue to increase.
The vendor developers of ct's application have identified a code problem with the Oracle client file ojdbc_14.jar. Their description follows.
The following is a technical description of the Oracle JDBC client library issue. The jar file in question is: ojdbc_14.jar. This issue is also present in the 9.2.05 and 9.2.06 versions of the client code.
The socket.close() call in TcpNTAdapter.disconnect() does not properly handle network exceptions. Where the exception should be handled within the code segment calling socket.close(), the class instead throws an exception without ensuring the socket is closed. The socket is not subsequently closed by clients of the class. This ultimately results in a connection leak. Overtime, the maximum number of Oracle database sessions is reached. The only work around for this issue in production, is to restart the effected processes.
The code segment:
public void disconnect()
throws IOException {
socket.close();
socket = null; }
should be along the lines of:
public void disconnect()
throws IOException {
try{ socket.close(); }
catch(IOException ioe){ throw ioe; }
finally{ socket = null; } }
The original code segment will not execute the statement "socket = null" when . an exception occurs. Given the fact that the exception is not subsequently processed properly, the object is never dereferenced, and the socket remains open for the life of the process. Adding this statement in the finally block . ensures the object will ultimately be destroyed by the garbage collector. . ct tested this change in their lab and found that the recommended modification successfully resolved the issue.
This problem has occurred with the previous ct's application releases, but the vendor has only recently been able to isolate the root cause. The JDBC connection pool slowly runs out of connections and hits the oracle db limit of max_sessions.
Increasing the db max_sessions does not help as the number of sessions continue to increase. This problem has been occuring in Production over the past few releases of the application, but usually the connections leak slowly. This problem can be duplicated under heavy load in just a few minutes . in the Loadtest environment.

Maximum Wait for WS Consumer: SOAMANAGER Logical port

Hello Everyone,
I was trying to configure consumer proxy through SOAMANAGER transaction. When you create a Logical port, within Transport setting you can see a Parameter called 'Maximum Wait for WS Consumer' which as per my understanding is the time for which the consumer is required to wait for a response from Provider.
The problem here is i cannot edit that value. The field is disabled with its default value as '0'(wait for infinite amount of time). I want to make that wait period as just 10 secs.
Am i heading in the right direction? If yes, then how can i edit that value?
Regards
Shailesh

Hello Shailesh
You should be able to modify this parameter. See the link:
Configuring a Consumer Proxy
http://help.sap.com/saphelp_nwpi71/helpdata/EN/9e/c7a3591dc74a679bbc9716354e42af/content.htm
Are you able to modify any of the other parameters? Does your user have the required authorizations?
Regards
Mark

Error : No available resource. Wait-time expired.

Hi,
We have a big problem of connection pooling in SunOne.
After out program execute a lot of sql command in a short time, SunOne 7.0 throws an Exception ---- No available resource. Wait-time expired. We modify the connection pool setting, but it doesn't work. Can someone help to solve problem.
Our connectiong pool setting as below :
<jdbc-connection-pool steady-pool-size="8" max-pool-size="32" max-wait-time-in-millis="60000" pool-resize-quantity="2" idle-timeout-in-seconds="300" is-isolation-level-guaranteed="false" is-connection-validation-required="true" connection-validation-method="auto-commit" fail-all-connections="false" datasource-classname="oracle.jdbc.pool.OracleDataSource" name="xxx">
<property value="jdbc:oracle:thin:@aa:1521:aa" name="URL"/>
<property value="xxx" name="user"/>
<property value="xxx" name="password"/>
</jdbc-connection-pool>
Thanks!
Elsa

This issue is not resolved. I got this message this afternoon. It has nothing to do with ejb. Just for confirming this issue again, I created a very simple application, a jsp that calls a servlet. In the servlet, I have a loop that calls a getNewConnection(). and returns the connection, then I create a Statement with that connection. Then I call another method releaseResources(Statement stmt)
Connection conn = stmt.getConnection();
if(conn != null)
System.out.println("connection: " + conn);
conn.close();
// conn = null; tried this one also, same result
The code is OK. including try/catch blocks ans so on.
If the number of loops greater than the connection pool size, then I get the same exception. It means the connections are not getting closed. But if I change the methode and pass Connection instead of Statement, then it workes fine.
I have tested this in App server7 with:
Oracle 9.2.0 client and ojdbc14.jar
Oracle 9.2.0 client and classes12.jar
Oracle 9.0.1 client and classes12.jar
Oracle 8.1.6 client and classes12.zip
all with thin or oci drivers.
It looks like something to do with Statement.getConnection() and the version of AppServer jdk (1.4.0.2).
I know the getConnection methode does return A connection. I can print the connection id.

Forms property 'Maximum Query Time'

Running Forms 6.0
I would like to use the forms property
'Maximum Query Time'
It doesn't seem to work.
Do I have to make some kind of setup on the server?
What unit is 'Maximum Query Time' - seconds?
- Flemming
null

Hello pradeepantony,
According to the help file, that property is:
Provides the option to abort a query when the elapsed time of the query (in seconds) exceeds the value of this property.
How you would use it would be if you did not want your user to sit and wait a significant amount of time while a query executes. Some processes can take a fair amount of time on a busy database. Setting this property will assure your user will not wait any longer than the number of seconds you set in this property.
I have a couple of stored procedures that take "many minutes" to execute. If a user had issued a query against a table that one of my stored procedures had locked and I had set this parameter, the screen would abort the query and not wait for my stored procedure to complete. Otherwise, the user would have to wait until the database freed up the table before completing the query.
Hope this helps,
Don.
You can reward this reply by marking it as either Helpful or Correct :)

Database Error: RSR0009: Resource not available for pool. Wait-time expired

i am occassionally receiving the following error during database connections in my servlet:
Database Error: RSR0009: Resource not available for pool [webAdvisorTestPool]. Wait-time expired
i understand that this is a result of a connection leak from improper closure of my Connection object, but i thought that i was properly closing my connection.
i can get the error if i do the following steps:
1) access my login page and enter login credentials.
2) submit the login which then hits the Authentication servlet.
3) Authentication servlet authenticates and takes me to home page.
4) hit the back button to get back to the login page.
5) repeat this process until i hit the Max Pool Size (from web server).
6) then i get the error message
here are some details:
i have an Authentication servlet; here is the pertinent code from that servlet:
try {     // retrieve the user and add the User object to the session     DAO dao = new DAO();     Person authenticUser = dao.getPerson(userID, password);     session.setAttribute("validUser", authenticUser);     redirectPage = mapping.findForward("success"); }
i also have a DAO object that handles all of my DB transactions (and you can see from my code above that the Authentication servlet is using that object); here is the pertinant code from that servlet:
public DAO() {     datasource = "java:comp/env/jdbc/webAdvisorTest"; } public Person getPerson(String userID, String password)     throws ObjectNotFoundException {     // JDBC variables     DataSource ds = null;     Connection conn = null;     PreparedStatement stmt = null;     ResultSet results = null;     // User variables     Person validUser = null;     try     {         // Retrieve the DataSource from JNDI         InitialContext ctx = new InitialContext();         // if this statement fails, NamingException is thrown         ds = (DataSource)ctx.lookup(datasource);         // get DB connection and perform SQL operations         conn = ds.getConnection();         // User variables         String validUserID = null;         String validFName = null;         String validLName = null;         String validEmail = null;         // get DB connection and perform SQL operations         conn = ds.getConnection();         stmt = conn.prepareStatement(PERSON_QUERY);         stmt.setString(1, userID);         stmt.setString(2, password);         results = stmt.executeQuery();         // iterate through the results         if (results.next())         {             validUserID = results.getString("id");             validFName = results.getString("first_name");             validLName = results.getString("last_name");             validUser = new Person(validUserID, validFName, validLName);         }     }     // handle SQL errors     catch(SQLException e)     {         e.printStackTrace(System.err);         throw new RuntimeException("Database Error: " + e.getMessage());     }     // handle JNDI errors     catch(NamingException e)     {         throw new RuntimeException("JNDI Error: " + e.getMessage());     }     // clean up resources     finally     {         doClosure(results, stmt, conn);     }     // if the user was not found, throw ObjectNotFoundException     if(validUser == null)     {         throw new ObjectNotFoundException();     }     return validUser; } protected void doClosure(ResultSet results, PreparedStatement stmt,     Connection conn) {     if (results != null)     {         try { results.close(); }         catch (SQLException e) { e.printStackTrace(System.err); }     }     if (stmt != null)     {         try { stmt.close(); }         catch (SQLException e) { e.printStackTrace(System.err); }     }     if (conn != null)     {         try         {             System.out.println("R18Resources.conn before close: " + conn);             conn.close();             System.out.println("R18Resources.conn after close: " + conn);             System.out.println("R18Resources.conn is closed? " +                 conn.isClosed());         }         catch (SQLException e)         {             System.out.println("R18Resource conn close error: " +                 e.getMessage());         }     } }
as you can see, i've added some print statements in my connection closure block. based on my output log, each connection is being properly closed and i am not encountering any errors during that closing block.
any ideas???
Message was edited by:
millerand

Please try the following code in your doClosure method. Replace your code with the following code.
public void doClosure(ResultSet pResultSet, Statement pStmt, Connection pConn) throws Exception {
try {
               if (pResultSet != null) {
                    pResultSet.close();
                    pResultSet = null;
          } catch (SQLException se) {
          logger.error( se );
          } finally {
               try {
                    if (pStmt != null) {
                         pStmt.close();
                         pStmt = null;
               } catch (SQLException se) {
               logger.error(se);
               } finally {
                    try {
                         if (pConn != null) {
                              pConn.close();
                              pConn = null;
                    } catch (SQLException se) {
                    logger.error(se);
And let me know if you still face this issue. What is the application server you are using?

What is normal range for CPU Wait time Per Dispatch on Hyper-V 2012

Hello.
I am trying to troubleshoot some performance issues with an application that utilizes sql server, which runs in a Hyper-V Guest.
I have found that the ram, cpu, disk i/o all appear to be within normal range.
Before troubleshooting the sql end of things, I wanted to make make sure the vm isn't waiting for cpu time.
In Vmware, the metric for this is " CPU Ready". From what I can tell, the equivilant to this for Hyper-V on server 2012 is:
Hyper-V Hypervisor Virtual processor\CPU Wait time per dispatch.
I have fired this up and been monitoring it and found that the average is around 22,000, maximum 41,000.
The problem is, I have no idea if this is a normal or acceptable range. I can't seem to find any further information on actually interpreting this data, as to what is acceptable and what will cause performance issues etc..
Can anyone help enlighten me further on this?
Thanks

Hello.
I am trying to troubleshoot some performance issues with an application that utilizes sql server, which runs in a Hyper-V Guest.
I have found that the ram, cpu, disk i/o all appear to be within normal range.
Before troubleshooting the sql end of things, I wanted to make make sure the vm isn't waiting for cpu time.
In Vmware, the metric for this is " CPU Ready". From what I can tell, the equivilant to this for Hyper-V on server 2012 is:
Hyper-V Hypervisor Virtual processor\CPU Wait time per dispatch.
I have fired this up and been monitoring it and found that the average is around 22,000, maximum 41,000.
The problem is, I have no idea if this is a normal or acceptable range. I can't seem to find any further information on actually interpreting this data, as to what is acceptable and what will cause performance issues etc..
Can anyone help enlighten me further on this?
Thanks
Hi,
Hyper-V reports this metric is in nano seconds. So, your average is around 22-41 ms (milliseconds). This is GOOD.
Take this example:
This would be comparable to vCenter VM CPU Ready graph which displays VM CPU Ready time in milliseconds.
Note #1: This measures each virtual core presented to an individual VM. This will be different if you're not using hyper-threading on the host
Note #2: This is scaled to a factor of 0.001, so that the scale on the left is in milliseconds - which is commonly confused with a percentage scale, which is is NOT.
Not to dismiss CPU issues, but generally the first place I look when troubleshooting SQL on a VM is storage access/speed/performance, regardless of what hypervisor is being used. I would verify best practices like putting databases on separate physical
storage that ends up on separate spindles on the storage back end, same for logs, same for temp db, same for temp log,...
Sam Boutros, Senior Consultant, Software Logic, KOP, PA http://superwidgets.wordpress.com (Please take a moment to Vote as Helpful and/or Mark as Answer, where applicable)

Maximum think time is 10 seconds?

I noticed that both in OpenScript and Oracle Load Testing, think (130.0) will result in 10 seconds waiting. I need a think time of 130 seconds to mimic real user behaviour. As 10 seconds a maximum, or is this a bug? Of course I can add multiple think (10.0) to my script but I do not see the need of a maximum here.

It sounds like you've got the setting in OpenScript for maximum think time set to 10s. The scripts will run in OLT with the 'true' think times.
Check here:
View/OpenScript Preferences/Playback
You should then see VU Pacing (Think Time) and there are minimum and maximum values that can also be applied.

The wait time and resolve time is DEPLORABLE

Today is the third day in a row I have called into Verizon for the same issue. Day one spent 25 minutes on hold and NEVER got to speak to a person before I hung up. Day 2 Had a 15 minute hold before I spoke with someone, who then told me I had to speak to directv about something that was related to the Verizon part of my service, called directv confirmed it was a Verizon thing with a supervisor. Called BACK into Verizon waited for 30 minutes before I spoke with someone, got 30 seconds worth of talk in before another 15 minute hold, he came back on no apology not anything about the absolute rudeness and lack of courtesy. He told me they would have it fixed by the end of the day. Now here it is the nest day still not resolved, So I write this (while on hold waiting to have the call answered, its been 20 minutes) She finally did answer and was down right rude and through me right back on hold. I am so fed up with big business...

topdog wrote:
It may be your location. Here in Baltimore, there is little wait time and the representitives I get do not speak with accents.
Agree. I rarely wait more than a minute or two. And except at really off hours don't hear a foreign accent. NY area.

Good day. as I can do to update my iphone 4 to the latest version of ios 5. whenever you connect to the pc and try to update the waiting time is very long, sometimes up to 12 hours and despite the wait always produce an error message for a long time waiti

good day. as I can do to update my iphone 4 to the latest version of ios 5. whenever you connect to the pc and try to update the waiting time is very long, sometimes up to 12 hours and despite the wait always produce an error message for a long time waiting

Disable ALL security software (firewall, antivirus/spyware, etc.) running on your PC while updating.

How to keep waiting time between processed messages !!

Hi Folks,
I have got one scenario required waiting time between processed messages. The problem as follows !!
File --> Proxy scenario. I receive 15 messages from sender side (same messages structure) so working with one interfaces. File picking and transforming this message and split into 2 messages. messages are receiving to receiver. I am using BPM with 7,8 steps like receiving step, block , message transformation step , internal block 1 for sender 1, internal block 2 for sender 2.
All things are working fine, messages are going to receiver properly. But customer requirement is , wait step required between processed messages before sender1. I have put wait step still, PI picks all messages in one shot processing and waiting for 2 minutes, after 2 minutes sending all messages at the same time, this process is not working.
I have tried with wait step in mapping (Sarvesh) given excellent idea, still PI works the same way.
Can someone please explain a bit why the messages or not waiting message by message. I am using EOIO with Queue name and file process mode "BY NAME" and I have tried "BY TIME" as well. I have given priority to this Queue. On BPM Queue assignment : One Queue.
Please I am expecting positive answer !!
Many Thanks in Advance
San

Hi Rudolf Yaskorski ,
Not sure about your PI release and BPM model, do you create separate process instance for each file, or do you process files collecting them in one single instance? Are you using parallelization within your ccBPM ?
I am using serialization, I don't think bpm can do Parallization until PI 7.0, but PI 7.11 has got has queue assignment. But I am using one queue. This must be serialization.
To me it looks like your issue is not in ccBPM but rather more in polling files (as per your post file CC polls all 15 files in one shot). So if you wish to poll the files not at the same time some workaround is required. Possible options you could check out:
A. Either implement "wait" in your mapping based on file name or other criteria (e.g. directory name). Check out if respective BPM instances are really created at different times.
I have used wait step in mapping. These 15 messages has to go through one interface. So I am using one interface. But I have checked mapping process time in all messages on receiver system. Shows same timing, even though I put 40000 ms waiting time in mapping.
B. Try polling different files (or use different directories) with different channels and coordinate starting / stopping of your channels by scheduling availability for each CC in RWB. E.g. you poll file 1 with CC 1. You start 2 minutes later CC 2 and poll file 2. And so on.
I am not clear about this . On BPM waiting step is working and it keeps wait all messages, which are coming through one interface. Then it releases all messages at the same time.
I don't know how to resolve this. I have tried with Transport acknowledgment, but all messages are going to reciver system waiting at receiver system in priority queue and processing in EOIO, but taking so long. Rather all messages go and sits in queue, I want to stop messages by message with 2 minutes time gap. How please?
Kind Regards
San

Waiting time between entry posting in R/3 and avail. in BW

Dear SAP community,
We have set up a process chain which gives us the freedom to load GL account into BW on an ad-hoc basis.
Unfortunately it is not really ad-hoc after we have posted an entry in GL account in R/3 we need to wait approximately 1 hour before we run process chain in order to see posted entry. If we run process chain immediatly after posting entry we woul not see the entry in BW.
Does anyone knows if there is a waiting time from when we post an entry into SAP R3 to when we can run the process chain and see the posting in BW?
Thanks a lot for you help.
Stefanie

Hi Stefanie,
What is the Datasource being used?
For old GL extractors, like 0FI_GL_4, there is a safety interval upper limit of 1 day, meaning data posted till yesterday will be extracted if the chains run today. There are workarouds given by SAP to extract most recent data for these.
For new GL extractors like 0FI_GL_10, there is a safety interval lower limit of 1 hour, meaning the most current data would be extracted and there would be an overlap of 1 hour between delta loads and some records are extracted twice.

Wait Time / Timeout Time in waiting events

Hi,
From manual, I came to know that some of waiting events having wait time or time out duration. I have not understood, what happens if it has reached timeout. What happens next ? ( Will you explain in more detail ). It saysl it will renew wait event. ( I have not understood what does mean "RENEW", Or what steps will be taken by Oracle, what happens if again reached timeout ) ?
Thanks for clearing my doubt in detail.
regards
pjp

Please read the FAQ and learn how to enclose your listings in tags so we can read them.
I can't help you at this time because I can not read what you posted.

How to increase the waiting time for response in Adapter Engine not in IE

Hi Experts,
It is a SOAP to Proxy Synchronous interface. SOAP system is sending the request to PI, PI sending the same request to ECC system, After execution of some logic response back to PI in 7 minutes. In ABAP Stack(sxmb_moni) processing the response message also successfully with success flag after completion of these 7 minutes. But exactly 5 minutes later getting the error at Java Stack RWB- in communication channel monitoring i.e
com.sap.engine.interfaces.messaging.api.exception.MessagingException: com.sap.engine.interfaces.messaging.api.exception.MessageExpiredException: Message bd2bf8d0-b2c2-11e0-c383-001cc4fb5cb7(OUTBOUND) expired. We have set the "runtime-HTTP_TIMEOUT" parameter as 3600. thats why in Integration engine it is processing successfully.
kindly suggest me how to increase the waiting time for response in Adapter Engine. Exactly after 5 mins getting the above error in rwb, but in Integration Engine getting successful flag after 7 mins until then it is waiting for response with status flag Log version.
Thanks & Regards,
Srihari.

Hi,
Please see
How To... Investigate Timeouts In Synchronous XI/PI Scenarios
It will answer all your queries
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/c059d583-a551-2c10-e095-eb5d95e03747?QuickLink=index&overridelayout=true

JDBC Maximum Waiting Time

Similar Messages

Maybe you are looking for