HTTP time out Error in BPM.....

Hi
Error Description:
We have created a Sync-Async Bridge BPM scenario in XI.
In the BPM scenario we are calling the web service, and if the response from the web service is an error message then we have retry in a loop up to 24 times after wait for every 1 min.
We are sending the data to the web service using a proxy created in the R/3 system.
We are getting the time out error in the R/3 system. 
We have changed the following parameters in XI.
In SXMB_ADM of XI we have set the value for the following parameter.
Category                      parameter                                                                    current value
SA_COMM                    CHECK_FOR_ASYNC_RESPONSE_TIMEOUT                120
In SXMB_ADM of R/3 we have set the value for the following parameter.
Category                      parameter                                                                    current value
RUNTIME                      HTTP_TIMEOUT                                                            120
When we put the value as 120 for the above parameters and we try for 2 times in the BPM process, then it is sending the response back to the R/3 system after completing the whole BPM process.
But when we increase the no of retries in the BPM process then it is not sending the response back to the R/3 system in the same way, at that time we are getting the error in SXMB_MONI of R/3 system as given below.
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
-   <!--
    Inbound Message
  -->
- <SAP:ErrorHeader xmlns:SAP="http://sap.com/exchange/MessageFormat">
  <SAP:Context />
  <SAP:Code p1="500" p2="Timeout" p3="" p4="">HTTP.HTTP_STATUS_CODE_NEQ_OK</SAP:Code>
  <SAP:Text language="EN">HTTP status code 500 : Timeout</SAP:Text>
  </SAP:ErrorHeader>
Please provide the solution for the same.
Many Thanks
Rinku Gangwani

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

