500 Connection timed out when in SXMB_MONI in "Call Adapter"

Hi,
We are using SOAP as a receiver adpter. It is working fine all the time but some times we are getting "500 Connection timed out" error in SXMB_MONI in the "Call Adapter" then it retries again and it works fine but I want to know why we are getting this 500 connection time out error and in another try it works.. and what we need to do to correct it.
Here is the error message from SXMB_MONI. Any help is appreciated!
<SAP:AdditionalText><html><head><title>Application Server Error</title> <style type="text/css"> body { font-family: arial, sans-serif;} </style> </head> <BODY><table width=800> <tr><td width=50 nowrap> </td><td> <H2>500 Connection timed out</H2><br><hr> <table border="0"> <tr><td>Error:</td><td>-5</td></tr> <tr><td>Version:</td><td>7000</td></tr> <tr><td>Component:</td><td>ICM</td></tr> <tr><td>Date/Time:</td><td>Thu Oct 4 03:26:15 2007 </td></tr> <tr><td>Module:</td><td>icxxthr_mt.c</td></tr> <tr><td>Line:</td><td>2698</td></tr>
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>HTTP response contains status code 500 with the description Timeout Error while sending by HTTP (error code: 500, error text: Timeout)</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
Thanks!
MP

can you please look in to this blog by Michal.
/people/michal.krawczyk2/blog/2006/06/08/xi-timeouts-timeouts-timeouts

Similar Messages

Error "500 Connection timed out" when starting a Web Interface

Hello,
when starting a Web Interface
(either from preview in Web Interface Builder or directly via transaction BPS_WIF0),
after around 2 minutes I get the following Error Message: "500 Connection timed out"
(in Detail, it says "Connection to partner timed out").
If I use a less complex web interface, this error does not come up.
What can I do to avoid this?
Thank you in advance,
Stephan

Hello Stephan,
if a basic web interface is fast enough, this is normally a confirmation, that the problem does not depend on network performance. We do this test always as an initial test to exclude network issues before we analyze BPS.
So it looks like you do have BPS performance issues. What I can tell you is that multiple variable selectors decrease performance. If this is not you problem I would recommend to check how-to-paper "performance".
It could be related to HTTP-services as well, you will find SAP notes about this topics in OSS.
regards
Eckhard Lewin

'500 Connection timed out' Error in Sender SOAP Scenario

Hi mates,
I exposed o/b synch MI as a webservice. This webservice is received by a BPM and it triggers an IDOC generation program on R/3. BPM waits & collects the IDOCs and cosntructs the response from these IDOCs and returns it to the webservice caller.
I'm making the SOAP call from a client program and I get the correct response in some cases where the data requested is not huge...normally with in 30 sec.
But in some cases I get the error '500 Connection timed out' after 60 sec. The detailed message is as follows.
<i>500 Connection timed out
Connection timed out (-5)
Error: -5
Version: 6040
Component: ICM
Date/Time: Thu Jun 15 17:06:10 2006
Module: icxxthr_mt.c
Line: 2551
Server: hcidx1_DX1_03
Detail: Connection to partner timed out after 60s</i>
My BPM waits for 10 minutes and I set the parameter XI.Timeout to 600000 (i.e. 10 minutes) in module parameter table for the sender SOAP adapter as per the note 856597. And in SXMB_ADM, I set the parameter CHECK_FOR_ASYNC_RESPONSE_TIMEOUT of category SA_COMM to 600. In my client program, I set the timeout as 1 hour. All these config params are supposed to make sure that all the components involved wait for atleast 10 mins before they timeout.
But I get timeout after 60 sec. Whats wrong/missing?
I highly appreciate your inputs.
thx in adv
praveen

Hey Praveen,
<i>I'm making the SOAP call from a client program and I get the correct response in some cases where the data requested is not huge...normally with in 30 sec.
But in some cases I get the error '500 Connection timed out' after 60 sec. The detailed message is as follows.</i>
does this mean you are getting some response in some cases where u r payload is small , and if its large ur getting some timeout like this? Also is ur scenario Sync / Async?
Assuming i understood correctly , i came a similar situation but that has to do some thing with Paging file / memory issues when the files are too huge and no. of users are high please let me know if this is the case.
best regards
Vara
[PLEASE REWARD FOR POSTING]

