Same for me. Just try again and that works
Em 08/07/2011 11:29, "Antonio" escreveu:
> Same issue for me today.
>
> On May 19, 12:27 am, simonc wrote:
>> Seems to have gone away overnight. I did nothing except go to sleep
>> at my end, and it now worked.
>>
>> On May 18, 6:20 am, simonc wrote:
>
Same issue for me today.
On May 19, 12:27 am, simonc wrote:
> Seems to have gone away overnight. I did nothing except go to sleep
> at my end, and it now worked.
>
> On May 18, 6:20 am, simonc wrote:
>
>
>
>
>
>
>
> > Any ideas? - see the deployment log below.
>
> > Basically I am trying to re-
Seems to have gone away overnight. I did nothing except go to sleep
at my end, and it now worked.
On May 18, 6:20 am, simonc wrote:
> Any ideas? - see the deployment log below.
>
> Basically I am trying to re-deploy my app - nothing special.
>
> I have tried running on versions 1.5.0.1 and 1.3.4
Facing the same problem (error 400).
Maybe I did the same super stupid error as you did.
What did you do ?
--
You received this message because you are subscribed to the Google Groups
"Google App Engine for Java" group.
To post to this group, send email to google-appengine-java@googlegroups.com.
Problem solved!
Super stupid mistake from my site.
On Nov 19, 9:30 am, Mike wrote:
> Thx for the response,
>
> but when the issue you mentioned appeared I have had the error 500
> message.
> After this was solved, I'm still having the same problem (client error
> - 400).
> Dont know what to do. I
Thx for the response,
but when the issue you mentioned appeared I have had the error 500
message.
After this was solved, I'm still having the same problem (client error
- 400).
Dont know what to do. In the forum I read it can happen if you havent
received an email which unlocks the account or some
Are you behind a proxy?
On 2 Set, 10:17, "f...@ncky" wrote:
> Hello,
> I try do deploy with eclipse and i have that message:
>
> Unable to update:
> java.net.ConnectException: Connection timed out: connect
> at java.net.PlainSocketImpl.socketConnect(Native Method)
> at java.net.Pl
Thanks Jerome, we're investigating...
On Wed, May 5, 2010 at 2:09 PM, Jerome wrote:
> Things are back up... We were completely down for 15 minutes following
> the end of the planned downtime.
>
> Jerome
>
> On May 5, 4:01 pm, Jerome wrote:
> > Max, the GAE team sent the notice that the maintena
Things are back up... We were completely down for 15 minutes following
the end of the planned downtime.
Jerome
On May 5, 4:01 pm, Jerome wrote:
> Max, the GAE team sent the notice that the maintenance has been
> completed, but our app is totally DOA now. Every single servlet or JSP
> just 500 wi
Max, the GAE team sent the notice that the maintenance has been
completed, but our app is totally DOA now. Every single servlet or JSP
just 500 with a:
Request was aborted after waiting too long to attempt to service your
request. This may happen sporadically when the App Engine serving
cluster is
Normally this error is transient and your app will deploy fine later.
On 6 Mar 2010, at 06:22, markanson wrote:
I am using Eclipse and I am repeatedly getting this error
Unable to update app: Version not ready. See the deployment...
I have tried changing the version number as well as changing
I am using Eclipse and I am repeatedly getting this error
Unable to update app: Version not ready. See the deployment...
I have tried changing the version number as well as changing the
Application ID. Even doing those things, I still get this error.
mark
On Feb 18, 2:45 pm, App Engine Team
w
Its a bug ... in your code. You update fields directly so no
persistence mechanism will have a chance of knowing that the field has
changed. Either annotate the class updating the field as
@PersistenceAware, or update using setters.
--
You received this message because you are subscribed to the G
Should we monitor this thread for updates ? or just try again and
etc ?
On Feb 18, 5:45 am, App Engine Team
wrote:
> This is a known issue resulting from today's schedule maintenance.
> We're currently working on a fix, but there is a work around that
> should work for most developers:
>
> 1. De
This is a known issue resulting from today's schedule maintenance.
We're currently working on a fix, but there is a work around that
should work for most developers:
1. Deploy your application as a new version. Please do not constantly
attempt to redeploy your app. Your app is already in the queue
Same problem here, tried many time and now my app isn't working at all
(I opened a separate thread)
On Feb 18, 4:48 am, John Patterson wrote:
> Jut keep trying... it happens at busy times.
>
> On 18 Feb 2010, at 09:43, Andrei wrote:
>
>
>
> > i am getting this now
> > Unable to update app: Versio
I have the same problem when trying to upload an application that
contains a jsp file that
uses JSTL to include a map. I've also ensured that the jdk is used,
and when I run the
upload in verbose mode I can see the jars that are included.
I can see a repackaged-appengine-jakarta-jstl-1.1.2.jar,
Can anybody reply to me on this, I am still facing this issue.
Thanks,
Muhammad Umair
On Dec 3, 5:32 pm, umair wrote:
> Does anybody have a solution to this problem, an immediate reply will
> be highly appreciated.
>
> Thanks,
> Muhammad Umair
>
> On Dec 3, 2:29 am, umair wrote:
>
> > I am gett
Does anybody have a solution to this problem, an immediate reply will
be highly appreciated.
Thanks,
Muhammad Umair
On Dec 3, 2:29 am, umair wrote:
> I am getting this error when deploying the youtube direct application
> to google app engine.
>
> Unable to update:
> com.google.appengine.tools.a
I solved my own problem. It turned out an empty in
security-constraint > web-resource-collection in my web.xml is causing
this error.
On Nov 19, 11:10 am, Leonard Siu wrote:
> I received the following error when I tried to deploy an application
> to google hosted appengine (GAE/J). Any idea w
20 matches
Mail list logo
