SOAP time out

Hello.
I have an application that use the API of the portal. There are several activities that are performed but the time used for doing them is so much. As a consequence, a SOAP client null message appear in the application. I can't decrease the time used by the application. However, I need to increase the time out of the SOAP connection.
Does anyone know how to set the time out to a SOAP application?
Thanks,
Luis.

There is currently no support to increase the SOAP timeout programmatically. The default is set to 1 min in PRC.

Similar Messages

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.

Soap Reciver Time out connection

hai,
iam doing idoc to soap. iam send the data from sap side this data is going xi server but problem is reciver side is connection time out. iam check the monitoring in sxmb_moni the status is block flag status is successful going to xi server and xiserver sending to receiver system the receiver is connection is time out iam providing the reciver url and user name and pwd.
plz help me any this is very urgent.

After checking in sxmb_adm even when i send the data iam getting the same error.
<SAP:AdditionalText>com.sap.aii.af.ra.ms.api.RecoverableException: Connection timed out: connect: java.net.ConnectException: Connection timed out: connect</SAP:AdditionalText>
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack />
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
plz help me out .

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

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.

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

SOAP ADPTER TIME OUT

hi
i am getting error.
SOAP: call failed java.net. connect exception: connection time out.
Kindly suggest how 2 increase time out.
Sachin

Hi Sachin,
It could be a connection time out issue or it could be that the web service is unavailable or in even some remote cases this error has come up due to the firewall itself.
Source:SOAP Receiver adapter error. SOAP CALL Failed
Regarding timeout parameter increase it through visual admin ask your basis guy to do it for you.
Regards
joel
Edited by: joel trinidade on Mar 18, 2009 2:50 PM

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.

Time Out Error in BPEL

Hi,
We are trying to invoke a Web Service from BPEL Process (10.1.3.3.0) and we received below time out error message in em console.
</part></Invoke_1_setJobPostingXML_InputVariable></input><fault><remoteFault xmlns="http://schemas.oracle.com/bpel/extension"><part name="summary"><summary>exception on JaxRpc invoke: HTTP transport error: javax.xml.soap.SOAPException: java.security.PrivilegedActionException: javax.xml.soap.SOAPException: Message send failed: Read timed out</summary>
Problem here is this error is not coming for all the invocation. For ex. We have posted the input payload at 3:15:34PM today and it thrown an error at 3:45:12 PM with above message. Also its not huge load hitting their server as we are calling the webservice once in 4-5 mins and if we repost the same message, its posting without any issue. This time out error comes 4-5 times daily and want to understand why it occurs everyday.
1. Will BPEL receive an error if we post huge payload to web service?
2. Do we need to set some waiting time to receive the response after posting the data to Web service?
3. Other possible scneario's for timeout error?
Thanks,
Saravana

Hi Saravana,
It's likely to be a problem at the remote side or a network latency/communication problem...
How can you affirm "its not huge load hitting their server"? Your service may not be the only source of load...
Cheers,
Vlad

Time Out Error while waiting for response from DB Procedure

Hi Gurus,
We are encountering a problem in our production environment. The system is implemented using AIA foundation pack 2.5 on SOA suite 10.1.3.4.
We have a BPEL process A which calls an ESB Service which inturn calls BPEL Process B. In process B, we have a DB procedure call which waits for a response from
a DB procedure. The procedure doesn't reply on time and Process B remains in waiting state to get the response from DB Procedure wherein Process A errors out by showing as "Timed Out Error".
This issue is intermittent and we have already increased transaction-time outs in transaction-manager.xml to 7200 and ejb-orion-jar.xml to 3600.
When we encountered this problem, we found out that there are too many connections open and when we bounced the server, everything was restored to nornal but as it is a production env. we can't do it over and over again.
We have 2 nodes each having max connections as 100 and min. as 0.
Is there a limit to max no. of connections or can we do something in DB side to ensure that it doesn't happen again ?
Please suggest.
Thanks,
Vikas Manchanda

