onerandomgig / typica Goto Github PK

[deleted issue]

It would be useful to be able to retrieve the BoxUsage value from SimpleDB
requests.

Project Home

Dependency link broken:
http://jakarta.apache.org/site/downloads/downloads_commons-httpclient-3.x.cgi

Hi, 
I am specifying a visibility timeout of 300 when invoking
MessageQueue.receive(300), however I keep getting the same messages
returned, seems like it is ignored... typica 0.8 is being used.... 
is this a known issue? 

the default queue timeout is however 0 - but this should be overwritten
with my attempt - is this assumption correct?

thanks, 

flo

What steps will reproduce the problem?

1. Look in ImageDescription.java
2. Observe that there is getPlatform() method

What is the expected output?

--> The value of the 'platform' element of the response from the EC2 web
service.

What do you see instead?

--> Nothing.

What steps will reproduce the problem?

Saving an item id with an accented character (like é)

Domain test = sdb.getDomain("test");
Item item = test.getItem("café");
List<ItemAttribute> attrs = new ArrayList<ItemAttribute>();
attrs.add(new ItemAttribute("name","value",true));
item.putAttributes(attrs);

What is the expected output? What do you see instead?
Expected: the item is saved
Instead: Client error : The request signature we calculated does not match
the signature you provided. Check your AWS Secret Access Key and signing
method. Consult the service documentation for details.


What version of the product are you using? On what operating system?
Typica 1.5.1
Windows Vista

Please provide any additional information below.
When using the Firefox SimpleDB plugin, I'm able to use accents.

I'm playing around with the API to fetch EC2 instance metadata.
http://code.google.com/p/typica/source/browse/trunk/java/com/xerox/amazonws/ec2/
EC2Utils.java

I noticed that if I pass in a bogus key it goes into an infinite loop. The
problem seems to be that the retries variable is never incremented.

Switch from requiring log4j to commons-logging. See forum posts for
compelling arguments.

In some cases, the web services report additional error details. Those
should be parsed and returned in the exception message.

I am using Typica for developing a monitor UI of our application server
cluster. So far so good, until I realized that Typica doesn't support
bundling Amazon Instances. I guess it's because this operation is for
Windows AMIs only, and it was not available until recently Amazon started
to support Windows instances. 

Since all our instances are Windows, I couldn't proceed without
BundleInstance operation supported. I am stuck. It'd be great if you can
implement this in the near future. Thanks for listening.

What steps will reproduce the problem?
1. run sdbShell, set a domain and try "item ItemWhatever"

What is the expected output? What do you see instead?
Error is:
java.util.NoSuchElementException
        at java.util.StringTokenizer.nextToken(Unknown Source)
        at sdbShell.main(sdbShell.java:211)

What version of the product are you using? On what operating system?
Version 1.1 of sdbShell (typica1.5 download) and svn checkout
The old version 1.0 works fine

Seems like the line 211
List<ItemAttribute> attrs = item.getAttributes(st.nextToken);
should be replaced by
List<ItemAttribute> attrs = item.getAttributes();

At least for me this works fine.

cheers,
Raffael

Improved the enum type to have more information about the instance type.
Applications need them to make intelligent decisions.

When trying to put an attribute/value that contains * character, the 
following exception is thrown:

Exception caught when trying to update the EC2Object to SimpleDB storage : 
com.xerox.amazonws.sdb.SDBException: Client error : The request signature 
we calculated does not match the signature you provided. Check your AWS 
Secret Access Key and signing method. Consult the service documentation for 
details.

Is * a special character that we should avoid? Or it's not properly URL-
encoded in Typica? I assume the client code doesn't need to URL-encode 
anything. Correct me if I am wrong.

Exception in thread "Thread-1" java.lang.ArrayStoreException
    at java.lang.System.arraycopy(Native Method)
    at java.util.Arrays.copyOf(Arrays.java:2763)
    at java.util.ArrayList.toArray(ArrayList.java:305)
    at
com.xerox.amazonws.sqs2.QueueService.listMessageQueues(QueueService.java:179)
    at com.xerox.amazonws.sqs2.SQSUtils.getMessageQueue(SQSUtils.java:104)
    at com.xerox.amazonws.sqs2.SQSUtils.connectToQueue(SQSUtils.java:63)
    at com.xerox.amazonws.sqs2.SQSUtils.connectToQueue(SQSUtils.java:44)
    at offline.WorkerThread.run(MapPlayedWorkerThread.java:22)
    at java.lang.Thread.run(Thread.java:619)


