Network connection takes to long

I am connecting to a PC operating windows 2000, via an ethernet network. I can connect to this PC from my mac operating OSX panther, but I have to connect via the route "Menu bar - Go - Connect to Server". I am able to connect in the Network icon found in the side bar but it takes a very long time. Is there a way to speed up this process? As I much prefer connecting via the network Icon.
Any help would be greatly appreciated.

Hi Pete, Are you connecting with IP address or name?
have you tried vice versa?
Have you entered your DNS settings in System Prefs?
What is the FQDN you're using .com? .local?
Cheers.

Similar Messages

Deserializing obj on network drive take a long time -- any ideas to improve

Good morning!
Deserializing objects from a network drive is taking way too long, much slower than deserializing the same object files stored on the local hard drive of the development PC. How I can reduce the time??
The size of the serialized objects is small (72K and 17K).
The PC access network drives quickly enough (word processing, text editing, etc). The PC JVM is 1.5.0_09 and the OS is Windows XP.
Here is the background.
I had the idea to create objects and serialized them on my server (an AS400) and let client applications deserialize them.
Now that I have it running I find that deserializing the objects off the server take way too long! Does anyone have any ideas how to improve this.
If I copy the serialized objects off the server onto the local hard drive of the development PC and access them from the local hard drive the speed is fine.
To my mind that eliminates the potential for incompatibility between the JVM which serialized the objects and the JVM which descerialized the object. That is, the deserialize fast on the local drive, slow over the network.
Used both UNC and mapped drive to access the server and I can't see any performance difference. That is
filename = "//server/java/ftpaudit/SerializedObject.ser"
and
filename = "J:/ftpaudit/SerializedObject.ser"
where J: is mapped to //server/java
This is the code which deserialize the objects.
try {
     File file = new File(filename);
     FileInputStream f = new FileInputStream(file);
     ObjectInputStream ois = new ObjectInputStream(f);
     Object returnObj = ois.readObject();
     ois.close();
     f.close();
     return returnObj;
} catch (InvalidClassException ice) {
     ....Thank you for your time and help.
BillB

Could the file be locked on the server?I don't believe it is. It eventually (minutes loads). The delay is consistent. I haven't put the logging to see what part of the deserialize method is chewing up the time yet.
Putting in code to copy the file from the server to the local hard drive then deserializing performs much, much faster (milliseconds, almost as fast as deserializing directly from the local drive).
I modified this from another post to this forum
try {
        FileChannel srcChannel = new FileInputStream(file).getChannel();
        FileChannel dstChannel = new FileOutputStream(dir+file).getChannel();
        dstChannel.transferFrom(srcChannel, 0, srcChannel.size());
        srcChannel.close();
        dstChannel.close();
    } catch (IOException e) {
        e.printStackTrace();
    }I was wondering if there was a more efficient way to deserialize an object than the one in my original post. Or if there were hidden aspects to consider such as buffer size.
Here's an alternative approach: since the server side
is written in Java (I'm assuming, since you say that
it writes a file containing serialized data), why not
create an RMI interface for retrieving the
information? The current approach, of opening a file
over the network, is very fragile -- what happens in
the network mount point or share name changes?Thank you. Good suggestion.

InDesign 9.2 - Save to network location takes a long time.

Saving InDesign files to a network location seems to take an extremely long time during which I am unable to do anything else inside InDesign.
I know that this has been an issue for me for at least 2 weeks (since March 3, 2014, possibly earlier). I am not certain whether I have updated InDesign since then, but have consistently been experiencing this same problem.
Today I ran some tests (all using the same ~20MB file).
Save from InDesign to network location: 12 seconds
Save from InDesign to desktop: <2 seconds
Copy file (in Windows Explorer) from desktop to network: <2 seconds
Copy file from network to desktop: <2 seconds
I know I can work on the file locally and copy my saved versions out at the end of the day, but this was not necessary before, and I don't know what changed to make this take so much longer than it used to.
Current system configuration: InDesign 9.2 x64 running on a Win 7 Pro 64-bit with 16GB RAM and a Xeon 3.6GHz processor.
Is anyone else experiencing this? Any ideas on how to resolve?
Thanks!

Daylight savings time started on the 9th, right? I'm not sure about what a "server time sync problem" would be, but since my problem started before the DST switch, it doesn't seem that this could be the cause.
Also, since I am able to copy to and from the server outside of InDesign without any problems, doesn't this indicate the server and my computer are communicating just fine?
Thank you for your assistance!

A network account take a long tme to be loged into the network

I still have the same problem but I got a new information:
I have a Mac Pro OS X 10.6.2 Server with several network accounts.
My boss does not want to use Mobility (from Workgroup manager -> Preferences)
I also have 6 iMacs 10.6.2 and about 9 users, in my group.
All of the users have an account on the server.
I also have a model called Master, from which I create a clone with CCC (Carbon Copy Cloner) and I installed all iMac with that clone.
Apparentely somme users are complaining that it take a while to log in to the server.
But it does not happen often.
Today some one reported me that it happens when some one has be loged with the iMac and another user came to the same iMac in order to be loged. At this time it take a while.
One of the user, told me, he always restart the iMac when he use the iMac after someone else.
From my Mister, I tried to be logged with different user, but I could not reproduce the problem.
Some one can help me to find the reason while, it take a while to be log into the server?
If you need more information, let me know?
Pierre

Thank for your reply.
I did see anythink special.
But did I look from the right place?
I look from:
Server Admin -> Open Directory
Then I displayed "password service error"
I also looked in " LDAP Log" and I saw somethink special:
Nov 3 18:29:06 lmommac18 slapd[50]: slapd starting
Nov 10 09:40:08 lmommac18 slapd[50]: Entry (uid=untitled_1,cn=users,dc=lmommac18,dc=yyyy,dc=zz): object class 'posixAccount' requires attribute 'homeDirectory'
Nov 10 09:40:08 lmommac18 slapd[50]: entry failed schema check: object class 'posixAccount' requires attribute 'homeDirectory'
Nov 17 10:03:36 lmommac18 slapd[50]: Entry (uid=untitled_1,cn=users,dc=lmommac18,dc=xxxx,dc=cc): object class 'posixAccount' requires attribute 'homeDirectory'
Nov 17 10:03:36 lmommac18 slapd[50]: entry failed schema check: object class 'posixAccount' requires attribute 'homeDirectory'
Nov 17 10:04:20 lmommac18 slapd[50]: Entry (uid=justin,cn=users,dc=lmommac18,dc=xxxx,dc=zz): object class 'posixAccount' requires attribute 'homeDirectory'
Nov 17 10:04:20 lmommac18 slapd[50]: entry failed schema check: object class 'posixAccount' requires attribute 'homeDirectory'
Nov 17 15:07:32 lmommac18 slapd[50]: connection_read(54): no connection!
Nov 17 15:16:24 lmommac18 slapd[50]: Entry (uid=untitled_1,cn=users,dc=lmommac18,dc=xxx,dc=cc): object class 'posixAccount' requires attribute 'homeDirectory'
Nov 17 15:16:24 lmommac18 slapd[50]: entry failed schema check: object class 'posixAccount' requires attribute 'homeDirectory'
Nov 17 15:42:31 lmommac18 slapd[50]: Entry (uid=untitled_1,cn=users,dc=lmommac18,dc=xxxx,dc=cc): object class 'posixAccount' requires attribute 'homeDirectory'
Nov 17 15:42:31 lmommac18 slapd[50]: entry failed schema check: object class 'posixAccount' requires attribute 'homeDirectory'
Nov 17 15:43:03 lmommac18 slapd[50]: Entry (uid=test2,cn=users,dc=lmommac18,dc=xxx,dc=cc): object class 'posixAccount' requires attribute 'homeDirectory'
Nov 17 15:43:03 lmommac18 slapd[50]: entry failed schema check: object class 'posixAccount' requires attribute 'homeDirectory'
Nov 18 08:22:41 lmommac18 slapd[49]: @(#) $OpenLDAP: slapd 2.4.11 (Jul 16 2009 22:42:57) $
Nov 18 08:22:41 lmommac18 slapd[49]: daemon: SLAPSOCKINIT: dtblsize=8192
Nov 18 08:22:42 lmommac18 slapd[49]: bdbdbopen: database "dc=lmommac18,dc=xxx,dc=cc": unclean shutdown detected; attempting recovery.
Nov 18 08:22:43 lmommac18 slapd[49]: bdbmonitor_dbopen: monitoring disabled; configure monitor database to enable
Nov 18 08:22:43 lmommac18 slapd[49]: slapd starting
Nov 24 11:18:47 lmommac18 slapd[49]: connection_input: conn=2407 deferring operation: too many executing
Nov 24 11:18:47 lmommac18 slapd[49]: Entry (uid=untitled_1,cn=users,dc=lmommac18,dc=xxxx,dc=cc): object class 'posixAccount' requires attribute 'homeDirectory'
Nov 24 11:18:47 lmommac18 slapd[49]: entry failed schema check: object class 'posixAccount' requires attribute 'homeDirectory'
Nov 24 14:23:23 lmommac18 slapd[64]: @(#) $OpenLDAP: slapd 2.4.11 (Jul 16 2009 22:42:57) $
Nov 24 14:23:23 lmommac18 slapd[64]: daemon: SLAPSOCKINIT: dtblsize=8192
Nov 24 14:23:23 lmommac18 slapd[64]: bdbdbopen: database "dc=lmommac18,dc=xxxx,dc=cc": unclean shutdown detected; attempting recovery.
Nov 24 14:23:23 lmommac18 slapd[64]: bdb(dc=lmommac18,dc=xxxx,dc=cc): unable to join the environment
Nov 24 14:23:24 lmommac18 slapd[64]: bdbmonitor_dbopen: monitoring disabled; configure monitor database to enable
Nov 24 14:23:24 lmommac18 slapd[64]: slapd starting
Nov 24 14:24:35 lmommac18 slapd[64]: connection_read(23): no connection!
Nov 24 14:58:50 lmommac18 slapd[64]: daemon: shutdown requested and initiated.
Nov 24 14:58:50 lmommac18 slapd[64]: slapd shutdown: waiting for 0 threads to terminate
Nov 24 14:58:54 lmommac18 slapd[64]: slapd stopped.
Nov 24 15:00:16 lmommac18 slapd[49]: @(#) $OpenLDAP: slapd 2.4.11 (Oct 16 2009 05:52:14) $
Nov 24 15:00:16 lmommac18 slapd[49]: daemon: SLAPSOCKINIT: dtblsize=8192
Nov 24 15:00:27 lmommac18 slapd[49]: bdbmonitor_dbopen: monitoring disabled; configure monitor database to enable
Nov 24 15:00:27 lmommac18 slapd[49]: slapd starting
The think which seams to be special are:
1) untitled_1
2) Nov 17 15:07:32 lmommac18 slapd[50]: connection_read(54): no connection!
3) Nov 24 11:18:47 lmommac18 slapd[49]: connection_input: conn=2407 deferring operation: too many executing
4) Nov 24 14:23:23 lmommac18 slapd[64]: bdb(dc=lmommac18,dc=xxxx,dc=cc): unable to join the environment
Do you have an idea which can help me o undertand the reason?
Many thank

