Long Response of Web Service Causes Timeout

Hi All,
We are having a synchronous senario: RFC -> XI -> Web Service. The web service takes quite long time (2~4 min) to finish its job. So the caller RFC adapter times out and an exception is thrown on the caller RFC side. Can anybody tell me how to increase the timeout threshold on the RFC adapter or SOAP adater, whichever determines the behaviour of RFC call?
Thanks + Best Regards
Jerome

I would like to know in details how can I enter and change the exact place for the RFC adapter.
I would like to enlarge my time out in the RFC before returning to the WS
Thanks
kfir

Similar Messages

Manage the response of Web Service in case of Fault

Hi,
invoking the adapter HTTA, the Web Service send a response. B1i manage only the failure of adapter HTTA, but not the response of Web Service. If you want use the PostProcessing BizFlow correctly, i need to manage the response for check the presence of node Fault.
This is the generic code for check this:
<?xml version="1.0" encoding="UTF-8"?>
<xsl:stylesheet version="1.0" xmlns:env="http://www.w3.org/2003/05/soap-envelope" xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/" xmlns:b1im="urn:com.sap.b1i.sim:b1imessage" xmlns:xsl="http://www.w3.org/1999/XSL/Transform" xmlns:bfa="urn:com.sap.b1i.bizprocessor:bizatoms" xmlns:fo="http://www.w3.org/1999/XSL/Format" bfa:force="">
     <xsl:output method="xml" encoding="UTF-8" indent="yes"/>
     <xsl:param name="IDOCNUM"></xsl:param>
     <xsl:template match="/">
          <bfa:call>
               <xsl:copy-of select="/bfa:call/bfa:in_doc"/>
               <xsl:copy-of select="/bfa:call/bfa:inbound"/>
               <bfa:outbound>
                    <bfa:payload>
                         <xsl:apply-templates select="bfa:call/bfa:outbound/bfa:payload"/>
                    </bfa:payload>
                    <xsl:copy-of select="/bfa:call/bfa:outbound/bfa:propertylist"/>
               </bfa:outbound>
          </bfa:call>
     </xsl:template>
     <xsl:template match="bfa:call/bfa:outbound/bfa:payload">
          <Envelope xmlns="">
               <Header>
                    <xsl:choose>
                         <xsl:when test="soap:Envelope/soap:Body/node()/node()/env:Envelope/env:Body/env:Fault">
                              <ActionResult>failure</ActionResult>
                              <ActionMessage>
                                   <xsl:text>PROCESS FAILURE - IDOC NUM: </xsl:text>
                                   <xsl:value-of select="$IDOCNUM"></xsl:value-of>
                                   <xsl:text> - CAUSE OF FAILURE: </xsl:text>
                                   <xsl:value-of select="soap:Envelope/soap:Body/node()/node()/env:Envelope/env:Body/env:Fault/env:Reason/env:Text"/>
                              </ActionMessage>
                              <Exception>
                              <xsl:value-of select="soap:Envelope/soap:Body/node()/node()/env:Envelope/env:Body/env:Fault/env:Reason/env:Text"/>
                              </Exception>
                         </xsl:when>
                         <xsl:otherwise>
                              <ActionResult>success</ActionResult>
                              <ActionMessage>
                              <xsl:text>PROCESS SUCCESS - IDOC NUM: </xsl:text>
                              <xsl:value-of select="$IDOCNUM"></xsl:value-of>
                              </ActionMessage>
                         </xsl:otherwise>
                    </xsl:choose>
               </Header>
          </Envelope>
     </xsl:template>
</xsl:stylesheet>
With this example you can set the message in B1i GUI (Message Log, Message Result column) and you can set the result of action (success or failure).

