Web service timeout

When i communicate with external system using web service call, i can transafer 3500 record. if i run it for more than 3500 records it gives error "SOAP:1,023 SRT: Processing error in Internet Communication".
i tried to use SM59, HTTP connection to external server. current set up is ICM Default timeout..
I want to change but rfc destination is generated and i dont have option to change it to "no timeout" or specify timeout.
you help is appreciated. .

Hello Vipul
Enter the RZ10 and validates the TIMEOUT value of parameter "icm/server_port_<x>" for PROT=HTTP and PROT=HTTPS.
For example, the HTTP service is on port 0 and TIMEOUT=600 seconds
icm/server_port_0 = PROT=HTTP,PORT=80$$,PROCTIMEOUT=600,TIMEOUT=600
in your case, increasing the TIMEOUT and validates the WS again
regards
Juan

Similar Messages

EDQ Web Service Timeout setting

Hi,
We have integrated OEDQ with Siebel. Requests are flowing as expected. Just want to know, how long the connector will be waiting for web service response from OEDQ.
Is there place where timeout is set by default?
Best Regards
Moorthy

Hi,
We have integrated OEDQ with Siebel. Requests are flowing as expected. Just want to know, how long the connector will be waiting for web service response from OEDQ.
Is there place where timeout is set by default?
Best Regards
Moorthy

"JSR 172 Web Service Timeout"

I have successfully used JSR172 and Sun's stub generator to access my web services and it works very nicely. The only hitch I see is that if for some reason ( not very likely but I'd like to handle it anyway ) the Blackberry client connects to the service by never receives a response, it appears to hang indefinitely.
Is there a way to set a time out, since it doesn't seem to fall through normal error trapping
I suppose I could kill the thread after a certain amount of time but that seems rude and would likely cause other problems
This is at the point where the JSR172 Invoke api is called.
thnx in advance...

Hi,
Check parameters *icm/server_port_<xx> *
In my CRM system, I have setup :
icm/server_port_0 = PROT=HTTP,PORT=80,TIMEOUT=90,PROCTIMEOUT=600
The PROCTIMEOUT is the one interesting for you.
I have set up it to 600 seconds to get the same timeout as with the sapgui.
Check also rdisp/plugin_auto_logout but it is more useful for the webui than for web services.
Regards,
Olivier

Web service Timeouts

Version : Informatica 9.6.1 Hot Fix 1Installation Server : AIX server Informatica workflow reads records from an Oracle table and makes a web service calls. I am seeing the below error message in the session log. Time out defined in the connection object is 450s (7.5 min). Need you inputs in understanding the timeouts i am seeing in the session log. The job runs in 4 partitions and i see few transactions getting dropped as well during this web service calls. Open Issues1. Where does this timeout enforced? In the application level the request completes before 7 mins.2. Why does Informatica drops requests while making web service calls (partition is pass through). Session Log ErrorTRANSF_1_2_4> PMWS_33016 [ERROR] Web Service invoker encountered an error while invoking the Web Service. Reason: Operation timed out after 60014 milliseconds with 0 out of -1 bytes receivedTRANSF_1_2_4> CMN_1761 Timestamp Event: [Wed Jul 15 04:05:19 2015]TRANSF_1_2_4> PMWS_33016 [ERROR] Web Service invoker encountered an error while invoking the Web Service. Reason:TRANSF_1_2_4> CMN_1761 Timestamp Event: [Wed Jul 15 04:06:19 2015]TRANSF_1_2_4> PMWS_33016 [ERROR] Web Service invoker encountered an error while invoking the Web Service. Reason: Operation timed out after 60069 milliseconds with 0 out of -1 bytes received

Hi all, Please help me with metadata query to extract each session RUN_DURTION, Start Time, end time for last 10 runs of each session at a workflow level. I know we can get information from REP_WFLOW_RUN table but i dont know table strucure and I dont have access to Repository database and we need an exact query to raise it to admin team. so please provide me an exact query. Thanks

Where to increase Web Service timeout property