500 Connection timed out

Hello,
I receive a 500 Connection timed out error.
I know that there are some threads to this error but I can´t find a solution for us.
This is the error description:
Error:            -5
Version:        7000
Component: ICM
Date/Time:    Tue Mar 04 07:02:38 2008
Module:        icxxthr.c
Line:             2698
Server:         crmprod_CRP_01
Error Tag:     {-}
Detail:          Connection to partner timed out after 60s
Now I have found in this forum some information about the parameters icm/keep_alive_timeout, icm/conn_timeout and icm/server_port_*
Our settings for this parameters are:
icm/server_port_0 = PROT=HTTP,PORT=8001
icm/server_port_1 = PROT=SMTP,PORT=25
icm/keep_alive_timeout (sec.) = 600
icm/conn_timeout (msec.) = 5000
Can someone please explain me which parameters occurs this error and which parameters I can change that the connection time is longer than 60 seconds?
Where can I change the parameters?
Regards
Philipp

Hi,
Parameter icm/conn_timeout
icm/conn_timeout is used to set the timeout when setting up the connection. If the timeout is exceeded, an error page is generally displayed with the information "404 Resource not found" "Partner not reached".
Therefore, exceeding the icm/conn_timeout does not lead to a "500 Connection timed out" error message.
Processing timeout and keepalive timeout
The icm/keep_alive_timeout and icm/server_port_< n > parameters define the keepalive timeout and the processing timeout.
ICM distinguishes between these two types of timeout.
The processing timeout is the timeout between the HTTP request being issued and the HTTP response being received.
If the ICM is used as a server for the relevant HTTP request (in other words, when it forwards an incoming request to the SAP Web Application Server), the processing timeout is the time that the ICM will wait until a response is received from the SAP Web Application Server (ABAP or J2EE). This interval may be exceeded with long-running applications in ABAP or the J2EE engine. If the processing timeouts are exceeded, the ICM sends the client an HTTP response with the error code "500 Connection timed out".
If the ICM serves as a client for the relevant HTTP request (that is, when it forwards outgoing requests from the SAP Web Application Server), the processing timeout is the time that the ICM waits until a response is received from the network. This interval may also be exceeded in the case of long-running applications in the network.
The keepalive timeout specifies how long the network should remain open after a request has been processed successfully so that the TCP/IP connection does not have to be reestablished if additional requests are received.
When you set the keepalive timeout, this does not normally lead to timeout errors. You should set the keepalive timeout high enough that the connection does not have to be reestablished for requests that are sent within a short time of each other, but low enough that the number of unused open TCP/IP connections is not unnecessarily high. Exceeding the Keepalive timeout should never cause an error.
Configuration of the ICM parameters for the processing timeout and the keepalive timeout
For the ICM, the parameters mentioned here are in the instance profile.
The processing timeout is set for individual services with the following parameter:
icm/server_port_ < n > = ...,PROCTIMEOUT=< s >.
The keepalive timeout can be set globally for all services of the ICM with the parameter icm/keepalive_timeout.
You can also set it for individual services by using the following parameter:
icm/server_port_ < n > = ...,TIMEOUT=< s >.
If you set this parameter, it overwrites parameter icm/keepalive_timeout for the specified service.
Even if the ICM serves as client for a request, the TIMEOUT and PROCTIMEOUT parameters of icm/server_port_ < n > control the timeouts for the relevant protocol, provided that you have set TIMEOUT or PROCTIMEOUT.
If you have not set the PROCTIMEOUT parameter, TIMEOUT (or icm/keepalive_timeout) defines both the processing timeout and the keepalive timeout. Also, as of release 6.40, the keepalive timeout is limited to a maximum of 30 seconds.
In a system where the default timeout settings of 30 seconds for the keepalive timeout and the processing timeout are not sufficient because of long-running applications, we recommend that you set the TIMEOUT and PROCTIMEOUT parameters for the relevant services so that you can configure them independently of each other. In addition, we recommend that you do not set the TIMEOUT value higher than necessary, for example, to the usual default value of 30 seconds.
We recommend, for example, the following settings:
icm/server_port_0 = PROT=HTTP,PORT=1080,TIMEOUT=30,PROCTIMEOUT=600
to allow a maximum processing time of 10 minutes.
I hope this info will help you to sort out the error you getting.
Regards
Aashish Sinha
PS : reward points if helpful

