Synchronous timeout

Hi,
I developed a Synchronous webservice, using Stateless Session Bean (SLSB) as the
starting point. But the client wants a response back in 30seconds, otherwise I
should time-out.
That is the instant I get the request to the instant I send the response back
should not be more than 30 seconds.
How should I implement it. I looked at ejb-jar.xml and weblogic-ejb-jar.xml file,
I could not find anything there.
I am on WLS 7.0 Sp2.
Anyhelp would be appreciated.
Thanks
---Radhe

Hi Radhe,
On the client side you can set a timeout with the property
"weblogic.webservice.rpc.timeoutsecs".
<Stub>
Stub stub = (Stub)port;
stub._setProperty("weblogic.webservice.rpc.timeoutsecs", "30");
</Stub>
or
<Call>
Call call = service.createCall();
call.setProperty("weblogic.webservice.rpc.timeoutsecs", "30");
</Call>
You will need 7.0SP4, or contact our fantastic support team
(http://support.bea.com or [email protected]) and reference CR107171.
Hope this helps,
Bruce
Radhe wrote:
>
Hi,
I developed a Synchronous webservice, using Stateless Session Bean (SLSB) as the
starting point. But the client wants a response back in 30seconds, otherwise I
should time-out.
That is the instant I get the request to the instant I send the response back
should not be more than 30 seconds.
How should I implement it. I looked at ejb-jar.xml and weblogic-ejb-jar.xml file,
I could not find anything there.
I am on WLS 7.0 Sp2.
Anyhelp would be appreciated.
Thanks
---Radhe

Similar Messages

Synchronous timeouts

Hi all,
In XI 3.0 SP 20 is there a way to set a synchronous timeout (at the Sender end )
1) specific to every communication channel.
2) specific to the Sender type (timeout specific to all RFC Senders)
3) Generic to all syncronous senders irrespective of their type.
Regards,
Arvind R

Check these links:
Re: SOAP Receiver communication channel Error
http://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/c059d583-a551-2c10-e095-eb5d95e03747

AEX JDBC Synchronous Timeout

Hi everyone!
I have a synchronous scenario Proxy->JDBC On PI 7.4 Java Only.
I have imported this scenario from another server dual stack, there it works.
I following this thread
SOAP Receiver adapter on 7.4 AEX exeeds synchronous timeout
, but it´s not answered.
do i forgot something?

Hi guys,
I found a solution.
Applying the SAPnote 0001493502.
Our problem was the paralelism, this wasn´t set.

Synchronous timeouts in 11.1.1.5

Hi,
I am looking at the following documentation:
Oracle® Fusion Middleware Developer's Guide for Oracle SOA Suite - 11g Release 1 (11.1.1.6.1)
http://docs.oracle.com/cd/E25178_01/dev.1111/e10224/bp_events.htm#CHDDGCGH
Section 15.3 Setting Timeouts for Request-Reply and In-Only Operations in Receive Activities
I am currently using SOA version 11.1.1.5.
I have a request/reply (synchronous) service and I need to create a BPEL that will call it and wait up to a certain maximum time for a response.
If it recieves a response it will continue processing, if it does not get a response in the alloted time it should respond with something like Service down.
I have looked at using the pick activity for this but I think this will only work with asynchronous operations. Looking at the documentation reference I have put I notice that there is a timeout tab in JDeveloper which seems to do what I want.
This does not appear in my JDeveloper.
Is this a new 11.1.1.6 feature?
Is it possible for me to achieve what I want in 11.1.1.5 or do I need to break down my service into two async services?
Thanks
Robert

Robert,
You can't find it because you are looking at the Invoke activity. The doc is talking about Receive activity use cases.
To determine the timeout for synh' processes using Invoke activity, you should use the 'SyncMaxWaitTime' property.
You can find it on EM control->Right click SOA Infrastructure menu and select SOA Administration-> BPEL Properties->Click More BPEL Configuration Properties->Find the SyncMaxWaitTime property and change it value-> apply
Arik

Timeout Error in a Synchronous XI - SOAP scenario