Hello All,
I have developed a stateless java web service that executes a sql query.
Query exectung for more than 5 minutes by the time the web service is throughing an exception:
****************Exception Message**********************
WARNING: Unable to connect to URL: http://testhost.appsassociates.com:7781/TimeOutTest/TimeOutTestSoapHttpPort due to java.security.PrivilegedActionException: oracle.j2ee.ws.saaj.ContentTypeException: Not a valid SOAP Content-Type: text/html; charset=iso-8859-1
java.rmi.RemoteException: ; nested exception is:
     HTTP transport error: javax.xml.soap.SOAPException: java.security.PrivilegedActionException: oracle.j2ee.ws.saaj.ContentTypeException: Not a valid SOAP Content-Type: text/html; charset=iso-8859-1
     at proxycallertimeout.proxy.runtime.TimeOutTestSoapHttp_Stub.testMethod(TimeOutTestSoapHttp_Stub.java:84)
     at proxycallertimeout.proxy.TimeOutTestSoapHttpPortClient.testMethod(TimeOutTestSoapHttpPortClient.java:43)
     at proxycallertimeout.proxy.TimeOutTestSoapHttpPortClient.main(TimeOutTestSoapHttpPortClient.java:30)
Caused by: HTTP transport error: javax.xml.soap.SOAPException: java.security.PrivilegedActionException: oracle.j2ee.ws.saaj.ContentTypeException: Not a valid SOAP Content-Type: text/html; charset=iso-8859-1
     at oracle.j2ee.ws.client.http.HttpClientTransport.invokeImpl(HttpClientTransport.java:174)
     at oracle.j2ee.ws.client.http.HttpClientTransport.invoke(HttpClientTransport.java:150)
     at oracle.j2ee.ws.client.StreamingSender._sendImpl(StreamingSender.java:176)
     at oracle.j2ee.ws.client.StreamingSender._send(StreamingSender.java:113)
     at proxycallertimeout.proxy.runtime.TimeOutTestSoapHttp_Stub.testMethod(TimeOutTestSoapHttp_Stub.java:77)
If query tekes less time to finish everything is working fine.
How to make the webservice wait for more time.
Thanks
Saikrishna

Async process can be fire and forget, meaning you don't ever want to response from the client. You can also have a response that will return in any time in the future.
A human task is an example of this. You create a work list for someone. The BPEL process waits for the person to either accept or reject.
The beauty of calling a BPEL process is that this is managed out of the box. If you are doind some bespoke development then you may need to use correlation sets.
cheers
James

Web Service Timeout & connection errors

Using jwsdp 2, i have developed a client that has a timeout property set. How are timeouts processed? Is an exception thrown by the port? or does the web method just return with a null return value?
I also have noticed that in simulating a connection error (by stopping my app server) that an exception is thrown by the web method? but the exception is a javax.xml.ws.WebServiceException. How do I distinguish connection errors from other exceptions? what other exceptions are there?
Basically, where is this info documented?

Hello Vipul
Enter the RZ10 and validates the TIMEOUT value of parameter "icm/server_port_<x>" for PROT=HTTP and PROT=HTTPS.
For example, the HTTP service is on port 0 and TIMEOUT=600 seconds
icm/server_port_0 = PROT=HTTP,PORT=80$$,PROCTIMEOUT=600,TIMEOUT=600
in your case, increasing the TIMEOUT and validates the WS again
regards
Juan

Web Services Timeout

