Wait/Time ratio 100%

Hi,
We are doing some performance tests of a web-service.
After a few hours into the test (with moderate/low load), the database metric Wait/Time ratio suddenly goes up to 100%.
What does this mean? That the databse is now spending all its time on I/O, or that it's not doing anything?
Before the 100% spike, the Wait/Time ratio is about 50%, but I have read that as close to 0% as possible (and high CPU/Time ratio) is good performance?
Regards,
Axel

Hi,
Please always write your code/outputs in tag for readability. For listener error, see bellow post which may help you
http://www.shutdownabort.com/errors/ORA-12520.php
enq: TX - row lock contention 20,514 60,011 2925 98.6 ApplicatioFirst of all tune your application for locks contention which you can only solve at your application side.
db file parallel write 23,810 322 14 0.5 System I/O
og file sync 11,713 295 25 0.5 Commit
og file parallel write 18,673 267 14 0.4 System I/O
Your application is doing excessive COMMITS which is causing these IO wait events. Again you need to tune your application side and COMMIT as less as you can because each commit needs a write to the disk which is causing SYSTEM I/O wait events
See following
http://salmandba.blogspot.com/2011/03/dont-commit-too-often.html
Salman

Similar Messages

Database CPU Time Ratio" 100

Hi,
I am useing the following query which gives output of "Database CPU Time Ratio" > 100. But how it could be greater that 100? It's looks odd. Could you please explain?...
select to_char(end_time, 'dd-mon-yyyy hh24:mi:ss')end_time,
value
from sys.v_$sysmetric_history
where metric_name = 'Database CPU Time Ratio'
and value>100
order by 1;
END_TIME VALUE
01-nov-2012 10:34:33 111.662276737285
1 rows selected

I'm referring to metric_id: 2108
select metric_name from v$metricname
where metric_id = 2108
and group_name = 'System Metrics Long Duration'
METRIC_NAME
Database CPU Time Ratio
select to_char(begin_time, 'dd-hh24') || ':00' as hour,
round(avg(maxval)) as maxval,
round(avg(average)) as average
from dba_hist_sysmetric_summary
where metric_id = 2108
and begin_time >= sysdate - 1
group by to_char(begin_time, 'dd-hh24') || ':00'
order by 1
HOUR     MAXVAL     AVERAGE
14-21:00     2247     156
14-22:00     118     54
14-23:00     214     112
15-00:00     206     83
15-01:00     196     97
15-02:00     201     100
15-03:00     207     88
15-04:00     195     92
15-05:00     200     59
15-06:00     66     14
15-07:00     168     75
15-08:00     186     87
15-09:00     196     102
15-10:00     184     98
15-11:00     200     114
15-12:00     195     103
15-13:00     188     100
15-15:00     201     101
15-16:00     196     105
15-17:00     213     89
15-18:00     197     107
15-19:00     295     126
what the value 2247 on 14 dec at 21:00 means ??

Metrics "Database Time Spent Waiting (%) is ar 100 for event class "Applica

Metrics "Database Time Spent Waiting (%) is ar 100 for event class "Application".
i get this error in database. help me regarding this error.

Streams AQ: qmn coordinator idle wait     31     16     42598     1374.12     425976281     989870553     2723168908     6     Idle
Streams AQ: qmn slave idle wait     15     0     41599     2773.27     415990747     1830121438     2723168908     6     Idle
Streams AQ: waiting for messages in the queue     83     83     41478     499.73     414776290     3955192389     2723168908     6     Idle
jobq slave wait     134     131     39906     297.8     399055017     782339817     2723168908     6     Idle
Streams AQ: waiting for time management or cleanup tasks     7     4     3778     539.71     37779540     3702640206     2723168908     6     Idle
class slave wait     3     3     1499     499.54     14986144     1055154682     2723168908     6     Idle
Streams AQ: qmn coordinator waiting for slave to start     2     1     500     249.95     4999066     1565566389     1893977003     0     Other
LGWR wait for redo copy     1     0     0     0     1     4266849434     1893977003     0     Other