Hi All,
I have developed a Synchronous ABAP proxy to SOAP web service scenario.
ECC sends an ABAP proxy request to PI, PI forwards the request to the target system as SOAP message.
I have checked the interface via SOAP UI and it works fine but when we run the end-to-end flow it always ends with a Synchronous timeout error.
The Target system confirms that the response is sent from there side but in PI we are not receiving any response and the system throws a timeout error.
As both PI and the Target system are in same Landscape there is no firewall in between.
Please suggest what can be the possible reasons and the approach to resolve the same?
Thanks in advance,
Shashank

Hi,
"The target system needed credentials for one inbound interface, so for this synchronous scenario(PI<->Target) should the target system maintain credentials some where when the response is sent back to PI as the SOAP channel is on Java Stack?"
Generally for receiver channel we get the user name and password from target system ie web service.
How did you test in SOAPUI? did you test it with providing username and password or not?
even if web service requires user/pwd then it will throw 401 unauthorized error.
check this
can you go to RWB-->component monitoring-->adapter Engine-->communication channel monitoring-->your channel
check if the channel has any errors/exceptions logs.
Regards,
Muni.

Synchronous JDBC Timeout

Hi Experts, I have a synchronous proxy-jdbc with SQL_QUERY (Select) as action. When the query is executed directly in the DB, it's only taking 3-4 minutes to get the results. But when it's run thru PI, we always encounter synchronous timeout exceeded error (20 minutes). Since the query is getting results on time in the DB, I'm thinking the problem could be in PI side but I'm running out of options to check. Has anyone faced this problem before? Any inputs will be greatly appreciated. Thanks!

Hi Mark,
It looks like a network problem. Can you ping the database hostname in your PI system (create ping command in SM69)? Also take a look at this note: Note 1085539 - XI JDBC/FTP connection Test and XML Validation Application
Hope this helps,
Mark

Long sync calls and timeout.

2. TIMEOUT
Consider the following situation :
Flows 1 --- async call ----> FLows 2 ------ async call --------> Flows 3 -----sync call ----> axis ws
The last sync call can take a long time.
If this time is too long , Flows 1 , FLows 2 , Flows 3 goes in stale state ...
How can i manage timeout/set maximum time for Async and Sync call ?
What's the best way to manage this ?

I circled back with the engineering team on this: we are in the process of adding a timeout configuration parameter to the partnerLinkBinding information embedded in the BPEL deployment descriptor (bpel.xml). An associated runtime BPEL fault will be defined for process designer to catch and handle this type of synchronous timeout. This feature will be available in the September service pack.
The async timeout can be managed using the bpel pick/onMessage and onAlarm.
Edwin

Message Timeout in Peoplesoft

In configuration PSAPPSRV timeout is set to 300 seconds. There are instances when for an inbound syncrequest the processing time in Peoplesoft might take more than 300 seconds. Since IG doesnt receive a response within 300 seconds it reposts the same message again to Peoplesoft (with a different message transaction_id). Is there a way to stop these messages from being reposted? I do not want to change the timeout specified in the configuration file. I just want to stop these messages from being re-posted
SO Used: Inbound Synchronous
Message Type: Non-Rowset (transformed)
PT version : 8.51.10

Hi,
See this doc which explains how you can override the timeout on runtime for a specific service operation
E-IB: How to Override Default Timeout for Integration Broker Synchronous Service Operations (Messages) [ID 658690.1]
Also see PeopleBooks > Enterprise PeopleTools 8.51 PeopleBook: Integration Broker > Sending and Receiving Messages > Generating and Sending Messages > Overriding Synchronous Timeout Intervals at Runtime
This PeopleBooks uses the SyncServiceTimeout property of the IBInfo Class.
PeopleBooks > Enterprise PeopleTools 8.51 PeopleBook: PeopleCode API Reference > Message Classes
Snipet from PeopleBooks:
SyncServiceTimeout
Description
This property takes a time (in seconds). This time overrides the default HTTP timeout that is used for all requests. If you set this property, you can use this to read back the time, that is, set the time before the SyncRequest is executed, then see when it is changed in an implementation of the OnSend method.
Note. This property is only for synchronous requests.
Generally, you use SyncServiceTimeout to dynamically set the timeout value for a specific transaction. The http header file is modified to take this new parameter. In addition this value is sent to the gateway to be used for the http timeout. Use this so that a long running transaction will not timeout. In addition, you don't have to wait through the default period for a specific transaction to timeout.
The following is a typical example of using this property:
&MSG.SetXmlDoc(&xmlReq);
&MSG.IBInfo.LoadConnectorPropFromNode(Node.EAI)
&MSG.IBInfo.SyncServiceTimeout = 360000;
&MSG.IBInfo.ConnectorOverride = true;
&MSG_Resp = SyncRequest(&MSG, Node.EAI);
&xmlResponseDoc = &MSG.GetXmlDoc();
Setting the XML directly is not valid. You need to use the message object to set the value. In order for this to work you must override the connector properties, which means you must set up the connector properties for this transaction, using one of the load methods (such as LoadConnectorPropFromNode, LoadConnectorPropFromTrx, and so on.)
This property is read-write.

