Got I/O exception when trying to create load balancer

[GoogleCodeExporter]

        LoadBalancing lb = new LoadBalancing(env.getAccessKey(),
env.getSecretKey());
        Listener listener = new Listener("TCP", 80, 8080);
        List<Listener> listeners = new ArrayList<Listener>();
        listeners.add(listener);

        List<String> zones = new ArrayList<String>();
        zones.add(EC2ServerService.EC2_ZONE);
        String dns = lb.createLoadBalancer("test_a_test", listeners, zones);

        System.out.println(dns);

        List<String> instances = new ArrayList<String>();
        instances.add("i-ad82e7c5");
        instances.add("i-1be28773");

        lb.registerInstancesWithLoadBalancer("test_a_test", instances);

The whole thing stops at this line:
         String dns = lb.createLoadBalancer("test_a_test", listeners, zones);

And this is what I got:
2009-11-13 13:40:24,129 [org.apache.commons.httpclient.HttpMethodDirector]
INFO - I/O exception (java.net.ConnectException) caught when processing
request: Connection timed out: connect
2009-11-13 13:40:24,129 [org.apache.commons.httpclient.HttpMethodDirector]
INFO - Retrying request

I am using typica 1.6 and Jec2 works in my environment. I searched the
Internet and it seems there is no working example for the LoadBalancer API.
So I am trying to see if you have known anything about it.

Original issue reported on code.google.com by weili.s...@gmail.com on 13 Nov 2009 at 9:46

• Merged into: #62

[GoogleCodeExporter]

I am seeing this same sort of exception logged just for 
describeLoadBalancers(). This
part of the API does not seem to work at all. The command-line tools for elb do 
work,
so I think this is specifically typica, not an authentication issue. 

I'll take a look at the typica code to see if I might be able to help fix this 
issue.

Original comment by jncorp...@gmail.com on 19 Jan 2010 at 1:53

[GoogleCodeExporter]

Looks like this is related to, or a duplicate of issue #62.

Original comment by jncorp...@gmail.com on 19 Jan 2010 at 2:43

[GoogleCodeExporter]

I switched to amazon's lib. A little bit more verbose, but works well.

Original comment by weili.s...@gmail.com on 19 Jan 2010 at 6:51

[GoogleCodeExporter]

This was probably related to the bad endpoint configured in the 1.6 release. 
Sorry it has 
taken so long with the new release.

Original comment by dkavan...@gmail.com on 23 Mar 2010 at 10:57

• Changed state: Duplicate