deploy failures

[Nick Renny]

been getting constant deploy failures for the last week. No issues are
being reported on system status, but syncdb is the most common failure
point.

Is anyone else experiencing this behaviour? Is there a way to
mitigate? Is it a known issue?

[Robert Kluin]

If you are using Python, try deploying with appcfg.py using the -v (or
--verbose) option. Maybe that will get you enough information to
figure out the problem.

Robert

> --
> You received this message because you are subscribed to the Google Groups "Google App Engine" group.
> To post to this group, send email to google-a...@googlegroups.com.
> To unsubscribe from this group, send email to google-appengi...@googlegroups.com.
> For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.
>
>

[Erik Wilson]

I have also been getting constant deployment errors with Java
deployment for the past couple days, seems like something is funny on
the google side, don't think my connection is flaky:

Nov 9, 2010 7:18:59 AM
com.google.apphosting.utils.config.AbstractConfigXmlReader
getTopLevelNode
SEVERE: Received IOException parsing the input stream for /home/erik/
workspace/wikihop/war/WEB-INF/web.xml
java.net.ConnectException: Connection timed out
at java.net.PlainSocketImpl.socketConnect(Native Method)
...
SEVERE: Received exception processing /home/erik/workspace/wikihop/war/
WEB-INF/web.xml
com.google.apphosting.utils.config.AppEngineConfigException: Received
IOException parsing the input stream for /home/erik/workspace/wikihop/
war/WEB-INF/web.xml
at
com.google.apphosting.utils.config.AbstractConfigXmlReader.getTopLevelNode(AbstractConfigXmlReader.java:
210)
...
Bad configuration: Received IOException parsing the input stream for /
home/erik/workspace/wikihop/war/WEB-INF/web.xml
Caused by: Connection timed out

[Alexandru Farcaş]

I also receive this error : SEVERE: Received IOException parsing the
input stream for my_path/war/WEB_INF//web.xml)
I am using java sdk and Eclipse Helios.
After I restart the eclipse it's working ok.

[David Watson]

Also happening to me constantly when doing Java deployment via command-
line (automated deploy script). I'm getting about a 75% failure rate,
which is a gigantic time waster.

I don't know how Google can claim to have a reasonable system when
their deployment tools fail so much. This is really getting
ridiculous.

On Nov 9, 8:22 am, Alexandru Farcaş <alex.far...@expert-group.biz>
wrote:

[Martin Ceperley]

Don't know if this has anything to do with your problems, but my (python) deployments began failing recently because my error_handlers: page directive, defined in app.yaml, was pointing to an error page in a subdirectory. When I moved it up to the top-level directory it worked.  Filed a bug here: http://code.google.com/p/googleappengine/issues/detail?id=4032

[Stream18]

Exactly the same problem for me since yesterday. I'm using both
eclipse plugin and appcfg.

On Nov 9, 2:22 pm, Alexandru Farcaş <alex.far...@expert-group.biz>
wrote:

[culov]

I'm also getting this error. It's very frustrating because my app has
lots of modules and it takes 15 minutes to compile, so I end up
wasting 20 minutes before I receive an error.

[George Moschovitis]

I am getting a similar error, very frustrating...

-g.

On Nov 9, 2:47 pm, Erik <erik.e.wil...@gmail.com> wrote:

[Stream18]

I finally found the reason for this error. It is java.sun.com server
that is failing to serve the DTD file we reference in our web.xml. It
seems sun (now Oracle) servers for http are not serving well these
days, maybe it is related with Oracle migrating java web servers to
new platform.

I solved this problem referencing https://java.sun.com/dtd/web-app_2_3.dtd
(SSL secured version) instead of the original http://java.sun.com/dtd/web-app_2_3.dtd
in the web.xml file (DOCTYPE definition)

There is another possibility: you can use and reference a local copy
of this DTD file, see here how to do it:
http://stackoverflow.com/questions/4195022/local-copy-of-http-java-sun-com-dtd-web-app-2-3-dtd/4203934#4203934

Eduardo G.

On Nov 16, 8:23 am, George Moschovitis <george.moschovi...@gmail.com>
wrote:

[Jeff Schwartz]

The https version isn't available either. Attempts to reference it in the web.xml file abort with the following message:

Connection timed out: connect    web.xml

A temporary solution is to remove or comment out the reference to the dtd from the web.xml file until the issue is resolved which will permit you to deploy your application.