500 Connection timed out issue

Hi Experts,
In my webdynpro JAVA application I am making a call to MDX query to get data from BW.
If the query returns the value before 60 sec, I am able to view the data.Else I am getting error message "500 Connection timed out"
In my application I have not set the any timeout in application property.So the application is taking the default timeout settings from the server.
When i checked with admin team, they give the timeout settings of server as below.Still I am facing the issue of tiemout.
Can anyone help to find the solution for this?
Below are the error details:
500 Connection timed out
Error:
-5
Version:
7200
Component:
ICM
Date/Time:
Wed Nov 28 01:15:28 2012
Module:
icxxthr_mt.c
Line:
4295
Server:
a6bwp02__75
Error Tag:
Detail:
Connection to partner timed out after 60s
Thanks in advance,
Ram

Hi
Check the following settings:
In BW system:
Run Transaction -> SMICM From Menu Bar GOTO->Services-> Select HTTP Service-> Now select SERVICE from menu bar->Change option-> Change Max. Processing Time to your convienient.
Since you are using WDJ:
http://help.sap.com/saphelp_nw04s/helpdata/en/43/8a1a8ece230c8ce10000000a11466f/frameset.htm
From Portal:
1. Default Timeout: This is the most used and the most common parameter used for portal component timeout. It is set at portal - System Administration –> System Configuration –> Service Configuration –> Default configuration.
Parameter is Default.component.timeout
2. Portal Page Timeout: This parameter portal page timeout. This is applicable to browser page not to portal page object. In simpler terms, this parameters is not applicable to PCD objects like iView, workset or a page.
This is set from portal system admnistration and the parameter is: Com.sap.portal.page.PageTimeout
3. WebDynpro Component Timeout: This parameter controls expiry time of a webdynpro component. This parameter would override all other parameters and is configured in Visual Administrator You can locate the following parameter and configure appropriate time.
Parameter is: Tc~wd~dispwda – DefaultExpirationTime
4. WebDynpro Application timeout: This parameter controls timeout of a webdynpro application inside a component. When you want to have a different timeout for application, you can use this parameter. This parameter also overrides timeout parameters set in Service Configuration.
The parameter is: ExpirationTime
Hope this helps. Please mention the solution.

Connection timed out when try to connect orb through iiop