I have a problem to specify the timeout of a service web. I have a client who accedes with Axis to a service web. I have the following code but it does not work:
locator= new Locator();
servicio= locator.getPort();
((org.apache.axis.client.Stub)(servicio)).setTimeout(Constantes.TIME_OUT);
servicio.saluda("Juan");
As I have the timeout of the Axis understood it is not of connection, but itcontrols the timeout when already these connected to the service web. There exists some way of specifying timeout of connection (socket)? Some suggestion?
The problem that I have is that the application continues waiting for the connection for the service web until he(she) returns the following mistake:
AxisFault
faultCode: {http://schemas.xmlsoap.org/soap/envelope/}Server.userException
faultSubcode:
faultString: java.net.ConnectException: Connection timed out
faultActor:
faultNode:
faultDetail:
{http://xml.apache.org/axis/}stackTrace: java.net.ConnectException: Connection timed out
at java.net.PlainSocketImpl.socketConnect(Native Method)
at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:305)
at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:171)
at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:158)
at java.net.Socket.connect(Socket.java:452)
at java.net.Socket.connect(Socket.java:402)
at java.net.Socket.<init>(Socket.java:309)
at java.net.Socket.<init>(Socket.java:124)
at org.apache.axis.components.net.DefaultSocketFactory.create(DefaultSocketFactory.java:129)
at org.apache.axis.transport.http.HTTPSender.getSocket(HTTPSender.java:157)
at org.apache.axis.transport.http.HTTPSender.invoke(HTTPSender.java:114)
at org.apache.axis.strategies.InvocationStrategy.visit(InvocationStrategy.java:71)
at org.apache.axis.SimpleChain.doVisiting(SimpleChain.java:150)
at org.apache.axis.SimpleChain.invoke(SimpleChain.java:120)
at org.apache.axis.client.AxisClient.invoke(AxisClient.java:180)
at org.apache.axis.client.Call.invokeEngine(Call.java:2564)
at org.apache.axis.client.Call.invoke(Call.java:2553)
at org.apache.axis.client.Call.invoke(Call.java:2248)
at org.apache.axis.client.Call.invoke(Call.java:2171)
at org.apache.axis.client.Call.invoke(Call.java:1691)
java.net.ConnectException: Connection timed out
at org.apache.axis.AxisFault.makeFault(AxisFault.java:129)
at org.apache.axis.transport.http.HTTPSender.invoke(HTTPSender.java:131)
at org.apache.axis.strategies.InvocationStrategy.visit(InvocationStrategy.java:71)
at org.apache.axis.SimpleChain.doVisiting(SimpleChain.java:150)
at org.apache.axis.SimpleChain.invoke(SimpleChain.java:120)
at org.apache.axis.client.AxisClient.invoke(AxisClient.java:180)
at org.apache.axis.client.Call.invokeEngine(Call.java:2564)
at org.apache.axis.client.Call.invoke(Call.java:2553)
at org.apache.axis.client.Call.invoke(Call.java:2248)
at org.apache.axis.client.Call.invoke(Call.java:2171)
at org.apache.axis.client.Call.invoke(Call.java:1691)
Caused by: java.net.ConnectException: Connection timed out
at java.net.PlainSocketImpl.socketConnect(Native Method)
at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:305)
at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:171)
at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:158)
at java.net.Socket.connect(Socket.java:452)
at java.net.Socket.connect(Socket.java:402)
at java.net.Socket.<init>(Socket.java:309)
at java.net.Socket.<init>(Socket.java:124)
at org.apache.axis.components.net.DefaultSocketFactory.create(DefaultSocketFactory.java:129)
at org.apache.axis.transport.http.HTTPSender.getSocket(HTTPSender.java:157)
at org.apache.axis.transport.http.HTTPSender.invoke(HTTPSender.java:114)
... 13 more