Similar Messages

  • 402,HTTP-TIME-OUT-Error

    Hi all,
    The scenario is FILE to FILE,While executing the scenario,I see 402,HTTP-TIME-OUT-Error in SXMB_MONI,The file are placed at respective destinations.I dont understand why I see error in MONI.
    Thanks,
    Srinivasa

    hi,
    Go through this blog..
    /people/michal.krawczyk2/blog/2006/06/08/xi-timeouts-timeouts-timeouts
    Regards,
    Sarvesh

  • Connection time out error in HTTP

    Hey guys
    i m getting connection time out error in a HTTP scenario,when i go in SXMB_ADM i dont find any entry with the name HTTP_TIMEOUT.
    even in RZ10 i cant find the correct profile parameter.
    i m taking help from michaels blog
    /people/michal.krawczyk2/blog/2006/06/08/xi-timeouts-timeouts-timeouts
    i m on PI7.0 SP09
    is there some other place i can find this entry? or do i need to ask the basis guys to add it?
    thanx
    ahmad

    Also, there may be other factors to consider depending on your scenario.  If you don't have it already, look at the latest <a href="http://service.sap.com/~sapidb/011000358700005909032005E/XI30XI70_TroubleGuide.pdf">XI Troubleshooting Guide</a> - Section 9.2 on "Timeouts in XI".
    Regards,
    Jin

  • 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 on deploying to SAP-J2EE engine.

    I got a problem while deploying to SAP-J2EE engine using ant. It takes a lot of time and then throws a time out error.
    The problem is with the web.xml file pointing to a DTD in the internet, I have pasted some part of the web.xml below,
    <?xml version="1.0" encoding="UTF-8" ?>
    <!DOCTYPE web-app
      PUBLIC "-//Sun Microsystems, Inc.//DTD Web Application 2.2//EN"
      "http://java.sun.com/j2ee/dtds/web-app_2_2.dtd">
    <web-app>
        <display-name>MyPay</display-name>
        <description>MyPay</description>
    Once I write down the DTD description in the web.xml itself, it works fine.
    I have pasted the error trace below,
    j2eedeploy:
         [echo] Deploying to Local environment...
         [echo] C:\Java\Projects/MyPay/dist/MyPay.ear
    BUILD FAILED
    C:\Java\Projects\MyPay\build.xml:445: java.lang.RuntimeException: ERROR: ID90507:  Error occured during getting EARDescriptor : Failed to load resource from the context classloader of the current thread! Loading from classloader was caused by: java.net.ConnectException: Connection timed out: connect
    Exception is :
    java.io.IOException: Failed to load resource from the context classloader of the current thread! Loading from classloader was caused by: java.net.ConnectException: Connection timed out: connect
         at com.sap.engine.lib.xml.parser.URLLoaderBase.resolveEntity(URLLoaderBase.java:148)
         at com.sap.engine.lib.xml.parser.XMLParser.scanDTD(XMLParser.java:1271)
         at com.sap.engine.lib.xml.parser.XMLParser.scanProlog(XMLParser.java:2795)
         at com.sap.engine.lib.xml.parser.XMLParser.scanDocument(XMLParser.java:2830)
         at com.sap.engine.lib.xml.parser.XMLParser.parse0(XMLParser.java:229)
         at com.sap.engine.lib.xml.parser.AbstractXMLParser.parseAndCatchException(AbstractXMLParser.java:145)
         at com.sap.engine.lib.xml.parser.AbstractXMLParser.parse(AbstractXMLParser.java:160)
         at com.sap.engine.lib.xml.parser.AbstractXMLParser.parse(AbstractXMLParser.java:261)
         at com.sap.engine.lib.xml.parser.Parser.parseWithoutSchemaValidationProcessing(Parser.java:280)
         at com.sap.engine.lib.xml.parser.Parser.parse(Parser.java:342)
         at com.sap.engine.lib.xml.parser.DOMParser.parse(DOMParser.java:101)
         at com.sap.engine.lib.jaxp.DocumentBuilderImpl.parse(DocumentBuilderImpl.java:127)
         at com.inqmy.lib.xml.StandardDOMParser.parse(StandardDOMParser.java:127)
         at com.inqmy.lib.xml.StandardDOMParser.parse(StandardDOMParser.java:120)
         at com.inqmy.services.servlets_jsp.descriptor.jar.WebWar.getWebDescriptor(WebWar.java:98)
         at com.inqmy.deploy.tool.deployer.ExtendedEarReader.loadDescriptorFromFile(ExtendedEarReader.java:175)
         at com.inqmy.deploy.tool.deployer.ExtendedEarReader.getFullEarDescriptor(ExtendedEarReader.java:104)
         at com.inqmy.deploy.manager.DeployManagerImpl.setEar(DeployManagerImpl.java:355)
         at com.inqmy.deploy.manager.DeployManagerImpl.setEar(DeployManagerImpl.java:325)
         at com.pg.sap.deploy620.SAPDeploy620Manager.process(SAPDeploy620Manager.java:84)
         at com.pg.ant.tasks.j2ee620.J2ee620EngineDeployTask.execute(J2ee620EngineDeployTask.java:40)
         at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:275)
         at org.apache.tools.ant.Task.perform(Task.java:364)
         at org.apache.tools.ant.Target.execute(Target.java:341)
         at org.apache.tools.ant.Target.performTasks(Target.java:369)
         at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1216)
         at org.apache.tools.ant.Project.executeTarget(Project.java:1185)
         at org.apache.tools.ant.helper.DefaultExecutor.executeTargets(DefaultExecutor.java:40)
         at org.eclipse.ant.internal.ui.antsupport.EclipseDefaultExecutor.executeTargets(EclipseDefaultExecutor.java:32)
         at org.apache.tools.ant.Project.executeTargets(Project.java:1068)
         at org.eclipse.ant.internal.ui.antsupport.InternalAntRunner.run(InternalAntRunner.java:423)
         at org.eclipse.ant.internal.ui.antsupport.InternalAntRunner.main(InternalAntRunner.java:137)

    Thanks for your reply Kalyan,
    The problem seems to be with my system, because I had run the same ant script in another system and it deployed successfully.
    The problem does not seem to be with the dtd, whereas it seems that the SAP-J2EE engine is not able to open the link to the dtd giving a time out error.
    Is it possible to switch off the validation process of the SAP-J2EE engine of an xml with the dtd?

  • 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

  • Connection time out error in server proxy

    Hi
    My scenario is file to proxy. . It is synchronous scenario.
    I am giving wait time as input and in the proxy i wrote a code to wait till the inputed value and  after that send a response. it is working fine only if i give less than 60 sec.
    If i specify above 60 sec i am getting the connection time out error in SXMB_MONI.
    Please help me to solve this.
    Regards
    Divia

    To increase Timeout use
    Go to transaction SMICM........ Goto->services......choose HTTP.....edit this service.........increase maximum processing time and activate this service
    look blog for timeouts:
    The specified item was not found.

  • TIME OUT error in ECC SM58

    hi All,
    We have sent some 2000 Idocs from ECC,
    my scenario is   FILE to FILE.
    I am collecting all the idocs into a file using IDOC XML port..
    File havnt reached XI.. even not created in application server ... all idoc are stuck in ECC side.. when i go to SM58.. getting error like  TIME OUT error ...
    Please help guys.. how i can sent those.... 2000 stuck Idocs?

    Hi Sam,
      check the 'Timeouts in PI' section in the PI Troubleshooting Guide -
    [#1060264 PI Troubleshooting Guide 7.1|http://service.sap.com/sap/support/notes/1060264]
    Regards
    Kenny

  • Time Out ERROR CC Risk Analysis RFC

    Hi Friends,
    I am getting time out error when I am testing the CC risk analysis RFC. One thiing I monitor here is that when I am changing the parameters to 'YES' in tcode '/virsa/zrtcnfg',this RFC time out is occuring,when I am changing it back to 'NO' it is working fine.
    I beleive there is some system perfomance issue or any bottleneck is happenning.
    Please check error details of the Rfc below
    Logon     Connection Error
    Error Details     Error when opening an RFC connection
    Error Details     ERROR: program GRCRTTOCC5X not registered
    Error Details     LOCATION: SAP-Gateway on host hostname / sapgw00
    Error Details     DETAIL: TP GRCRTTOCC5X not registered
    Error Details     COMPONENT: SAP-Gateway
    Error Details     COUNTER: 65055
    Error Details     MODULE: gwr3cpic.c
    Error Details     LINE: 1960
    Error Details     RETURN CODE: 679
    Error Details     SUBRC: 0
    Error Details     RELEASE: 700
    Error Details     TIME: Thu Mar 11 09:21:35 2010
    Error Details     VERSION: 2
    and also some time I am getting below error
    Logon     Connection Error
    Error Details     Error when opening an RFC connection
    Error Details     ERROR: timeout during allocate of registered program
    Error Details     LOCATION: SAP-Gateway on host hostname / sapgw00
    Error Details     DETAIL: TP GRCRTTOCC5X init/busy for more than 60 sec
    Error Details     COMPONENT: SAP-Gateway
    Error Details     COUNTER: 65068
    Error Details     MODULE: gwr3cpic.c
    Error Details     LINE: 1937
    Error Details     RETURN CODE: 677
    Error Details     SUBRC: 0
    Error Details     RELEASE: 700
    Error Details     TIME: Thu Mar 11 09:29:56 2010
    Error Details     VERSION: 2
    Any suggestion please..
    Thanks & Regards,
    Satyabrat
    Edited by: Satyabrat Mohanty on Mar 11, 2010 11:54 AM
    Edited by: Satyabrat Mohanty on Mar 11, 2010 12:00 PM

    Hi,
    for further information  the latest log is
    2010-04-28 07:01:47,706 [SAPEngine_Application_Thread[impl:3]_18] ERROR  User :   not found to get full name
    2010-04-28 07:02:21,066 [SAPEngine_Application_Thread[impl:3]_11] ERROR
    java.lang.Throwable: java.lang.NullPointerException
         at com.virsa.re.workflow.client.WorkflowRequestClient.getRoleProcessContextDtos(WorkflowRequestClient.java:284)
         at com.virsa.re.workflow.client.WorkflowRequestClient.execSubmitRoleApprovalWF(WorkflowRequestClient.java:83)
         at com.virsa.re.workflow.actions.WorkflowRequestAction.submitApprovalRequest(WorkflowRequestAction.java:95)
         at com.virsa.re.workflow.actions.WorkflowRequestAction.execute(WorkflowRequestAction.java:54)
         at com.virsa.framework.NavigationEngine.execute(NavigationEngine.java:273)
         at com.virsa.framework.servlet.VFrameworkServlet.service(VFrameworkServlet.java:230)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at com.sap.engine.services.servlets_jsp.server.runtime.FilterChainImpl.runServlet(FilterChainImpl.java:117)
         at com.sap.engine.services.servlets_jsp.server.runtime.FilterChainImpl.doFilter(FilterChainImpl.java:62)
         at com.virsa.comp.history.filter.HistoryFilter.doFilter(HistoryFilter.java:43)
         at com.sap.engine.services.servlets_jsp.server.runtime.FilterChainImpl.doFilter(FilterChainImpl.java:58)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:384)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:386)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:364)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1039)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:265)
         at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
         at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)
         at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
         at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
         at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
         at java.security.AccessController.doPrivileged(AccessController.java:219)
         at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:102)
         at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172)
    FYI
    I have already checked all the webservices urls and password everything is fine.am I missing something.
    Regards,
    Satyabrat

  • Time out errors when trying to download ios5

    I am trying to download the latest version for my iPad but keep getting time out errors and the download fails. My internet connection is still there and hasn't dropped off. Not sure why the download won't 'finish'.  Thanks for any help.

    I get the same issue on my Windows7 PC.  I have noted a manual upgrade path on this site
    http://osxdaily.com/2011/10/12/ios-5-download-available/
    But I'm not sure I know the difference between GSM and CDMA To be able to download the correct version.
    I'm in the uk

  • Time out error  on front end ( 60 seconds) developed in web dynpro ABAP

    Hi all
    I am getting TIME OUT error ( ERROR :-  Connection to partner break in 60 seconds) on front end (on web) because in SAP backend there is a function module excuting and taking 3 minutes. But on front end developed in web dynpro ABAP time out is coming in 60 seconds.
    Please help me how can i increase this TIME OUT time on front end more than 60 seconds.
    Please help as soon as possible

    Hi,
    see the <a href="http://help.sap.com/saphelp_nw70/helpdata/en/7b/72092aaa1342c5a3af7ce0b9a11ff9/frameset.htm">Documentation</a> and
    <a href="http://help.sap.com/saphelp_nw70/helpdata/en/78/9852b7c06b11d4ad310000e83539c3/frameset.htm">this</a>
    Regards, Heidi

  • Foreground job - Standard report - Time out error

    Hi,
    I have a standard SAP report which is executed from portal and the report is failing in the foreground with a time out error. As there is time set for foreground process and probably the volume of the report is big which is not good enough to execute in the foreground time frame.
    The customer wants to run it only in the foreground and does not want to schedule in the background and the reason being he wants to do some customization on the columns when the report is displayed back on the portal screen.
    Now my question is there any other option to get the requirement and increasing the foreground time is ruled out by Basis team.
    I was thinking if I can use a wrapper report on the standard report and include SAPGUI_PROGRESS_INDICATOR to keep the connection between the dialog and the presentation server going without dis-connecting. Is this a better option and I am not sure if it will work ?
    Please let me know if any one else has resolved such issues earlier.
    Regards
    Praneeth Kumar
    Edited by: gansprasan on Sep 20, 2011 2:07 PM

    Hi,
          Though it is not advisable to change max run time... if need you you consult with your basis and you can change run time dynamically in your program and reset to original. I agree even CL_gui_timer class wont help.
    you can check below link.. handle it carefully..
    [http://help.sap.com/bp_bw370/documentation/How_To_Change_the_Maximum_Dialog_Runtime_of_a_Process_in_NW2004s.pdf]
    data: old_value(100).
    CONSTANTS: parameter LIKE tpfet-parname
    VALUE 'rdisp/max_wprun_time'.
    CALL 'C_SAPGPARAM' ID 'NAME' FIELD parameter
    ID 'VALUE' FIELD old_value. " old_value will have value set by basis.
    IF sy-subrc <> 0.
      RAISE not_found.
      ENDIF.
    use FM TH_CHANGE_PARAMETER to change value. Again reset the value with old value..
    Regards,
    Ravi.

  • 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.

  • MacAir- Wifii "connected" no loading or "time out" errors

    I have a MacAir and all of the sudden the Wifii wouldn't connect to the wifii server at school. 
    Other students were having no issues.  It would say "time out" error.
    Then it would connect to the guest network and full bars would show but wont load any pages. 
    My ipad is able to connect normally. Therefore it must be my OS on the MacAir.
    If followed other support threads and reset the network but still having the same issue
    I really need to get this fixed if possible, any help would be appreciated. Thank you~

    Hi aimomo!
    I have a few articles here for you that will help you troubleshoot this issue with your Wi-Fi connection:
    Wi-Fi: How to troubleshoot Wi-Fi connectivity
    http://support.apple.com/kb/HT4628
    Non-responsive DNS server or invalid DNS configuration can cause long delay before webpages load
    http://support.apple.com/kb/ts2296
    Safari 5.0.1 or later: Slow or partial webpage loading, or webpage cannot be found
    http://support.apple.com/kb/ts3408
    Safari 6 (OS X Mountain Lion): If Safari can’t open a website
    http://support.apple.com/kb/PH11883
    A few of these articles are for specific circumstances related to loading pages in Safari, but I thought they may be helpful if it seems like your issue is similar to what is described in the articles. Thanks for being a part of the Apple Support Communities!
    Regards,
    Braden

  • SoA Couldnt start- Time Out Error

    Hi,
    My oracle SOA version is 10.1.3.1. I have created a application ( say sampleApplication) in jdeveloper (webservice from wsdl). When deploying the application to the application server it takes a long time to complete (approx 30 mins) but it gets deployed without error. I got a perm gen error and I stopped the SOA. When started it again after incresing the perm gen size, the SOA couldnt start. Got the following error
    <ERROR> <collaxa> <ProcessJob::execute> Attempt (1/15) ... failed to connect ... retrying in 5 seconds ...
    <2009-09-11 17:55:13,130> <ERROR> <collaxa> <ProcessJob::execute> Timed out reading http://myURl....
    Maximum attempt of 15 was reached and the SOA failed to restart.
    After playing around with the server.xml (trying to remove all application entries and adding it one by one) found that when i removed the sampleApplication's entry from server.xml and tried starting SOA , it worked and it Started fine.
    Can any one point what might be the problem in my case.?
    Thanks in advance..
    (P.S: The other application deployed are developed in the same way as that of sampleApplication. So couldnt see any thing wrong with the sampleApplication. Other application entries in server.xml do not create this problem.)
    Edited by: user8655700 on Sep 11, 2009 7:03 AM

    Hi James,
    Thank You for your suggestion. I have some doubts.
    1) You suggested to revert back to old parameter and restart jDEV. What is the parameter i need to revert? I have only changed the max,min and perm size in opmn.xml because I keep getting perm gen error quite often. Did you mean those parameters ?
    2)Restarting jDev will solve the issue of longer deployment time for applications. But when I restart the SOA itself, it fails to start.I get the Time out error. On removing the application which took longer time to deploy from server.xml, SOA starts without error. No other changes have been made. So the question is why is the application which is successfully deployed from jdeveloper like many other applications stopping the SOA to start.?
    3)Or is the load during SOA startup is high, which results in it failing to start? If so how can I overcome this issue.
    Thanks,
    Ananth
    Edited by: user8655700 on Sep 14, 2009 10:25 PM

Maybe you are looking for