Hi Anuj,
I don't think it is a problem with connection reaching to max numbers because this issue is coming on very intermittent basis.we don't have any other processes using
the same connection pool and this issue is coming even when there is no load on the server. This is recent trace from the production environment. Also i don't have any thing called "abandoned-connection-pool" in my data-sources.xml.
<2011-07-07 13:09:16,101> <ERROR> <default.collaxa.cube> <BaseCubeSessionBean::logError> Error while invoking bean "delivery": Waiting for response has timed out. The conversation id is null. Please check the process instance for detail.
com.oracle.bpel.client.delivery.ReceiveTimeOutException: Waiting for response has timed out. The conversation id is null. Please check the process instance for detail.
at com.collaxa.cube.ejb.impl.DeliveryBean.request(DeliveryBean.java:109)
at sun.reflect.GeneratedMethodAccessor113.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:592)
at com.evermind.server.ejb.interceptor.joinpoint.EJBJoinPointImpl.invoke(EJBJoinPointImpl.java:35)
at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:119)
at com.evermind.server.ejb.interceptor.system.DMSInterceptor.invoke(DMSInterceptor.java:52)
at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:119)
at com.evermind.server.ejb.interceptor.system.JAASInterceptor$1.run(JAASInterceptor.java:31)
at com.evermind.server.ThreadState.runAs(ThreadState.java:693)
at com.evermind.server.ejb.interceptor.system.JAASInterceptor.invoke(JAASInterceptor.java:34)
at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:119)
at com.evermind.server.ejb.interceptor.system.TxRequiredInterceptor.invoke(TxRequiredInterceptor.java:50)
at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:119)
at com.evermind.server.ejb.interceptor.system.DMSInterceptor.invoke(DMSInterceptor.java:52)
at com.evermind.server.ejb.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:119)
at com.evermind.server.ejb.InvocationContextPool.invoke(InvocationContextPool.java:55)
at com.evermind.server.ejb.StatelessSessionEJBObject.OC4J_invokeMethod(StatelessSessionEJBObject.java:87)
at DeliveryBean_RemoteProxy_4bin6i8.request(Unknown Source)
at com.collaxa.cube.ws.soap.oc4j.SOAPRequestProvider.processNormalOperation(SOAPRequestProvider.java:451)
at com.collaxa.cube.ws.soap.oc4j.SOAPRequestProvider.processBPELMessage(SOAPRequestProvider.java:274)
at com.collaxa.cube.ws.soap.oc4j.SOAPRequestProvider.processMessage(SOAPRequestProvider.java:120)
at oracle.j2ee.ws.server.provider.ProviderProcessor.doEndpointProcessing(ProviderProcessor.java:956)
at oracle.j2ee.ws.server.WebServiceProcessor.invokeEndpointImplementation(WebServiceProcessor.java:349)
at oracle.j2ee.ws.server.provider.ProviderProcessor.doRequestProcessing(ProviderProcessor.java:466)
at oracle.j2ee.ws.server.WebServiceProcessor.processRequest(WebServiceProcessor.java:114)
at oracle.j2ee.ws.server.WebServiceProcessor.doService(WebServiceProcessor.java:96)
at oracle.j2ee.ws.server.WebServiceServlet.doPost(WebServiceServlet.java:194)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:763)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:856)
at com.evermind.server.http.ResourceFilterChain.doFilter(ResourceFilterChain.java:64)
at oracle.security.jazn.oc4j.JAZNFilter$1.run(JAZNFilter.java:400)
at java.security.AccessController.doPrivileged(Native Method)
at javax.security.auth.Subject.doAsPrivileged(Subject.java:517)
at oracle.security.jazn.oc4j.JAZNFilter.doFilter(JAZNFilter.java:414)
at com.evermind.server.http.ServletRequestDispatcher.invoke(ServletRequestDispatcher.java:623)
at com.evermind.server.http.ServletRequestDispatcher.forwardInternal(ServletRequestDispatcher.java:370)
at com.evermind.server.http.HttpRequestHandler.doProcessRequest(HttpRequestHandler.java:871)
at com.evermind.server.http.HttpRequestHandler.processRequest(HttpRequestHandler.java:453)
at com.evermind.server.http.AJPRequestHandler.run(AJPRequestHandler.java:313)
at com.evermind.server.http.AJPRequestHandler.run(AJPRequestHandler.java:199)
at oracle.oc4j.network.ServerSocketReadHandler$SafeRunnable.run(ServerSocketReadHandler.java:260)
at com.evermind.util.ReleasableResourcePooledExecutor$MyWorker.run(ReleasableResourcePooledExecutor.java:303)
at java.lang.Thread.run(Thread.java:595)
Caused by: com.oracle.bpel.client.delivery.ReceiveTimeOutException: Waiting for response has timed out. The conversation id is null. Please check the process instance for detail.
at com.collaxa.cube.engine.delivery.DeliveryHandler.initialRequestAnyType(DeliveryHandler.java:576)
at com.collaxa.cube.engine.delivery.DeliveryHandler.initialRequest(DeliveryHandler.java:465)
at com.collaxa.cube.engine.delivery.DeliveryHandler.request(DeliveryHandler.java:134)
at com.collaxa.cube.ejb.impl.DeliveryBean.request(DeliveryBean.java)
Please suggest.
Thanks,
Vikas Manchanda

Management console-connection time out please help

