Performance Problems - Adapter Engine

Hi all,
something strange is happening... In scenario Soap -> XI -> Abap proxy, sync, my legacy make a soap call to xi web service. The message sent arrives at sxmb_moni only 2,5 or 3 minutes after the legacy has send it. Sometimes does not appear at sxmb_moni because expires in adapter engine.
After sending the message from legacy, I can see the message in runtime workbench imediately. There it remains as "request received", but no message at sxmb_moni. After 2 or 3 minutes appears a "call completed" on runtime workbench, and then it appears on sxmb_moni, goes to ecc, execute the query and returns.
As basis team said, only 15% to 20%  of processor and memory resources are in use...
Some of you have some tip about it?
thanks!
roberti

Hi,
Don't know how to see if the adapter engine is "loaded fully" as you said...
But there are lots of memory and processor free.
Yes, we have multiple adapters running in parallel, but this seems to be a normal scenario.
Actually we found the interface that was causing this problem. It is a synchronous interface that run in 8 seconds. It has been used to load data from a legacy app to sap ecc, and the client program was executing 6 threads at same time calling this interface. If I stop this data load, all other interfaces works fast.
I can't understand why this happens... We normally have 250 messages per minute from many different interfaces and all of them working fast. If we put 3 or 4 threads asking for this one, all other interfaces begins to be slow... and slower, and timed-out sometimes.
regards.
roberti