Connecting takes a long time

For some reason connecting to Flash Media Server 3.5 takes around 40 seconds. The server is running on Windows Server 2008 (64-bit edition) on a virtual server located in a reliable hosting center and I'm connecting to it over the internet. The server is using built-in Windows Firewall with all the inbound TCP ports required by Flash Media Server opened (80, 1935 and 1111). If I disable the server's firewall the connection time drops to 20 seconds, but it's still pretty damn long time just for establishing connection. We probably have some company firewall at this end (the client side), but other streaming media services works just fine over this connection.
Any suggestions? I was under the impression that the connection should be practically instant (practically meaning that the user shouldn't have to wait for it).

You have it right, the flashplayer will fall back on RTMPT:80 if it can't make an RTMP connection. If you let the flashplayer use it's default behavior, I find it takes about 20 seconds for each protocol/port combination to time out. Unfortunately, there's no access to that timeout value through the actionscript API.
A lot of developers like to use the "shotgun" method of connecting, where separate netconnections are create for each port:protocol combination and connected to at once. The first one to receive a success status becomes the winner (the connection that will actually be used), and the rest are closed and discarded.
Another option is to try your preferred port:protocol combinations in sequence, and use a Timer() to set your own timeout for each, each combination in succession. I personally prefer this method, as it reduces the number of handlshakes and connect requests the server has to handle (I'll trad a few seconds of wait time on the client side to save load on the server any day).
One thing to keep in mind, Mac OS may give you problems if you make your timeout too short. You can read more about that here:
http://blog.jaycharles.net/?p=47

MDM JCo Connection takes a long time

Hi,
I've just timed the time it takes from my java application to establish a connection to MDM.
It takes 14 seconds.
catalog.Login(server,port,login,password,language,1,10,5000,"C://temp.txt");
Our J2EE server and MDM is on a separate box on the same LAN. Once the connection is established, the queries are very fast.
Is there any way to speed this up?
Cheers,
Michael.

Hi Michael,
from my experience you can try two / three things to speed up connection / login operation.
First: as Mausam suggested since you are developing application on J2EE stack - you should use MDM JCA connector (with connection pooling mechanism)
Second: each time the you trying to establish connection from java application to
MDM server using Java API - all lookup tables data will be transfered to client side (cached on the java application side). Try to reduce size of the lookup tables.
and one more thing: you can try to use MDM Java API 2
Regards, marcin

File save to networked drive takes a long time

I have been putting up with a real slowness with saving files in DW CS4. The save of a file is to a local network drive (H: drive). I can use other apps like a text editor and saving a file to the same drive is pretty near instant. But when I save a .cfm file in DW to the same drive it will often take 30 sec to up to 5 minutes...all of which is unacceptible for me. It's not every file either that is taking the same delay in time to save. It doesn't seem related to file length either. I have a file just now that is 47 lines of CF code, I saved it and it took about 3 or 4 minutes.
What is going on? Is this DW doing some funcky syntax checking or web standards checking or is it our network issue? If this is a configuration issue I'd sure like to know how to fix this. It's extremely annoying as I forget my train of thought by the time the file has saved.
All suggestions welcomed!

Well I probably should have checked around here some more. Just talked to someone in our IT dept. and they believe (unproven theory) that it is likely our network configuration and design. However if you have a few things to try to eliminate any other possibilities I'd like to hear them.

Office 2007 saving documents over mapped network drive takes abnormally long

On a new Windows 8.1 Pro 64 bit computer, I have installed Office 2007. When I attempt to save documents to a mapped network drive on a peer network (saving to a Windows 8.1 Pro 64 bit computer), I have abnormally long save times. However, when I attempt
to save documents to my computer, I have no issues. I do not have any issues when opening the files over the mapped drive.
Turning off the third-party Bullguard Internet Security antivirus and firewall makes no difference. Setting as an exception the excluded mapped drive folder makes no difference either.
I have disconnected the mapped drive and re-mapped the network drive, but this makes no difference.
I had no problem with the same software on a prior computer running the same Office 2007 version. Another computer on the network has no issues either.
Please advise how to speed up the saved documents (Word, Excel).

Hi,
As the slow to save files issue, please try the suggestion below to modify the registry:
Important
This section, method, or task contains steps that tell you how to modify the registry. However, serious problems might occur if you modify the registry incorrectly. Therefore, make sure that you follow these steps carefully. For added protection, back up the
registry before you modify it. Then, you can restore the registry if a problem occurs. For more information about how to back up and restore the registry,
http://windows.microsoft.com/en-US/windows7/Back-up-the-registry
To start the Registry Editor, press Win + R, type "regedit.exe" in the blank box, press Enter. Then add the following registry key to the machine:
[Hkey_Current_User\Software\Microsoft\Office\12.0\Word\Options]
"DisableRobustifiedUNC"=Dword:00000001
[Hkey_Current_User\Software\Microsoft\Office\12.0\Excel\Options]
"DisableRobustifiedUNC"=Dword:00000001
I hope this can help.
Regards,
Melon Chen
TechNet Community Support

Socket connection takes to long

I'am using the s = new java.net.Socket(TheURL,80); to connect to a socket.
But when the TheURL is wrong, or the URL does not respond, I have to wait a very long time before the call returns.
I'am working within a LAN and I'am conecting to LOCAL embeded webservers. (up to 100 pieces) When one or more of those are switch off (dead) the will block the timerloop in witch I switch from one server to an other.
I like to set some time out in getting he connection of 5 seconds. How do I do such?

I'am using the s = new java.net.Socket(TheURL,80); to
connect to a socket.
But when the TheURL is wrong, or the URL does not
respond, I have to wait a very long time before the
call returns.
I'am working within a LAN and I'am conecting to LOCAL
embeded webservers. (up to 100 pieces) When one or
more of those are switch off (dead) the will block the
timerloop in witch I switch from one server to an
other.
I like to set some time out in getting he connection
of 5 seconds. How do I do such?Depends on the version of java.
For versions before 1.4 you need to use threads. Either create a thread for each connect and don't worry about the ones that don't connect. Or create a timer thread that explicitly calls Socket.close() when the timer expires.
Or write your own sockets in JNI.

Retreive External data from SQL making connection to SQL server take a long time

I have an Excel pivottable based on a view from SQL server. The view gets data from 2 databases on the sames server. I have the sames login for both databases and also the same rights (datareader, datawriter and owner). When running the view from within
the SQL Server management tool it goes quick. In Excel once the connection is made everything goes fast. Only making the connection takes a very long time. When I use a view with data from a single database then everything is fine and goes fast.
Example of the situation: I use the example view below in an excel pivot. This gives as result that the connection takes very long.
SQLServer A
View CustomerInfo which contains the following query.
Select * FROM databaseA.dbo.Customers as Customers
CROSS APPLY
SELECT *
FROM databaseB.dbo.Contacts as Contacts
Where Customers.Number = Contacts.CustomerNumber
) AS Contactdata
When I remove the CROSS APPLY part, the connection is made directly
We login to SQL with normal logon (not windows security) The user has the same rights on both databases.
I hope the problem is clear. Does anyone have an idea of how I can solve this problem?

-1* ( prior dataid ) = parentid
is it multiplying -1 times the prior dataid ?that's exactly what it's doing
you need:
prior dataid = ABS(parentid);
not knowing you're data, and therefore assuming that dataid is always positive (since it doesn't have an ABS), and that parentid can be positive or negative, your criteria becomes
parentid = prior dataid (handles both are positive)
or parentid = negative of prior dataid (handles parentid is neg, dataid is pos)
since the "prior" must be right next to the column (dataid), I put parens around the whole thing, and then mult by -1