Performance problem in RFC to JDBC interface

Hello everybody!
i'm working whit SAP PI 7.1
We defined some interfaces RFC - PI - JDBC (SQL server) but we have some performance problem.
If we have many row to write on the table then interface finish in timeout :
Synchronous timeout exceeded.
Returning to application. Exception: com.sap.engine.interfaces.messaging.api.exception.MessageExpiredException: Message 1d1f00b0-fecf-11de-8738-0015600446f0(OUTBOUND) expired.
I read the PI tuning document and i tried to apply configuration whit Advanced Adapter Engine but whitout result.
Now we want change the timeout in visual admin and maybe we solve the error but i'm asking myself....:
It's normal that for write 1500 row in a table we need more than 4 minuts????
It's possible accelerate this process??? After go live we will write messages whit more than 50.000 row.
somebody may help me?
PS: please no link to tuning guide or to notes (to increase the timeout parameter).

This could be because your Database system (JDBC server) is taking more time to insert. The problem is not on PI side but on the receiving system side. Try inserting the same number od rows on the database server itself and check for the time taken for execution. Adding indexes on your database table solves the issue lot of times.
Here PI is not the culprit but definitely the receiver system.
VJ

Thread Error

Hi Guys,
I have a problem with a thread. I would appreciate any help.
I have an applet (called BaseApplet) that is the basis for all my applets. This BaseApplet is basically an extension of Applet that implements Runnable. A thread runs which simply waits for a given time then aborts (basically a timeout). I am getting the following error, apparently randomly);
java.lang.NullPointerException
     at com/innsite/applet/BaseApplet.run
     at java/lang/Thread.run
The BaseApplet is defined as follows;
public class BaseApplet extends Applet implements Runnableand the code to execute the thread is as follows;
public void init()
    super.init();
    // start the timeout monitor
    timeout = new Thread(this);
    timeout.setDaemon(true);
    timeout.start();
}First of all can I ask;
Is the error because some code is trying to execute the thread that is not instantiated? If not what could be causing this error?
I can provide the run() method if required but I have put some System.out's and it doesn't appear to run when I get this error. The application does time out as required. I have searched the application and cannot find any other call to start this thread.
Sorry to be so vague. The application is large/commercial so I cannot realistically post all of it.
Has anyone experienced problems with threads being executed?
Thanks in advance.
Slacks