Similar Messages

  • RFC Adapter Problem: Adapter Engine Field Blank

    Hi,
    I want to invoke a BAPI defined on a R/3 system. I am trying to create a RFC Adapter in the Integration Directory by creating a communication channel.
    The problem I am facing is that when I define the Adapter Type as RFC, the Adapter Engine dropdown list is blank and it does not contain any entries.
    On passing a document through XI, I can see the following error in the monitor:
    <SAP:Code area="INTERNAL">ADAPTER_NAME_INVALID</SAP:Code>
      <SAP:P1>RFC</SAP:P1>
      <SAP:P2>PLSRV_CALL_ADAPTER</SAP:P2>
      <SAP:P3 />
      <SAP:P4 />
      <SAP:AdditionalText />
      <SAP:ApplicationFaultMessage namespace="" />
      <SAP:Stack>Unknown receiver adapter (name = RFC)</SAP:Stack>
    what do i need to configure on the XI and R/3 side ?
    thanks,
    Manish

    i followed the steps but i am not getting the populated adapter engine list.
    Actually, the Association shows a list of logical systems to be added (Application System, BC Application Server, BC Central Server Instance .....). I experimented with many systems but it is not working.
    My basic problem is I need to call a BAPI from XI. The XI monitor shows the error :
    Adapter Name Invalid.
    Unknown Receiver Adapter (name=RFC).
    Now, for the RFC adapter, I have not given it any name. My Communication Channel is called GeneratedChannelRFC.  I am not sure where this error is coming from. I would appreciate any help to solve this error.
    thanks,
    Manish

  • 1636215 - Performance monitoring for the Advanced Adapter Engine

    Hi ALL,
    How can we monitor the performance by changing the parameter to true in the above note please please help me
    Thanks,
    Raj

    Hi Dheeraj,
    Since you've gone through the note, I'm assuming you know how to activate the performance monitoring for adapter engine.
    However, there are reservations against doing it in any system Dev/Quality/Production. Reason being, it becomes performance/load intensive when the perf. monitoring is on.
    Still, you can diagnose bottlenecks and execution trends in Dev/Quality using performance monitoring as suggested in the note but be aware that your box is coping well with it. Please note, once activated, you don't have to do anything else. System will automatically collect performance data and you will be able to browse through it using the performance monitoring link.
    How to use it???
    You see a performance monitoring link in Monitoring Home (navigate via Configuration and Monitoring home from PI/PO homepage).
    It will help you analyze the flow of message on periodical basis (hourly/daily etc) and will give you more stats on number of messages in that time duration, average time taken, message sizes (min, max and avg), interface-by-interface detail of runtime consumption at every stage etc.
    Please go through standard SAP help for more clarity:
    Monitoring Performance - Advanced Adapter Engine - SAP Library
    Apart from this, there is this great blog by Suseelan around monitoring:
    http://scn.sap.com/docs/DOC-35805
    Hope this helps.
    Regards,
    Abhishek

  • Configuration Steps for Decentralized Adapter Engine

    Hi all,
    What all configuration steps are required to make Adapter Engine as
    Decentralized AE.
    I have made required changes in SLD DataSupplier in Visual Administrator.
    what more configurations have to be done? On SAP XI Server and Decentralized
    Adapter Engine.
    With regards
    Prasad

    Prasad,
    After configuring SLD data supplier in Visual Admin, you need to the following
    1) Configure the gateway service for the central integration server on adapter engine host.
    2) Perform Initial adapter engine cache refresh
    3) Trigger data transfer to SLD
    4) Check the connection parameters in exchangeProfile
    5) Create HTTP destination pmistore in java environment
    you have to go through all these tests for decentralized adapter engine. If you have XI configuration guide, it has all these steps in detail for you to configure
    --Archana

  • "Performance" problems with the File adapter on Plain J2SE Adapter Engine

    Hi,
    At the moment I'm on a customer side to solve some XI issues for a few days. One of the issues is the performance of the Plain J2SE Adapter Engine, using the file adapter to transfer XML messages(already XI message format) from the legacy system to the Integration Engine. The File adapter has to deal with "large" XML messages(max at the moment is 65 Mb) and the engine fails with the following error when transferring the big XML file: "ERROR: Finished sending to Integration Engine with error "java.lang.OutOfMemoryError". Skip confirmation and quit this loop".
    As far I got the information from the customer the memory use of the Plain adapter engine is set to 512Mb. This is maybe to low. But I don't know where to look for this, I only have the adapter web interface in front of me, no access to the OS it self via for example remote connection.
    On the Integration Engine I know there is the ability to split large message with the file adapter(File Content Conversion), but I don't know this for the Plain Adapter Engine. Is there a possibility to do this also on the Plain Adapter Engine?
    Thanks in advance for any input.
    Greetings,
    Patrick

    Hi Sameer,
    Thanks for your answers.
    On the first solution, yes that is possible, we first decided to see if the legacy system can do the splitting, before starting developing a Java program.
    On the second solution, as far as I know is this solution possible on the Integration Engine. But we are facing the problems on the Plain J2SE Adapter Engine. I went trough that documentation(link:
    http://help.sap.com/saphelp_nw04/helpdata/en/6f/246b3de666930fe10000000a114084/frameset.htm ), to look for I similiar solution in the Plain Adapter Engine. So my question is, is this possible with the Plain Adapter? And if so, what kind of parameters I need to use to achieve this.
    Regards,
    Patrick

  • Seeburger EDI Adapter with terrible performance problems

    Hi,
    we installed seeburger edi adapter on PI 7.1 and we have terrible performance problems:
    We have a mail sender adapter polling a mail account.
    Till the message is visible inside integration engine it takes sometimes 1-2 minutes or longer.
    We already tuned the j2ee-engine and checked the DB-indexes (there are some OSS Notes) - no success.
    We think that the problem is inside the DB-tables of Seeburger an that some indexes are missing (Oracle DB).
    Any ideas?
    Thanx
    regards
    Wolfgang Hummel

    Hi,
    I think in PI 7.1 SAP installed their own Java-VM (compatible with Sun 1.5) - is it true?
    Do you have the same performance problems inside the adapter?
    The adapter is like a black hole and it take sometimes one hour till you can see a message inside the integration engine (sxmb_moni).
    Regards
    Wolfgang

  • Adapter Engine / Integration Server Problem

    Hi,
    I'm new to SAP and I have some questions regarding my new PI 7.0 SP10 setup.
    Problem:
    In Integration Directory, when I tried to define a communication channel, after specifying the "Adapter Type" (File in my case), I had to specify the "Adapter Engine" from a drop-down. But the dropdown list is empty!
    What I've done & Observations:
    1. I've recently imported the file "XI7_0_SAP_BASIS_7.00_06_00.tpz" (From the installation DVD). After importing, I've refreshed the SLD cache.
    2. SLDCHECK reveals that the connection to SLD is successful.
    3. RWB component monitoring shows:
        Integration Server - No light (Node cannot be expanded)
        Integration Engines - No light (Node cannot be expanded)
        Non-Central Adapter Engines -
            Adapter Engine ootspdbs02 (Red Light)
              - Self Test Failed - Details: Client 010 is not available in this system.
              - Cache Connectivity Test:
                Attempt to fetch cache data from Integration Directory failed; cache could not be updated
                [Fetch Data]: Unable to find an associated SLD element (source element: SAP_XIIntegrationServer, [CreationClassName, SAP_XIIntegrationServer, string, Name, is.01.ootspdbs02, string], target element type: SAP_BusinessSystem)
        J2SE Adapter - No light (Node cannot be expanded)
        Tools
            - System Landscape Directory ootspdbs02 (Green Light)
            - Integration Directory ootspdbs02 (Green Light)
            - Integration Repository ootspdbs02 (Green Light)
            - Runtime Workbench ootspdbs02 (Green Light)
    4. In my SLD - I've defined a business system PI_BS_01
        Role: Integration Server
        Pipeline URL: http://OOTSPDBS02:8001/sap/xi/engine?type=entry
        Group - No Group Assigned.
        Client: 001 of PI1
        Technical System: PI1 on ootspdbs02 - Release 700
    Given the above observations, can anyone please point out to me where I went wrong?
    Any advise is greatly appreciated.
    Thank you.
    Best Regards,
    Ron Lai

    Hi Archana,
    The configuration in SLD DataSupplier is:
    Latest Send Activity               
         2007/01/04  09:18:09:564
    Used HTTP Parameters [http host:port] [user] [protocol]     
         [ootspdbs02:50100] [SLDDSUSER] [http]
    Sending Node [nodeID] [hostname]     
         [11621750] [ootspdbs02]
    Send Result     
         Success
    Next Automatic Send Timestamp     
         2007/01/04  21:18:08:189
    Send Type
         Automatic (Time Scheduled)
    Configuration Status     
         Valid
    The hierarchy of this business system is:
    Business System:
       BS_NAUTICUS_OOTS [Role = Application System, Related Integration Server = PI1_BS_01, Technical System = TS_NAUTICUS_OOTS]
    Technical System:
       TS_NAUTICUS_OOTS [Type = Third Party, Software Component = SWC_NAUTICUS_OOTS, Product = Product_NAUTICUS_OOTS]
    Basically I created product, software component, technical system, business system from scratch.
    I did not put any dependencies to existing products/software components.
    Regards,
    Ron

  • Performance problems with File Adapter and XI freeze

    Hi NetWeaver XI geeks,
    We are deploying a XI based product and encounter some huge performance problems. Here after the scenario and the issues:
    - NetWeaver XI 2004
    - SAP 4.6c
    - Outbound Channel
    - No mapping used and only the iDocs Adapter is involved in the pipeline processing
    - File Adapter
    - message file size < 2Ko
    We have zeroed down the problem to Idoc adapter’s performance.
    We are using a file channel and  every 15 seconds a file in a valid Idoc format is placed in a folder, Idoc adapter picks up the file from this folder and sends it  to the SAP R/3 instance.
    For few minutes (approx 5 mins) it works (the CPU usage is less then 20% even if processing time seems huge : <b>5sec/msg</b>) but after this time the application gets blocked and the CPU gets overloaded at 100% (2 processes disp_worker.exe at 50% each).
    If we inject several files in the source folder at the same time or if we decrease the time gap (from 15 seconds to 10 seconds) between creation of 2 Idoc files , the process blocks after posting  2-3 docs to SAP R/3.
    Could you point us some reasons that could provoke that behavior?
    Basically looking for some help in improving performance of the Idoc adapter.
    Thanks in advance for your help and regards,
    Adalbert

    Hi Bhavesh,
    Thanks for your suggestions. We will test...
    We wonder if the hardware is not the problem of this extremely poor performance.
    Our XI server is:
    •     Windows 2003 Server
    •     Processors: 2x3GHZ
    •     RAM: 4GB (the memory do not soak)
    The messages are well formed iDocs = single line INVOICES.
    Some posts are talking 2000 messages processed in some seconds... whereas we got 5 sec per message.
    Tnanks for your help.
    Adalbert

  • Problem With Seeing Message in Adapter Engine

    Hello Everyone,
    We are facing a strange problem while running an <b>Integration Process</b>, <b>BPM</b> in PI. In the process, we are trying to read a .CSV File and convert it into a .XML File via FCC. The .CSV file is placed in the XI box itself, under a certain directory. We have configured the process such that whenever the .CSV file is read, its attributes are set to <b>'read only'</b>. After configuring the process, the required XML file did not show up. So we checked that whether the .CSV file was read and it showed up attributes of 'read only'.We cross checked
        -First by going to <b>SXMB_MONI</b>; here it said 'No messages available for selection'
        -Then by examining the 'channel monitoring' in AE; where we found both the sender and receiver channel are showing green. The sender channel first shows up that <b>'Processing started'</b> and then <b>'Processing Completed Successfully'.</b> The receiver channel does not show up any messages.
        -we checked for the XML messages that are in the Adapter in <b>IDX5</b>; it shows <b>'no messages selected'</b>.
        -We anticipated that it may be a cache problem and cleared all the caches; but when we tried to clear the Adapter Framework Cache, it popped up an authorization error and the problem persisted.
    We are using NW2004s with SP6 at the ABAP and BASIS stack and SP 9 at the Java Stack. Also, all the required connections made in SM59 are in order.
    Now, <b>What can be the problem? Is it the difference in SP level that is causing the problem? Or is it something else? What have we missed?</b> Guys, please help us solve this problem.
    Need Help. Pleae Reply. Points will be awarded.
    Thanking in anticipation.
    Amitabha

    Hi Shabarish,
    1.Document name <b>is indeed</b> the name of message type in our case.
    2. We did not use delete mode; but once the file was read- we manually changed its attributes from 'RA' to 'A'..and it became 'RA' again after 2 seconds; which is our polling interval.
    3. And we have discovered that the file is being read properly..because we can see the XML payload of it and it contains the correct data.But still it does neither show up in SXMB_MONI..nor in IDX5.
    <b>Can you please tell us what are the necessary roles for the User PIAFUSER?</b> We suspect that somewhere's an authorization error we are getting; because the AF cache refresh attempt shows "Forbidden" and we are getting an error in Tcode SXI_SHOW_MESSAGE as:
    <b>AE_DETAILS_GET_ERROR: no_adapter_engine_found: Unable to find Adapter Engine:</b>; Stack trace shows:<b>Error while reading access data (URL, user, password) for the Adapter Engine</b>

  • JBBD Sender - Problem with Adapter Engine - Message status Delivering -

    Hi all,
    I've a rare problem. My scenario is JDBC (EO) to IDOC. If the SELECT query from SQL database arrows 8000 lines, the message was sent from PI to R/3 succesfully and Idocs was generated.
    But if the query is larger than 10.000 lines, the message was stopped in the sender queue in AE with status "Delivering". In SXMB_MONI I can't see the message, only in RW in Message Monitoring or Component Monitoring in Engine Status.
    I've applied note  Note 937159 - XI Adapter Engine is stuck, and follow this blog
    /people/kenny.scott/blog/2007/08/20/messaging-system-queue-properties-after-xi-30-sp19-xi-70sp11
    Using Configtool I modified these parameters (MaxConsumers). But message still puts in sender queue.
    I have in PI 7.1 SPs 0004.
    Any suggestions??
    Edited by: Pablete on Sep 13, 2010 8:41 PM

    I have the same requirement and for solving this, I have to apply a very complex select statement.
    But it works perfekt for MS SQL:
    select * from table where order_no in (SELECT distinct top(1000) order_no FROM table where any_clause) and any_clause order by order_no
    update table where invoice_no in (SELECT distinct top(1000) invoice_no FROM table where any_clause) and any_clause
    I create an IDoc for each order_no, so I have to make sure, that all lines belonging to one invoice are in the same select.
    My select statement has 463 characters

  • Performance Problem with File Adapter using FTP Conection

    Hi All,
    I have a pool of 19 interfaces that send data from R/3 using RFC Adpater, and these interfaces generate 30 TXT files in a target Server. I'm using File Adapters as Receiver Comunication Channel. It's generating a serious perfomance problem. In File Adpater I'm using FTP Conection with Permanently Conection, Somebody knows if PERMANENTLY CONECTION is the cause of performances problem ?
    These interfaces will run once a day with total of 600 messages.
    We still using a Test Server with few messages.

    Hi Regis,
        We also faced teh same porblem. Whats happening is that when the FTP session is initiated by the file adapter, then its getting done from teh XI server. Hence the memory of the server is also eaten up. Why dont you give a try by using 'per file transfer'.
        If this folder to which you are connecting is within your XI server network then you can mount(or map) that drive to the XI server and use it with a NFS protocol of the file adapter and thereby increasing the performance.
    Cheers
    JK

  • Problem posting message from adapter engine to IS

    Hello,
    We experience the next problem. We use JMS sender adapter to post message into XI. Message comes into the adapter engine and tries to post it into integration server. http://<host>:8000/sap/xi/engine?type=entry
    When posting we get the (very generic) error:
    Received HTTP response code 500..
    The Adapter engine does a retry every 5 minutes.
    After the 3th retry most of the status of the message in the adapter engine is set to NON_DELIVERED.
    However for what ever reason sometimes  the 2nd or 3th time the message does get processed to the IS.
    Is there anyone who experienced similar problems or does anyone know a solution for this.
    tnx
    Emile

    Hi,
    Is this the problem with JMS adapter or with any other Adapter.
    <b>8000</b>, is this the same port in smicm-->services. B'cos sometimes people might have a different instance number even.
    Cheers,
    Siva Maranani.

  • SOAP adapter engine with system error, problem with fault message.

    HI,
    I have IDOC -> PI -> SOAP scenario.
    Idoc to PI is async. I have no problem in receiving the idoc in PI. The message mapping is carried out and sent to the adapter engine. I can also see the technical routing payload. It is sucessful at XML monitoring in SXMB_MONI.
    The error is at PI -> SOAP.
    I have wsdl provided by the receiver webservice. Which I have imported.
    And created a service interface against this wsdl. I tried changing it to both sync and async.
    I have also provided fault message.
    I have set a receiver soap communication channel and provided the target URL like "http://xxx/services" and soap
    action = processDocument. Also provided user id and password.
    I have a
    Sender Agreement
    Receiver determination
    Interface determination
    Receiver Agreement
    I check in RWB adapter engine, this message goes to system error. The error log is as shown at the bottom.
    When I see the message content, the SOap document shows me the details about IDOC, Instead I feel it should match
    with the wsdl, where they have specified the corresponding interface name and address location etc.Please correct me.
    How does the receiver know which service interface is it? The Service Interface which I created in the ER is
    different from the WSDL, Does this have to be same? I see that the soap document in the adapter engine has the
    Service interface name which I created in the  ER. Where in the document the Reciever interface name is sent?
    Where can I see the generated soap document for the receiver?
    Is there some setting/configuration required in PI for this to work?
    I tried using the tcpgw to see the error. If I dont provide the service interface name in the communication channel
    then I get the following error in the TCPGW. "The service cannot be found for the endpoint reference"
    When I provide the service interface name in the communication channel I get a valid fault message.
    Similarly
    When I use SOAPUI, I can see the fault exception being return. The adapter engine doesnot show an equivalent message
    instead it goes into system error as shown at the bottom. I guess this is expected, if so what is the work around? (I found this weblog /people/alessandro.guarneri/blog/2011/01/10/soap-fault-in-sap-pi-hijack-it, do I need to implement this? Or use ALEAUD?
    The fault message what I see in SOAPUI has the below format.
    <soapenv:Fault xmlns:axis2ns1="http://schemas.xmlsoap.org/soap/envelope/">
             <faultcode>axis2ns1:Server</faultcode>
             <faultstring>nested exception is: psdi.util.MXApplicationException: BMXAA7136E - Validation failed when the
                                database default values were set. See the associated message for more information.
               BMXAA4190E - Country NZ is not in the value list.</faultstring>
             <detail>
                <Exception>org.apache.axis2.AxisFault: nested exception is: psdi.util.MXApplicationException: BMXAA7136E
                          - Validation failed when the database default values were set. See the associated message for more information.
         BMXAA4190E - Country NZ is not in the value list.
                /Exception>
             </detail>
      </soapenv:Fault>
    And the fault message in my ER service interface is stanadard datatype ExchangeFaultData, which is different from
    the above. Is this the problem? Can I change the data type here to be the same as above?
    Audit log in the RWB adapter engine.
    Time Stamp Type Description
    30.09.2011 15:10:57 Information MP: processing local module Localejbs/sap.com/com.sap.aii.af.soapadapter/XISOAPAdapterBean
    30.09.2011 15:10:57 Information SOAP: request message entering the adapter with user J2EE_GUEST
    30.09.2011 15:10:57 Information SOAP: completed the processing
    30.09.2011 15:10:57 Information SOAP: sending a delivery error ack ...
    30.09.2011 15:10:57 Information SOAP: sent a delivery error ack
    30.09.2011 15:10:57 Error MP: exception caught with cause
    com.sap.engine.interfaces.messaging.api.exception.MessagingException
    30.09.2011 15:10:57 Error Adapter Framework caught exception: null
    30.09.2011 15:10:57 Error Delivering the message to the application using connection
    SOAP_http://sap.com/xi/XI/System failed, due to:
    com.sap.engine.interfaces.messaging.api.exception.MessagingException.
    30.09.2011 15:10:57 Information The message status was set to WAIT.
    30.09.2011 15:10:57 Information The asynchronous message was successfully scheduled to be delivered at Fri Sep 30
    15:15:57 NZDT 2011.

    I tried changing it to both sync and async.
    I have also provided fault message.
    dont feel that you need to do above steps.
    I have a
    Sender Agreement
    ideally you dont need a sender agreement (and a channel) for IDOC --> PI flow.
    When I see the message content, the SOap document shows me the details about IDOC
    this is fine...you may see fields as seen in EDI_DC40 of the IDOC...
    How does the receiver know which service interface is it?
    receiver need not know about the SI created in PI.
    The Service Interface which I created in the ER is
    different from the WSDL, Does this have to be same?
    you should the WSDL (external definition) as the Request Message in your service interface.
    Is there some setting/configuration required in PI for this to work?
    nothing specific...AFAIK
    I have set a receiver soap communication channel and provided the target URL like "http://xxx/services" and soap action
    can you open the URL from Internet explorer...from your machine or from the machine which is in the same network as your PI server?
    Things to check:
    WSDL structure in PI and in target system is exactly the same.
    does the target system require mesage in SOAP format (SOAP envelope - SOAP Header + SOAP body)?
    target system is up and running?

  • FQDN problem in adapter engine,communication channel monitoring

    Hi all,
    Recently i configured FQDN for PI system while configuring END to END monitoring. Everything is going fine and end to end monitored worked smoothly.
    But Problem started in comminuication channel monitring.adapter engine status and others. Because its trying to retrieval the URl without FQDN and its showing an error as requested resource does not exist.
    I changed the exchange profile paramters also. But still i am afcing the problem.
    So,please suggest me to overcome from this issue.
    Regards
    Vijay

    /people/kenny.scott/blog/2009/03/08/pi-71-af-messaging-system-audit-log-persistence
    Did you tried this paramter even though the above is  applicable for PI 7.1
    Rajesh

  • Adavance Adapter  Engine Performance Tuning

    Hi all,
    We are using PI-7.11 .  We are working on an asynchronus scenario that reads JMS queue and  calls  server proxy at the receiver. The interface is configured  to bypass the ABAP stack(Integration server) by  using advance adapter configuration. The PI-7.11 supports Proxy through a soap apter at the receiver. All this works fine and problem we are facing is the message processing time. Currently we are getting  a throughput of 10 messages per second and each message of size 2k.  If we combine 100 such messages into a single message then we get a throughput of 50  single messages per second. To keep up the incoming messages on the sender queue, we need to process at least 30 messages per sec. Instead of packaging(combing) the messages , we  created a couple of communication channels to read the same JMS queue and simulated the multi-threading on reading the sender queue. The reason we are doing this because we do not  want write an intermediate process to package the messages from the source system.  The bottle neck we are seeing in  the RWB(Run time work bench) is the 'DispatchDisp' queue  in  the adapter engine. Based on the RWB display, this queue has single thread  and it can not keep up  with the multiple senders .  Anyone knows how this queue being used in the Advance adapter engine and how can we change this to multiple threads.  Is it used before calling the PI mapping  or after calling the mapping ? We are able to increase the number of consumer threads of other queues related to the JMS  queue in the adapter engine.
    Thanks in advance.
    Meghanth

    Hi Meghanth,
    From what i hear it sounds like you can push more into your adapter engine with the JMS sender then your SOAP receiver can process in the same time, right?
    The DispatchDisp Thread (1) is usually not the bottle neck, as far as i know the Dispatcher is just dedicated to dispatch messages to the receiver threads.
    If you see an accumulation there (i guess in Message Display Tool->Engine Status under Queues) its a typical sign, that your receiver Threads are all busy and cannot accept more at that time.
    How many Threads did you assign to your SOAP Receiver?
    Usually the possible count for throughput with the available Threads is easy to calculate that way:
    E.g. transfer to your ECC takes 200 ms (check your audit log steps) -> you can process about 5 / second / Thread ..with e.g. 5 Threads maximum 25/sec).
    You can try analyze this with the "old" MessagingSystem Monitoring, there are timestamps in milliseconds available. (http://<host>:<port>/MessagingSystem).
    According to that i d try to improve the count of your possible receiver threats..(take care that there are enought threads overall on your machine and the receiver ECC can take this).
    With best regards
                      Sebastian

Maybe you are looking for