Network connection slow to become active after waking from sleep.

Using MBP (2007) with OS 10.8.2 I put my machine to sleep each night after work. Each morning when I wake it, the network connection takes over 90 seconds to become active. This is on a WIRED network. Didn't have this problem before Mountain Lion upgrade. Before ML the connection was nearly instant. Any clues?

I am seeing the same issue. I believe it started after upgrading to 10.8.2. (I did not notice such long network reconnections after wake with either 10.8.0 or 10.8.1.) I am also on a wired network. Same result using DHCP and fixed IP.
The network reconnection after wake used to be nearly instantaneous.

Error re Messaging Server Network Connection?

When I try to sync from my Desktop Manager, I get an error message stating: "The messaging server network connection is no longer available. Message synchronization cannot continue." I have tried everything I can think of (even uninstalling DM and resetting configurations). Nothing worked. Can anyone help me? I have a BB Tour and the DM (version 5.0.1) is running on Windows 7. Thank you!

Are you connected to a BES and exchange server at work?
If someone has been helpful please consider giving them kudos by clicking the star to the left of their post.
Remember to resolve your thread by clicking Accepted Solution.

Sometimes my computer takes too long to connect to new website. I am running a pretty powerful work program at same time, what is the best solution? Upgrading speed from cable network, is it a hard drive issue? do I need to "clean out" the computer?