Hi,
invoking the adapter HTTA, the Web Service send a response. B1i manage only the failure of adapter HTTA, but not the response of Web Service. If you want use the PostProcessing BizFlow correctly, i need to manage the response for check the presence of node Fault.
This is the generic code for check this:
<?xml version="1.0" encoding="UTF-8"?>
<xsl:stylesheet version="1.0" xmlns:env="http://www.w3.org/2003/05/soap-envelope" xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/" xmlns:b1im="urn:com.sap.b1i.sim:b1imessage" xmlns:xsl="http://www.w3.org/1999/XSL/Transform" xmlns:bfa="urn:com.sap.b1i.bizprocessor:bizatoms" xmlns:fo="http://www.w3.org/1999/XSL/Format" bfa:force="">
     <xsl:output method="xml" encoding="UTF-8" indent="yes"/>
     <xsl:param name="IDOCNUM"></xsl:param>
     <xsl:template match="/">
          <bfa:call>
               <xsl:copy-of select="/bfa:call/bfa:in_doc"/>
               <xsl:copy-of select="/bfa:call/bfa:inbound"/>
               <bfa:outbound>
                    <bfa:payload>
                         <xsl:apply-templates select="bfa:call/bfa:outbound/bfa:payload"/>
                    </bfa:payload>
                    <xsl:copy-of select="/bfa:call/bfa:outbound/bfa:propertylist"/>
               </bfa:outbound>
          </bfa:call>
     </xsl:template>
     <xsl:template match="bfa:call/bfa:outbound/bfa:payload">
          <Envelope xmlns="">
               <Header>
                    <xsl:choose>
                         <xsl:when test="soap:Envelope/soap:Body/node()/node()/env:Envelope/env:Body/env:Fault">
                              <ActionResult>failure</ActionResult>
                              <ActionMessage>
                                   <xsl:text>PROCESS FAILURE - IDOC NUM: </xsl:text>
                                   <xsl:value-of select="$IDOCNUM"></xsl:value-of>
                                   <xsl:text> - CAUSE OF FAILURE: </xsl:text>
                                   <xsl:value-of select="soap:Envelope/soap:Body/node()/node()/env:Envelope/env:Body/env:Fault/env:Reason/env:Text"/>
                              </ActionMessage>
                              <Exception>
                              <xsl:value-of select="soap:Envelope/soap:Body/node()/node()/env:Envelope/env:Body/env:Fault/env:Reason/env:Text"/>
                              </Exception>
                         </xsl:when>
                         <xsl:otherwise>
                              <ActionResult>success</ActionResult>
                              <ActionMessage>
                              <xsl:text>PROCESS SUCCESS - IDOC NUM: </xsl:text>
                              <xsl:value-of select="$IDOCNUM"></xsl:value-of>
                              </ActionMessage>
                         </xsl:otherwise>
                    </xsl:choose>
               </Header>
          </Envelope>
     </xsl:template>
</xsl:stylesheet>
With this example you can set the message in B1i GUI (Message Log, Message Result column) and you can set the result of action (success or failure).

Web Service connection timeout

How to configure the web service connection timeout properties (eg. weblogic.wsee.transport.connection.timeout) in configuration files rather setting them at client's stub code?
Help is appreciated.

This might be due to following reasons.
Please check whether firewall exist between Pi and external system. If so check with network team weather port or connectivity is established between PI server and external system. This should be the main reason. Also check the target URL and see whether you can able to consume the webservice directly from Soapui without PI. If your workstation is within PI's landscape and you see the same timed out error, then the network connectivity is the issue. Ask them to enable the port.

What do I do to close eform on screen and display response of web service in another screen.?

