SOAP synchronous channel specific call time out configuration

Hi,
This is regarding channel specific timeout configuration in SOAP sender and receiver channel.
We are having SOAP to Proxy synchronous web services. One of the web service is taking longer to execute the RFC's in ECC and getting the results back to PI.
The error we are getting is Message Expired in soap ui and PI logs.
When I checked the execution time it says 301165 ms from soap ui.
The default setting of XI is 180000 ms i.e 3 mins.
I configured channel specific time out in both sender and receiver channels. Now the configuration has timeout of 600000 ms. Below is the screen shot.
SENDER:
RECEIVER:
But still the message is getting timed out and below is the error:
Unable to contact target server XXXXXXXX:8000 after 1 tries.
Below is the error log from PI :
Please suggest the solution. I am not sure whether its actually taking the specific configured time.
Thanks,
Vertika

Hi Vertika,
Please check
SAP Note 1660913 - SOAP/XI Adapter - XI.Timeout parameter support in 7.30+
For soap sender channel
SAP Note 1644846 - Parameter syncTimeout doesn't work under SOAP sender channel
regards,
Harish

Similar Messages

SOAP TO RFC SYNC call time out

Hi,
Did anyone know how to set the rfc timeout? I try to set it at visual admin but it didn't work. Is that others place to set it?
Thanks.

Hi,
Thanks for respond. This is what i set on visual admin but seem it not work. For testing i put the value 10 after restart the adapter and test it the function still respond after 10ms.
thanks.

Time out configuration in SAP ME

Hi, I would like to know how to define the time out in ME ? Is it something we can configure or is it a default value we cannot change ?
Thanks for Help,
Michaël.

Michael,
okay, now I see what you need. It is HTTP session timeout for /manufacturing web-module, as far as I understand. It is set to 30 min by default and can be changed, though I never heard about any recommendations to do so. Hence, it will be up to you to try adjusting this setting.
You can check/modify timeout in Netweaver Administrator -> Configuration Management -> Infrastructure -> Application Modules. Find Web Module called "manufacturing", and below, in Web Module Details, go to Context tab. There is a Session Timeout parameter, it is 30 by default, though you can try and change it to something else (e.g. for manufacturing-services it is set to 60 by default).
Regards,
Anton

Time-Out Configuration in EP6?

Hi,
it´s possible to change the time-out for a user in EP6.0?
Best regards
Christian

If you are thinking of like the idle time out in R/3, then no. However... you can set how long the saplogonticket (non-persistant cookie) is valid for. As default this is 8 hours. If you reduce it to 2 hours for example, then any user still in their session after two hours will have to re-authenticate.
Paul

Reg:Normal Webservice call TIME OUT(SocketTimedOut Exception)

Hi All,
   I am using a normal WebService Model to access TIBCO Webservcie. when Services are DOWN, i am getting Exceptions and showing that Servcie is down.
if a request is not completed for long time we are Getting "SocketTimedOut Exception"
for this is there any place to set increase or decrease the TIME.
Please help me
Thanks
Nagaraju