IO Exception: Lock timeout exceeded for documents , wait time = 60014

Hi,
We are getting an error while uploading any document on portal in KM content area. The full error details as follows
#D27E2001B003002500000D210005D0D20004520E6FF2B6FB#1216121868039#com.sapportals.wcm.repository.service.accessstatistic.AccessStatisticManager#sap.com/irj#com.sapportals.wcm.repository.service.accessstatistic.AccessStatisticManager#BMERRON#71986##<host name>_7664450#BMERRON#3f730c80526211ddb0fcd27e2001b003#SAPEngine_Application_Thread[impl:3]_4##0#0#Error##Plain###error while handling event - com.sapportals.wcm.WcmException: IO Exception: Lock timeout exceeded for <documents>, wait time = 60006
     at com.sapportals.wcm.repository.service.appproperties.PropertiesService.setProperty(PropertiesService.java:984)
     at com.sapportals.wcm.repository.service.appproperties.PropertiesService.setProperty(PropertiesService.java:1203)
     at com.sapportals.wcm.repository.service.appproperties.PropertiesManager.setProperty(PropertiesManager.java:176)
     at com.sapportals.wcm.repository.service.accessstatistic.AccessStatisticManager.updateLastReadDate(AccessStatisticManager.java:177)
     at com.sapportals.wcm.repository.service.accessstatistic.AccessStatisticManager.received(AccessStatisticManager.java:253)
     at com.sapportals.wcm.util.events.ReceiverEntry.doSend(ReceiverEntry.java:223)
     at com.sapportals.wcm.util.events.EventBroker.send(EventBroker.java:86)
     at com.sapportals.wcm.util.events.TransactionalEventBroker.send(TransactionalEventBroker.java:56)
     at com.sapportals.wcm.repository.manager.ResourceEventBroker.send(ResourceEventBroker.java:219)
     at com.sapportals.wcm.repository.manager.AbstractRepositoryManager.sendEvent(AbstractRepositoryManager.java:322)
     at com.sapportals.wcm.repository.RMAdapter.sendEvent(RMAdapter.java:342)
     at com.sapportals.wcm.repository.ResourceImpl.sendEvent(ResourceImpl.java:4206)
     at com.sapportals.wcm.repository.ContentImpl.getInputStream(ContentImpl.java:119)
     at com.sapportals.wcm.repository.ContentImpl.getInputStream(ContentImpl.java:132)
     at com.sapportals.wcm.service.xmlforms.transformation.ResourceDemultiplexer.getContentStream(ResourceDemultiplexer.java:71)
     at com.sapportals.wcm.service.xmlforms.transformation.Transformation.render(Transformation.java:209)
     at com.sapportals.wcm.app.xmlforms.PreviewServlet.sendForm(PreviewServlet.java:165)
     at com.sapportals.wcm.app.xmlforms.PreviewServlet.doGetAction(PreviewServlet.java:130)
     at com.sapportals.wcm.app.xmlforms.XFBaseServlet.doGet(XFBaseServlet.java:241)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
     at com.sapportals.wcm.app.xmlforms.XFBaseServlet.service(XFBaseServlet.java:134)
     at com.sapportals.wcm.portal.proxy.PCProxyServlet.service(PCProxyServlet.java:333)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
     at com.sapportals.portal.prt.core.broker.ServletComponentItem$ServletWrapperComponent.doContent(ServletComponentItem.java:110)
     at com.sapportals.portal.prt.component.AbstractPortalComponent.serviceDeprecated(AbstractPortalComponent.java:209)
     at com.sapportals.portal.prt.component.AbstractPortalComponent.service(AbstractPortalComponent.java:114)
     at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:328)
     at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:136)
     at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:189)
     at com.sapportals.portal.prt.component.PortalComponentResponse.include(PortalComponentResponse.java:215)
     at com.sapportals.portal.prt.pom.PortalNode.service(PortalNode.java:645)
     at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:328)
     at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:136)
     at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:189)
     at com.sapportals.portal.prt.core.PortalRequestManager.runRequestCycle(PortalRequestManager.java:753)
     at com.sapportals.portal.prt.connection.ServletConnection.handleRequest(ServletConnection.java:240)
     at com.sapportals.portal.prt.dispatcher.Dispatcher$doService.run(Dispatcher.java:524)
     at java.security.AccessController.doPrivileged(AccessController.java:242)
     at com.sapportals.portal.prt.dispatcher.Dispatcher.service(Dispatcher.java:407)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
     at com.sap.engine.services.servlets_jsp.server.servlet.InvokerServlet.service(InvokerServlet.java:156)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
     at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)
     at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:387)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:365)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:944)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:266)
     at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
     at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)
     at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
     at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
     at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
     at java.security.AccessController.doPrivileged(AccessController.java:215)
     at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
     at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