Hi,
I am trying to build following functionality.
I want to submit form to a web service through SOAP request on click of a button.
I want to display response of web service like “form has been submitted successfully” on screen.
What has been achieved.
I am able to submit form to an adobe web service passing base64 string to adobe process.(see the script in image#1).
When I receive base64 string in adobe process, I am able to re-generate document (using getDocFromBase64(/process_data/@inputStr) ).
After that I am returning a message string to as response “Form submitted successfully”.
When I get the response I populate response to a text field variable (Out Str). See image#2
Problem/Desirable functionality.
I want to close this eform and display the message “form has been submitted successfully” on another page in browser so that it depicts to end user that form has been submitted successfully with confirmation.
What do I do to close eform on screen and display response of web service in another screen.?
Image#1
Image#2

Method1: This method only works in same PDF window.
On the click of the submit button, based on the webservice result we can close the PDF. As you already having in the "Out Str", this variable having detailed message kind of thing, so it would be easier if you have one more output variable to know if this submission is success or failure or can use the "Out Str", it self to compare and close the PDF.
Here i am using "strResult" to hold webservice success or failure using true/ false values.
Get the "strResult" value from binded field of webservice response and compare and close or display messages based on requirement.
var strResult = YourFieldname.rawValue;
                    if(strResult != "" && strResult != null){
                              if(strResult.toUpperCase() == "TRUE"){
                                        xfa.host.messageBox("Successfully Saved the Data.", "Submit Confirmation", 3,0);
                                        //Close the PDF
                                        app.execMenuItem("Close");
                    else{
                              xfa.host.messageBox("Failed to Save the Data.", "Submit Confirmation", 3,0);
If the result need to show in separate window and having LiveCycle process connected to PDF via. webservice or REST:
Method2. If the PDF inside the browser
Type1 - You can set the process output is document variable, this PDF may contain your static/dynamic message and this PDF. But with this method result PDF opens in same window, host pdf will be disappeared.
Type2 - You can set the process output is string variable, this STRING may contain your static/dynamic message. In this method the string will be appered in the same PDF window, host pdf will be disappeared.
Method3. If the PDF is stand alone (not opend in any browser)
Type1 - You can set the process output is document variable, this PDF may contain your static/dynamic message and this PDF. But with this method result PDF opens in new window, host pdf will be also stayed and may make readonly after submission success.
Type2 - If the process output is string, it cannot handle this situation, may get the content type exception while receiving the result string, because.
Used all of the above methods in various situations and it worked without any issues.
-Raghu.

Late response from a sap web service or timeout

Hi,
I have developed a function module an exposed it as web service. The consumer developed by the partner is a java client. Every request for the ws lasts 18 seconds. The response time is unacceptable. I have developed a .net client and called the ws. the first call lasts nearly as long as the java client but the repsonse time for successive calls is very short.
How can I get the responses faster with the java client?
thanks,
- ferudun

Paula,
I suppose you're using CFINVOKE (http://www.activsoftware.com/code_samples/code.cfm/CodeID/44/ColdFusion/Invoking_SOAP_Web_Services_with_ColdFusion_MX_CFINVOKE_Tag) or are you using a third party tool like CFX_SOAP (http://www.activsoftware.com/products/productdetail.cfm/id/1015)?
Are you working with WebAS 6.4 or 6.2?
It works with web services created with WebAS 6.4, but you should generate proxy classes. Check Thomas' weblog (second part of it)->https://www.sdn.sap.com/irj/sdn/weblogs?blog=/pub/wlg/1012. [original link is broken] [original link is broken] [original link is broken] [original link is broken] [original link is broken] [original link is broken] [original link is broken] [original link is broken] [original link is broken]
The WSDL generated by this method is more standard than the one generated when you just Remote enable an FM and look at the webservice browser.
Th core of CF MX is Java and that engine is rather strict in standards.
Eddy

Abap Proxy = Web Service - Connection timeout

Hi Experts,
I request your help on some issue we encounter actually on our Web services interfaces.
We have sceanario in which from SAP, we are sending a message to PI via Abap proxy.
PI then, send the message to the external system via a Web Service (we have configured the URL and authentification values).
When we want to test the scenario we have an issue.
- We see in SXMB_MONI message has status sent succesfully
- When we check the external system, we see that no message is received (no trace of message from PI).
- Then we check on PI runtime workbench, we see in the receiver communication channel error saying "Connextion Timeout"
(in detail: SOAP: call failed: java.net.ConnectException: Connection timed out")
We would like to investigate the issue.
Have you already encountered this kind of issues ? And how we could investigate the root cause here ?
And thanks for ur help,
S.N

This might be due to following reasons.
Please check whether firewall exist between Pi and external system. If so check with network team weather port or connectivity is established between PI server and external system. This should be the main reason. Also check the target URL and see whether you can able to consume the webservice directly from Soapui without PI. If your workstation is within PI's landscape and you see the same timed out error, then the network connectivity is the issue. Ask them to enable the port.

Erorr calling long running sync web service

Hello
I have definied simple async process:
assign (from process input to ws invoke input)
sync ws invoke
assign (from ws invoke output to process output)
Sync Web Service is long running (few minutes). In order to avoid timeout I have accordingly set sync-max-wait-time property.
I have observed that after starting process instance I can't see it in BPEL Console (however I know it is working). Furthermore when invoke activity ends (so instance state must be saved in database) I can see following error on system console:
<BaseCubeSessionBean::logError> Error while invoking bean "delivery": Cannot ins
ert audit trail.
The process domain was unable to insert the current log entries for the instance
"2314" to the audit trail table. The exception reported is: RollbackException:
The transaction has been marked for rollback (timed out)
Please check that the machine hosting the datasource is physically connected to
the network. Otherwise, check that the datasource connection parameters (user/p
assword) is currently valid.
sql statement: INSERT INTO audit_trail ( cikey, domain_ref, count_id, log ) VALU
ES ( ?, ?, ?, ? )
<2005-01-06 13:14:10,268> <ERROR> <default.collaxa.cube.engine.dispatch> <BaseSc
heduledWorker::process> Failed to handle dispatch message invoke instance messag
e 0c92305db480f36d:149b290:10147dc1b2e:-7fd6 ... exception Message handle error.
An exception occurred while attempting to process the message "com.collaxa.cube.
engine.dispatch.message.invoke.InvokeInstanceMessage"; the exception is: Transac
tion was rolled back: timed out; nested exception is: java.rmi.RemoteException:
No Exception - originate from:java.lang.Exception: No Exception - originate from
:; nested exception is:
java.lang.Exception: No Exception - originate from:
Best Regards

Hi,
There are 2 ways to work around the error that you are seeing.
Option #1: increase the JTA timeout of the underlying application server.
Option #2: in the bpel.xml of your process, add a "nonBlockingInvoke" property to the partnerLink representing the interaction with the long running service.
Option #2 should also address the fact that the instance is not visible in the bpel console.
Edwin

Web service problem (Timeout)

hello
i hope this is the right category to post my problem
i want to use the service "customerCRMChangeRequestConfirmation_In"
but i get this error message: "Error getting response; java.net SocketTimeoutException: Read timed out.
on my search to fix this problem i found the SAP Note 826419.
with following advice:
===========================================================================================
Version NW 7.10
Using NetWeaver Administrator
          o For standard Web service deployable proxy:
            1. Open SAP NetWeaver Administrator in a browser: http:// "Web Services Administration".
            3. Choose "Proxy Definitions by Name" and click "GO".
            4. Select the proxy you want to configure.
            5. Choose the "Configuration" tab.
            6. Choose the "Logical Ports" tab.
            7. Select the logical port you want to configure and choose "Edit".
            8. Choose the "Transport Settings" tab.
            9. Edit the "Max wait-time for HTTP response (in milliseconds)" field.
            10. Click "Save" to save the settings.
============================================================================================
but in my Transport Settings are no "May wait-Time for HTTP response-field"
what is the problem? i have an SAP CRM IDES System with Netweaver 7.1
do I need to install an sp?
I also found this solution for my read time out problem:
http://wiki.sdn.sap.com/wiki/display/TechTSG/%28WSR%29Problems-P01
but this solution with "Visual Administrator" is for java stack, right?
thank you for your help!
kind regards
sven möller

Hi Sven,
There could be several reasons for this timeout but seeing as this is an IDES System things should generally work fine (it's not always the case though).
I would suggest increasing the socket timeout on SoapUI & then test the webservice again. If you are unsure of how to do this just Google 'SoapUI Test Case Socket Timeout' or something similar. You first need to create a test suite/case & then you can control the socket timeout on SoapUI.
Just in case, I would also check that the webservice service is configured correctly by launching transaction code SOAMANAGER from the IDES CRM & searching for this service (look for the change customer service under service providers). Just verify that all endpoint configuration is correct.
I would also verify if you have the necessary authorizations (for your IDES login user) to change a customer.
Lastly, I would setup a trace/recording using the ICF Recorder for your IDES login user (Google 'SAP ICF Recorder' for correct usage). Turn on the recorder to trace your incoming request in IDES & trace the outgoing response from IDES.
You could also try viewing Transaction Codes ST11 & ST22 that trace incoming requests into the IDES Application Server. This may highlight any authorization related issues.
Best Regards, Trevor

Web Service Connection Timeout - Whats the default value?

Does anyone know the default value of connection timeout property in Web Service activity?
One of my web service takes longer time for processing. So just wanted to know this value for debugging.
Thanks,
Nith

Hi Dexter,
In your case, we can try to increasing the size of the connection pool to resolve the issue. By default, the Max Pool Size is 100. You can refer to the similar issue below:
http://social.msdn.microsoft.com/Forums/en-US/c57c0432-c27b-45ab-81ca-b2df76c911ef/timeout-expired-the-timeout-period-elapsed-prior-to-obtaining-a-connection-from-the-pool?forum=adodotnetdataproviders
Since the issue is related with ADO.NET. I suggestion you post the question in the following forum:
http://social.msdn.microsoft.com/Forums/en-US/home?forum=adodotnetdataproviders
It is appropriate and more experts will assist you.
Regards,
Alisa Tang
Alisa Tang
TechNet Community Support

How to attach XML file in the response of Web Services

Hi
I am new to the WEB SERVICE. this my requirement.
I need to make a class file a web service. and i need to get data from the data base and attach it in the response. I need to use SOAP MEssaging for this. so how to call the service from the JSP and how to get the data from the response,Before that which technology i need to use for this requirement. Plz let me know how to accomplish this task. I have gone thur lot of tech stuff and i am confused a lot, what to use and how to use. Will any one help me out.
Thanks
Vidya

Hey VP, thanks for replyng.
I have read the codes from a book and havesome code for client. The server side is yet to be done....but I have problems in compiling them as I am Unable to import javax.xml.soap.*;
This is basically a request to the Server asking it to find the match of the word "Mickey" from the XMLfile at the server...JAXRPC is involved(I Presume:) There are some supporting files.........hey But it doesn't compile only here. Hope it does in yrs
*******The client..........**********
* Client
package com.aby.jwsdp.soap.client;//the package
import javax.xml.messaging.URLEndpoint;
import javax.xml.soap.SOAPConnectionFactory;
import javax.xml.soap.SOAPConnection;
import javax.xml.soap.SOAPMessage;
import javax.xml.transform.Transformer;
import javax.xml.transform.TransformerFactory;
import javax.xml.transform.Source;
import javax.xml.transform.stream.StreamResult;
import com.aby.jwsdp.soap.client.Fault;//supporting file
import com.aby.jwsdp.soap.client.RequestMessage;//supporting file
public class Client {
     static final string SERVICE_ENDPOINT="http://localhost:8080/chap/servlet/chap.RecieveServlet";
     public static void main(String args[]) {
          if(1!=args.length) {
               System.err.println("Usage: java "+"com.aby.jwsdp.soap.client.Client <name>");
          } else {
               new Client(args[0]);
     public Client(String name) {
          try{
               URLEndpoint endpoint = new URLEndpoint(SERVICE_ENDPOINT);
               SOAPConnectionFactory scf=SOAPConnectionFactory.newInstance();
               SOAPConnection connection = scf.createConnection();
               RequestMessage reqMsg = new RequestMessage();
               reqMsg.setName(name);
               SOAPMessage replySOAP = connection.call(reqMsq.getMessage(),endpoint);
               if(Fault.hasFault(replySOAP)) {
                    Fault fault = new Fault(replySOAP);
                    System.err.println("Recieved SOAP Fault");
                    System.err.println("Fault Code: "+fault.getFaultCode());
                    System.err.println("Fault string: "+fault.getFaultString());
                    System.err.println("Fault detail: "+fault.getFaultDetail());
               }else {
                    ResponseMessage respMsg = new ResponseMessage(replySOAP);
                    String responseValue = null;
                    try{
                         responseValue = respMsg.getValue();
                         System.out.println("Response: "+responseValue);
                    }catch(SchemaException e) {
                         System.err.println("Parsing error");
               connection.close();
          }catch(EXception e) {
               System.err.println(e/toString());
/*@author Aby
*Fault.java
package com.aby.jwsdp.soap.client;
import javax.xml.soap.SOAPMessage;
import javax.xml.soap.SOAPPart;
import javax.xml.soap.SOAPEnvelope;
import javax.xml.soap.SOAPBody;
import javax.xml.soap.SOAPFault;
import javax.xml.soap.SOAPException;
import javax.xml.soap.Detail;
import javax.xml.soap.DetailEntry;
import java.util.Iterator;
public class Fault {
     protected SOAPFault soapFault;
     public Fault(SOAPMessage msg) throws SOAPException {
          SOAPPart soapPart = msg.getSOAPPart();
          SOAPEnvelope envelope = soapPart.getEnvelope();
          SOAPBody soapBody = envelope.getBody();
          soapFault = soapBody.getFault();
     public static boolean hasFault(SOAPMessage msg) throws SOAPException {
          SOAPPart soapPart = msg.getSOAPPart();
          SOAPEnvelope envelop = soapPart.getEnvelop();
          SOAPBody soapBody = envelop.getBody();
          return soapBody.hasFault();
     public String getFault() {
          return soapFault.getFaultCode();
     public String getFaultString() {
          return soapFault.getFaultString();
     public String getFaultDetail() {
          String ret = null;
          Detail detail = soapFault.getDetail();
          if(null!=detail) {
               Iterator it = detail.getDetailEntries();
               if(it.hasNext()) {
                    DetailEntry detEntry = (DetailEntry)it.next();
               ret = detEntry.getValue();
          return ret;
* RequestMessage.java
package com.aby.jwsdp.soap.client;
import com.aby.jwsdp.soap.client.Client;
import javax.xml.soap.MessageFactory;
import javax.xml.soap.SOAPMessage;
import javax.xml.soap.SOAPPart;
import javax.xml.soap.SOAPEnvelope;
import javax.xml.soap.SOAPBody;
import javax.xml.soap.SOAPElement;
import javax.xml.soap.SOAPException;
public class RequestMessage {
     protected SOAPMessage soapMessage = null;
     public RequestMessage()
     throws SOAPException {
          MessageFactory mf = MessageFactory.newInstance();
          soapMessage = mf.createMessage();
     public void setName(String name)
     throws SOAPException {
          SOAPPart soapPart = soapMessage.getSOAPPart();
          SOAPEnvelope envelope = soapPart.getEnvelope();
          SOAPBody body = envelope.getBody();
          SOAPElement requestElement;
          requestElement = body.addChildElement(envelope.createName("GetValueByName","myns","www.syngress.com/JWSDP/soap-example"));
          SOAPElement paramElement;
          paramElement = requestElement.addChildElement("name");
          paramElement.addTextNode(name);
     public SOAPMessage getMessage() {
          return soapMessage;
check this out then we will see

Web service client timeout

Hi,
I'm trying to set a timeout on my web service client. But its not working. Your tutorials do not seem to address this.
I am using weblogic 10.3.2, with Java 1.6.
============
Properties propSys = System.getProperties();
propSys.put( "weblogic.webservice.UseWebLogicURLStreamHandler", "true" );
Stub stub = (Stub)portObject;
BindingInfo bindingInfo = (weblogic.webservice.binding.BindingInfo)stub._getProperty("weblogic.webservice.bindinginfo");
bindingInfo.setTimeout(1);
Iterator itr = stub._getPropertyNames();
while (itr.hasNext()){
Object element = itr.next();
log("\n properties that can be set: "+element);
stub._setProperty("weblogic.webservice.rpc.timeoutsecs","1");
===========
I've also tried setting the transaction-timeout and the remove-client-timeout in the weblogic-ear-jar.xml.
===========
<weblogic-ejb-jar>
<weblogic-enterprise-bean>
<ejb-name>ExternalEntryEJB</ejb-name>
<transaction-descriptor>
<trans-timeout-seconds>1</trans-timeout-seconds>
</transaction-descriptor>
<enable-call-by-reference>True</enable-call-by-reference>
<jndi-name>ExternalEntry</jndi-name>
<remote-client-timeout>1</remote-client-timeout>
</weblogic-enterprise-bean>
<weblogic-enterprise-bean>
<ejb-name>InternalEJB</ejb-name>
<local-jndi-name>Internal</local-jndi-name>
<enable-call-by-reference>True</enable-call-by-reference>
<remote-client-timeout>1</remote-client-timeout>
<transaction-descriptor>
<trans-timeout-seconds>1</trans-timeout-seconds>
</transaction-descriptor>
</weblogic-enterprise-bean>
</weblogic-ejb-jar>
===========
in case it matters, I am using weblogic.ant.taskdefs.webservices.clientgen.ClientGenTask as the clientgen task in my build.xml
============
<clientgen autotype="False" ear="${dist}/${app.earname}" warName="${servlet.warname}" packageName="MyPackage.webservices.client"
keepgenerated="False" useServerTypes="True" clientJar="${dist}/MyAppClient.jar">
<classpath refid="build.classpath.builddir"/>
</clientgen>
============
I am testing by putting a Thread.sleep(75000) in the method which is called in the internal EJB. But the method runs to completion and returns the reply object after 90 seconds or so (it normally takes about 12 seconds), but does not timeout.
I've been told that because it is a web services client, the remote-client-timeout will be ineffective. I've also been told that because the EJBs run in the same JVM, the transaction-timeout will be ineffective. Is this so?
Thanks,
Walter

Can you change the clientgen task to weblogic.wsee.tools.anttasks.ClientGenTask this is for jax-rpc 1.1.
<taskdef name="clientgen"
classname="weblogic.wsee.tools.anttasks.ClientGenTask" />
((Stub)port)._setProperty(weblogic.wsee.transport.connection.timeout,2);
((Stub)port)._setProperty(weblogic.wsee.transport.read.timeoutt,2);
Hope that helps.

How to implement web service client timeout

I'm trying to implement a web service client using JAX-RPC specification and the client is generated by clientgen utility. We are using weblogic8.1(sp5).
How do I control the connection timeout and data transmission timeout? I have tried:
BindingInfo.setTimeout() method and stub._setProperty("weblogic.webservice.rpc.timeoutsecs", "1" /* secs */);
and they don't seem to be working...
I have searched the web service documentation and didn't found any mentioning on this. Can someone shred some light on this?
Thanks.
Ren
null

Hi,
I had a problem too for setting the timeout of a webservice client. but i didn't find any thing on this.
But there is a work around for this see if it suits you but for this you have to use Apache AXIS webservice api to generate the client in that Api you have the Stub.timeOut() function to over come this problem
Cheers !!
Vivek:-)

Set Web Service Call Timeout

Hi,
in earlier JDeveloper while creating a web service client we used to easily set the call timeout, but now we're using JDev 10.1.3, generating a proxy create a lot of new classes, moreover, the methods calls is not handled the same way it was, but we still need to set the call timeout.
The automaticaly generated code is something like this:
public MyServiceClient() throws Exception {
ServiceFactory factory = ServiceFactory.newInstance();
port = ((servicesource.proxy.MyServiceService)factory.loadService(servicesource.proxy.MyService_Service.class)).getMyService();
this.setEndpoint("http://server/MyService");
nothing extends neither implements the OracleSOAPHTTPConnection (which has the setTimeout method we used to use)
Any ideas?
Thanks.

ahhh,
is there any available explanation why it is not available anymore? specs?
Calls are hanging now, what would be the defaul timeout value?
it can't be changed programmatically? can't we modify it by some global variable/property/xmlFile ?
thank you.

Web Services Connection Timeout

Hello All,
I have a web services client that runs in Tomcat. When making a web service call, I am getting the following exception:
HTTP transport error: java.net.ConnectException: A remote host did not respond within the timeout period.
at com.sun.xml.rpc.client.http.HttpClientTransport.invoke(HttpClientTransport.java:87)
at com.sun.xml.rpc.client.StreamingSender._send(StreamingSender.java:71)
Initially, I thought this was a tomcat problem and just to prove that it was, I added code to make a HTTPS connection to the server that is running the web service. I am able to connect and download the WSDL through the client code running on Tomcat. So this seems to be a web services client problem rather than a tomcat problem. I am using the following:
JDK = 1.3.1
OS = IBM AIX 5.2
Tomcat = 4.1.27
Web Services = 1.1
JAX RPC = 1.0.3
Any help is appreciated.
Regards,
Jeba

I am able to make HTTPS connection from the Tomcat. If is the connection time out, would that affect the straight HTTPS call also. Also this seems to work on a Windows box. The connection timeout is being received on AIX only and I am able to make HTTPS connection from within tomcat. The web service call using HTTPS is getting the connection time out error message.

XML Input String too long to Test Web Service in App Server

We have a Web Service that accepts an XML input string but when we deploy this web service and try to test it through the Application Server it errors out because the input string is too long. Is there any way around this??
Thanks...

Update:
Now I see that there are in fact two error messages. The second one is the one presented above. But the first one says:
Line: 145
Char: 97
Error: Expected ';'
Code: 0
My question now is to what file it is referring?? Is it to ProjectAccountingPort.js that is automatically created? THen why is it not properly created??
Please, please help me with this! The deadline is in a few days...

Long Response of Web Service Causes Timeout

Similar Messages

Maybe you are looking for