after Composite environment installation,first time I am trying to open the management console. It throws a dialog window connection error. and in the text message connection to <host name and nr > failed.
In the exception message, i can see connection time out:connect
Here is the log
java.net.ConnectException: Connection timed out: connect
     at java.net.PlainSocketImpl.socketConnect(Native Method)
     at java.net.PlainSocketImpl.doConnect(Unknown Source)
     at java.net.PlainSocketImpl.connectToAddress(Unknown Source)
     at java.net.PlainSocketImpl.connect(Unknown Source)
     at java.net.SocksSocketImpl.connect(Unknown Source)
     at java.net.Socket.connect(Unknown Source)
     at java.net.Socket.connect(Unknown Source)
     at java.net.Socket.<init>(Unknown Source)
     at java.net.Socket.<init>(Unknown Source)
     at com.sap.engine.services.webservices.jaxm.soap.HTTPSocket.initStreamsFromSocket(HTTPSocket.java:648)
     at com.sap.engine.services.webservices.jaxm.soap.HTTPSocket.initializeStreams(HTTPSocket.java:470)
     at com.sap.engine.services.webservices.jaxm.soap.HTTPSocket.getOutputStream(HTTPSocket.java:427)
     at com.sap.engine.services.webservices.jaxrpc.wsdl2java.soapbinding.HTTPTransport.getRequestStream(HTTPTransport.java:355)
     at com.sap.engine.services.webservices.jaxrpc.wsdl2java.soapbinding.MimeHttpBinding.outputMessage(MimeHttpBinding.java:548)
     at com.sap.engine.services.webservices.jaxrpc.wsdl2java.soapbinding.MimeHttpBinding.call(MimeHttpBinding.java:1425)
     at com.sap.managementconsole.soap.sap.sapcontrol.SAPControlStub.getInstanceProperties(SAPControlStub.java:1248)
     at com.sap.managementconsole.dataloader.soap.sap.SAPSOAPDataLoader.getInstanceProperties(SAPSOAPDataLoader.java:823)
     at com.sap.managementconsole.dataloader.soap.sap.SAPSOAPDataLoader.<init>(SAPSOAPDataLoader.java:87)
     at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
     at sun.reflect.NativeConstructorAccessorImpl.newInstance(Unknown Source)
     at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(Unknown Source)
     at java.lang.reflect.Constructor.newInstance(Unknown Source)
     at com.sap.managementconsole.common.SapControlInterfaceFactory.getControlInterface(SapControlInterfaceFactory.java:91)
     at com.sap.managementconsole.common.DataLoader.createControlInterface(DataLoader.java:313)
     at com.sap.managementconsole.common.DataLoader.startup(DataLoader.java:232)
     at com.sap.managementconsole.common.DataLoader.access$100(DataLoader.java:64)
     at com.sap.managementconsole.common.DataLoader$1.execute(DataLoader.java:437)
     at com.sap.managementconsole.operations.AuthorizedOperation.execute(AuthorizedOperation.java:38)
     at com.sap.managementconsole.common.DataLoader.reinitialize(DataLoader.java:444)
     at com.sap.managementconsole.common.DataLoader.run(DataLoader.java:542)
     at java.lang.Thread.run(Unknown Source)

Hello,
Can you post the std_server0 log ?
Regards,
Siddhesh

Time Out Settings in OSB

Hi All,
I have a service which calls DB via DB adapter. For the webservice call, I have an option of read time out settings in the business service, so that it will get time out after the configured time period.
But for the DB call I dont have this option in the business service and we are getting stuck thread exceptions when the legacy is taking more time to respond back. We have a requirement that all the services realted to DB call have to get time out when the legacy takes more time.
Kindly help me in doing this.
Thanks and Regards,
Prabhu