Many times my computer takes too long to connect to new website. I have wireless internet (time capsule) and I am running a pretty powerful real time financial work program at same time, what is the best solution? Upgrading speed from cable network? is it a hard drive issue? do I only need to "clean out" the computer? Or all of the above...not to computer saavy. It is a Macbook Pro osx 10.6.8 (late 2010).

Almost certainly none of the above! Try each of the following in this order:
Select 'Reset Safari' from the Safari menu.
Close down Safari; move <home>/Library/Caches/com.apple.Safari/Cache.db to the trash; restart Safari.
Change the DNS servers in your network settings to use the OpenDNS servers: 208.67.222.222 and 208.67.220.220
Turn off DNS pre-fetching by entering the following command in Terminal and restarting Safari:
defaults write com.apple.safari WebKitDNSPrefetchingEnabled -boolean false

MBP takes long time to restore wired network connection after wake-up

Hello...
My Mid-2010 MBP (MacBookPro6,2) has been experiencing this problem recently -- Whenever I wake up the computer from sleep, it needs approximately 10 seconds to restore its wired network connection. I know there are other annoying connection issues with MBP's WiFi/AirPort out there, but I'm talking about the wired connection here.
Maybe some don't even think this slowness is a problem at all, but this laptop used to be network-ready right after wake-up until 3~4 months ago. That was around the time when I upgraded to SSD and changed some settings via pmset, not sure if that's the culprit. It is now running OS X 10.8.5 and its pmset settings are:
Battery Power:
lidwake              1
ttyskeepawake        1
hibernatemode        3
gpuswitch            2
hibernatefile        /var/vm/sleepimage
displaysleep         2
sleep                15
acwake               0
halfdim              1
sms                  0
lessbright           1
disksleep            10
AC Power:
lidwake              1
ttyskeepawake        1
hibernatemode        0
gpuswitch            2
hibernatefile        /var/vm/sleepimage
womp                 1
displaysleep         10
networkoversleep     0
sleep                60
acwake               0
halfdim              1
sms                  0
disksleep            0
I'd appreciate help of any kind
Thanks,
zuoy