Code that generate this error:

        MessageQueue msgQueue;
        try {
            msgQueue = SQSUtils.connectToQueue(Constants.AWS_MAPPLAYEDQUE,
Constants.AWS_ACCESSKEY, Constants.AWS_SECRETACCESSKEY);
        } catch(SQSException notGood) {
            log.severe("Failed to connect to the que " +
Constants.AWS_MAPPLAYEDQUE + " for processing: " + notGood);
            return;
        }

When constructing the URL the userData is not base64 encoded.
The following patch fixes this issue:

--- Jec2.java.orig      2007-06-13 14:44:05.000000000 +0200
+++ Jec2.java   2007-06-17 02:48:15.000000000 +0200
@@ -386,7 +386,7 @@
                params.put("MinCount", ""+minCount);
                params.put("MaxCount", ""+maxCount);
                if (userData != null && !userData.trim().equals("")) {
-                       params.put("UserData", userData);
+                       params.put("UserData",
Base64Coder.encodeString(userData));
                }
                if (publicAddr) {
                        params.put("AddressingType", "public");

It looks like the "params" Hashtable was converted to the LinkedHashSet.  That 
map is only used in 
creating the request, the "results" Hashtable needs to be changed to affect the 
ordering of the 
returned items.

Hi, 
firstly, thanks for this great library, makes SQS access extremely
convenient for me. I am using typica 0.8 at the moment.

I have a problem however, calling the MessageQueue.receive(int timeout)
seems to be blocking at times - I have 50 messages in the queue (each
around 1K) and retrieving them takes an awfully long time (several minutes)
- it seems as if instead of returning null it blocks until the next one
becomes available? is this the case?

thanks, 
Flo

Hi

I cannot use as-is the runInstance

The error returned by amazon:

<?xml version="1.0"?>
<Response><Errors><Error><Code>InvalidParameterValue</Code><Message>Direct
addressing has been deprecated and is not available to this EC2 account.
Please specify an alternate addressing type. Supp
rted addressing types are:
public</Message></Error></Errors><RequestID>1dc3c0d1-1029-4347-a907-59544b41d583
</RequestID></Response>titi

The file to update : Jec2.java
change 
   params.put("AddressingType", "direct);
to 
   params.put("AddressingType", "public");

Everything else works great, thanks for sharing this lib.

Enjoy your day !
Florent

What steps will reproduce the problem?
1. connect to another service URL than https://ec2.amazonaws.com, e.g.
http://mayhem9.cs.ucsb.edu:8773/services/Eucalyptus

The problem here is that Typica only allows specifying protocol, port and
host, not path.

If one user has been granted access to a queue from another user, there is
currently no way to supply the the full queue designator and access that
queue. (i.e. /A928B2389E/grantedQueue)

What steps will reproduce the problem?

trying to use the EC2 QUERTY API against an eucalyptus instance whose
endpoint is
http://myeuca.localhost:8888/services/euca

the endpoint to which the requests are sent is built in
com.xerox.amazonws.common.AWSConnection.makeURL(String)

that now looks like

protected URL makeURL(String resource) throws MalformedURLException {
        String protocol = this.isSecure ? "https" : "http";
        return new URL(protocol, this.server, this.port, this.virtualPath +
resource);
    }


What version of the product are you using? On what operating system?

1.5 (as euca doesn't support 2009-03-01 schema)


Please provide any additional information below.

I have modified the ctor as 
    public AWSConnection(String awsAccessId, String awsSecretKey, boolean
isSecure,
                             String server, int port, String virtualPath)
    {
        this.awsAccessId = awsAccessId;
        this.awsSecretKey = awsSecretKey;
        this.isSecure = isSecure;
        this.server = server;
        this.port = port;
        this.virtualPath = sanitise(virtualPath);
        this.headers = new TreeMap<String, List<String>>();
    }

and added 

    private String sanitise(String virtualPath) {
        if (virtualPath == null || "".equals(virtualPath.trim())) {
            return "";
        }
        String ret = virtualPath.trim();
        if (ret.endsWith("/")) {
            ret = ret.substring(0, virtualPath.length() - 1);
        }
        if (ret.length() > 1 && !ret.startsWith("/")) {
            ret = "/" + ret;
        }
        return ret;
    }

I have had to fix the derived classes accordingly

I'd appreciate if you could retrofit these changes in v1.5 and v1.5.1

MessageQueue.sendMessage() doesn't support the visibility timeout. It should

What steps will reproduce the problem?
1. Downloaded jars and sample code
2. Set class path
3. Eclipse doesn't find import com.xerox.amazonws.tools.LoggingConfigurator;

What is the expected output? What do you see instead?
http://typica.googlecode.com/svn/trunk/java/com/xerox/amazonws/ doesn't contain 
any 
LoggingCofigurator class in it's tools package.

What version of the product are you using? On what operating system?
Latest typica on Mac OS X 10.5.1 

Please provide any additional information below.

What steps will reproduce the problem?
1. The Amazon SQS schema and api was recently changed.  Document:
http://developer.amazonwebservices.com/connect/entry.jspa?externalID=1148.
 Since this affects pricing, users will definately be looking for it soon.
2. When do you expect to update the library to support this?
3. Thanks for the great tool!

What is the expected output? What do you see instead?


What version of the product are you using? On what operating system?


Please provide any additional information below.

Couldn't find the api to set connection timeout while connecting to a 
queue.
if the network connection breaks how long it will keep trying to make 
connection ?

What steps will reproduce the problem?
1.
2.
3.

What is the expected output? What do you see instead?


What version of the product are you using? On what operating system?


Please provide any additional information below.

Its hard to say the exact cause of the problem, but basically i am getting 
all sorts of funny behavior with results when i use 
listItemsWithAttributes() (and it may also be related to the other query 
commands as well i haven't verified)

The max results field seems to change the output as well. When it is set 
below the number of results that will be returned i get a good inital list 
and the token to continue.  however when i use the continuation token i 
seem to be getting more (still not all) of the results but duplicate 
results. I will try my best to explain a way to reproduce it.  but there is 
more going on than what i can mention. I can confirm that the results from 
the java T-437 app are different.


Domain: accounts
<displayname> <username> 
a            aasdf
a            aaa
aaaaa        aaaaa
test         afdasdf
a            a
a            boschb4
aaaa         aaaa


What is the expected output? What do you see instead?
I wont mention the expected output because its obvious, but here are some 
scenarios i ran...

['username' starts-with 'a'] maxresults: 10 yields: 
<a,a> 
<aaaa,aaaa> 
<aaaaa,aaaaa> 
<test,afdasdf>

['username' starts-with 'a'] union ['displayname' starts-with 'a']
maxresults: 4 yields: 
<a,a> 
<aaaa,aaaa> 
<aaaaa,aaaaa>
+ CONT TOKEN
<a,a>
<test,afdasdf> 
+ CONT TOKEN
<a, aasdf>
<aaaa,aaaa>
<aaaaa,aaaaa>


['username' starts-with 'a']
maxresults: 3 yields: 
<a,a>
<aaaa,aaaa>
+CONT TOKEN
<a,aasdf>
<aaaaa,aaaaa>
<test,afdasdf>

['username' starts-with 'a'] union ['displayname' starts-with 'a']
maxresults: 3 yields: 
<a,a> 
<aaaa,aaaa> 
+ CONT TOKEN
<a,aasdf>
<aaaaa,aaaaa>
<test,afdasdf> 
+ CONT TOKEN
<a, a>
+ CONT TOKEN
<a,aasdf>
<aaaa,aaaa>
<aaaaa,aaaaa>


What version of the product are you using? On what operating system?
1.4.1 with Java 6 (x86) on Flex Builder(Eclipse 3.3 x86) on Vista x64


Hope this is enough to start on.

What steps will reproduce the problem?
1. Checkout latest code from CVS.
2. Compile with Eclipse or Ant...

What is the expected output? What do you see instead?
Expected:
No Compile Errors.

Actual result:
Missing java classes within
com.xerox.amazonws.ec2.DescribeImageAttributeResult and
com.xerox.amazonws.ec2.Jec2

com/xerox/amazonws/ec2/DescribeImageAttributeResult.java:31: cannot find symbol
    [javac] symbol  : class BlockDeviceMapping
    [javac] location: class com.xerox.amazonws.ec2.DescribeImageAttributeResult
    [javac]     private List<BlockDeviceMapping> blockDeviceMappings;

What version of the product are you using? On what operating system?
Latest from SVN.

Please provide any additional information below.
Possible bug with the XSD generation or bug with the latest EC2 WSDL.

What steps will reproduce the problem?
1. Attempt to get data out of a SDB Domain that does not exist.
2. AttrWorker.java line 47 will enter an infinite loop.  Since the Domain
doesn't exist, an exception is thrown, then eaten, but there's no break
statement (or at least the 'done' boolean doesn't get set).

What is the expected output? What do you see instead?
The program should continue on normally.  Instead, I see the following in
the console:
2008-09-18 15:11:51,565 ERROR [STDERR] some sdb error, retrying...
Client error : The specified domain does not exist.
2008-09-18 15:11:51,729 ERROR [STDERR] some sdb error, retrying...
Client error : The specified domain does not exist.
2008-09-18 15:11:51,856 ERROR [STDERR] some sdb error, retrying...
Client error : The specified domain does not exist.
2008-09-18 15:11:52,012 ERROR [STDERR] some sdb error, retrying...
Client error : The specified domain does not exist.


What version of the product are you using? On what operating system?
Java 6, Typica Head, Windows Vista 64

Please provide any additional information below.
This problem could arise if any SDBError gets thrown here, not just a
non-existent Domain.

What steps will reproduce the problem?
1. Include typica and log4j.xml in a jar.

What is the expected output? What do you see instead?

Expect no error, but see:
I get the following:

ROOT CAUSE:
java.lang.IllegalArgumentException: URI is not hierarchical
        at java.io.File.<init>(File.java:363)
        at
com.xerox.amazonws.tools.LoggingConfigurator.configureLogging(Logging
Configurator.java:47)
        at
com.xerox.amazonws.sqs.QueueService.<clinit>(QueueService.java:52)
        at
com.xerox.amazonws.sqs.SQSUtils.getQueueService(SQSUtils.java:81)
        at
com.xerox.amazonws.sqs.SQSUtils.connectToQueue(SQSUtils.java:60)

Please provide any additional information below.

The fix is to comment out the file stuff:


If you don't use File in LoggingConfigurator this will go away, eg:

public class LoggingConfigurator {
    private static boolean loggingConfigured = false;
    private static final String LOGGER_CONFIG = "Log4j.xml";

    public static Logger configureLogging(Class callingClass) {
        if (!loggingConfigured) {
            URL configFileURL =
callingClass.getClassLoader().getResource(LOGGER_CONFIG);
            if (configFileURL == null){
                System.err.println("The log4j configuration file
\""+LOGGER_CONFIG+
                    "\" was not found on the classpath.");
            }
            /*File configFile = null;
            try {   
                configFile = new File(configFileURL.toURI());
            }catch (URISyntaxException e) {
                System.err.println("Log4J config file URL "+configFileURL+
                        " couldn't be converted to a URI.");
                e.printStackTrace(System.err);
            }*/
            DOMConfigurator.configureAndWatch(configFileURL.toString());
            loggingConfigured = true;
            System.out.println("\n\nLogging initial configuration complete
according to file "+configFileURL);
        }
        System.out.println("Log4j logger created.");
        return Logger.getLogger(callingClass.getName());
    }
}

When using the "sort" option in SimpleDB, the ordering of the items is not 
retained.

In the implementation of the listItemsWithAttributes() method in Domain.java, 
it stores the results 
of the query in a Hashtable which does not retain insertion order.  This can be 
fixed by using a 
LinkedHashSet wrapped to retain the thread safety of the Hashtable.

Attached is a Subversion diff which implements this change to retain proper 
ordering of sorted 
query results.

What steps will reproduce the problem?
1. Creating a MessageQueue and calling receiveMessage on a schedule (once 
per minute, etc.)

What is the expected output? What do you see instead?
Expected - the app should keep running normally.  Instead, the memory 
keeps increasing until an OOM situation occurs and the JVM crashes.

What version of the product are you using? On what operating system?
Current CVS.  Deployed on CentOS5 under JRockitR27-3.1 and Tomcat 6.  Same 
symptoms also occured with an extension of AbstractBaseService running on 
a CentOS5/JRockitR27-3.1 EC2 instance (no Tomcat).

Please provide any additional information below.
Spent a few days tracking this one down, and once located, the fix was 
pretty easy.  In receiveMessages I simply wrapped everything the 
HttpURLConnection with a finally to disconnect it and wrapped the 
InputStream with a finally to close it.  This immediately stopped the 
memory leak.  However, there are a number of other methods which work the 
same way which (I expect) will cause similiar problems once used (with 
pooling, etc.).

While it would be a fairly dramatic change, I would suggest creating a 
control object which calls the AWSQueryConnection.makeRequest method, then 
an abstract "execute" method which could be implemented by users of the 
client, followed by the cleanup.  This inverted-control would ensure that 
the clients can use it safely without having to understand how it works 
and dealing with clean-up.  You could leave the existing makeRequest 
method for backwards compatibility with existing users, but deprecate it 
with warnings about cleanup.

It would be great to be able to collect box usage statistics for 
putAttributes(), deleteAttributes() and 
other methods on Item.

for ( MessageQueue mq : msgQueuesFound ) {
   if ( mq.getUrl().toString().endsWith( msgQueueName ) ) {
                                msgQueueFound = mq;
      }
}


The name resolution is incorrect.  If I have queue by the name of FooBar
and another by the name of Bar.  And if FooBar was instantiated before Bar.  

The getQueueService() method would end up serving FooBar when requesting Bar.

public QueryResult listItems(String queryString, String nextToken) throws
SDBException {
    return listItems(queryString, null, 0);
}

the parameter nextToken is lost

What steps will reproduce the problem?
1. dom = sdb.createDomain(domainname);
2.
3.

What is the expected output? What do you see instead?
I should receive de Domain Object instead Receive
com.xerox.amazonws.sdb.SDBException: Problem parsing returned message.
    at com.xerox.amazonws.sdb.SimpleDB.createDomain(SimpleDB.java:161)
    at com.unience.simpleDB.SimpleDbHelper.createDomain(SimpleDbHelper.java:58)
    at com.unience.discovery.InstanceDAO.<init>(InstanceDAO.java:62)
    at
com.unience.instcontroller.core.DiscoveryPublisher.isPublishedSimpleDB(Discovery
Publisher.java:100)
    at
com.unience.instcontroller.core.DiscoveryPublisher.run(DiscoveryPublisher.java:4
9)
Caused by: javax.xml.bind.UnmarshalException
 - with linked exception:
[org.xml.sax.SAXParseException: Premature end of file.]
    at
javax.xml.bind.helpers.AbstractUnmarshallerImpl.createUnmarshalException(Abstrac
tUnmarshallerImpl.java:315)
    at
com.sun.xml.bind.v2.runtime.unmarshaller.UnmarshallerImpl.createUnmarshalExcepti
on(UnmarshallerImpl.java:481)
    at
com.sun.xml.bind.v2.runtime.unmarshaller.UnmarshallerImpl.unmarshal0(Unmarshalle
rImpl.java:199)
    at
com.sun.xml.bind.v2.runtime.unmarshaller.UnmarshallerImpl.unmarshal(Unmarshaller
Impl.java:168)
    at
javax.xml.bind.helpers.AbstractUnmarshallerImpl.unmarshal(AbstractUnmarshallerIm
pl.java:137)
    at
javax.xml.bind.helpers.AbstractUnmarshallerImpl.unmarshal(AbstractUnmarshallerIm
pl.java:184)
    at com.xerox.amazonws.common.JAXBuddy.deserializeXMLStream(JAXBuddy.java:80)
    at
com.xerox.amazonws.common.AWSQueryConnection.makeRequest(AWSQueryConnection.java
:341)
    at com.xerox.amazonws.sdb.SimpleDB.createDomain(SimpleDB.java:153)
    ... 4 more
Caused by: org.xml.sax.SAXParseException: Premature end of file.
    at
com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.createSAXParseExcept
ion(Unknown
Source)
    at
com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.fatalError(Unknown
Source)
    at
com.sun.org.apache.xerces.internal.impl.XMLErrorReporter.reportError(Unknown 
Source)
    at
com.sun.org.apache.xerces.internal.impl.XMLErrorReporter.reportError(Unknown 
Source)
    at
com.sun.org.apache.xerces.internal.impl.XMLVersionDetector.determineDocVersion(U
nknown
Source)
    at
com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(Unknown
Source)
    at
com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(Unknown
Source)
    at com.sun.org.apache.xerces.internal.parsers.XMLParser.parse(Unknown Source)
    at
com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.parse(Unknown
Source)
    at
com.sun.xml.bind.v2.runtime.unmarshaller.UnmarshallerImpl.unmarshal0(Unmarshalle
rImpl.java:195)
    ... 10 more


What version of the product are you using? On what operating system?
Typica 1.3
JDK 1.5.15
Please provide any additional information below.

What steps will reproduce the problem?
1. Try to run an Instance with the Jec2.runInstances method
2  
3.

What is the expected output? What do you see instead?

an instance should be started, but the URL constructed ist incorrect


What version of the product are you using? On what operating system?

current svn


Please provide any additional information below.

The runInstance method of Jec2 doesn´t construct the URL parameters for
Security Groups correctly.

For Security Groups a paramter "n" instead of "SecurityGroup.n" is
constructed. 

The following patch corrects this issue:

 mo@slartibartfast:~/typicasvn$ svn diff
Index: java/com/xerox/amazonws/ec2/Jec2.java
===================================================================
--- java/com/xerox/amazonws/ec2/Jec2.java       (revision 51)
+++ java/com/xerox/amazonws/ec2/Jec2.java       (working copy)
@@ -398,7 +398,7 @@
                        params.put("KeyName", keyName);
                }
                for (int i=0 ; i<groupSet.size(); i++) {
-                       params.put(""+(i+1), groupSet.get(i));
+                       params.put("SecurityGroup."+(i+1), groupSet.get(i));
                }

                try {

Possibly due to the padding added on the end of some base64 encoded
strings, the query authentication is messed up. This results in a 401
response code.

Looking at the API Docs for SimpleDB#listDomains which describes the
function as: "Terminates a selection of running instances." which seems to
be a copy and paste error from Jec2? Are these docs correct?

I've been trying to figure out how to create an item in a SimpleDB domain, 
and it eluded me, until I found this thread in the Typica forums:

http://groups.google.com/group/typica/browse_thread/thread/e19c89b63b21ac61
/3e7be075b30aa67b?lnk=gst&q=simpledb#3e7be075b30aa67b

In the thread, David K says this is a bit deceiving, and he's right ;)  
Would it be possible to add a simple function or two to the domain class, 
like so:

public Item add(final List<ItemAttribute> attributes) { ... }

It would make learning the library just a bit easier.  Thanks for a great 
library, we've been using it in production for months now, and it's 
awesome.

The JavaDoc is MIA

I use Typica 1.5 to bundle an image. The bundle task can be started. But 
when the progress goes to the end, the task fails with the following error:
SignatureDoesNotMatch(403)- The request signature we calculated does not 
match the signature you provided. Check your key and signing method.

Here is how I called the new BundleInstance API:

ec2.bundleInstance(instanceID, accessId, bucketName, amiName, new 
UploadPolicy(60, bucketName, "aws-exec-read"));

I use the same accessId as EC2 for S3 storage. Anything wrong with my way 
of calling the API?

I think it should be optional, but turned on by default, or not? Since we
don't currently base64 encode, should we do it by default?

I'm seeing this message being logged, for queues that have already been
created and used.

[java] INFO  com.xerox.amazonws.sqs.SQSUtils  - Message queue couldn't be l
isted, going to create it.

Need to fix this!

When executing Jec2.describeImagesByImageType(ImageType.MACHINE), it always 
throws Exception as below:

com.xerox.amazonws.ec2.EC2Exception: Client error : The parameter ImageType 
is not recognized

If you care to have a Maven POM for building as well one for distribution, here 
you go.

What steps will reproduce the problem?
1. Try to get the list of KeyPairInfo 
2. I get it but the material attribute it is set to null
3.

try {
            List<KeyPairInfo> keyPairs = ec2Instance.getEc2().describeKeyPairs(
                    new ArrayList<String>());
            for (KeyPairInfo keyPairInfo : keyPairs) {
                log.debug(keyPairInfo.getKeyName());
                log.debug(keyPairInfo.getKeyMaterial());
            }
        } catch (Exception e) {
            log.error("error get KeyPairs", e);
        }


What version of the product are you using? On what operating system?
Typica 1.2 over Java Jdk 1.6.X

Please provide any additional information below.

What steps will reproduce the problem?

1. Download and install http://code.google.com/p/simpledb-dev/
2. Launch simpledb-dev (NB: defaults to port 8080)
3. Run:

SimpleDB simpleDb = new SimpleDB("x", "x", false, "localhost", 8080);
simpleDb.setMaxRetries(0);
System.out.println("DB max retries: " + simpleDb.getMaxRetries());
Domain d = simpleDb.createDomain("issue_report");
System.out.println("Domain max retries: " + d.getMaxRetries());
QueryResult result = d.listItems();
System.out.println("Result box use: " + result.getBoxUsage());

What is the expected output? What do you see instead?

Expected:

DB max retries: 0
Domain max retries: 0
Result box use: 0.0000219907

Received:

DB max retries: 0
Domain max retries: 5
I/O exception (java.net.ConnectException) caught when processing request:
Connection refused
Retrying request
I/O exception (java.net.ConnectException) caught when processing request:
Connection refused
Retrying request
I/O exception (java.net.ConnectException) caught when processing request:
Connection refused
Retrying request
I/O exception (java.net.ConnectException) caught when processing request:
Connection refused
Retrying request
I/O exception (java.net.ConnectException) caught when processing request:
Connection refused
Retrying request
I/O exception (java.net.ConnectException) caught when processing request:
Connection refused
Retrying request
I/O exception (java.net.ConnectException) caught when processing request:
Connection refused
Retrying request
I/O exception (java.net.ConnectException) caught when processing request:
Connection refused
Retrying request
I/O exception (java.net.ConnectException) caught when processing request:
Connection refused
Retrying request
I/O exception (java.net.ConnectException) caught when processing request:
Connection refused
Retrying request
I/O exception (java.net.ConnectException) caught when processing request:
Connection refused
Retrying request
I/O exception (java.net.ConnectException) caught when processing request:
Connection refused
Retrying request
I/O exception (java.net.ConnectException) caught when processing request:
Connection refused
Retrying request
I/O exception (java.net.ConnectException) caught when processing request:
Connection refused
Retrying request
I/O exception (java.net.ConnectException) caught when processing request:
Connection refused
Retrying request
I/O exception (java.net.ConnectException) caught when processing request:
Connection refused
Retrying request
I/O exception (java.net.ConnectException) caught when processing request:
Connection refused
Retrying request
I/O exception (java.net.ConnectException) caught when processing request:
Connection refused
Retrying request

There are two issues: (a) Typica does not observe port 8080 in the created
Domain (nor any other object subsequently created by Domain); and (b) the
setMaxRetries(0) is being ignored in the created Domain.

It is possible to use port 80 instead of 8080 with simpledb-dev. This works
around issue (a) and suggests simpledb-dev is working correctly.
Simpledev-dev port 8080 usage was tested successfully using
http://code.google.com/p/amazon-simpledb-cli/.

What version of the product are you using? On what operating system?

Typica 1.5; Ubuntu 8.10 (2.6.27-11-generic i686); Java 1.6.0_10.

What steps will reproduce the problem?
There is no opportunity to get image architecture.

What is the expected output? What do you see instead?
Would be good to have method
com.xerox.amazonws.ec2.ImageDescription::getArchitecture()

What version of the product are you using? On what operating system?
v1.4

Please provide any additional information below.

Useful when publishing typica to a Maven repository:

  <target name="source-jar" depends="compile">
    <zip destfile="${typica.jar}/typica-sources.jar">
      <fileset dir="${typica.src}" />
      <fileset dir="${typica.generated}" />
    </zip>
  </target>

What steps will reproduce the problem?
1. Create a Jec2 Object with the Ject(String awsAccessId, String
awsSecretKey, boolean isSecure, String server) constructor.  I used
ec2-merlot.amazonaws.com as the server, isSecure=true.
2. Call ec2.runInstances() or ec2.describe*
3. Catch Exception.

What is the expected output? What do you see instead?
I expect a return value describing the call, but an exception is thrown

What version of the product are you using? On what operating system?
I have tried Versions 1.2, 1.1, and a build from trunk.  I have gotten this
to work on a 1.1.  I'm using a 64 Ubuntu Hardy box.

Please provide any additional information below.
The problem seams to spur from a change in AWSQueryConnection.  The
makeRequest method was changed to use Java URL for the http request after
v1.1 and it doesn't seem to like different server names.