Any Help?
Regards,
Sree

Hi sreedhar Gunda,
Check whether the repositories are in active and running mode or not. If they are running fine. then check the authorization is sufficient from BASIS people.
points if useful
Thanks
Suresh

Statspack Total Wait time

hi -
using v 9.2
I'm wondering about the Total Wait Time (s) in the Top 5 wait Events list.
I took a snapshot for 10.55(min) but some of the Time (s) exceeds this, so i'm clearly interpreting something incorrectly:
Top 5 Timed Events
~~~~~~~~~~~~~~~~~~                                                     % Total
Event                                               Waits    Time (s) Ela Time
db file scattered read                            587,895       1,464    37.24
CPU time                                                        1,205    30.66
SQL*Net message from dblink                        22,597         609    15.49
db file sequential read                           478,006         554    14.11
log file parallel write                             6,335          28      .72
          -------------------------------------------------------------For example the db file scattered read is 1,464(s) which is more than the 10.55(min) of the snapshot.
how correlate this Time(s) to clock time?
My assumption is that multiple sessions are added and this number can exceed snapshot time?
Edited by: stg on Oct 17, 2008 9:50 AM

rocr wrote:
the time is per processor so if you have 8 processors and the clock time of the report is 6 minutes but 5 cpus use 3 minutes of processing each then the total time is 15 minutes.rocr,
You're thinking of the "CPU time" component only.
The wait time can be much greater than "snapshot interval * CPU_count". It can be as large as "snapshot interval * number of sessions".
For example:
I lock a table in exclusive mode for 15 minutes.
100 other users try to update that table, and have to wait for me to release my lock.
Elapsed time = 15 minutes
Wait time = 100 * 15 minutes = 1,500 minutes.
Regards
Jonathan Lewis
http://jonathanlewis.wordpress.com
http://www.jlcomp.demon.co.uk
"The greatest enemy of knowledge is not ignorance, it is the illusion of knowledge." Stephen Hawking.

SCOM2012 Alert: SQL 2008 DB Average Wait Time & Recompilationis too high

WE have SCOM 2012sp1 CU3 updated.
I receive the below critical alerts from SQL servers continuously, please help me to resolve this issue.
SQL 2008 DB Average Wait Time is too high
SQL DB 2008 SQL Recompilation is too high

I don't know about anyone else but overriding those monitors and rules didn’t work for me, I had to override<o:p></o:p>
SQL Re-Compilation monitor for SQL 2012 DB Engine<o:p></o:p>
SQL Re-Compilation monitor for SQL 2008 DB Engine<o:p></o:p>
Average Wait Time monitor for SQL 2012 DB<o:p></o:p>
Average Wait Time monitor for SQL 2008 DB<o:p></o:p>
Now I am wondering if other monitors are valid as well in particular I have multiple alerts for<o:p></o:p>
Buffer Cache Hit Ratio monitor for SQL 2008 DB Engine is too low<o:p></o:p>
Page Life Expectancy (s) for 2008 DB Engine is too low<o:p></o:p>
is anyone else seeing these issues as well?

Inconsistent IO Wait Time

