Long response times calling XE on a Linux Server

I've installed XE on a Suse 9.2 Linux Server.
In most cases I get a fast access to XE over APEX. But sometimes, I get a timeout when a I call a page on APEX.
There is also a paralell running Apache webserver (port 80) on the server.
XE port 8080.
Does anybody know what's the reason for this?

you may catch cpu consuming processes from operating system and if they are related to xe instance you can use this easily to identify what is going on behind;
-- who is doing what
SELECT sq.sql_text,
se.status,
se.username,
se.osuser,
se.terminal,
se.machine,
'ALTER SYSTEM KILL SESSION ''' || se.sid || ', ' || se.serial# ||
''' IMMEDIATE ;',
se.sid,
se.serial#,
pr.spid,
se.saddr,
se.schemaname,
se.program,
se.logon_time,
sq.hash_value,
sq.address,
sq.buffer_gets,
sq.disk_reads,
sq.executions,
sq.fetches,
sq.rows_processed,
io.block_gets,
io.consistent_gets,
io.physical_reads,
io.block_changes,
io.consistent_changes,
se.module,
se.action,
se.client_info,
sw.event,
sw.p1text,
sw.p1,
sw.p2text,
sw.p2,
pr.pga_used_mem,
pr.pga_alloc_mem,
pr.pga_freeable_mem,
pr.pga_max_mem,
'exec dbms_support.start_trace_in_session(' || se.sid || ', ' || se.serial# || ', ' ||
'waits => TRUE' || ', ' || 'binds => TRUE);',
'exec dbms_support.stop_trace_in_session(' || se.sid || ', ' || se.serial# || ');'
FROM v$session se, v$sqlarea sq, v$process pr, v$session_wait sw, v$sess_io io
WHERE status IN ('ACTIVE', 'KILLED', ' INACTIVE', ' CACHED', ' SNIPED')
AND se.sql_hash_value = sq.hash_value(+)
AND se.sql_address = sq.address(+)
AND se.paddr = pr.addr
AND se.sid = sw.sid
AND se.sid = io.sid
ORDER BY sq.sql_text, se.username, se.schemaname, se.osuser, se.program, se.sid
You need to match the top cpu os processes' id with the "pr.spid" column, then you might look at the other columns of that row for details.
Also the database runs a number of jobs - backups, etc. these may be the problems.
Kind regards,
Tonguç

Similar Messages

  • SBWP  transaction - viewing folders/sending documents Long response times

    Hi all,
    I have some complains from some users (about 3-4 out of ~3000 user in my ECC 6.0 system) within my company about their response times on the Business Workplace. In particulat they started complaining about the response time of calling the TCOD SBWP . For 1-2 of them up to 4-5 minutes when myself as well as my other 2 colleagues were getting response of 500ms.
    Then they wanted also to view some folders on the Workplace and they had also response times of minutes instead of seconds.
    I checked that some of their shared folders as well as the Trash Bin had thousands of PDFs. I told to delete them and they deleted most of them. Stil when they want to open a folder it takes >2 minutes while for me to open the same shared folder takes 1-2 seconds.
    I checked in ST03N (user profiles, single records) and 1 of them had long database calls and request time in the Analysis of ABAP/4 database requests (Single Statistical Records).
    I am running out of ideas as I cannot explain why only for those 2-3 users happens to have long response times.
    Is it related to their folders in the Workplace? Where should I focus my investigation for the SBWP like transactions? Is it the case that some Oracle parameters might need to be checked?
    I run the automatic Oracle parameters check (O/S AIX 5.3 , Oracle 10.2 , ECC 6.0) and here are some recommandations:
    fixcontrol (5705630)                   add with value "5705630:ON"                                                                                use optimal OR concatenation; note 176754                    NO                                                          5705630:ON                                         B          1             
    fixcontrol (5765456)                   add with value "5765456:3"                                                                                no further information available                             NO                                                          5765456:3                                          B          1             
    optimpeek_user_binds                   add with value "FALSE"                                                                                avoid bind value peaking                                     NO                                                          FALSE                                              B          1             
    optimizerbetter_inlist_costing         add with value "OFF"                                                                                avoid preference of index supporting inlist                  NO                                                          OFF                                                B          1             
    optimizermjc_enabled                   add with value "FALSE"                                                                                avoid cartesean merge joins in general                       NO                                                          FALSE                                              B          1             
    sortelimination_cost_ratio             add with value "10"                                                                                use non-order-by-sorted indexes (first_rows)                 NO                                                          10                                                 B          1             
    event (10027)                            add with value "10027 trace name context forever, level 1"                                                               avoid process state dump at deadlock                         NO                                                          10027 trace name context forever, level 1          B          1             
    event (10028)                            add with value "10028 trace name context forever, level 1"                                                               do not wait while writing deadlock trace                     NO                                                          10028 trace name context forever, level 1          B          1             
    event (10091)                            add with value "10091 trace name context forever, level 1"                                                               avoid CU Enqueue during parsing                              NO                                                          10091 trace name context forever, level 1          B          1             
    event (10142)                            add with value "10142 trace name context forever, level 1"                                                               avoid Btree Bitmap Conversion plans                          NO                                                          10142 trace name context forever, level 1          B          1             
    event (10183)                            add with value "10183 trace name context forever, level 1"                                                               avoid rounding during cost calculation                       NO                                                          10183 trace name context forever, level 1          B          1             
    event (10191)                            add with value "10191 trace name context forever, level 1"                                                               avoid high CBO memory consumption                            NO                                                          10191 trace name context forever, level 1          B          1             
    event (10411)                            add with value "10411 trace name context forever, level 1"                                                               fixes int-does-not-correspond-to-number bug                  NO                                                          10411 trace name context forever, level 1          B          1             
    event (10629)                            add with value "10629 trace name context forever, level 32"                                                              influence rebuild online error handling                      NO                                                          10629 trace name context forever, level 32         B          1             
    event (10753)                            add with value "10753 trace name context forever, level 2"                                                               avoid wrong values caused by prefetch; note 1351737          NO                                                          10753 trace name context forever, level 2          B          1             
    event (10891)                            add with value "10891 trace name context forever, level 1"                                                               avoid high parsing times joining many tables                 NO                                                          10891 trace name context forever, level 1          B          1             
    event (14532)                            add with value "14532 trace name context forever, level 1"                                                               avoid massive shared pool consumption                        NO                                                          14532 trace name context forever, level 1          B          1             
    event (38068)                            add with value "38068 trace name context forever, level 100"                                                             long raw statistic; implement note 948197                    NO                                                          38068 trace name context forever, level 100        B          1             
    event (38085)                            add with value "38085 trace name context forever, level 1"                                                               consider cost adjust for index fast full scan                NO                                                          38085 trace name context forever, level 1          B          1             
    event (38087)                            add with value "38087 trace name context forever, level 1"                                                               avoid ora-600 at star transformation                         NO                                                          38087 trace name context forever, level 1          B          1             
    event (44951)                            add with value "44951 trace name context forever, level 1024"                                                            avoid HW enqueues during LOB inserts                         NO

    Hi Loukas,
    Your message is not well formatted so you are making it harder for people to read. However your problem is that you have 3-4 users of SBWP with slow runtimes when accessing folders. Correct ?
    You mentioned that there is a large number of documents in the users folders so usually these type of problems are caused by a large number of table joins on the SAPoffice tables specific to your users.
    Firstly please refer to SAP Note 988057 Reorganization - Information.
    To help with this issue you can use report RSBCS_REORG in SE38 to remove any deleted documents from the SAPoffice folders. This should speed up the access to your users documents in folders as it removes unnecessary documents from the SAPoffice tables.
    If your users do not show a significant speed up of access to their SAPoffice folders please refer to SAP Note 904711 - SAPoffice: Where are documents physically stored and verify that your statistics and indexes mentioned in this note are up to date.
    If neither of these help with the issue you can trace these users in ST12 and find out which table is cauing the longest runtime and see if there is a solution to either reduce this table or improve the access method on the DB level.
    Hope this helps
    Michael

  • Problem with long response time when looking at queues!

    Hello,
    I have a problem with extream long response times, when looking at the queues in Message mapping test tool . Does anyone know how to improve performance.
    The source message I use is about 200 segments (idoc)
    The mapping is done with the graphical tool, with 10-15 field contain standard sap functions for mapping.
    Target structure is EDIFACT (xml)
    Brgds
    Karl Bergströ

    Hi Rod.
    Go to Apple Menu > System Preferences > Network > Show: Network Port Configurations. Make sure that the configuration used to connect to Internet is at the top of the list. Also, disable any communications/networking configuration enabled, but not in use.
    If the above doesn't fix the problem, open Keychain Access > Preferences, and disable Search .Mac For Certificates if it's enabled. Take a look at the following articles for an explanation of why this could fix the problem:
    http://www.hawkwings.net/2006/07/18/apple-mail-phones-home-too/
    http://www.macgeekery.com/tips/mailapp_doesnt_phone_homeeither

  • Quering UCCX Call Centers from a linux server

    Hello,
         I would like to query the UCCX call center server in our environment from a linux server and am looking for some light guidance.  I work with MySQL and PHP and am quite comfortable with both, but most of my work in these areas are in web development.  UCCX run Informix, but as I understand, SQL queries are supported.  Do I need to download and install an ODBC or JDBC driver in order to do this?  How would I go about setting up a server to be able to query information from the UCCX server for rendering to a web page?  Any help is appreciated.

    Hi Anthony (how' it going)
         I'm looking to pull pretty standard stats and post them to a web page (so, a wallboard basically).  I can use PHP to authenticate to a mysql server and pass queries, then render the output however I need.  I'll like to see if I can do something like this for CUCCX, but I'm not sure how to connect from Linux to something that's not a MySQL server (I'll worry about the db schema after connectivity is sorted out).  Have you done any work in this regard?

  • Very low upload speed or long response times

    Hi,
    Just connected my Airport Extreme. Unfortunately, the upload speed appears to be extremely slow. Checking my connection using Speedtest.net reveals that it takes very long for my workstation to connect to the Speedtest server via my APExt, before it starts uploading the testpackage. I've also tested the performance of my ADSL connection by directly plugging a workstation into the DSL modem and retesting the connection via Speedtest.net. This shows a normal response between the client and the server.
    How do I further diagnose this problem? I didn't have this problem before a replaced my Sitecom wireless router with the Airport Extreme.
    Thanks,
    J

    And all that took was a firmware upgrade to version 7.6

  • Long response time for input help (on Portal Only) BW7

    Dear All,
      I have made a variable for InfoObject 0COSTCENTER(hierarchy) in the query.
      When I run the query in RSRT/ABAP Web and hit the input help, it only takes 2 secs to show all the possible values. But by executing the same query on portal and hit the same input help would take more than 3 mins. Any idea ?? Please help.
    Charlie

    Charlie,
    Check what is the read mode for the variable in the template (can check in the properties), If it is master data then it will go to master data and bring all the data. If it is posted value it will bring the data from infoprovider.
    Rergards,
    Kams

  • Time Capsule, AEBS+USB drive, Linux server: Which system for Time Machine?

    I'm planning to get a new Macbook Pro, and upgrading my iMac in the near future. In making the big leap to Leopard, I am going to upgrade my router to at least the AEBS. But I'm not sure what the best way is to take advantage of the Time Machine function.
    Here's my take on the situation:
    Time Capsule
    Pros: all in one solution
    Cons: I'm stuck if one day I need a bigger drive, or need to replace it.
    AEBS+USB drive
    Pros: Easy way to upgrade/replace drive if needed
    Cons: Extra device needed
    Using a drive on my Linux fileserver
    Pros: Easy way to upgrade/replace drive(s) if needed, can set up RAID1 for extra redundancy
    Cons: Not officially supported, but apparently can use the "defaults write com.apple.systempreferences TMShowUnsupportedNetworkVolumes 1" tweak to get this going.
    Which would you do?

    Assuming that the USB drive has been formatted in Mac OS Extended (Journaled)......
    Open System Preferences (gear icon on the dock) on your Mac
    Open Time Machine
    Insure that the USB drive is configured as a destination for Time Machine backups
    If it is not, click Add or Remove Disks
    Click the USB drive to highlight it
    Click Use Disk
    Time Machine will now backup to the USB disk, and alternate disks if you have other disks selected as Time Machine backup destinations.

  • Response Time BPEL Fault

    Hi everybody,
    i have the following Problem:
    create a simple composite with one Mediator wiring to one simple BPEL Process.
    The BPEL throws his own Business Fault define within the WSDL.
    The Mediator propagate this Fault to the inital caller.
    Everthing works fine but...
    The Response Time for the normal request and response of the BPEL is 300 - 400ms.
    If the BPEL throws the Fault, the response Time is over 6 Seconds!!
    Has anyone an idea why the Response Time from the BPEL Fault is so much higher?
    Thanks a lot
    regs Stefan

    Hi Neeraj,
    the Problem is identified. The long Response Time comes from our internal Company Network.
    The Response Times if calling the Service from hosted Environment is OK.
    Regards Stefan
    Edited by: stisiman on 27.03.2013 14:57

  • Response times select  on resource_view

    Hi
    I have an application handle quite large volumes of documents. All documents are stored in XDB. Now starting to get long response times. It has not been a problem in the past but are now becoming more acute. I use resource_view frequently to list files and folders. I know that you should use "equals_path" when searching in resource_view for best response times. But for various reasons, there are few places where I have to do select on RESID. My question is are there any easy ways to get better response time if you select by RESID. See the example below, if I search on RESID, it takes 4 seconds if I use "equals_path" a few milliseconds. Is there any way to speed up the search on RESID?
    I'm running Oracle 11g.
    select any_path from resource_view where resid='9F124A513AAC9A44E040240A43227D33'; --4 sec
    select any_path from resource_view where equals_path(RES, '/public/infoportal/stapswe/BLIVATEST117_45100') = 1 --32 msec
    Lennart

    Hi,
    Try with HEXTORAW function :
    select any_path
    from resource_view
    where resid = hextoraw('9F124A513AAC9A44E040240A43227D33')
    ;The optimizer should then consider using an access path based on the index because the datatypes are matching each other.
    On the contrary, with no explicit conversion to the RAW datatype, the optimizer internally converts RESID to VARCHAR2 by applying a function on it, thus preventing the index from being used.
    See both explain plans for the details.
    SQL> explain plan for
      2  select * from resource_view where resid = '8BAE7B7BE7D14E07A13E73F6824648E3'
      3  ;
    Explicité.
    SQL> select * from table(dbms_xplan.display);
    PLAN_TABLE_OUTPUT
    Plan hash value: 3007404872
    | Id  | Operation                   | Name         | Rows  | Bytes | Cost (%CPU)| Time     |
    |   0 | SELECT STATEMENT            |              |     1 |   132 |     3   (0)| 00:00:01 |
    |*  1 |  TABLE ACCESS BY INDEX ROWID| XDB$RESOURCE |     1 |   132 |     3   (0)| 00:00:01 |
    |*  2 |   DOMAIN INDEX              | XDBHI_IDX    |       |       |            |          |
    Predicate Information (identified by operation id):
       1 - filter(RAWTOHEX("SYS_NC_OID$")='8BAE7B7BE7D14E07A13E73F6824648E3')
       2 - access("XDB"."UNDER_PATH"(SYS_MAKEXML('8758D485E6004793E034080020B242C6',734,
                  "XMLEXTRA","XMLDATA"),'/',9999)=1)
    16 ligne(s) sélectionnée(s).
    SQL> explain plan for
      2  select * from resource_view where resid = hextoraw('8BAE7B7BE7D14E07A13E73F6824648E3')
      3  ;
    Explicité.
    SQL> select * from table(dbms_xplan.display);
    PLAN_TABLE_OUTPUT
    Plan hash value: 1655379850
    | Id  | Operation                        | Name         | Rows  | Bytes | Cost (%CPU)| Time     |
    |   0 | SELECT STATEMENT                 |              |     1 |   132 |     3   (0)| 00:00:01 |
    |   1 |  TABLE ACCESS BY INDEX ROWID     | XDB$RESOURCE |     1 |   132 |     3   (0)| 00:00:01 |
    |   2 |   BITMAP CONVERSION TO ROWIDS    |              |       |       |            |          |
    |   3 |    BITMAP AND                    |              |       |       |            |          |
    |   4 |     BITMAP CONVERSION FROM ROWIDS|              |       |       |            |          |
    |*  5 |      INDEX RANGE SCAN            | SYS_C003123  |     1 |       |     0   (0)| 00:00:01 |
    |   6 |     BITMAP CONVERSION FROM ROWIDS|              |       |       |            |          |
    |   7 |      SORT ORDER BY               |              |       |       |            |          |
    |*  8 |       DOMAIN INDEX               | XDBHI_IDX    |     1 |       |            |          |
    Predicate Information (identified by operation id):
       5 - access("SYS_NC_OID$"=HEXTORAW('8BAE7B7BE7D14E07A13E73F6824648E3') )
       8 - access("XDB"."UNDER_PATH"(SYS_MAKEXML('8758D485E6004793E034080020B242C6',734,"XMLE
                  XTRA","XMLDATA"),'/',9999)=1)
    22 ligne(s) sélectionnée(s).Edited by: odie_63 on 8 avr. 2011 08:55

  • Problem with response time

    Hi, I am experiencing long response time for my dashboard(40 seconds on some PC). I wonder what is the normal response time for your dashboards, and what is the size of your worksheet?
    For me, I have a tab set with 5 tabs, under each tab, there are about 100 row* AH cloumn. And as it is still the proof of concept stage in my company, I am using offline data, but if we use live data from BW, what would it mean to the resopnse time, even longer?
    Thank you very much.

    Hello,
    We try to keep our SWF size under 1024 kb, but that doesn't mean it will load fast since the connection loads little after Initializing the component. We have around 100 components on an average, and some custom components. One thing you should stay away from is doing lot of grouping in the Object Browser.
    Questions for you:
    Which version of xcelsius and service pack are you using?
    How many connections run when the dashboard loads initially?
    How many total connections?
    How many rows and columns does the initial load connection bring?
    How much time does the same query take in the database?
    Edited by: msaraogi on Dec 15, 2010 10:32 PM

  • ACE 4710: Find out the response time of a real server

    Hi to everyone,
    I have a couple of ACE 4710 and I need to find out what is the response time of a real server.
    Is there a way for this?
    Thank you for any answer!
      giorgio romano

    Hi,
    Kindly add the following line in your serverfarm configuration:
    predictor response syn-to-synack
    Suppose your serverfarm looks like this:
    serverfarm host AAA_FARM
    predictor response syn-to-synack
    probe HTTP_PROBE
    probe TCP9001_PROBE
    rserver SC106
    inservice
    rserver SC107
    inservice
    rserver SC108
    inservice
    rserver SC109
    inservice
    rserver SC110
    inservice
    rserver SC111
    inservice
    rserver SC112
    inservice
    rserver SC113
    inservice
    rserver SC114
    inservice
    rserver SC120
    inservice
    rserver SC131
    inservice
    And then use the following command to see the average response time from your rserver as follows:
    ACE1/prod# show serverfarm AAA_FARM detail
    serverfarm     : AAA_FARM, type: HOST
    total rservers : 11
    active rservers: 11
    description    : ServerFarm AAA
    state          : ACTIVE
    predictor      : RESPONSE
    method            : syn-to-synack
    samples           : 8
    failaction     : -
    back-inservice    : 0
    partial-threshold : 0
    num times failover       : 0
    num times back inservice : 0
    total conn-dropcount : 0
    Probe(s) :
    HTTP_PROBE,  type = HTTP
    TCP9001_PROBE,  type = TCP
    ----------connections-----------
    real                  weight state        current    total      failures
    ---+---------------------+------+------------+----------+----------+---------
    rserver: SC106
    x.x.x.x.:0        8      OPERATIONAL  2          1125       0
    max-conns            : 4000000   , out-of-rotation count : 0
    min-conns            : 4000000
    conn-rate-limit      : -         , out-of-rotation count : -
    bandwidth-rate-limit : -         , out-of-rotation count : -
    retcode out-of-rotation count : -
    load value           : 0
    average response time (usecs) : 81   ----> thats what you might be looking for
    From other day :
    rserver: SC114
    x.x.x.x:0        8      OPERATIONAL  70         10903      2
    max-conns            : 4000000   , out-of-rotation count : 0
    min-conns            : 4000000
    conn-rate-limit      : -         , out-of-rotation count : -
    bandwidth-rate-limit : -         , out-of-rotation count : -
    retcode out-of-rotation count : -
    load value           : 0
             average response time (usecs) : 1334                       ----> thats what you might be looking for
    For Serverfarm BBB_FARM
    serverfarm     : BBB_FARM, type: HOST
    total rservers : 1
    active rservers: 1
    description    : ServerFarm BBB
    state          : ACTIVE
    predictor      : RESPONSE
    method            : syn-to-synack
    samples           : 8
    failaction     : -
    back-inservice    : 0
    partial-threshold : 0
    num times failover       : 1
    num times back inservice : 1
    total conn-dropcount : 0
    Probe(s) :
    ----------connections-----------
    real                  weight state        current    total      failures
    ---+---------------------+------+------------+----------+----------+---------
    rserver: SC208
    x.x.x.x:0        8      OPERATIONAL  0          0          0
    max-conns            : 4000000   , out-of-rotation count : 0
    min-conns            : 4000000
    conn-rate-limit      : -         , out-of-rotation count : -
    bandwidth-rate-limit : -         , out-of-rotation count : -
    retcode out-of-rotation count : -
    load value           : 0
             average response time (usecs) : 0   ----> thats what you might be looking for
    Use more detials for response predictor:
    http://www.cisco.com/en/US/docs/app_ntwk_services/data_center_app_services/ace_appliances/vA3_1_0/configuration/slb/guide/rsfarms.html#wp1068831
    Configuring the Application Response Predictor
    To instruct the ACE to select the server with the lowest average response time for the specified response-time measurement based on the current connection count and server weight (if configured), use the predictor response command in server farm host or redirect configuration mode. This predictor is considered adaptive because the ACE continuously provides feedback to the load-balancing algorithm based on the behavior of the real server.
    To select the appropriate server, the ACE measures the absolute response time for each server in the server farm and averages the result over a specified number of samples (if configured). With the default weight connection option configured, the ACE also takes into account the server's average response time and current connection count. This calculation results in a connection distribution that is proportional to the average response time of the server.
    The syntax of this command is as follows:
    predictor response {app-req-to-resp | syn-to-close | syn-to-synack}[samples number]
    The keywords and arguments are as follows:
    •app-request-to-resp—Measures the response time from when the ACE sends an HTTP request to a server to the time that the ACE receives a response from the server for that request.
    •syn-to-close—Measures the response time from when the ACE sends a TCP SYN to a server to the time that the ACE receives a CLOSE from the server.
    •syn-to-synack—Measures the response time from when the ACE sends a TCP SYN to a server to the time that the ACE receives the SYN-ACK from the server.
    •samples number—(Optional) Specifies the number of samples over which you want to average the results of the response time measurement. Enter an integer from 1 to 16 in powers of 2. Valid values are 1, 2, 4, 8, and 16. The default is 8.
    For example, to configure the response predictor to load balance a request based on the response time from when the ACE sends an HTTP request to a server to when the ACE receives a response back from the server and average the results over four samples, enter:
    host1/Admin(config)# serverfarm SFARM1
    host1/Admin(config-sfarm-host)# predictor response app-req-to-resp
    samples 4
    To reset the predictor method to the default of round-robin, enter:
    host1/Admin(config-sfarm-host)# no predictor
    To configure an additional parameter to take into account the current connection count of the servers in a server farm, use the weight connection command in server farm host predictor configuration mode. By default, this command is enabled. The syntax of this command is as follows:
    weight connection
    For example, enter:
    host1/Admin(config)# serverfarm SF1
    host1/Admin(config-sfarm-host)# predictor response app-request-to-resp
    samples 4
    host1/Admin(config-sfarm-host-predictor)# weight connection
    To remove the current connection count from the calculation of the average server response time, enter:
    host1/Admin(config-sfarm-host-predictor)# no weight connection
    You can use threshold milliseconds parameter which is optional Specifies the required minimum average response time for a server. If the server response time is greater than the specified threshold value, the ACE removes the server from the load-balancing decision process (takes the server out of service).
    Enter an integer from 1 to 300000 milliseconds (5 minutes). The default is no threshold (servers are not taken out of service).
    In case if you have measures the response time from  when the ACE sends a TCP SYN to a server to the time that the ACE receives a CLOSE from the server  use syn-to-close      (already discussed previously)
    If you have to measures the response time from when the ACE sends a TCP SYN to a server to the time that the ACE receives the SYN-ACK from the server use syn-to-synack   (already discussed previously)
    SAMPLES parameter is optional and  specifies the number of samples that you want to average from the results of the response time measurement and response time is used to select the server with the lowest response time for the requested response-time measurement. If you do not specify a response-time measurement method, the ACE uses the HTTP app-req-to-response method.
    Whenever a server's load reaches zero, by default, the ACE uses the autoadjust feature to assign a maximum load value of 16000 to that server to prevent it from being flooded with new incoming connections. The ACE periodically adjusts this load value based on feedback from the server's SNMP probe and other configured options.
    Using the least-loaded predictor with the configured server weight and the current connection count option enabled, the ACE calculates the final load of a real server as follows:
    final load = weighted load × static weight × current connection count
    where:
    •weighted load is the load reported by the SNMP probe
    •static weight is the configured weight of the real server
    •current connection count is the total number of active connections to the real server
    The ACE recalculates the final load whenever the connection count changes, provided that the (config-sfarm-host-predictor) weight connection command is configured. If the (config-sfarm-host-predictor) weight connection command is not configured, the ACE updates the final load when the next load update arrives from the SNMP probe.
    If two servers have the same lowest load (either zero or nonzero), the ACE load balances the connections between the two servers in a round-robin manner.
    HTH
    Plz rate if u find it useful.
    Sachin

  • I am have problems with the ipad mini, it is a little crazy. It controls by itself, opens and closes application zooms in and out, end my facetime calls, Also Un certain part of the screen is no longer responsive to the touch.

    I am have problems with the ipad mini, it is a little crazy. It controls by itself, opens and closes application zooms in and out, end my facetime calls, Also Un certain part of the screen is no longer responsive to the touch, it Should be having so much problems. Thanks for your help.
    iPad, iOS 7.0.4

    Try reset iPad
    Hold down the Sleep/Wake button and the Home button at the same time for at least ten seconds, until the Apple logo appears
    Note: Data will not be affected.

  • Strange response time for an RFC call viewed from STAD on R/3 4.7

    Hello,
    On our R/3 4.7 production system, we have a lot of external RFC calls to execute an  abap module function. There are 70 000 of these calls per day.
    The mean response time for this RFC call is 35 ms.
    Some times a few of them (maybe 10 to 20 per day) are way much longer.
    I am currently analysing with STAD one of these long calls  which lasted 10 seconds !
    Here is the info from STAD
    Response time :                10 683 ms
    Total time in workprocess : 10 683 ms
    CPU time  :                               0 ms
    RFC+CPIC time :                       0 ms
    Wait for work process           0 ms
    Processing time           10.679 ms
    Load time                            1 ms
    Generating time                   0 ms
    Roll (in) time                        0 ms
    Database request time         3 ms
    Enqueue time                      0 ms
    Number      Roll ins            0
                     Roll outs           0
                     Enqueues         0
    Load time   Program             1  ms
                      Screen              0  ms
                     CUA interf.          0  ms
    Roll time    Out                 0  ms
                      In                  0  ms
                    Wait                0  ms
    Frontend    No.roundtrips       0   
                      GUI time            0  ms
                      Net time            0  ms
    There is nearly no abap processing in the function module.
    I really don't uderstand what is this  10 679 ms processing time especially with 0 ms cpu time and 0 ms wait time.
    A usual fast RFC call gives this data
    23 ms response time
    16 ms cpu time
    14 ms processing time
    1 ms load time
    8 ms Database request time
    Does anybody have an idea of what is the system doing during the 10 seconds  processing time ?
    Regards,
    Olivier

    Hi Graham,
    Thank you for your input and thoughts.
    I will have to investigate on RZ23N and RZ21 because I'm not used to use them.
    I'm used to investigate performance problems with ST03 and STAD.
    My system is R/3 4.7 WAS 6.20. ABAP and BASIS 43
    Kernel 6.40 patch level 109
    We know these are old patch levels but we are not allowed to stop this system for upgrade "if it's not broken" as it is used 7/7 24/24.
    I'm nearlly sure that the problem is not an RFC issue because I've found other slow dialog steps for web service calls and even for a SAPSYS technical dialog step  of type <no buffer>. (what is this ?)
    This SAPSYS dialog step has the following data :
    User : SAPSYS
    Task type : B
    Program : <no buffer>
    CPU time                       0 ms
    RFC+CPIC time              0 ms
    Total time in workprocs    5.490 ms
    Response time               5.490 ms
    Wait for work process           0 ms
    Processing time             5.489 ms
    Load time                            0 ms
    Generating time                   0 ms
    Roll (in+wait) time                0 ms
    Database request time          1 ms ( 3 Database requests)
    Enqueue time                       0 ms
    All hundreds of other SAPSYS <no buffer> steps have a less than 5 ms response time.
    It looks like the system was frozen during 5 seconds...
    Here are some extracts from STAD of another case from last saturday.
    11:00:03     bt1fsaplpr02_PLG RFC     R     3     USER_LECKIT     13     13     0     0
    11:00:03     bt1sqkvf_PLG_18      RFC     R     4     USER_LECDIS     13     13     0     0
    11:00:04     bt1sqkvh_PLG_18      RFC     R     0     USER_LECKIT     19     19     0     16
    11:00:04     bt1sqkvf_PLG_18      RFC     R     4     USER_LECKIT     77     77     0     16
    11:00:04     bt1sqkve_PLG_18      RFC     R     4     USER_LECDIS     13     13     0     0
    11:00:04     bt1sqkvf_PLG_18      RFC     R     4     USER_LECDIS     14     14     0     16
    11:00:05     bt1sqkvg_PLG_18      RFC     R     0     USER_LECKIT     12     12     0     16
    11:00:05     bt1sqkve_PLG_18      RFC     R     4     USER_LECKIT     53     53     0     0
    11:00:06     bt1sqkvh_PLG_18      RFC     R     0     USER_LECKIT     76     76     0     0
    11:00:06     bt1sqk2t_PLG_18      RFC     R     0     USER_LECDIS     20     20     0     31
    11:00:06     bt1sqk2t_PLG_18      RFC     R     0     USER_LECKIT     12     12     0     0
    11:00:06     bt1sqkve_PLG_18      RFC     R     4     USER_LECKIT     13     13     0     0
    11:00:06     bt1sqkvf_PLG_18      RFC     R     4     USER_LECKIT     34     34     0     16
    11:00:07     bt1sqkvh_PLG_18      RFC     R     0     USER_LECDIS     15     15     0     0
    11:00:07     bt1sqkvg_PLG_18      RFC     R     0     USER_LECKIT     13     13     0     16
    11:00:07     bt1sqk2t_PLG_18      RFC     R     0     USER_LECKIT     19     19     0     0
    11:00:07     bt1fsaplpr02_PLG RFC     R     3     USER_LECKIT     23     13     10     0
    11:00:07     bt1sqkve_PLG_18      RFC     R     4     USER_LECDIS     38     38     0     0
    11:00:08     bt1sqkvf_PLG_18      RFC     R     4     USER_LECKIT     20     20     0     16
    11:00:09     bt1sqkvg_PLG_18      RFC     R     0     USER_LECDIS     9 495     9 495     0     16
    11:00:09     bt1sqk2t_PLG_18      RFC     R     0     USER_LECDIS     9 404     9 404     0     0
    11:00:09     bt1sqkvh_PLG_18      RFC     R     1     USER_LECKIT     9 181     9 181     0     0
    11:00:10     bt1fsaplpr02_PLG RFC     R     3     USER_LECDIS     23     23     0     0
    11:00:10     bt1sqkve_PLG_18      RFC     R     4     USER_LECKIT     8 465     8 465     0     16
    11:00:18     bt1sqkvh_PLG_18      RFC     R     0     USER_LECKIT     18     18     0     16
    11:00:18     bt1sqkvg_PLG_18      RFC     R     0     USER_LECKIT     89     89     0     0
    11:00:18     bt1sqk2t_PLG_18      RFC     R     0     USER_LECKIT     75     75     0     0
    11:00:18     bt1sqkvh_PLG_18      RFC     R     1     USER_LECDIS     43     43     0     0
    11:00:18     bt1sqk2t_PLG_18      RFC     R     1     USER_LECDIS     32     32     0     16
    11:00:18     bt1sqkvg_PLG_18      RFC     R     1     USER_LECDIS     15     15     0     16
    11:00:18     bt1sqkve_PLG_18      RFC     R     4     USER_LECDIS     13     13     0     0
    11:00:18     bt1sqkve_PLG_18      RFC     R     4     USER_LECDIS     14     14     0     0
    11:00:18     bt1sqkvf_PLG_18      RFC     R     4     USER_LECKIT     69     69     0     16
    11:00:18     bt1sqkvf_PLG_18     RFC     R     5     USER_LECDIS     49     49     0     16
    11:00:18     bt1sqkve_PLG_18     RFC     R     5     USER_LECKIT     19     19     0     16
    11:00:18     bt1sqkvf_PLG_18     RFC     R     5     USER_LECDIS     15     15     0     16
    The load at that time was very light with only a few jobs starting :
    11:00:08 bt1fsaplpr02_PLG RSCONN01                     B 31 USER_BATCH     39
    11:00:08 bt1fsaplpr02_PLG RSBTCRTE                     B 31 USER_BATCH     34
    11:00:08 bt1fsaplpr02_PLG /SDF/RSORAVSH                B 33 USER_BATCH     64
    11:00:08 bt1fsaplpr02_PLG RSBTCRTE                     B 33 USER_BATCH     43
    11:00:08 bt1fsaplpr02_PLG RSBTCRTE                     B 34 USER_BATCH     34
    11:00:08 bt1fsaplpr02_PLG RSBTCRTE                     B 35 USER_BATCH     37
    11:00:09 bt1fsaplpr02_PLG RVV50R10C                    B 34 USER_BATCH     60
    11:00:09 bt1fsaplpr02_PLG ZLM_HDS_IS_PURGE_RESERVATION B 35 USER_BATCH    206
    I'm thinking also now about the message server as there is load balancing for each RFC call ?
    Regards,
    Olivier

  • Calling SAP Webservice from JAVA ME bad response time

    Hello together,
    I'm calling a SAP RFC as a Webservice from JAVA ME (Netbeans 6.8). The stub classes I've generated with the Sun Wireless Toolkit. The RFC function stores entries in a SAP database table. The call of the websevice with transmitting the data and the database update in SAP works fine, but I got the response message from SAP with a delay of 40 seconds.
    Does anyone know why there is so a long delay in the response and how to fix it?

    hi,
    is this reproducible or was it just the first call to that service?
    it usually occurs that once you call a webservice for the first time, some of the programs (be it your application programs or the even the SOAP runtime itself) required have not been compiled until that and so they are compiled during the webservice call.
    This leads to slow response times even time-outs. The effect vanishes once all sources are compiled (i.e. depending on the complexity of your calls after one to a few calls to that service).
    So, if the slow response times persist, you should turn on debugging in SICF and see where time is spent...
    my 2 cents,
    anton

  • Are Skype support response times too long for you?

    Just answer yes or no....
    ....and then tell me how long you waited.
    i.e. Yes 7 hours 
    I'm really interested in finding out how much I can rely on this forum for a quick response to problems as I use Skype to communicate with my customers, suppliers and colleagues worldwide.
    The response time to critical questions like "because of a 'technical problem at Skype" I can't allocate credit to my coworkers so as they can call up their contacts phones" - (a.k.a I want to give Skype some money) is unreasonably long. I'm trying to guage how long I can expect to wait.
    Sonic

    Hello  sonic,
    I see you are asking about response time on the forum for questions to be answered. 
    Well, it just depends on who is online at the time you post your question.  We have many professional users like TheUberOverlord and Primemover that are here all the time and answer qualified questions all day.  The Skype Enterprise Team are here 24/7 but are sometimes answering Chats from customers in the Live Chat Sessions of Skype Manager.
    If you want an immediate response, you need to log into your Skype Manager and click on the Chat Button in the top right of that screen and you will be connected to us immediately.  We are here 24/7 for your support.  It is a Business Class Service and we talk to customers from all over the world day and night. We are here to get customers PBX's and SIP compatable devices connected to Skype Connect and can answer most any question on products and devices.
    Thank You for using Skype and the Skype Community Forums.
    Regards,
    Victor S.
    Skype Enterprise Support

Maybe you are looking for