datatonic / typica

Automatically exported from code.google.com/p/typica
0 stars 0 forks source link

{Fatal Error }: [1:1] #127

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago
Hi This is pawan , I am getting this following problem while trying to run 
Typica.Tutorial in eclipse 

can any one knows that what mistake made output like this . if anyone knows 
please tell me it helps me allot... 

log4j:WARN No appenders could be found for logger 
(org.apache.http.impl.conn.tsccm.ThreadSafeClientConnManager).
log4j:WARN Please initialize the log4j system properly.
log4j:WARN See http://logging.apache.org/log4j/1.2/faq.html#noconfig for more 
info.
[Fatal Error] :1:1: Content is not allowed in prolog.
[Fatal Error] :1:1: Content is not allowed in prolog.
[Fatal Error] :1:1: Content is not allowed in prolog.
[Fatal Error] :1:1: Content is not allowed in prolog.
[Fatal Error] :1:1: Content is not allowed in prolog.
[Fatal Error] :1:1: Content is not allowed in prolog.
Exception in thread "main" com.xerox.amazonws.ec2.EC2Exception: Number of 
retries exceeded : DescribeAvailabilityZones
    at com.xerox.amazonws.ec2.Jec2.makeRequestInt(Jec2.java:2369)
    at com.xerox.amazonws.ec2.Jec2.describeAvailabilityZones(Jec2.java:1421)
    at Ex7.availZone(Ex7.java:51)
    at Ex7.main(Ex7.java:28)
Caused by: org.apache.http.HttpException: Number of retries exceeded : 
DescribeAvailabilityZones
    at com.xerox.amazonws.common.AWSQueryConnection.makeRequest(AWSQueryConnection.java:508)
    at com.xerox.amazonws.ec2.Jec2.makeRequestInt(Jec2.java:2357)
    ... 3 more
Caused by: com.xerox.amazonws.common.AWSException: Couldn't parse error 
response!
    at com.xerox.amazonws.common.AWSQueryConnection.createException(AWSQueryConnection.java:729)
    at com.xerox.amazonws.common.AWSQueryConnection.makeRequest(AWSQueryConnection.java:503)
What version of the product are you using? On what operating system?

Node{ System }  Architecture is 

Hypervisor -- xen 
Middleware -- Eucalyptus { Open Source }

Original issue reported on code.google.com by aravapal...@gmail.com on 23 Aug 2011 at 8:59