I have been trying to test a very basic corba example in weblogic 11g, it narrows an orb sucessfully with naming service, but I got connection timed out error when trying to call a function in the orb. My weblogic and my source code are on the same machine and I connect it with browser(coz it is a web application), so I doubt if it is firewall issues, but I could be wrong. I appericate so much if anyone can help.
Here is the error message I got, you can see I listed all the objects in the naming service and I am able to locate Hello object:
>
Context: weblogic
Object: Hello
Context: javax
Obtained a handle on server object: oraclecorba._HelloStub:Delegate(532227) [weblogic.iiop.IOR[IDL:oraclecorba/Hello:1.0] @xx.x.xx.xxx:xxxx, <0, null>]
org.omg.CORBA.COMM_FAILURE: Connection timed out vmcid: 0x0 minor code: 0 completed: No
at weblogic.iiop.Utils.mapToCORBAException(Utils.java:885)
at weblogic.corba.idl.RemoteDelegateImpl.request(RemoteDelegateImpl.java:311)
at org.omg.CORBA.portable.ObjectImpl._request(ObjectImpl.java:431)
at oraclecorba._HelloStub.sayHello(_HelloStub.java:18)
at oracle.demo.corba.MyJSPHelper.jspSayHello(MyJSPHelper.java:71)
at jsp_servlet._pages.__corbajsp._jspService(__corbajsp.java:92)
at weblogic.servlet.jsp.JspBase.service(JspBase.java:34)
at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227)
at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125)
at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:292)
at weblogic.servlet.internal.ServletStubImpl.onAddToMapException(ServletStubImpl.java:408)
at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:318)
at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:175)
at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3594)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2202)
at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2108)
at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1432)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
Caused by: java.net.ConnectException: Connection timed out
at java.net.PlainSocketImpl.socketConnect(Native Method)
at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:333)
at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:195)
at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:182)
at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:366)
at java.net.Socket.connect(Socket.java:519)
at weblogic.socket.SocketMuxer.newSocket(SocketMuxer.java:342)
at weblogic.socket.ChannelSocketFactory.createSocket(ChannelSocketFactory.java:79)
at weblogic.socket.BaseAbstractMuxableSocket.createSocket(BaseAbstractMuxableSocket.java:133)
at weblogic.iiop.MuxableSocketIIOP.newSocket(MuxableSocketIIOP.java:266)
at weblogic.iiop.MuxableSocketIIOP.createSocket(MuxableSocketIIOP.java:253)
at weblogic.socket.BaseAbstractMuxableSocket.connect(BaseAbstractMuxableSocket.java:106)
at weblogic.iiop.MuxableSocketIIOP.connect(MuxableSocketIIOP.java:238)
at weblogic.iiop.MuxableSocketIIOP.createConnection(MuxableSocketIIOP.java:222)
at weblogic.iiop.EndPointManager.createEndPoint(EndPointManager.java:464)
at weblogic.iiop.EndPointManager.findOrCreateEndPoint(EndPointManager.java:239)
at weblogic.iiop.EndPointManager.findOrCreateEndPoint(EndPointManager.java:256)
at weblogic.iiop.IIOPRemoteRef.locateIORForRequest(IIOPRemoteRef.java:383)
at weblogic.corba.idl.RemoteDelegateImpl.getInvocationIOR(RemoteDelegateImpl.java:535)
at weblogic.corba.idl.RemoteDelegateImpl.request(RemoteDelegateImpl.java:256)
... 19 more
>
Here are my source code
Server side
package oracle.demo.corba;
import oraclecorba.Hello;
import oraclecorba.HelloHelper;
import org.omg.CORBA.ORB;
import org.omg.CosNaming.Binding;
import org.omg.CosNaming.BindingIteratorHolder;
import org.omg.CosNaming.BindingListHolder;
import org.omg.CosNaming.BindingType;
import org.omg.CosNaming.NameComponent;
import org.omg.CosNaming.NamingContext;
import org.omg.CosNaming.NamingContextExt;
import org.omg.CosNaming.NamingContextExtHelper;
import org.omg.CosNaming.NamingContextPackage.NotFound;
import org.omg.PortableServer.POA;
import org.omg.PortableServer.POAHelper;
import weblogic.common.T3ServicesDef;
public class ORBStartup{
     private T3ServicesDef t3servicesdef;
     public void setServices(T3ServicesDef t3servicesdef)
        this.t3servicesdef = t3servicesdef;
     public static void main(String[] args)
        throws Exception
         try{
              args = new String[4];
              args[0] = "-ORBInitialHost";
              args[1] = "some_address";
              args[2] = "-ORBInitialPort";
              args[3] = "8056";
              System.out.println("...............startup...........");
               // Create a new object request broker
               ORB orb = ORB.init( args, null );
               // get the root POA
               POA rootpoa = POAHelper.narrow(orb.resolve_initial_references("RootPOA"));
               // Activate PersistentPOA's POAManager, Without this
               // All calls to Persistent Server will hang because POAManager
               // will be in the 'HOLD' state.
               rootpoa.the_POAManager().activate();
            // instantiate the servant
               CorbaHelloImpl helloImpl = new CorbaHelloImpl();
               helloImpl.setORB(orb);
               org.omg.CORBA.Object helloObj = rootpoa.servant_to_reference(helloImpl);
               Hello HelloRef = HelloHelper.narrow(helloObj);
           // Resolve RootNaming context and bind a name for the servant.
             // NOTE: If the Server is persistent in nature then using Persistent
             // Name Service is a good choice. Even if ORBD is restarted the Name
             // Bindings will be intact. To use Persistent Name Service use
             // 'NameService' as the key for resolve_initial_references() when
             // ORBD is running.
               org.omg.CORBA.Object ncObj = orb.resolve_initial_references("NameService");
               //This line works ONLY for INS(jdk 14 naming service)
               // Since we have only an object reference, we must
               // cast it to a NamingContext. We use a helper
              // class for this purpose
               NamingContextExt ncRef = NamingContextExtHelper.narrow( ncObj );
               String name = "Hello";
               NameComponent path[] = ncRef.to_name( name );
               try {
                    ncRef.rebind( path, HelloRef );
               } catch( org.omg.CosNaming.NamingContextPackage.NotFound nf ) {
                    NameComponent[] tmpName = new NameComponent[path.length-1];
                    for (int i=0; i < path.length-1; i++) { tmpName[i] = path; }
                    createContextPath(ncRef, tmpName);
                    ncRef.bind(path, HelloRef);
     BindingListHolder bl = new BindingListHolder();
     BindingIteratorHolder blIt= new BindingIteratorHolder();
     ncRef.list(1000, bl, blIt);
     Binding bindings[] = bl.value;
     for (int i=0; i < bindings.length; i++) {
     int lastIx = bindings[i].binding_name.length-1;
     // check to see if this is a naming context
     if (bindings[i].binding_type == BindingType.ncontext) {
     System.err.println( "Context: " +
     bindings[i].binding_name[lastIx].id);
     } else {
     System.err.println("Object: " +
     bindings[i].binding_name[lastIx].id);
               System.out.println( name + " for INS ready and waiting ...");
               // the server is now ready to receive the client request
               orb.run();
          } catch (Exception e) {
               System.err.println("ERROR: " + e);
               //e.printStackTrace(System.out);
               throw e;
          System.out.println("HelloServer Exiting ...");
public static void createContextPath(NamingContext nc, NameComponent[] name)
     throws org.omg.CORBA.UserException {
     try {
          nc.bind_new_context(name);
     } catch (NotFound nf) {
          for( int len = name.length - nf.rest_of_name.length + 1;
               len <= name.length; len++ )
               NameComponent[] tmpName = new NameComponent[len];
               for (int i=0; i < len; i++) { tmpName[i] = name[i]; }
               nc.bind_new_context(tmpName);
Client side:
package oracle.demo.corba;
import oraclecorba.Hello;
import oraclecorba.HelloHelper;
import org.omg.CORBA.ORB;
import org.omg.CosNaming.Binding;
import org.omg.CosNaming.BindingIteratorHolder;
import org.omg.CosNaming.BindingListHolder;
import org.omg.CosNaming.BindingType;
import org.omg.CosNaming.NamingContextExt;
import org.omg.CosNaming.NamingContextExtHelper;
public class MyJSPHelper
     public static String jspSayHello(String in)
          String rc = "";
          try
               ORB orb = ORB.init();
               // get the root naming context
               org.omg.CORBA.Object objRef;
               objRef = orb.resolve_initial_references("NameService");
               // Use NamingContextExt instead of NamingContext. This is
               // part of the Interoperable naming Service.
               NamingContextExt ncRef = NamingContextExtHelper.narrow(objRef);
               /*for(int i =0; i<orb.list_initial_services().length; i++)
                    rc += orb.list_initial_services()+": ";
                    System.err.println(orb.list_initial_services()[i]);
     BindingListHolder bl = new BindingListHolder();
     BindingIteratorHolder blIt= new BindingIteratorHolder();
     ncRef.list(1000, bl, blIt);
     Binding bindings[] = bl.value;
     for (int i=0; i < bindings.length; i++) {
     int lastIx = bindings[i].binding_name.length-1;
     // check to see if this is a naming context
     if (bindings[i].binding_type == BindingType.ncontext) {
     System.err.println( "Context: " +
     bindings[i].binding_name[lastIx].id);
     } else {
     System.err.println("Object: " +
     bindings[i].binding_name[lastIx].id);
               // resolve the Object Reference in Naming
               String name = "Hello";
               Hello helloImpl = HelloHelper.narrow(ncRef.resolve_str(name));
               System.err.println("Obtained a handle on server object: " + helloImpl);
//Hello helloImpl = HelloHelper.narrow(orb.string_to_object("corbaname:iiop:some_address:8056#Hello")); also tried that, but got the same problem
               rc = helloImpl.sayHello(in); //<----failed here
          catch(Exception e)
               // TODO Auto-generated catch block
               rc += e.toString();
               e.printStackTrace();
          return rc;
Edited by: user8904224 on 27/04/2010 23:06

Don't mean to add to the possible confusion here, but most newer routers (Apple included) allow their users to "hide" their network, so it's also very possible and likely in an apartment situation that you can pick up interference from a network that you or Air Radar cannot "see".
So, trying to find the "right" channel becomes a bit more of guessing game.
Understand that you need "g" for your devices. For the future though, you might watch the Air Radar screen for channels in the 36-48 and 149-161 range to see how much less activity is going on there.

Connection timed out, when server is present in far-off place

We have a web application on JBoss-3.2.3. It makes use of Applets. To paint the applet, a request is sent to a server using a HttpURLConnection. Evertyhing works fine when the browser(client) and the server are on the same network. However, if the client(browser) is in Australia and the server in India(i.e. long distance between server and client), then the Applet crashes with a Connection timed out exception. Any solution for this?
The code looks something like:
URL url = new URL(urlString);
HttpURLConnection connection = (HttpURLConnection) url.openConnection();
connection.setDoOutput(true);
connection.connect();

So I am facing the weirdest network/server problem ever!I have a customer which had a Supermicro server (Was there before me!). It was never used and they didn't know the password so i decided to format and re-install Windows Server 2012 R2 on it. I promoted it to a new domain and setup Windows Essentials so I could setup RDWeb for them quickly. They were up and running great. I also installed Trend Micro on the server and pushed it out to the client PC's. A little more info about my network before i get into the gritty. I have Brighthouse cable 35Mbps as an ISP with an ARRIS modem, a Ubiquiti Edgerouter Lite as my firewall and a cisco sg200-26 as my core switch. It's not a big location. We randomly started getting request timed out at the gateway level and the firewall level from outside and internet was dropping. We worked for weeks...
This topic first appeared in the Spiceworks Community

Connection timed out when accessing BPEL middle tier

I'm having fits over communicating with a Solaris middle tier PM from the PC JDev during construction, build, and deploy time and just can't make this out. I get a 'connect timed out' message immediately when a reference to the Solaris middle tier PM is made from JDev. Here are some particulars:
1. Connection from JDev and Middle Tier PM test successfully.
2. If I make no reference to the JDev middle tier process and I build and deploy a simple process successfully. It will also test okay.
3. If I try to use the simple process deployed on the Middle Tier PM as a partner link, when I attempt to browse the process when adding the partner link I get the 'Connect timed out' message immediately.
4. If I try to use a schema deployed to the xmllib I get the 'Connect Timed out' message when I attempt to build the process using the schema. (I can pull the same schema up in a browser on the Middle Tier PM).
Why does JDev complain that the connection timed out?
I am using 10.1.2 GA on both JDev and Middle Tier PM (deployed on top of Oracle AS).

I discovered a pilot error. Nevermind. I transposed some IP characters in my jdev.conf file for the non-proxy hosts.

Connection timed out when running snpsftp (Odisftp) jython procedure

Hi All,
Let me know the solution if any one of you have come across the "Connection Timed Out" error when running a jython snpsftp (Odisftp) procedure to exchange/import the files on a FTP server to the local system (Target Server).
This procedure was working fine until the IP Address of the Target Server was changed due to change to physical location of the Target server itself.
Since we are moving office to a different building the Target server which hosts the ODI Agent running as windows service are moved and since then the FTP Jython procedure is not working.
I can successfully ping the IP Address of the FTP server from the Target server that has got the new IP, but when running the FTP procedure from ODI tool ends up with Connection Timed Out error.
Thanks for providing some tips/ideas for resolving this urgent issue.
Thanks,
Raghu

Please check the hosts file for the new IP,
Also cehck the Agnet service login for wheter the user has the privledges to do a FTP access to the server or also connect to the server
Reshma

Connection timed out when making RMI call

Hello,
I am using a combination of Spring Remoting and Scheduling with Quartz Timer. Both are using RMI as a communication stack. The RMI server is located in sydney while the client is located in the US. This incurs large network lag which causes my RMI method calls to timeout. I am able to do a lookup on the RMI object and receive a stub reference to it with no problem but as soon as I try to invoke a remote method on that stub it eventually times out.
Thinking it was truly a timeout issue I implemented a Custom socket factory for RMI using RMISocketFactory.setSocketFactory(new TimeoutSocketFactory(120000));Here is the custom TimeoutSocketFactory:
public class TimeoutSocketFactory extends RMISocketFactory {
        private int timeout;
        private static final Logger log = Logger.getLogger(TimeoutSocketFactory.class);
        public TimeoutSocketFactory(int timeout) {
            this.timeout = timeout;
        public Socket createSocket(String host, int port) throws IOException {
            log.debug("Creating timeout socket with value - " + timeout);
            Socket ret = getDefaultSocketFactory().createSocket(host, port);
            ret.setSoTimeout(timeout);
            return ret;
        public ServerSocket createServerSocket(int port) throws IOException {
            ServerSocket ss = getDefaultSocketFactory().createServerSocket(port);
            ss.setSoTimeout(timeout);
            return ss;
}I implemented the custom socket factory both on the RMI server and on the RMI client. This had no effect on the time outs that occured when trying to make an RMI call to the server even though the sockets were being built by this custom class (have logging in place).
Is there something else I need to do to increase the timeout period? And how do I know if it's a server or a client issue?
Thanks,
Anthony Bargnesi
[Exception StackTrace]
java.rmi.ConnectException: Connection refused to host: 172.16.10.97; nested exception is:
     java.net.ConnectException: Connection timed out: connect
     at sun.rmi.transport.tcp.TCPEndpoint.newSocket(TCPEndpoint.java:574)
     at sun.rmi.transport.tcp.TCPChannel.createConnection(TCPChannel.java:185)
     at sun.rmi.transport.tcp.TCPChannel.newConnection(TCPChannel.java:171)
     at sun.rmi.server.UnicastRef.invoke(UnicastRef.java:94)
     at org.springframework.remoting.rmi.RmiInvocationWrapper_Stub.invoke(Unknown Source)
     at com.aquent.rmi.test.RMIClient.connectService(RMIClient.java:46)
     at com.aquent.rmi.test.RMIClient.main(RMIClient.java:81)
Caused by: java.net.ConnectException: Connection timed out: connect
     at java.net.PlainSocketImpl.socketConnect(Native Method)
     at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:333)
     at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:195)
     at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:182)
     at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:366)
     at java.net.Socket.connect(Socket.java:507)
     at java.net.Socket.connect(Socket.java:457)
     at java.net.Socket.<init>(Socket.java:365)
     at java.net.Socket.<init>(Socket.java:178)
     at sun.rmi.transport.proxy.RMIDirectSocketFactory.createSocket(RMIDirectSocketFactory.java:22)
     at sun.rmi.transport.proxy.RMIMasterSocketFactory.createSocket(RMIMasterSocketFactory.java:128)
     at com.aquent.rmi.test.TimeoutFactory.createSocket(TimeoutFactory.java:21)
     at sun.rmi.transport.tcp.TCPEndpoint.newSocket(TCPEndpoint.java:569)

Well this is a connect timeout, not a read timeout, so it has nothing to do with your socket factory, and your socket factory won't help. It's a connectivity issue. Can you ping that host from the client? Can you telnet to port 7?
In fact no socket factory will help because there is no way of increasing the connect timeout beyond the default: you can only reduce it.

ITunes network connection timing out when downloading

*When I try to download the new software 3.0 for my IPhone 3G, ITunes 8.2.1.6 says the network connection timed out as soon as it is 99% complete.*
It happens every time.
In fact the last time it had downloaded 230.0 MB of 230.1 MB and then gave me the message.
*The STATUS field in the Itune download window says*
*"0 KB of 230.1 MB - stopped (err = -3259)" after the message is given.*
I tried completely uninstalling Itunes and Bonjor est. (all Apple software) and downloaded a new copy and installed it.
I tried turning off my fire wall completely.
None of my other internet accessing software is having any problems.
Please help!!!
Ive had old software on my phone for a long time and this is really aggravating me.
Message was edited by: dave92983

Hi can youplease do the following
1 Bt quiet line test dial 17070 option 2 you should hear no noise any thing heard should be reported to Bt faults on 151 but do not mention broadband when you call once any noise is removed broadband should improve
2 run a Bt speed test speedtester.bt.com andpost back here the results in full
3 obtain your full hub stats byentering 192.168.1.254 into to your browser address bar and navigating to connection and post the full details back here then someone will be able to offer more help about your connection
If you want to say thanks for a helpful answer,please click on the Ratings star on the left-hand side If the reply answers your question then please mark as ’Mark as Accepted Solution’

Network Connection Timed Out - When downloading updates for IPOD

Just got new ipod, plugged in sync'd ok but when I had to update new version onto ipod, managed to get 3 hours in then with 12 minutes to go it says "network connection timed out" and nothing else - can anyone help? Thanks

Are you on dial up? No way should an ipod update take 3+ hours to download on broadband!

Network Connection Timed Out when downloading from...

I have only had BT broadband for a few months but am regretting it due to the huge number of dropouts I have - lose connection many times daily which is a big pain as I rely on this for my work.
One specific problem that has reared its head recently is if I try to download latest iphone upgrade from Itunes then after about 30 seconds it fails with "Network Connection Timed Out' and the connection breaks. This happens every time I try.
Also sometimes when I access sites I get TCP Network Error.
I know these problems are to do with the BTHub Router because if I switch to using my old Netgear Router which is still running on another line in the house (I need the backup as BT fails so often) then all works fine.
Can anybody help - or should I just throw it all away and try another provider?

Hi can youplease do the following
1 Bt quiet line test dial 17070 option 2 you should hear no noise any thing heard should be reported to Bt faults on 151 but do not mention broadband when you call once any noise is removed broadband should improve
2 run a Bt speed test speedtester.bt.com andpost back here the results in full
3 obtain your full hub stats byentering 192.168.1.254 into to your browser address bar and navigating to connection and post the full details back here then someone will be able to offer more help about your connection
If you want to say thanks for a helpful answer,please click on the Ratings star on the left-hand side If the reply answers your question then please mark as ’Mark as Accepted Solution’

Wget - Connection timed out when using "long" strings

I'm having a problem with a little script to change some settings for IP-phones. Here is the script:
#!/bin/bash
for i in "0" #"4"
do
for j in $(seq 176 176)
do
wget --timeout=1 --tries=1 --keep-session-cookies --save-cookies cookies.txt --post-file=postfile http://192.168.$i.$j/dologin.htm
wget --timeout=1 --tries=1 --load-cookies cookies.txt --post-file=postfile2 http://192.168.$i.$j/update.htm
done
done
postfile looks like this and is just for logging in:
P2=<pass>&
postfile2 looks like this:
P270=123456&
The problem now is, when using it like above, everything works fine. But if I make the text in postfile2 one character longer, I get this:
Connecting to 192.168.0.176:80... connected.
HTTP request sent, awaiting response... Read error (Connection timed out) in headers.
Giving up.
It doesn't matter where I put the character to make the string longer (I can for example use P32=1234567& and it works). I have tested the script from different machines and used different phones, always the same. Any ideas?

daf666 wrote:The two files look identical, are you sure that the "bad" one is actually a capture of the timed out session? (both have same data length and same value in the content-length header).
Yes, they are different and the bad is is from the timeout .
daf666 wrote:Anyway, this timeout might occur, if for some reason wget will say content length is 10 and send only 9 characters in the post request..
Any idea what I can do about it? There is something fishy going on. I did this once before a few month ago when I wanted to change other settings. I tried to do the same thing again but even this doesn't work anymore. Maybe I should just try curl .

Losing Airport/ Get message "connection timed out" when try to re-connect

This has happened several times over the past few days. First time, trying to re-connect, it didn't see my network name. Then re-entered name, selected/joined, password shows up, but connection times out. Tonight, it saw my name, password showed up, but wouldn't connect, not matter what, with message "connection timed out."
Both times the only thing that worked was a re-start. Tonight, even after a re-start, got "connection timed out" message at first, but was able to get back on by clicking on the icon. I see the following logs.
Error: airportd MIG failed = -6 ((null)) (port = 26123)
Macintosh-3 Apple80211Agent[91]: Error joining .......: Connection timeout (-6 timeout connecting)
Macintosh-3 airportd[673]: Error: Apple80211Associate() failed -6
Until this happens, the connection is solid, usually with 54 mbs. I've googled around for these logs, but haven't seen anything conclusive. Any ideas? Thanks.

Don't mean to add to the possible confusion here, but most newer routers (Apple included) allow their users to "hide" their network, so it's also very possible and likely in an apartment situation that you can pick up interference from a network that you or Air Radar cannot "see".
So, trying to find the "right" channel becomes a bit more of guessing game.
Understand that you need "g" for your devices. For the future though, you might watch the Air Radar screen for channels in the 36-48 and 149-161 range to see how much less activity is going on there.

500 Connection timed out when in SXMB_MONI in "Call Adapter"

Similar Messages

Maybe you are looking for