I'm trying to comprehend why oracle seems to more efficiently table scan a table when it has more rows than when it has less.
I have run a bunch of queries against the database, and I have tracked their wait events stats.
And it seems that this ratio:
ReacorsPerWait = #records/ wait_time,
where db_file_scattered_read is the most significant wait event by a lot
This Ratio simply Increases on and on, although the rate of increase grows eventually slower.
Namely, this ratio is practically the same when the relatio changes from 25 Million tuples to 125 Million tuples. But
before reaching that ratio threshold, the ratio increases quite significantly from test to test.
(From 0.2 Million to 1 million, to 5 million and to 25 Million...
It increases way too fast. I get changes in rate of more than 40%)
I just cannot make any sense of this performance change, If the number of records is increasing by 5 the IO time should also be increasing by 5.
What I have tried to do to fix this at some constant rate was: set the db_multiblock_read_count at some constant value. I set it up to like 10 MB. (10* 1024 KB / 8 KB)
But the results are the same, with or without a fixed multiblock read count, Oracle IOs faster when the relation is bigger. What is the cause of this? Any Ideas.
Another interesting thing is that the Cache Hit Ratio is reducing as the IO speed is increasing.
But the number of physical reads increase proportionately (times 5). I thought that this migh be explained because Oracle might Use larger Multi Block Reads when the relation was larger - or something like that.
But now I know that that cannot be the reason.
(By the way: this change in rate could be explained - partially - in the tests from 0.2Million to 1 million due to other wait time like reading control file, which is significant for small examples. But from 1 Million oward, approximately 99% of the wait time is doing the db file scattered read)
Edited by: sono99 on Nov 4, 2009 4:22 AM
Edited by: sono99 on Nov 4, 2009 4:30 AM
Edited by: sono99 on Nov 4, 2009 4:32 AM

sono99 wrote:
HI, thank you for trying to help.
"It's likely that measurements also vary with row size and not just row count ... not to mention half a dozen other features.
There are a couple of obvious possibilities:"I think that are not likely to be reason of the improvement in IO performance. Sure, I am not saying that standard deviation of row size is 0, but I'd say whichever the STD for the row size is, it will be pretty small.
To begin with, the table is populated with data generated by a home coocked program.
The table has like 6 collumns of integer type, none of them has null values.
If you ask a generic question you get generic answers.
Your original posting was about "the database", not about "a specific table created on a single disc for test purposes".
Have you tried cloning the table several times and seeing if the results are consistent across all clones ? There are several possible causes of variation in your case, for example has part of your table has ended up on a less fragmented part of the disc, or on the outer edge of the disc, so that the multiblock reads are more effective, or the disk-level track caching is more effective.
All sorts of strange side effects can appear when you create single user tests on small machines, and you have to be careful to consider the effects of multi-user activity on "realistic" system when constructing tests. It can be quite difficult to identify the points where a test is not properly representative of the mechanism you are trying to investigate.
Regards
Jonathan Lewis
http://jonathanlewis.wordpress.com
http://www.jlcomp.demon.co.uk
To post code, statspack/AWR report, execution plans or trace files, start and end the section with the tag {noformat}{noformat} (lowercase, curly brackets, no spaces) so that the text appears in fixed format.
"Science is more than a body of knowledge; it is a way of thinking"
Carl Sagan

How to monitor SM50 spool work process wait time from RZ20

Hello All,
I want to monitor the SM50 spool work process wait time from RZ20 (like dialog response time from rz20). Please help me to how to do this.
Regards
Subbu

Hi Subbu,
You may refer SAP help on CCMS to get the list of MTEs to be configured for spool monitoring.
MTE
Description
SpoolNumbers
Spool numbers that every output request is assigned
UsedNumbers
Percentage usage of the spool numbers; you must delete old output requests before this number reaches 100 percent
Status
Is only displayed if the spool service belongs to an SAP application server
WaitTime
Wait time in the spool service in seconds
Monitoring the Spool System (SAP Library - SAP Printing Guide (BC-CCM-PRN))
Hope this helps.
Regards,
Deepak Kori