Hi
I used axis to generate the stubs..
In the stub "MySericeSoapStub extends org.apache.axis.client.Stub"
i added the following line in the createCall() Routine
protected org.apache.axis.client.Call createCall() throws java.rmi.RemoteException {
try {
org.apache.axis.client.Call call = super.createCall();
System.out.println( "Calling :"+ super.cachedEndpoint) ;
_call.setTimeout( new Integer(10000) ) ;
System.out.println( "Setting the timeout 10 seconds ..." ) ;
if (super.maintainSessionSet) {
_call.setMaintainSession(super.maintainSession);
.......................

BAM getting random timeouts calling BPEL web service as alert rule

I have a BAM alert rule set up to call a BPEL process (web service call basically). This is part of our custom error notification and escalation solution.
In production I randomly see timeouts in the BAM event engine logs where the web service call has timed out. On the BPEL side these processes never show as being invoked, nor are they in manual recovery.
This only happens at random times, although usually in "clumps" lasting a few minutes. The rest of the time this has been fairly reliable.
Any help from the BAM experts would be appreciated. I would open an SR on this, but I have found support to literally take days/weeks to get back to me on BAM issues -- and this particular issue does not seem to be reliably reproduceable.
Here is the event engine log message:
2008-01-31 14:46:35,303 [ActionThreadPool (dynamic 11309)] ERROR - EventEngine Action exception: EEInstEv218067 EEInstAct218066 Rule Id: 1 exception: The operation has timed-out. (http://mcsbpel:8888/orabpel/MAEF/svcMaefErrorAlert/1.0)
2008-01-31 14:46:35,303 [ActionThreadPool (dynamic 11304)] ERROR - EventEngine Action exception: EEInstEv218066 EEInstAct218065 Rule Id: 1 exception: The operation has timed-out. (http://mcsbpel:8888/orabpel/MAEF/svcMaefErrorAlert/1.0)
2008-01-31 14:46:35,303 [ActionThreadPool (dynamic 11309)] WARN - EventEngine Exception stack trace: at Oracle.BAM.Middleware.EventEngine.ExternalActions.WebServiceCaller.TakeAction(Hashtable oParameters, String strDataObject, Hashtable oDataValues, Hashtable oDataTypes)
at Oracle.BAM.EventEngine.Actions.TakeExternalAction.TakeAction(String strSysIterID, Hashtable oParameters, String strDatasetName, XmlDocument xmlSchemaDoc, IDictionary intDataDictionary)
at Oracle.BAM.EventEngine.Actions.ActionProcessor.ExternalAction(ActionQueueItem oActionQueueItem)
at Oracle.BAM.EventEngine.Actions.ActionProcessor.ActionHandler(Object state, DateTime requestEnqueueTime)
2008-01-31 14:46:35,303 [ActionThreadPool (dynamic 11304)] WARN - EventEngine Exception stack trace: at Oracle.BAM.Middleware.EventEngine.ExternalActions.WebServiceCaller.TakeAction(Hashtable oParameters, String strDataObject, Hashtable oDataValues, Hashtable oDataTypes)
at Oracle.BAM.EventEngine.Actions.TakeExternalAction.TakeAction(String strSysIterID, Hashtable oParameters, String strDatasetName, XmlDocument xmlSchemaDoc, IDictionary intDataDictionary)
at Oracle.BAM.EventEngine.Actions.ActionProcessor.ExternalAction(ActionQueueItem oActionQueueItem)
at Oracle.BAM.EventEngine.Actions.ActionProcessor.ActionHandler(Object state, DateTime requestEnqueueTime)

I should note that both BPEL and BAM are at version 10.1.3.1

Timeout when consuming a SOAP web service

Hello,
I'm quite new to Labview and I'm trying to consume a SOAP web service created using a very simple WCF example, but I keep on getting a WebException because of a timeout.
The web service has been created using the example from the WCF getting started tutotial (to keep things simple) http://msdn.microsoft.com/en-us/library/ms734712.aspx
You'll find my .Net solution attached to this message. (You'll have to be administrator to run the service though).
I have used the import web service tool in Labview to create the VI to connect to the web service and all went fine, it created the VI correctly. You'll find the created VI also attached to this message.
Then, I'm trying to create a very simple VI to call the webservice and put the return value inside a numeric indicator. Unfortunately, when I run this VI it crashes with a WebException because of a timeout.
If I run the .Net client, everything goes fine, and if I go to the web service address with a browser, I get the service website, so I know that the server is registered correctly, only Labview can't connect to it for an unknown reason. Everything is setup to connect through localhost:8000, so it can't really be a network problem, I've tried disabling the Windows firewall to see if that was the problem, but it persists.
I've also tried to do something similar using the CDYNE web service, like in the example http://www.ni.com/white-paper/4728/en/, and it works perfectly.
Does anybody have an idea about what could be the issue?
Regards.
Attachments:
WcfTestApp.zip ‏453 KB
_Calculator.zip ‏72 KB

OK, I found the problem myself, it was a problem with the configuration of the WCF service, I was missing the ServiceMetadata endpoint.
For reference, if somebody stumbles upon the same issue as I had, here's a service configuration that works with Labview (using .Net >=4.0)
  <system.serviceModel>
    <behaviors>
      <serviceBehaviors>
        <behavior name="">
          <serviceMetadata httpGetEnabled="true" />
          <serviceDebug includeExceptionDetailInFaults="true" />
        </behavior>
      </serviceBehaviors>
    </behaviors>
    <protocolMapping>
      <add scheme="http" binding="basicHttpBinding" />
    </protocolMapping>
  </system.serviceModel>
And here's how to create and run the service host.
using (ServiceHost selfHost = new ServiceHost(typeof(Calculator), new Uri("http://localhost:8000/Calculator")))
                try
                    selfHost.Open();
                    Console.ReadLine();
                    selfHost.Close();
                catch (CommunicationException e)
                    selfHost.Abort();
                    throw;

Invoking web service from OBIEE11g failed socket timeout

Hi,
I encountered an error when I invoke web service from OBIEE 11g. The web serivce resides on Websphere running on other machine.
An error says that "Invoking web service failed due to socket timeout." and it seems that it stopped in just 40 secs.
Is there any settings of WebLogic server to avoid this? This web service normally runs for more than 60 sec.
I have checked several parameters in WebLogic admin console and changed those values, but I still receive the same error.
Invoking the same web service from SOAPUI sustains for more than 60 secs.
Regards,
Fujio Sonehara

Don't be too surprised. Sun figured this bug out in short order. I got the same error message when trying to do the same thing, just for the heck of it. Reference this article for details.
http://java.sun.com/webservices/docs/ea2/jaxrpc/ReleaseNotes.html
It contains information about bugs fixed in the WSDP EA2. So in answer to your question, download the newer pack from
http://java.sun.com/webservices/downloads/webservicespack.html
and your bug will go away. Happy Coding.
Legal Problems?
Legal Solutions, for a lot less than you might think.
[email protected]
http://www.prepaidlegal.com/go/pritchard45

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

Setting timeout of web service client

I created a web service client using the java proxy for
a web service by running my web service in weblogic workshop test browser and by using
the jar file created by clicking on "Java Proxy" button.
i am calling my web service my adding code similar to this and it works
HelloWorld_Impl proxy = new HelloWorld_Impl();
HelloWorldSoap soapProxy = proxy.getHelloWorldSoap();
But, i am not sure how to set the timeout of my client programatically.
Is there a way to do this ?
Any help is greatly appreciated.

Anyway,
I figured it out myself, by looking at other posts and applying some reflection API
HelloWorld_Impl proxy = new HelloWorld_Impl();
HelloWorldSoap soapProxy = proxy.getHelloWorldSoap();
// I learnt that this soapProxy is infact an object of HelloWorldSoap_Stub class
HelloWorldSoap_Stub myStub = (HelloWorldSoap_Stub)proxy.getHelloWorldSoap();
BindingInfo bInfo = (BindingInfo)myStub._getProperty("weblogic.webservice.bindinginfo");
bInfo.setTimeout(5); //secs
myStub._setProperty("weblogic.webservice.rpc.timeoutsecs", "5"); // secs
// finally you can call the methods of the web service
soapProxy.Hello();
Please be aware that, upon time out, you would get an exception : <class = java.rmi.RemoteException
cause = javax.xml.rpc.soap.SOAPFaultException: javax.xml.rpc.JAXRPCException:java.net.SocketTimeoutException: Read timed out.>
Also, my env : Weblogic 8.1 SP4

Setting timeout in Oracle Web Service Callouts

We have a 10.1.0.4 Enterprise DB with dbwsclient.jar loaded. Currently using the database callouts. The problem is there seems to be no timeout when the called web service does not respond. I did not see a setting for the socket timeout in the code produced by JPublisher.
Thanks

Hi,
Where the properties need to be put and how can they be read really depends on how your Web Service is implemented. What is the WS based on - EJB, POJO, PL/SQL, JMS...?
Yogesh

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.

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.

Web service timeout

Similar Messages

Maybe you are looking for