Hi Nagaraju,
Try the InvocationModifier below. It worked for Adaptative Web Service Models.
import com.sap.tc.webdynpro.model.webservice.api.IWDWSInvocationModifier;
YourModel yourModel = new YourModel();
//Request structure
request_GetTransfers = new Request_GetTransfers(yourModel );
//Change request's default socketTimeout to the value you want to (in miliseconds).
request_GetTransfers.wdSetInvocationModifier(new IWDWSInvocationModifier() {
     public void doModifyInvocation(Object port) {
          HTTPControlInterface httpItf = HTTPControlFactory.getInterface(port);
          httpItf.setSocketTimeout(180000);
     public void doModifyAfterInvocation(){}
Regards,
Douglas Frankenberger

Time out - SOAP Receiver Channel

Hi All,
My Scenario is Database --> PI (7.1) --> SOAP (synchronous) .
The WebService is taking around 15 mins for giving the Response back to PI SOAP Adapter.But, because of Time Out at the PI SOAP Receiver adapter , I am getting "INBOUND EXPIRED" error.
I referred the following links and tried to Increase the time out value in the SOAP Receiver communication channel - Module Parameters.But, this is not working.
1. Note : 856597
2.XMBWS.Timeout in soap receiver channel not working
Can you please let me know if there any possible approach to increase the time out for SOAP Receiver Channel ?
Thanks and regards,
Midhusha.

Hi,
Have a look to below discussions
XMBWS.Timeout in soap receiver channel not working
SOAP Receiver communication channel Error
Timeouts in SOAP Receiver Adapter
Regards
Aashish Sinha

Problem with Synchronous abap proxy time out

Hi there.
I have the following scenario:
                  sync                   sync
3rd party <--> PI    <--
> ERP
                   http                    abap proxy
In the implementing class on the abap proxy i'm calling an standard BAPI, followed by a commit and returning the result.
The 3rd party app has a mechanism that when a message fails, he'll retry each 5 mins until it gets the response.
Last night there where some delays on ERP that cause the sync mesages to timeout, the 3rd party retried about 10 times to send the message until it finally went off. This morning i check and i have the same message 11 times on ERP!!, to my understanding if the sync comm timed out the process will abort and the message will not be processed on ERP, does anybody knows if im missing some configuration for this to work this way??.
Kind Regards,
Roberto.

Hi Roberto.
There are a lot of time out configures in PI .
Follow the link that explain about this:
How to Investigate Timeouts In Synchronous XI PI Scenarios
http://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/c059d583-a551-2c10-e095-eb5d95e03747
I hope to help you.
If you still keep this problem, you can ask me more about it.
Regards..
Bruno.

ERROR During call of SOAP with a SOAP- RFC- SOAP Synchronous scenario

Hello Experts,
I've recently created a SOAP->RFC->SOAP synchronous scenario but every time I'm invoking the SOAP via XMLSpy then i will hang and send a timeout error. Also a log in XI was generated as shown below.
I hope you could help me on this one.
Runtime Errors         DBIF_RSQL_SQL_ERROR
Exception              CX_SY_OPEN_SQL_DB
Date and Time          28.09.2010 09:31:23
Short text
     SQL error in the database when accessing a table.
What happened?
     The database system detected a deadlock and avoided it by rolling back
     your transaction.
What can you do?
     If possible (and necessary), repeat the last database transaction in the
      hope that locking the object will not result in another deadlock.
     Note which actions and input led to the error.
     For further help in handling the problem, contact your SAP administrator
     You can use the ABAP dump analysis transaction ST22 to view and manage
     termination messages, in particular for long term reference.
     Note which actions and input led to the error.
     For further help in handling the problem, contact your SAP administrator
     You can use the ABAP dump analysis transaction ST22 to view and manage
     termination messages, in particular for long term reference.
Error analysis
     An exception occurred that is explained in detail below.
     The exception, which is assigned to class 'CX_SY_OPEN_SQL_DB', was not caught
      in
     procedure "DELETE_LUW_PACKET" "(FORM)", nor was it propagated by a RAISING
      clause.
     Since the caller of the procedure could not have anticipated that the
     exception would occur, the current program is terminated.
     The reason for the exception is:
     The database system recognized that your last operation on the database
     would have led to a deadlock.
     Therefore, your transaction was rolled back
     to avoid this.
     ORACLE always terminates any transaction that would result in deadlock.
     The other transactions involved in this potential deadlock
     are not affected by the termination.
Regards,
Alfred

Normally such an error comes when the DB of SAP PI is full.
Contact your BASIS or ADMIN team and ask them to free the DB space.
Regards,
Abhishek.

RCA Connection Pool idle Time-Out takes no effect !

My question description goes here.
According to JCA specification, I developed my 'ManagedConnectionImpl' class from the interface 'ManagedConnection'. I realize the 'destroy()' function to send out logout request to the EIS.
Then I deployed the connector in Sun Java System Application Server, I noticed there are two parameters in Connection Pool part, they are:
1. Idle Timeout. It said it's the maximum time that a connection can remain idle in the pool. I assume the connection will be removed after the specific time expired and before it's removed it will call the recallable function, 'destroy()', in my concrete class, 'ManagedConnectionImpl'.
2. Pool Resize Quantity. it said it's number of connections to be removed when pool idle time expired.
I am weird about it. I think EIS had itself session control strategy, if the specific session time-out expired, it will invalidate this session. So I think we will set 'Idle Timeout' in application server to be shorter than the EIS session time-out. If the 'Idle Timeout' in application server expired, it should remove all connections inside otherwise maybe the connection with invalid session will exist! (the background knowledge is our system will return back soap fault when it meets invalid session, so the invalid connections will not be removed by switching on your configuration item, 'On Any Failure')
So I set "inital and minimum pool size" to 8, "maximum pool size" to 32 and "Pool Resize Quantity" to 32. (I expect AS to remove all when pool idle time expired)
After deploying, I send out requests at the first round and wait for the time expired but I can't see the desired logout requests from pool automatically even one. Firstly I guess if my recallable function definition is wrong but when I shut down the Application Server, the desired logout requests are sent out from pool automatically. So I think my recallable function definition is workable.
What's your comments on it?
P.S.
I am using Sun Java System Application Server 8.1.
Thanks in advance!
BRs
/Leo

I have had following test to ensure I sent out notification to listener.
[#|2005-08-23T16:14:25.061+0800|INFO|sun-appserver-pe8.1_01|javax.enterprise.system.stream.out|_ThreadID=12;|
It's in managed env!|#]
[#|2005-08-23T16:14:25.062+0800|INFO|sun-appserver-pe8.1_01|javax.enterprise.system.stream.out|_ThreadID=12;|
enter matchManagedConnections() !|#]
[#|2005-08-23T16:14:25.062+0800|INFO|sun-appserver-pe8.1_01|javax.enterprise.system.stream.out|_ThreadID=12;|
try to find a matching and existing one, reuse it!|#]
[#|2005-08-23T16:14:25.062+0800|INFO|sun-appserver-pe8.1_01|javax.enterprise.system.stream.out|_ThreadID=12;|
Found a matching and existing one, reuse it!|#]
[#|2005-08-23T16:14:25.495+0800|INFO|sun-appserver-pe8.1_01|javax.enterprise.system.stream.out|_ThreadID=12;|
tearDown() is called, the application-level connection is released!|#]
[#|2005-08-23T16:14:25.496+0800|INFO|sun-appserver-pe8.1_01|javax.enterprise.system.stream.out|_ThreadID=12;|
enter calling close() of managed connection.|#]
[#|2005-08-23T16:14:25.496+0800|INFO|sun-appserver-pe8.1_01|javax.enterprise.system.stream.out|_ThreadID=12;|
Start calling close() of managed connection.|#]
[#|2005-08-23T16:14:25.496+0800|INFO|sun-appserver-pe8.1_01|javax.enterprise.system.stream.out|_ThreadID=12;|
start to notify the listener the completeness of connection.|#]
[#|2005-08-23T16:14:25.496+0800|INFO|sun-appserver-pe8.1_01|javax.enterprise.system.stream.out|_ThreadID=12;|
notify the listener the completeness of connection successfully.|#]
Whether it's related with the initial and minimum number parameter? Although I found it will not be created during AS start-up and will be created at the first request.
Whether it shall be kept to meet the minimum requirement? I have failed to set it to 0.

Receiver SOAP Communication channel -- Target URL

Hi Experts,
Can anyone provide some inputs for my below question?
How the receiver SOAP Communication channel internally calls the Target URL?
What is the internal process behind this call?
I would really appreciate you all if could provide answers.
Thanks & Regards,
Prabu Muthu

Hi...
To be able to send SOAP messages from the Integration Server/PCK to remote clients or Web service servers, you must first configure the receiver SOAP adapter. The receiver adapter supports system acknowledgments but not application acknowledgments
Find the below link .
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/40611dd6-e66e-2910-f383-e80fb44f9cd4
Regards,
Leela

SOAP Adapter: Connection time out error

Hi Guys,
I do it one scenario for Proxy to webservice Asynchronous . I have send the input details through Proxy. In Sxmb_Moni shows success message. But Receiver side doesn't reach the payload. Because receiver side (Soap Adapter) shows connection time out error. But i have given correct URL and SOAP Action in receiver communication channel. Please give some suggestions to solve that issues. Please don't refer links.
Thanks & Regards
Vijay

hi
this is a time out error
increase the timeout value by specifying the parameter
XI.Timeout in the module parameter of soap Adapter
OR
1. This is because of TimeOut. The default timeout value for synchronous calls is 5
minutes. You can increase this value by setting parameter XI.Timeout in the module parameter table of
the SOAP adapter. The value must be given in milliseconds. For example, value 600000
represents the timeout value of 10 minutes. This parameter is not recognized in systems prior to SP13.
2.The Other Options is send the queue id with your request message.
http://host:port/XISOAPAdapter/MessageServlet?channel=p:s:c
&version=3.0&...&QueueId=xxxxxxxxxxxxxxxx
where xxxxxxxxxxxxxxxx is an ABAP queue ID.
3.Check your RWB message monitoring.
Is there any system failure message and holding message be there.
If then clear the messages.
4. Increase the time out parameter for HTTP in your altova xml spy.Defaultly it will be very low.

Time out error in receiver soap adapter

Hi,
My scenario is file to soap file with out BPM.I am using a currency converter wsdl.
I am getting a time out error in soap receiver channel.
Do i need to change the time out parameter?Where do i change that?Please help me to solve it out.
Following are the errors in the soap communication channel.
SOAP: call failed: java.net.ConnectException: Connection timed out
SOAP: error occured: com.sap.aii.af.ra.ms.api.RecoverableException: Connection timed out: java.net.ConnectException: Connection timed out
MP: Exception caught with cause com.sap.aii.af.ra.ms.api.RecoverableException: Connection timed out: java.net.ConnectException: Connection timed out
Delivery of the message to the application using connection SOAP_http://sap.com/xi/XI/System failed, due to: com.sap.aii.af.ra.ms.api.RecoverableException: Connection timed out: java.net.ConnectException: Connection timed out. Setting message to status failed.
Regards
Divia

Hi Prateek,
Thanks for your replay. I am able to open the URL from XI/PI.
I tried by testing the same URL by using XI 3.0, its working fine and i am getting required data, but in PI 7.1 i am getting an error.
Error is:
In MONI:
com.sap.engine.interfaces.messaging.api.exception.MessagingException: java.net.ConnectException: Connection refused: connect
In RWB:
Message processing failed. Cause: com.sap.engine.interfaces.messaging.api.exception.MessagingException: java.net.ConnectException: Connection timed out: connect
What could be the reason?
Regards,
Venu

SOAP ADAPTER TIME OUT ISSUE

We are getting the data from sql server into PI through Soap adapter.
Till day before yesterday everything is running fine .But now it has started giving us the below error.
there were no changes done in the interface.
I am not able to see any error in the runtime workbench ,communication channel monitoring, message monitoring.
This below error is giving in sql server.
Can any PI expert explain or provide me a solution to solve this issue.
Msg 6522, Level 16, State 1, Procedure sp_PI_WS_Backflush_Production_V2, Line 0
A .NET Framework error occurred during execution of user-defined routine or aggregate "sp_PI_WS_Backflush_Production_V2":
System.Net.WebException: The operation has timed out
System.Net.WebException:
   at System.Net.HttpWebRequest.GetRequestStream()
   at System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String methodName, Object[] parameters)
   at PI_WS_Backflush_Production_V2.Backflush_OB_Sync_SIService.Backflush_OB_Sync_SI(BackflushRequest_DT BackflushRequest_MT)
   at PI_WS_Backflush_Production_V2.StoredProcedures.Backflush_Production_V2(String PalletNumber, String StockKeepingUnit, String ProductionPlant, String BatchNumber, DateTime ProductionDate, String Quantity, String UnitOfMeasure, String Destination, String& uState, String SAPUser, String SAPPassword)

Time out issue could be due to the long running process in your SQL server. please check the SQL server for its performance and also check the number of http worker threads on the SQL server side where the SOAP adapter makes the call and get the request back.

Issue in Synchronous SOAP Communication channel

hi Experts,
   I stuck in one scenario where my requirment is:--
At Receiver side SOAP adapter(which is Synchronous Communication) accepts data as Attachment.
But the response mustn't be in form of attachment.
If i use Keep Attachment at SOAP receiver channel, I will get response in the form of Attachment which doesn't meet my requirment.
Is it possible to extract the data from attachment.
I used PayloadSwapBean Module at SOAP receiver side but still I am getting response as Attachment.
Please help me out.
Is there any other approch for my Requirment which is as follows:---
FTP--->SOAP request(as an Attachment) >SOAP response(Without Attachment)->FTP
Solutions will be awarded with points:)
Thanks,
Jaideep Jain

Hi Jaydeep,
The other way is to develope the develope our own Module.
As you are using SOAP in sych ( you are using it as Receiver adapter Also we cant develope Modules for Sender SOAP adapter for that we have to look for AXIS SOAP adapter).
Here is module code that you can use for Module development.
public ModuleData process(ModuleContext moduleContext, ModuleData inputData)
            throws ModuleException{
           String str = "";
            Message mes = null;
      //Fetch the Message Data from Module Data
            mes = (Message) inputData.getPrincipalData();
            XMLPayload xmlpayload = mes.getDocument();
            String xmlText = xmlpayload.getText();
            String temp = "";
      // For Audit Log Fetch the Audit Message key from the message.
      amk = new AuditMessageKey(mes.getMessageId(), AuditDirection.OUTBOUND);
      Audit.addAuditLogEntry(amk,   AuditLogStatus.SUCCESS, "Excel to XML Module called");
      try {
            Iterator itr = mes.getAttachmentIterator();
//to iterate through all the attached messages.
            Payload pay = null;
            int i = xmlText.indexOf("<Content>");
            while(itr.hasNext()){
            pay = (Payload) itr.next();
          Audit.addAuditLogEntry(amk,AuditLogStatus.SUCCESS, "Payload Description: " + pay.getContentType());
            if(pay.getContentType().indexOf("Excel-sheet") > 0)
//only to process excel type attachment
      temp = temp + convert(pay.getContent()) ; //call the function that will convert the Excel data into xml formate
pay.setContent(new byte[0]); //set the attachment to zero because they are not required any more this will reduce system load
Audit.addAuditLogEntry(amk,   AuditLogStatus.SUCCESS, "Excel to XML Module DATA"+ temp);
            String payText = "";
            payText = xmlText.substring(0, i + 9)+ temp +xmlText.substring(xmlText.indexOf("</Content>"));
            xmlpayload.setText(payText);
            mes.setDocument(xmlpayload);
inputData.setPrincipalData(mes);
      } catch (RuntimeException e) {
            e.printStackTrace();
      Audit.addAuditLogEntry(amk,   AuditLogStatus.SUCCESS, "error caught " + e.getMessage());
      catch (Exception e1) {
                              e1.printStackTrace();
            return inputData;
I had written this code to convert the Excel Attachment(there could me many attachments) in the Mail to the XML .
Thanks
Sunil Singh

How to call the Application configuration in run time.

hi guru,
i have created two Application configuraton and it working fine.
my question how to call the application configuration in run time.
Example :
Based on the user i want to change the Application Configuration.like Super user and Normal user.
Advance thank's
Regard's
Vivekanathan.S

Hi,
Please try out this way-
Have a look at this table -
WDY_CONF_APPLU - (Customizing Data for Web Dynpro Applications).
after you are done with the configuration--
Ge the config id for the given application from this table. And depending on the user get an entry from this table and display accordingly.
Please refer to these links -
different default layouts for different CONFIG_IDs
Get WDCONFIGURATIONID
Regards
Lekha

SOAP synchronous channel specific call time out configuration

Similar Messages

Maybe you are looking for