Applications waiting on locks 100%

Hello all,
from time to time we get some errors in our bw system. The monitoring tool send the error called "Percentage of the applications that are currently waiting on locks (100%)". For this we´ve changed the parameters but nothing helps.
We´re using db6 9.5 with fixpack 4.
Regards Olaf

Hi Olaf,
Impossible to help you without more info. A few questions:
Which monitoring tool are you talking about?
Which parameters did you change?
Did you check the database snapshot or db2diag.log for lock escalations?
If this is not the case could you please collect more information with db6util ( note 327595 )?
Regards
Frank

No available resource. Wait-time expired.

Dear All
I am using sun ONE applications server. I am struggling with No available resource. Wait-time expired problem. MY Pool configurations are steady:20,max:100,inc:2. My code is very straight forward.
Getting the connection, using the connection and closing the connection. I made sure that the connection opened is getting closed. But still after certain no. of requests my request is getting blocked. What might be the problem.
Regards,
Nagaraju.KV

Hi,
As you can see from other posts, this is a very common problem. Until now the cause always ends up pointing to a connection not being close.
I suggest you try to run through a full single cycle of you app, while using the CLI monitoting to check that the connections created/closed matches the expected created/closed connections. Also that the number of free connections at the end is correct.

Big wait time

Hi,
If we have statements at work which have very good cost / cardinality (as looking on the plan), with index range scans or index unique scans, but the wait time is a problem, what could be the problem? One of my collegue complain and don't understand why a statement which has an excellent plan, is executing by 5-10 minutes (and still executing), and if he modifies the statement so the plan uses a full table scan on some table, then the results are shown in 5-6 seconds. He thinks that Oracle "lies", and the execution plan is sometimes misleading.
So what could be the cause that Oracle decides that the results are got faster with a FTS, and not with the better plan?
Thank you.
p.s. I cannot put a plan here, as now I'm home.

Outdated table statistics could be a reason for Optimizer to come up with the wrong plan.
Remember that Full Table Scans are not always evil, but sometimes to be preferred over an Index Scan, which uses nested loops (= slow for large amounts of data).
Example: http://asktom.oracle.com/pls/apex/f?p=100:11:0::::P11_QUESTION_ID:9422487749968

Wait timer "challenge"

I am asking this "challenge" question because I am having doubts about a long held conception of mine re: how the Wait Timer in LabVIEW (Windows) behaves.
Look at the attached .jpg. The prize winning question is:
Do Output A and Output B turn on and off:
A) At the same time
B) In opposition to one another
C) It depends
My answer would normally be C, but I wonder if that is really true. We know how the Output B loop will behave, but can we tell without running the VI how Output A will behave? And once we compile and run the vi and observe the results, are we still 100% sure it will ALWAYS behave that way, no matter what PC we run it on and even if we build it into an executable file?
P.S. the "prize" is that I buy the winner a beer, redeemable anywhere within the city of Los Angeles.
Message Edited by Garvacious on 10-21-2005 05:52 PM
Message Edited by Garvacious on 10-21-2005 05:55 PM
Attachments:
Wait Timer Challenge.JPG ‏59 KB

The answer is probably very close to B.
Since there is no data dependency between the wait statement and other structures in the loop in the upper case, they all will execute roughly at the same time. It does not matter if the wait or the display update starts first, they will all start within "nanoseconds" of each other and the changed LED will be updated to the new value. (The NOT will execute after the display update, so it will not have any influence in the current iteration). The wait statement is not blocking anything that can go on in parallel, it will only prevent the loop from finishing because it will be the slowest node. Dataflow dictates that a frame can only finish once everything in it is done.
In the bottom case, the update of the LED is delayed until the first frame finishes.
Message Edited by altenbach on 10-21-2005 04:08 PM
LabVIEW Champion . Do more with less code and in less time .

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

Wait/Time ratio 100%

Similar Messages

Maybe you are looking for