Hi Anuj,
I did a sample stored procedure which will wait for number of seconds which we send as input and will send the success repose after the number of seconds.
StoredProcedure:
create or replace
procedure sleep (seconds in number,response out varchar2) as testdata number;
begin
testdata := seconds;
dbms_lock.sleep(testdata);
response := 'SUCCESS';
end;
Business Service XML:
<?xml version="1.0" encoding="UTF-8"?>
<xml-fragment xmlns:ser="http://www.bea.com/wli/sb/services" xmlns:tran="http://www.bea.com/wli/sb/transports" xmlns:env="http://www.bea.com/wli/config/env" xmlns:jca="http://www.bea.com/wli/sb/transports/jca" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<ser:coreEntry isProxy="false" isEnabled="true">
<ser:binding type="SOAP" isSoap12="false" xsi:type="con:SoapBindingType" xmlns:con="http://www.bea.com/wli/sb/services/bindings/config">
<con:wsdl ref="Sleep2/Sleep_dbBS"/>
<con:binding>
<con:name>Sleep_ptt-binding</con:name>
<con:namespace>http://xmlns.oracle.com/pcbpel/adapter/db/Application1/Project2/Sleep</con:namespace>
</con:binding>
</ser:binding>
<ser:monitoring isEnabled="false">
<ser:aggregationInterval>10</ser:aggregationInterval>
<ser:pipelineMonitoringLevel>Pipeline</ser:pipelineMonitoringLevel>
</ser:monitoring>
<ser:reporting>true</ser:reporting>
<ser:sla-alerting isEnabled="true">
<ser:alertLevel>normal</ser:alertLevel>
</ser:sla-alerting>
<ser:ws-policy>
<ser:binding-mode>wsdl-policy-attachments</ser:binding-mode>
</ser:ws-policy>
</ser:coreEntry>
<ser:endpointConfig>
<tran:provider-id>jca</tran:provider-id>
<tran:inbound>false</tran:inbound>
<tran:URI>
<env:value>jca://eis/DB/SleepConnection1</env:value>
</tran:URI>
<tran:outbound-properties>
<tran:load-balancing-algorithm>round-robin</tran:load-balancing-algorithm>
<tran:retry-count>0</tran:retry-count>
<tran:retry-interval>30</tran:retry-interval>
<tran:retry-application-errors>true</tran:retry-application-errors>
</tran:outbound-properties>
<tran:all-headers>false</tran:all-headers>
<tran:provider-specific>
<jca:jca-file ref="Sleep2/Sleep_db"/>
<jca:adapter-name>Sleep</jca:adapter-name>
<jca:adapter-type>DATABASE</jca:adapter-type>
<jca:always-use-wsdl>true</jca:always-use-wsdl>
<jca:connection-mode>managed</jca:connection-mode>
<jca:outbound-properties>
<jca:operation-properties>
<jca:operation-name>Sleep</jca:operation-name>
<jca:spec-properties>
<jca:property>
<jca:name>ProcedureName</jca:name>
<jca:value>SLEEP</jca:value>
</jca:property>
<jca:property>
<jca:name>QueryTimeout</jca:name>
<jca:value>2</jca:value>
</jca:property>
<jca:property>
<jca:name>GetActiveUnitOfWork</jca:name>
<jca:value>false</jca:value>
</jca:property>
</jca:spec-properties>
</jca:operation-properties>
</jca:outbound-properties>
</tran:provider-specific>
</ser:endpointConfig>
</xml-fragment>
When I run this from the business service, if I give the input as 10, we are getting error only after 10 seconds not in the query time out seconds. But the thing is we are getting error. If we set the time as 11 seconds we are getting success response. But our requirement is the procedure has to time out in the specified seconds. Kindly correct me if I am wrong.
Regards,
Prabhu

SSO Partner Application and Session Time out

Hi ,
We have an application on forums.oracle.com which is implementing the Authentication scheme as SSO, that is working well, now we want to implement Session Time out if the user is idle for some time and ask him to login again after the session fails, I have tried to implement this feature as given by Scott in the thread session timeout , well the problem is since we dont have a login page here how do we set the cookies owa_cookie.send(
name => 'HTMLDB_IDLE_SESSION',
value => to_char(sysdate+(20/1440),'DD-MON-YYYY HH24:MI:SS'),
expires => null,
path => '/',
domain => null
and where is the current point to implement it.
Any help on this is greatly welcome.
Thanks in Advance.

Naveen,
I don't remember how the solution works. But if you don't have a login page you can usually put code in the post-authentication process of your authentication scheme to do whatever the login page process would have done.
Scott

CRM WEB UI - Time out Pop-up

Dear All,
We have a business requirement to monitor and optimize the CRM WEB UI timeout and other related issues.
I would like to have time-out pop-up for the call center agents and hence they could better manage the sessions .
This will avoid loosing the valuable customer data for the session and so on.
We are now working on the following threads with CRM Technical folks.
Please share your experience or the detailed steps if you had implemented already.
SAP note 1877120 - CRM-IC: session timeout issue with CRM 7 EHP1 and higher
Also , have a look http://scn.sap.com/community/crm/webclient-ui-framework/blog/2012/05/17/session-time-out-warning-message-on-ui
2092893 - Session Time Out Notification
Regards
Venkat

Hello Venkat,
For business roles of type IC Webclient, you have to implement SAP Note 1877120. Don't forget to update your view layout in your custom enhancement if you have enhanced CRMCMP_IC_FRAME/HiddenView.
After implementation of 1887120, also implement 1977631 and 1955366.
Best Regards,
Sigrid

SOAP time out

Similar Messages

Maybe you are looking for