Maybe try this, i am not sure that it will resolve the problem, but it is worth trying anyways.
http://social.technet.microsoft.com/Forums/en-US/w7itpronetworking/thread/eef49e64-157c-4082-8e80-52e48309691f
Hi All,
I've seen this problem multiple times, especially with Windows 7 64-bit versions and Enterprise edition. The source of the problem appears to be the Bonjour service that is installed in the background and set to "Automatic" when installing certain 3rd
party applications. Apple applications like iTunes and Adobe applications like Acrobat Professional and Creative Suites have been known to cause this problem. I've also seen virtualization software like VMWare and VirtualBox cause similar issues
with network adapters.
The solution in most of the cases I've come across has been to stop and disable the Bonjour service. The Bonjour service also masquerades as a service with a name of the format "##Id_String1.6844F930_blahblahblah". Here's how to disable this service
in Windows 7:
Right-Click on Computer > Select 'Manage'
Expand the 'Services and Applications' section in the bottom of the Left-Nav dialog and Select 'Services'
Sort the Services list by name and look for either "Bonjour" or the "##Id_String..." name mentioned above
Right-Click on the service and select 'Properties'
Click the 'Stop' button to stop the service
Select 'Disabled' from the 'Startup type' drop down list
Click 'Apply' and then 'OK'
Reboot your machine and see if the "Multiple Networks" issue is resolved. If so, you should have internet connectivity again.
Hope this helps.
cheers,
Aaron

