Adapter engine calling IE failed

HI Friends,
In the adapter engine mesages are in 'to be delivered' state,audit log giving error as like url not correct. Recently some changes are done at the url level in the abap stack so messages at the sender adapter level are in error(to be delivered). i have compared the url in the sxmb_adm->intergration engine configuration and found these is mismatch in the url in the audit log error and in sxmb_adm. Please let us with am i checking at the right area or not?
and what i need to do next?
Regards,
Suresh.

Hi Suresh
You should have the following configuration in XI-sxmb_adm-Integration Engine Configuration .
Role of Business System  = Integration server
Corresponding Integ. Server = http://host:port/sap/xi/engine?type=entry
host = xi host
port = http port
for http port ...SMICM...goto....services..
Also URL should be same in integration server business system in SLD
Pipeline URL: http://host:port/sap/xi/engine?type=entry
port should be http port.
Regards
Abhijit

Similar Messages

  • Help!Cache status of object for Central Adapter Engine is incorrect

    this problem cconfused me several days!
    version:PI 7.1
    after i activate the communication channel, the cache not update for central adapter engine
    problem: in cache status overview, the update for central adapter engine not yet started, but notification is ok.
                     the update for integration server and mapping run time are all correct.
    then when i display wsdl for sender agreement(SOAP sender),  show message:Cache status of object abcd123 for Central Adapter Engine is incorrect
    if i ignore this message, error message popup:dapter Engine af.xid.sapittest for communication channel abcd123 not registered in SLD
    who can help me solve this problem.
    thank you in advance.

    Hi cheng,
    Kindly check if you have set theparameter 'com.sap.aii.connect.integrationserver.sld.name' in your
    Exchange Profile, since it's not set by default. Open note #1278563 and follow the procedures.
    And you may check the following notes:
    #1031321 - Self-Registration of Adapter Engine and RWB fails
    #1334053 - No automatic PI 7.10 SLD Registration (Here you'll see the note 764176 which you have already applied and also the note #1117249).
    In RWB, is the adapter Engine "red light"? If yes, what is the specific error?
    Regards,
    Caio Cagnani

  • Getting error in the adapter engine when sending a message

    Hi,
    I'm always getting this error in the adapter engine: Message processing failed. Cause: com.sap.aii.messaging.util.URI$MalformedURIException: no scheme
    The comm channel ends up in error because of messages having the above error.
    Could someone please help?
    Thanks.
    Mike

    Mike.
    Please check this links.
    Check your adapter and restarted.
    com.sap.aii.messaging.util.URI$MalformedURIException: invalid port number
    Re: Prerequisites to setup configure mail scenario.
    error in communication channel
    Error :Receiver File Channel not Initialized

  • Adapter Engine no register in SLD.

    Hi,
    The Adapter Engine not this registered in SLD-> Technical Systems -> Process Integration.
    The version in that we are working is:
    SAP_ABA          711     0004     SAPKA71104
    SAP_BASIS          711     0004     SAPKB71104
    PI_BASIS          711     0004     SAPK-71104INPIBASIS
    ST-PI          2005_1_710     0003     SAPKITLQJ3
    SAP_BW          711     0004     SAPKW71104
    Also we have applied the following SAP notes:
    1031321 u2013 Self-Registration of Adapter Engine and RWD fails
    764176 u2013 Error in XI inconsistent SLD content
    1278562 u2013 Specification of message server host in Exchange Profile
    Log:
    -     defaultTrace
    #2.0 #2010 03 10 13:17:37:097#+0100#Error#com.sap.nw.lm.aci.engine.base.sld.connection.AccSldConnector#
    #BC-AC-7XX#sap.com/tclmacienginebaselib05#005056911C95111C0000000100001234#7161750000045479#sap.com/tclmacimonitor~app#com.sap.nw.lm.aci.engine.base.sld.connection.AccSldConnector.getSldComputerSystemsForMonitoring(String)#AGUZMAN#0#SAP J2EE Engine JTA Transaction : [06d47ffffff96006d43]#2218C4902C1811DFCB06005056911C95#2218c4902c1811dfcb06005056911c95#2218c4902c1811dfcb06005056911c95#0#Thread[Managed_Application_Thread_21,5,Managed_Application_Thread]#Java##
    Unable to obtain Computer Systems, associated to NW Admin NWA_FOR_FirstLandScpSrvcName, from SLD. CIM_ERR_FAILED: No such instance: SAP_NWAdministrator.CreationClassName="SAP_NWAdministrator",Name="NWA_FOR_FirstLandScpSrvcName" [this message was repeated 60 times]
    [EXCEPTION]
    -     applications_00.1.txt
    #2.0 #2010 03 10 13:01:59:324#+0100#Error#/Applications/ExchangeInfrastructure#
    #BC-XI#com.sap.xi.util.misc#005056911C9500260000000C00001234#7161750000000001##com.sap.aii.ibdir.server.cache.monitoring.CacheMonitor####221828512C1811DF8ADA005056911C95#221828512c1811df8ada005056911c95#221828512c1811df8ada005056911c95#0#Timeout Service Synchronous Queue Processor#Java##
    No SLD elements of type SAP_XIAdapterFramework found
    Thrown:
    com.sap.aii.ib.bom.landscape.SLDElementNotFoundException: No SLD elements of type SAP_XIAdapterFramework found
    Thacks

    Hi,
    It follows without working.
    The connections with the SLD are correct
    SLD Connection Test
    Properties of RFC destination SAPSLDAPI
      RFC host:        %%RFCSERVER%%
      Program ID:      SAPSLDAPI_PID
      Gateway host:
      Gateway service:
    Testing RFC connection to the SLD java client...
    RFC ping was successful
    SLD destination settings:
      Alias:       SAP_CONFIG
      Host name:   SvFig2056
      Port number: 08100
      User:        SLD_CL_PID
    Testing HTTP connection to the SLD server...
    SLD ping was successful
    Connection to SLD works correctly
    http://svfig2056:8100/sap/xi/engine?type=entry
    - <SOAP:Envelope xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
      <SOAP:Header />
    - <SOAP:Body>
    - <SOAP:Fault xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
      <faultcode>SOAP:Client</faultcode>
      <faultstring>Empty HTTP request received</faultstring>
      <faultactor>http://sap.com/xi/XI/Message/30</faultactor>
    - <detail>
    - <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" SOAP:mustUnderstand="1">
      <SAP:Category>XIProtocol</SAP:Category>
      <SAP:Code area="MESSAGE">EMPTY_HTTP_REQUEST_RECEIVED</SAP:Code>
      <SAP:P1 />
      <SAP:P2 />
      <SAP:P3 />
      <SAP:P4 />
      <SAP:AdditionalText />
      <SAP:Stack>Empty HTTP query received; message processing not possible</SAP:Stack>
      </SAP:Error>
      </detail>
      </SOAP:Fault>
      </SOAP:Body>
      </SOAP:Envelope>

  • Messages are failed in Adapter Engine

    Hi Experts,
    give me solution as early as possible pls
    There is a problem with production system in XI.
    I am getting the error in Adapter Engine level in Runtime workbench.
    "Attempt to process file failed with
    com.sap.aii.adapter.file.configuration.DynamicConfigurationException: Error during variable substitution:
    com.sap.aii.adapter.file.varsubst.VariableDataSourceException: Caught SAXException while parsing XML payload:Fatal Error:com.sap.engine.lib.xml.parser.parserException: XMLparser: No data allowed here(:main:,row:,col:75)"
    The scenario is IDOC to JMS & File.
    There are 2 conditions
    if the data is coming from ECC is valid then Msg will go to the JMS
    other wise it will be dropped into File System.There is no problem with valid data.
    when ever invalid data will come 70% Messages are processed succefully and few Messages not processed.
    if i resend this error message 2 or 3 times it is processed succefully, iam getting huge number of messages like this,
    it is difficult to resend because if i select all Msg's it is not processed only one Msg will be processing when iam trying to re-send
    please can any body give me the permanent solution for it.
    Thanks & Regards
    Sankar

    Well,
    Take account the following considerations.
    1. Check your source code for the variable substitution(Maybe you can show us).
    2. check in the tab "Advanced" on you file adapter configuration, there are many checkBox, for example is you are replcainf the file name in you mapping The "File Name" check(in Adapter specific attributes) has to be checked, and if you are using other variables you need to do the same.
    I hope It helps you.
    Ivan

  • Auto restart of messages failed in Adapter Engine PI 7.0 and 7.1

    Hi,
    I am trying to figure out a way to automatically restart the messages failed with in the adapter engine (because of the target system not available etc.). These messages are in System Error status and I can restart them from RWB. But I am looking for any report or something available either on Java or ABAP engines so that I can automate the process.
    Thanks for the help.
    VJ

    I have come across the web service AdapterMessageMonitoring in PI 7.0 (Found it in Web service navigator) with possibly useful methods. But I could not find the same service on PI 7.1. Any clue on this?
    Also, the getMessageList methods works perfectly as expected but the resendMessages mehtod fails with the exception -
    com.sap.engine.services.ejb.exceptions.BaseEJBException xmlns:ns1="http://sap-j2ee-engine/client-runtime-error">Exception in method resendMessages.</ns1:com.sap.engine.services.ejb.exceptions.BaseEJBException>
    Will post more if move forward.
    VJ

  • Failed Messages In Adapter Engine in Pi 7.1 EHP1

    Hi All ,
    We have observed that Java stack AE  shows some error messages, but when we tried to open those failed messages, shows they were already processed successfully. And observed that this case is only happens in java stack only, we couldn't find any error messages in ABAP Stack moni. We thought this might be java stack issue.
    Please find the below screen shots attached for your reference,
    But above failed messages processed successfully in adapter engine please find below screen shot,
    ABAP Stack Moni: no messages .
    Regards ,
    Ravindar.a

    Hi ,
    Thanks for reply..
    Actually issue happened at that moment. But we were resend all the failed messages and they were processed successfully. We have observed no error messages found in ABAP stack MONI. In Java Stack adapter engine still observe the same error messages showing.

  • Outgoing messages failing in adapter engine

    Hi,
    I would like to know the cause of the following error which I frequently encounter in my Seeburger AS2 adapter engine for outgoing messages
    MIC not verified # MIC values not verified: QRP65LlObLvoGwZmMdIFpuXsvzA=-yqCovOQUkVWawfNVfSrXXaRRt8c=
    It appears only in the adapter engine and doesnt reflect as an error in RWB.
    We have already checked the certificate being used and found it to be valid.
    Would like to know the root cause of this.
    Thanks in advance

    MIC is the message digest sent by the receiver AS2 system as a part of MDN to acknowledge the status of sent message. This is used by sender for non-repudiation of sent message. This message indicates some problem in the message sent. The point of this verification is the at sender system. This is not exactly XI related problem.
    Found a similar problem in Seeburger guides but this is related to authentication failure
    Outbound: MIC not verified # authentication-failed, processing continued
    Cause:
    An incorrect signing certificate is being was used, but the trading partner continued with the
    processing, because it doesnu2019t matter, if the message is authenticated, or not.
    Solution:
    Check the signing certificate configuration.
    Regards,
    Prateek

  • Java program to restart failed message in Adapter Engine

    Hi,
    I am using PI 7.0.
    Could anyone tell me whether there is an automated job or URL I can schedule in order to periodically resend messages sitting in the Adapter Engine receive queue that are in status System Error, Holding, or Waiting?
    I want to avoid having to monitor the system through message monitoring and manually resending the messages...
    Many thanks
    Brian

    Hi,
    please check this link:
    http://help.sap.com/saphelp_nw04/helpdata/en/05/b1b740f83db533e10000000a155106/content.htm
    Restarting
    Instead of restarting messages with errors manually with message monitoring, you can schedule a job to automatically restart these messages. This is possible for all messages for which the number of defined restart attempts has been exceeded (messages with the System Error status).
    You can define one or more rules for each job to restart messages; these rules contain conditions that a message must meet in order to be restarted by the job. At least one of the defined rules must be met for archiving to take place.
    Rescheduling
    A standard job to reschedule messages is created automatically. The job runs once a day and ensures that messages lost as a result of database failure, for example, are rescheduled. You can schedule additional rescheduling jobs; however, you cannot define rules for them.

  • Resend Message that fails in adapter engine but shows success in sxmb_moni

    Hello SDN!!
    We are testing sending soap requests out via SSL. We are using a BEA as a pass through server for SSL encryption only.
    The scenerio is to send a message from SAP to PI 7.1 to BEA (SSL enc) to Receiving System. We successfully connect to BEA (only used as a pass-through) but the connection to Receiving System does not work. This returns an error to our adapter engine.
    My question is this, Since SXMB_MONI shows the message as successful, but the adapter engine is showing an error. What is the best way for
    1. Monitor the errors, (I only see where you can monitor the type of adapter only)
    2. Resend the message, since it shows valid in SXMB_MONI, it won't let me resend.
    Any help will be greatly appreciated and awarded
    Cheers
    Devlin

    1. Once the message is in successful status in moni, the best way to monitor becomes RWB -> Message Monitoring.
    2. For adapter engine related errors, you may resend the data manually using the resend option in the Message Monitoring. Otherwise, for automatic retry of messages, you may change the default settings.
    Regards,
    Prateek

  • RWB-Adapter Engine-Monitoring calling url of shorthost name

    Hi,
    I am familiar with where to set the domain name or short names for XI within the various connection settings
    in the Exchange Profile. Does anyone know where the adapter engine monitor settings are stored? We are suddenly getting errors for http://host:52100/mdt/AmtServlet but if I put the FQDN in a new browser window it works fine. But the developers
    here are unable to post to the adapter....
    Thanks so much in advance...
    Jim

    Hi James,
    FQDN is essential not only for RWB but for other components of WAS as well. Launch XI page wiht sxmb_ifr and check if it displays FQDN. Else follow the complete FQDN activation procedure as below.
    1. In RZ10, add the parameter icm/host_name_full in instance profile.
    2. Restart your system and follow note 764176 for changing SLD associations. This is important.
    3. For adapter engine, apply note 804124.
    Follow the complete procedure.
    Regards,
    Youvraj

  • J2ee Adapter engine installation error

    Hi All,
    I am installing XI with NW07. I had an ERP2005 server here with ABAP only. I installed Java Add In to it with usage type PI.
    Now I tried to install J2ee adapter engine. It showed if i want to run a new installation or continue the old one.
    I tried to install installation of J2ee adapter engine from a new directory.
    It is stuck in between. I choose it as a MCOD to existing DB.
    I can see a new instance for this in MMC and it is up and running.
    But the old java instance is not running. None of the Proceses of Old Java instance (dispatcher, server0 and SDM) are not running. Did I do something wrong?
    My JVM_BOOTSTRAP.OUT says this:-
    Exception occurred:
    com.sap.engine.frame.core.configuration.NameNotFoundException: A configuration with the path "cluster_data/dispatcher/ID4065200" does not exist.
    at com.sap.engine.core.configuration.impl.ConfigurationDataCacheAllImpl.getSubConfiguration(ConfigurationDataCacheAllImpl.java:107)
    at com.sap.engine.core.configuration.impl.ReadAccessConfiguration.getSubConfiguration(ReadAccessConfiguration.java:715)
    at com.sap.engine.bootstrap.Synchronizer.getConfiguration(Synchronizer.java:426)
    at com.sap.engine.bootstrap.Synchronizer.getElementType(Synchronizer.java:72)
    at com.sap.engine.bootstrap.Bootstrap.initDatabaseConnection(Bootstrap.java:420)
    at com.sap.engine.bootstrap.Bootstrap.<init>(Bootstrap.java:144)
    at com.sap.engine.bootstrap.Bootstrap.main(Bootstrap.java:814)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:324)
    at com.sap.engine.offline.OfflineToolStart.main(OfflineToolStart.java:81)
    Exception occurred:
    com.sap.engine.bootstrap.SynchronizationException: Database initialization failed! Check database properties!
    at com.sap.engine.bootstrap.Bootstrap.initDatabaseConnection(Bootstrap.java:422)
    at com.sap.engine.bootstrap.Bootstrap.<init>(Bootstrap.java:144)
    at com.sap.engine.bootstrap.Bootstrap.main(Bootstrap.java:814)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:324)
    at com.sap.engine.offline.OfflineToolStart.main(OfflineToolStart.java:81)
    == Caused by: ==----
    com.sap.engine.bootstrap.SynchronizationException: No such Dialog Instance (ID4065200) in the database! Check database consistency or local Bootstrap properties!
    at com.sap.engine.bootstrap.Synchronizer.getElementType(Synchronizer.java:75)
    at com.sap.engine.bootstrap.Bootstrap.initDatabaseConnection(Bootstrap.java:420)
    at com.sap.engine.bootstrap.Bootstrap.<init>(Bootstrap.java:144)
    at com.sap.engine.bootstrap.Bootstrap.main(Bootstrap.java:814)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:324)
    at com.sap.engine.offline.OfflineToolStart.main(OfflineToolStart.java:81)
    Bootstrap module> Problem occurred while performing synchronization.
    My dev_jcontrol.b00 shows:-
    JControlStartJLaunch: program = C:\usr\sap\IDE\DVEBMGS00\exe\jlaunch.exe
    -> arg00 = C:\usr\sap\IDE\DVEBMGS00\exe\jlaunch.exe
    -> arg01 = pf=C:\usr\sap\IDE\SYS\profile\IDE_DVEBMGS00_sapides
    -> arg02 = -DSAPINFO=IDE_00_bootstrap
    -> arg03 = -nodeId=-1
    -> arg04 = -file=C:\usr\sap\IDE\DVEBMGS00\j2ee\cluster\instance.properties
    -> arg05 = -syncSem=JSTARTUP_WAIT_ON_5284
    -> arg06 = -nodeName=bootstrap
    -> arg07 = -jvmOutFile=C:\usr\sap\IDE\DVEBMGS00\work\jvm_bootstrap.out
    -> arg08 = -stdOutFile=C:\usr\sap\IDE\DVEBMGS00\work\std_bootstrap.out
    -> arg09 = -locOutFile=C:\usr\sap\IDE\DVEBMGS00\work\dev_bootstrap
    -> arg10 = -mode=BOOTSTRAP
    -> arg11 = pf=C:\usr\sap\IDE\SYS\profile\IDE_DVEBMGS00_sapides
    -> arg12 = -DSAPSTART=1
    -> arg13 = -DCONNECT_PORT=4740
    -> arg14 = -DSAPSYSTEM=00
    -> arg15 = -DSAPSYSTEMNAME=IDE
    -> arg16 = -DSAPMYNAME=sapides_IDE_00
    -> arg17 = -DSAPPROFILE=C:\usr\sap\IDE\SYS\profile\IDE_DVEBMGS00_sapides
    -> arg18 = -DFRFC_FALLBACK=ON
    -> arg19 = -DFRFC_FALLBACK_HOST=localhost
    -> lib path = PATH=C:\j2sdk1.4.2_09\jre\bin\server;C:\j2sdk1.4.2_09\jre\bin;F:\oracle\IDE\102\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\j2sdk1.4.2_06\bin;C:\j2sdk1.4.2_06\lib;C:\usr\sap\IDE\SYS\exe\uc\NTI386
    -> exe path = PATH=C:\j2sdk1.4.2_09\bin;C:\usr\sap\IDE\DVEBMGS00\j2ee\os_libs;F:\oracle\IDE\102\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\j2sdk1.4.2_06\bin;C:\j2sdk1.4.2_06\lib;C:\usr\sap\IDE\SYS\exe\uc\NTI386
    Thr 4232 Tue Sep 16 17:48:04 2008
    Thr 4232 *** ERROR => invalid return code of process bootstrap (exitcode = 66) http://jstartxx.c 1642
    Thr 4232 JControlExecuteBootstrap: error executing bootstrap node bootstrap (rc = 66)
    Thr 4232 JControlCloseProgram: started (exitcode = 66)
    Thr 4232 JControlCloseProgram: good bye... (exitcode = 66)
    My DEV_BOOTSTRAP.B00 shows:-
    Thr 5984 Tue Sep 16 17:48:02 2008
    Thr 5984 JHVM_RegisterNatives: registering methods in com.sap.bc.krn.perf.PerfTimes
    Thr 5608 Tue Sep 16 17:48:04 2008
    Thr 5608 JLaunchIExitJava: exit hook is called (rc = 66)
    Thr 5608 **********************************************************************
    u2022     
    o     
         ERROR => The Java VM terminated with a non-zero exit code.
         Please see SAP Note 943602 , section 'J2EE Engine exit codes'
         for additional information and trouble shooting.
    Thr 5608 JLaunchCloseProgram: good bye (exitcode = 66)
    I ran the prerequisite checks before starting the installation.
    It shows everything ok except it told me to have a environmental variable as CPIC_MAX_CONV with the value 200 at least. And I did that.
    All the other checks were ok.
    All are on SAME OS and same machine.
    I have J2EE Adapter Engine installation guide, but there is nothing for this in that
    In Instance properties file for the old instance it is showing the instance ID which it is not able to find.
    In the configtool of both the instances, the instance ID is same under cluster_data and this is of the newer instance
    How did the instance ID and data got replaced in the configtool of old instance. I mean the new instance has its new directory or folder.
    What Could be the problem?
    Did I do anything wrong here?
    Kindly help

    Hi,
    Check out the SNote 997510, " Note 997510 - Troubleshooting
    J2EE Engine 6.40/7.0 Bootstrap Issues ".
    I hope it will help you to drill more in to the problem
    Rgds
    Radhakrishna D S

  • PI 7.1 SOAP Adapter - Message Payload for Failed Messages - Where to find

    We are exposing a webservice through SAP PI.  Occassionaly we have customers calling our webservice and some failure occurs.  The error is usually the way that the customer is calling the webservice (missing elements, misnamed tags, bad content in the WS payload..).  Generally in these cases we can see the error in communication channel monitoring. 
    Here is an example:
    12/12/11 4:39:07 PM   com.sap.engine.interfaces.messaging.api.exception.MessagingException: com.sap.engine.interfaces.messaging.api.exception.MessageFormatException: cvc-complex-type.2.4.b: The content of element 'SupplierInvoice' is not complete. One of '{"":Invoice}' is expected. at line 1, column 227
      12/12/11 4:39:06 PM   request received for a channel
    I understand the issue, but it would be extremely helpful to have the full SOAP Envelope and Payload of a request when it fails.  The communication channel will show a SUCESSFUL message payload with a link to it.  But it does not show a failed one.
    Where can I find the FAILED payload that accompanies this message?  These failures occurs before any mapping or being seen in RTWB Adapter Engine message monitoring...  I did some searching around, but did not find anything offhand.  I would greatly appreciate any pointers from anyone who has crossed this bridge.

    Hi,
    When the web service is being called by external application, the first point of contact would be the sender communication channel which converts the SOAP message into XML message and pass to integration engine ( In case of success )
    But if the web service call fails due to WSDL validation, Authentication issue, Bad content, invalid content type, you would not see the payload in the sender communication channel or in Adapter engine. You can just see error message in the sender communication channel . I have experienced this many times and i always ask the web service team to provide the SOAP message for validation/investigation purpose.

  • Messages got stuck in inbound adapter engine queue

    Hi Experts,
    My senario is File - XI -SAOP reciever and we have 8 usecases of same type. For 7 usecase, we dont have any problem. But for only one use case we have having heavy delay in processing messages.
    All  my messages got stuck in inbound queue of Adapter engine in to be delivered state, wait state, delivering state.
    Please see the below logs and suggest some solution.
    To be delivered Message log  :
    Time Stamp Status Description
    2008-06-30 06:54:20 Success Processing child message of multi-message with message ID 8c597510-466f-11dd-92f9-000f203c93e0
    2008-06-30 06:54:20 Success Using connection AFW. Trying to put the message into the receive queue.
    2008-06-30 06:54:20 Success Message successfully put into the queue.
    Waiting Message log :
    Audit Log for Message: 4864ad2b-cabd-5891-e100-00000aa3fdb2
    Time Stamp Status Description
    2008-06-30 06:42:24 Success Processing child message of multi-message with message I
    2008-06-30 06:42:24 Success Using connection AFW. Trying to put the message into the receive queue.
    2008-06-30 06:42:24 Success Message successfully put into the queue.
    2008-06-30 07:46:16 Success The message was successfully retrieved from the receive queue.
    2008-06-30 07:46:16 Success The message status set to DLNG.
    2008-06-30 07:46:16 Success Delivering to channel: CC_SOAP_Receiver
    2008-06-30 07:46:16 Success SOAP: request message entering the adapter
    2008-06-30 07:51:24 Success SOAP: call failed
    2008-06-30 07:51:24 Success SOAP: sending a delivery error ack ...
    2008-06-30 07:51:24 Success SOAP: sent a delivery error ack 
    2008-06-30 07:51:24 Error SOAP: error occured: java.net.SocketTimeoutException: Read timed out
    2008-06-30 07:51:24 Error Exception caught by adapter framework: Read timed out
    2008-06-30 07:51:24 Error Delivery of the message to the application using connection AFW failed, due to: Read timed out.
    2008-06-30 07:51:24 Success The asynchronous message was successfully scheduled to be delivered at Mon Jun 30 07:56:24 GMT 2008.
    2008-06-30 07:51:24 Success The message status set to WAIT.
    Delivering Message log :
    Audit Log for Message: 4864ad2d-cabd-5891-e100-00000aa3fdb2
    Time Stamp Status Description
    2008-06-30 06:42:24 Success Processing child message of multi-message with message ID 7481f110-466f-11dd-b8ce-000f203c93e0
    2008-06-30 06:42:24 Success Using connection AFW. Trying to put the message into the receive queue.
    2008-06-30 06:42:24 Success Message successfully put into the queue.
    2008-06-30 07:46:24 Success The message was successfully retrieved from the receive queue.
    2008-06-30 07:46:24 Success The message status set to DLNG.
    2008-06-30 07:46:24 Success Delivering to channel: CC_SOAP_Receiver
    2008-06-30 07:46:24 Success SOAP: request message entering the adapter
    2008-06-30 07:51:24 Success SOAP: call failed
    2008-06-30 07:51:24 Success SOAP: sending a delivery error ack ...
    2008-06-30 07:51:24 Success SOAP: sent a delivery error ack 
    2008-06-30 07:51:24 Error SOAP: error occured: java.net.SocketTimeoutException: Read timed out
    2008-06-30 07:51:24 Error Exception caught by adapter framework: Read timed out
    2008-06-30 07:51:24 Error Delivery of the message to the application using connection AFW failed, due to: Read timed out.
    2008-06-30 07:51:24 Success The asynchronous message was successfully scheduled to be delivered at Mon Jun 30 07:56:24 GMT 2008.
    2008-06-30 07:51:24 Success The message status set to WAIT.
    Thank you
    Subbu

    Dear Subramanyam,
    Some message might be struck in the queue. Because of this reason furthur processing is not performed on time.
    Please try to do like this:
    Go to SXMB_MONI, or SXi_monitor, select QueueID in the row, which is showing green flag. In the next window belongs to queue select the queue and press unlock button on the panel.
    This could possibly release the queue which is struck.
    Best Regards
    Praveen

  • Messages got stuck in Adapter engine

    We are doing http to RFC sysnchronous scenario
    Message got stuck in adapter engine.so we are getting 500 HTTP timeout error in Http client.
    Please help us to find why messages got stuck in Adapter engine.
    Below Adapter engine audit log message is pasted for your reference.
    Audit Log message:
    Time Stamp Status Description
    26.09.2008 06:33:54 Success Message successfully received by messaging system. Profile: XI URL: http://devsap01:51000/MessagingSystem/receive/AFW/XI Credential (User): PIISUSER
    26.09.2008 06:33:54 Success Using connection RFC_http://sap.com/xi/XI/System. Trying to put the message into the request queue.
    26.09.2008 06:33:54 Success Message successfully put into the queue.
    26.09.2008 06:33:54 Success The message was successfully retrieved from the request queue.
    26.09.2008 06:33:54 Success The message status set to DLNG.
    26.09.2008 06:33:54 Success Delivering to channel: RFC_out_Test
    26.09.2008 06:33:54 Success MP: entering
    26.09.2008 06:33:54 Success MP: processing local module localejbs/RfcAFBean
    26.09.2008 06:33:54 Success RFC adapter received a synchronous message. Attempting to send sRFC for ZFTestRFC
    26.09.2008 06:33:54 Success RFC adapter received a synchronous message. Attempting to send sRFC for J2EE_GUEST
    ime Stamp Status Description
    26.09.2008 06:56:15 Success MP: leaving
    26.09.2008 06:56:15 Error Delivery of the message to the application using connection RFC_http://sap.com/xi/XI/System failed, due to: com.sap.aii.af.ra.ms.api.MessageExpiredException: Sync application request expired.. Setting message to status failed.
    26.09.2008 06:56:15 Error The message status set to FAIL.
    26.09.2008 06:56:15 Error Returning synchronous error message to calling application: com.sap.aii.af.ra.ms.api.MessageExpiredException: Sync application request expired..
    Kindly advise us on this issue.

    Hi krish,
           when i send a http request it got stuck in adapter engine with status "delivering" for some time....
    We found that RFC got successfully executed in R/3 system but the synchronous message is not delivered to PI.since adapter engine message is having status "delivering"
    after some time we got adapter engine message status as "cancelled with error"
    Error is Message expired exception which you can see audit log message I have pasted in my previous post.
    Meanwhile we also got HTTP timeout error in Http client.
    Could you please tell me why it got stuck in Adapter engine with status "delivering" since RFC is executed successfully.
    Why we are not getting synchronous message reply back to PI?

Maybe you are looking for