Perhaps some other organization should step up and take responsibility for caching this file as Oracle doesn't seem to be the benevolent Java steward one would have hoped it would be. Perhaps Google itself could cache this on one of their servers and refactor the GWT plugin to reference that.

I am growing increasingly weary of Oracle and their handling of Java. Makes me regret the day I ever thought they might be good for the language and I hope Google whoops their butt in court over the Android suit. And don't even get me started on their latest shenanigans with Apple over the JRE.

Jeff

--
You received this message because you are subscribed to the Google Groups "Google App Engine" group.
To post to this group, send email to google-a...@googlegroups.com.
To unsubscribe from this group, send email to google-appengi...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.

--
Jeff Schwartz

[Stream18]

Jeff,

I've come up to a better solution: just create a servlet 2.5 style
header for web.xml. To to that,
1. Remove these two lines from web.xml
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE web-app
PUBLIC "-//Sun Microsystems, Inc.//DTD Web Application 2.3//
EN"
"http://java.sun.com/dtd/web-app_2_3.dtd">
2. Replace the first line (<web-app>) with this one:
<web-app xmlns="http://java.sun.com/xml/ns/javaee"
version="2.5">

On Nov 17, 1:48 pm, Jeff Schwartz <jefftschwa...@gmail.com> wrote:
> The https version isn't available either. Attempts to reference it in the
> web.xml file abort with the following message:
>
> Connection timed out: connect    web.xml
>
> A temporary solution is to remove or comment out the reference to the dtd
> from the web.xml file until the issue is resolved which will permit you to
> deploy your application.
>
> Perhaps some other organization should step up and take responsibility for
> caching this file as Oracle doesn't seem to be the benevolent Java steward
> one would have hoped it would be. Perhaps Google itself could cache this on
> one of their servers and refactor the GWT plugin to reference that.
>
> I am growing increasingly weary of Oracle and their handling of Java. Makes
> me regret the day I ever thought they might be good for the language and I
> hope Google whoops their butt in court over the Android suit. And don't even
> get me started on their latest shenanigans with Apple over the JRE.
>
> Jeff
>
>
>
> On Wed, Nov 17, 2010 at 6:41 AM, Stream18 <strea...@gmail.com> wrote:
> > I finally found the reason for this error. It is java.sun.com server
> > that is failing to serve the DTD file we reference in our web.xml. It
> > seems sun (now Oracle) servers for http are not serving well these
> > days, maybe it is related with Oracle migrating java web servers to
> > new platform.
>

> > I solved this problem referencinghttps://java.sun.com/dtd/web-app_2_3.dtd

> > (SSL secured version) instead of the original
> >http://java.sun.com/dtd/web-app_2_3.dtd
> > in the web.xml file (DOCTYPE definition)
>
> > There is another possibility: you can use and reference a local copy
> > of this DTD file, see here how to do it:
>

> >http://stackoverflow.com/questions/4195022/local-copy-of-http-java-su...

> > google-appengi...@googlegroups.com<google-appengine%2Bunsu...@googlegroups.com>
> > .

> > For more options, visit this group at
> >http://groups.google.com/group/google-appengine?hl=en.
>
> --

> *Jeff Schwartz*

[Simon]

I take it that the workaround suggested by Ikai doesn't work?

https://groups.google.com/group/google-appengine-java/msg/7c07a57fffd3b776?hl=en

On Nov 17, 1:40 pm, Stream18 <strea...@gmail.com> wrote:
> Jeff,
>
> I've come up to a better solution: just create a servlet 2.5 style
> header for web.xml. To to that,
>    1. Remove these two lines from web.xml
>       <?xml version="1.0" encoding="UTF-8"?>
>       <!DOCTYPE web-app
>           PUBLIC "-//Sun Microsystems, Inc.//DTD Web Application 2.3//
> EN"
>           "http://java.sun.com/dtd/web-app_2_3.dtd">
>    2. Replace the first line (<web-app>) with this one:
>       <web-app xmlns="http://java.sun.com/xml/ns/javaee"
> version="2.5">
>
> On Nov 17, 1:48 pm, Jeff Schwartz <jefftschwa...@gmail.com> wrote:
>
> > The https version isn't available either. Attempts to reference it in the
> > web.xml file abort with the following message:
>
> > Connection timed out: connect    web.xml
>
> > A temporary solution is to remove or comment out the reference to the dtd
> > from the web.xml file until the issue is resolved which will permit you to

> >deployyour application.