I have a little example. Running this eample if you press 'Destroy Thread' then close the the applet you get a similar error. This error gives the line number etc.
import java.applet.*;
import java.awt.*;
import java.awt.event.ActionEvent;
import java.awt.event.ActionListener;
import java.net.MalformedURLException;
import java.net.URL;
public class BaseApplet extends Applet implements Runnable {
     protected static BaseApplet instance;
     private transient Thread timeout = null;
     private transient Thread timeout1 = null;
     public BaseApplet() {
          super();
          instance = this;
     public void init() {
          super.init();
          // start the timeout monitor
          timeout = new Thread(this);
          timeout.setDaemon(true);
          timeout.start();
          timeout1 = new Thread(this);
          timeout1.setDaemon(true);
          timeout1.start();
          Panel p = new Panel();
          Button b1 = new Button("Reset");
          b1.addActionListener(new ActionListener() {
               public void actionPerformed(ActionEvent arg0) {
                    System.out.println("Timeout Reset : ");
                    resetTimeout();
          Button b2 = new Button("Distroy thread");
          b2.addActionListener(new ActionListener() {
               public void actionPerformed(ActionEvent arg0) {
                    System.out.println("Destroy Thread : ");
                    timeout=null;
                    timeout1=null;
          p.add(b1);
          p.add(b2);
          add(p);
     public void run() {
          int delay = 30000;
          boolean stopped = false;
          URL exitPage = null;
          try {
               exitPage = new URL("http://127.0.0.1/homepage.html");
          } catch (MalformedURLException e1) {
               e1.printStackTrace();
          while (!stopped) {
               try {
                    synchronized (timeout) {
                         // wait for n milliseconds or until interrupted
                         timeout.wait(delay);
                         System.out.println("Timeout!!!!");
                         stopped = true;
                         getAppletContext().showDocument(exitPage, "_self");
               } catch (InterruptedException e) {
                    // Invoked when interrupt() is called on the timeout thread.
                    // Means that the timeout whould either reset or stop.
          timeout = null;
     public final static void resetTimeout() {
          if ((instance != null) && (instance.timeout != null))
               instance.timeout.interrupt();

INTERNAL.HTTP_RESP_STATUS_CODE_NOT_OK HTTP response contains status code 50

Hi Gurus,
I am getting error message "INTERNAL.HTTP_RESP_STATUS_CODE_NOT_OK HTTP response contains status code 500 with the description Timeout" when I call a proxy to retrieve data from external database (oracle) through XI (Synchronous Call). This proxy works fine if the data size is limited to 120 MB but terminates with above message if data size is larger may be > 130 MB but some time it works as well with this data size.
Me & our basis team are working hard to fine out the issue but still could not succeeded. we have applied the OSS Note 807000 but still we are getting the error message. To make it more clear I am sending SQL Query to Reciever (Oracle) from SAP through ABAP proxies.
If I check the status of messages in "Monitor for processed XML messages" the message has status icon which says "Log version" I am new in XI Please help me to solve the issue.

hey...try increasing the synchronous timeout parameter. I think the default is 180 secs.
I would suggest you look at redesigning the the interface to pull the data in smaller pieces...120 Mb is really big...Pi gives max throughput at around 5 mb...
Dont worry about the log version....It just persisted in the system when a job is still running... try looking at the same message after a while...it would have changed its stsatus.
Arvind R

Catch Synch timout with failover

Hi,
Essentially I'am trying to find out which runtime fault to explicitly catch in order to catch a synchronous timeout error.
The background is that I have a synchronous service that is wrapping a sqlloader call. As the load could run for any arbitrary amount of time, it is likely that my synch call will timeout. This does not pose a huge issue as the sqlldr scipt outputs logs and, if i can catch the timeout, i can poll the logs to find the result of the service.
A catch here is that, this service is HA, and i have two instances of it in different AppServers. I am using the failover capability in the partnerlink to connect to the service.
i expect that the failover will be used in the initial attempt to invoke the service, if the service is down it will try the second service. The timeout catch will be used to catch the scenario where i have successfully invoked the service, and then it times out.
Which leads to, are these two scenarios going to conflict? Is there a differntiation within the BPEL engine as to the two error messages, or will one functionality overwrite the other?
Any help appreciated.
(I know, Asynch would fix everything.....lets not even discuss that ;-)

Could be wrong but I think if service A is down and the partnerlink fails over to service B and that then times out, you will get a remoteFault on service B
Pete

TimeOut Issue in invoking Synchronous Web Service in BPEL.

Hi All,
There is one BPEL process which is calling third party web service synchronously but sometimes my requests get failed in 30 sec giving the following error:-
*"oracle.fabric.common.FabricInvocationException: Unable to access the following endpoint(s): https://aaa.bb.cc.dd/abc/def/xyz"*
When I checked this in soa_server1-diagnostic.log, I found that it is giving some Read Time Out error.
Currently following settings are there on the server:-
syncMaxWaitTime = 45 sec
EJB Time Out:- 300 sec
JTA Timeout:- 360 sec
If there is no setting of 30 sec then why my partner link is failing in 30 sec. Morever the intresting point is that although It is giving some Exception but it is performing the operations successfully. Due to this exception rest of my BPEL does not work.
Please provide me the pointer how to increase the Read time out and is there any relation between httpReadTimeout (Defined in composite for Partner Link) and syncMaxWaitTime.
Thanks In Advance,
Regards,
Lovenish
Edited by: lovenish on Jun 13, 2012 10:56 PM

Hi Lovenish,
Goto console-> select domain> Configuration->JTA
Check timeout seconds.
2. i don't know what kind of partner link you are invoking.
check composite.xml, is there any property like retry.interval .
3. ◦SyncMaxWaitTime: The maximum time a request and response operation takes before timing out.
The maximum time a request/response operation will take before it times out. The default value is 45 seconds.
Regards,
Padmanabham

Timeout in synchronous SOAP-Proxy communication

Hi,
I have a synchronous SOAP-Proxy communication (3rd party - XI - ERP). 3rd party is always the initiator of the communication.
Is there a general rule about who should set a timeout? Does it should be set by a 3rd party, XI, or ERP? In our scenario it shouldn't be longer than 30 seconds.
If it needs to be set on SAP side, where it should be defined? On XI or on ERP, or on both systems?
Which SAP parameter is used for setting the timeout for synchronous communication that does not affect other already working ways of communication, like asynchronous.
Thanks for answers.
Janos

Hi,
The timeout property needs to be set at XI level. For SOAP sender timeout check sap note no. 856597 which reads as 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.
Thanks!

Synchronous Call Timeout but the PO still created in ECC.

Hi PI Expert,
I have problem with synchronous call (Web Service -
> RFC). Sometimes if the processing time in ECC take longer time the webservice will throw exception timeout but then the processing stil continue in receiver communication channel until success.
So if you use SXI_MONITOR you can see 2 transaction, Sender web service error timeout and RFC success.
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
<SAP:Category>XIServer</SAP:Category>
<SAP:Code area="INTERNAL">HTTP_RESP_STATUS_CODE_NOT_OK</SAP:Code>
<SAP:P1>500</SAP:P1>
<SAP:P2>Timeout</SAP:P2>
<SAP:P3 />
<SAP:P4 />
<SAP:Stack>HTTP response contains status code 500 with the description Timeout Error while sending by HTTP (error code: 500, error text: Timeout)</SAP:Stack>
<SAP:Retry>N</SAP:Retry>
</SAP:Error>
But the RFC communication still able to continue until succes. Supposed to be both error if the sender communication channel timeout ?
- <ns0:Z_MM_STO.Response xmlns:ns0="urn:sap-com:document:sap:rfc:functions">
<EX_RESULT><RETURN><item><TYPE>E</TYPE><ROW>0</ROW><PARAMETER>POHEADER</PARAMETER><MESSAGE>0100905701</MESSAGE><MESSAGE_V1></MESSAGE_V1><MESSAGE_V2></MESSAGE_V2><SYSTEM></SYSTEM></item><item><TYPE>E</TYPE><ROW>1</ROW><PARAMETER>POHEADER</PARAMETER><MESSAGE>External document number 100905701 already assigned</MESSAGE><MESSAGE_V1>100905701</MESSAGE_V1><MESSAGE_V2></MESSAGE_V2><SYSTEM>ECPCLNT300</SYSTEM></item></RETURN></EX_RESULT>
</ns0:Z_MM_STO.Response>
Please advise is that anything that i can check ?
Thank You and Best Regards
Fernand.
Edited by: Fernad Lesmana on Aug 23, 2010 7:59 AM
Edited by: Fernad Lesmana on Aug 23, 2010 8:00 AM
Edited by: Fernad Lesmana on Aug 23, 2010 8:01 AM

Hi Fernand,
The last parameter (syncMessageDeliveryTimeoutMsec) you mentioned is for general timeout setting of RFC receiver calls (see note FAQ RFC Adapter: https://service.sap.com/sap/support/notes/730870). That one seems high enough in your case
xiadapter.inbound.timeout.default is the default setting of 180 seconds, which is normally the default for all timeouts in PI.
Normally in icm there's a setting for the http port (e.g. something like icm/server_port_x prot=http,port=500xx,timeout=180,proctimeout=180)
Can you confirm that one is higher then 60 seconds? (Just saw you saying something about 60 seconds before editing the posting)
Best wishes
Sebastian
Edited by: Sebastian Simon on Aug 26, 2010 1:24 AM

Synchronous timeout

Similar Messages

Maybe you are looking for