HttpURLConnection.connect() takes long time (3 minutes)

I'm stumped on an unusual problem. I'm running java 1.3 and Apache JServ (don't ask, I inherited this set up), using JSSE. One of the things we do with our app involves some xml communication over SSL.
Starting last week, the time for the SSL communication jumped from about 15 seconds to around 3 minutes.
Here is the bit of code that does the actual communication. An example function call would be:
contactService("ShipConfirm", "ups.app/xml");and the function definition:
public void contactService(String service, String prefix) throws Exception {
HttpURLConnection connection;
URL url;
// the next 2 variables are stored elsewhere in the object
// these values are just examples of one invocation
String protocol = "https";
String hostname = "wwwcie.ups.com";
String urlStr = protocol + "://" + hostname + "/" + prefix + "/" + service;
// so for this test urlString = "https://wwwcie.ups.com/ups.app/xml/ShipConfirm";
try {
    if (protocol.equalsIgnoreCase("https")) {
      java.security.Security.addProvider(new com.sun.net.ssl.internal.ssl.Provider());
      System.getProperties().put("java.protocol.handler.pkgs", "com.sun.net.ssl.internal.www.protocol");
    url = new URL(urlString);
    // Trace.log is a convenience class that will print to a log file and include a timestamp
    Trace.log("open connection to " + urlString);
    connection = (HttpURLConnection) url.openConnection();
    // openConnection takes about 20 seconds now, before 1 or 2 seconds
    Trace.log("opened connection to " + urlString);
    connection.setDoOutput(true);
    connection.setDoInput(true);
    connection.setUseCaches(false);
    // XmlIn is an already generated xml file stored in a StringBuffer, declared elsewhere
    String queryString = XmlIn.toString();
    Trace.log("xml connection to " + urlString);
    connection.connect();
    // connect takes about 3 minutes 10 seconds now, before 15 seconds
    Trace.log("xml connection complete " + urlString);
    OutputStream out = connection.getOutputStream();
    out.write(queryString.getBytes());
    out.close();
    String data = "";
    try {
      // on the server this is actually a separate function
      StringBuffer buffer = new StringBuffer();
      BufferedReader reader = null;
      try {
        reader = new BufferedReader(new InputStreamReader(connection.getInputStream()));
        String line = null;
        int letter = 0;
        while ((letter = reader.read()) != -1)
          buffer.append((char) letter);
      catch (Exception e) {
        // Trace.major is like Trace.log, but is a higher severity
        Trace.major("Cannot read from URL" + e.toString());
        throw e;
      finally {
        try {
          reader.close();
        catch (IOException io) {
          Trace.major("Error closing URLReader!");
          throw io;
      data = buffer.toString(); // actually a return statement on server
    catch (Exception e) {
      Trace.major("Error in reading URL Connection" + e.getMessage());
      throw e;
    XmlOut = new StringBuffer(data); // XmlOut is a StringBuffer declared elsewhere
catch (Exception e1) {
    Trace.major("Error sending data to server" + e1.toString());
} Besides a couple of new Trace.log statements to pin down the what, exactly, is taking so long, I haven't touched this code in the year+ since I've inherited it. There haven't been any changes in the network setup for the last 3 weeks, either (last change was new reverse lookup zone for our internal network).
Any idea why the HttpURLConnection.connect() would take so long? Or any idea how I can find out what is going on for those 3 minutes? In my search so far, I found -Djava.net.debug=ssl,handshake,data and added it to my startup parameters, but in my frustration, I must have overlooked what I need do to make it show up in my logs.
I set up a tcpdump on the server to listen on the IP that I'm trying to connect to and the "xml connection to" log statement prints, then about 3 minutes and 10 seconds goes by, then tcpdump reports that we actually send the packets to the other server, then we get a response and print the "xml connection complete" log message. URL and HttpURLConnection are not subclassed at all.
To make things even more interesting, I broke out this code, and wrote a small test program. The test program has some minor changes (pulling the xml data from an already existing file, mainly), and this version runs lickety-split (about 5 seconds).
Any help or pointers would be greatly appreciated. Let me know if I can provide any more information.
Thanks,
Andy

Figured it out..
The other side removed a proxy server that we used to try to connect through. The server was taking 3 minutes and 10 seconds to time out when it trying to contact the proxy server.
To be honest, I don't know if we ever successfully connected through the proxy server. I'm inclined to believe we tried to contact it, but were rejected, but no one ever removed the proxy code.
Andy

Network connection takes to long

Similar Messages

Maybe you are looking for