thoughts???
On Jul 1, 1:13 pm, luijar wrote:
> Not sure what the problem is, all my queries are failing with this
> message:
>
> Illegal argument
> javax.jdo.JDOFatalUserException: Illegal argument at
> org.datanucleus.jdo.NucleusJDOHelper.getJDOExceptionForNu
(JDOQuery.java:252) at
Environment: SDK 1.3.4
JUnit = 4
Is there a code sample we can use as reference?, with all of the
required JAR files?. I haven't been able to run a single test that
requires accessing datastore.
On Jun 30, 5:58 pm, luijar wrote:
> I am seeing this however,
>
> Exec
I am seeing this however,
Executing a simple query:
Illegal argument
javax.jdo.JDOFatalUserException: Illegal argument at
org.datanucleus.jdo.NucleusJDOHelper.getJDOExceptionForNucleusException(NucleusJDOHelper.java:
344) at org.datanucleus.jdo.JDOQuery.execute(JDOQuery.java:252) at
This query
I was seeing the same thing, I am using JUnit4. I fixed that by doing:
TestSuite suite = new TestSuite();
suite.addTestSuite(MemcacheTest.class);
return new JUnitTestRun(suite);
On Jun 12, 11:57 pm, "Max Ross (Google)"
wrote:
> This most likely means that your tests aren't available as part o
8:55AM Pacific was the last error we saw. Basically, it was throwing
DeadlineExceededExceptions quickly all of the time.
On Apr 27, 12:11 pm, luijar wrote:
> We just experienced an outtage that seems to be from Google App Engine
> for one of our registered app ID's. It lasted for se
We just experienced an outtage that seems to be from Google App Engine
for one of our registered app ID's. It lasted for several hours and it
seems to be back up again without us making any changes. Has anyone
else experienced this? If so, what was the cause?
--
You received this message because
Ikai, is there any other reason (aside from energy consumption) that
instances will become idle after x amount of time? I've done some
scripted testing and I haven't seen a constant time for when
applications become idle, some blogs say 1 minute some say other
values, I saw a different value. Is th
Any idea what components of JEE6 are supported?
--
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-j...@googlegroups.com.
To unsubscribe from this group, send email to
google-appe
chnologies) is that I am also using
Spring AOP, which I suspect adds a lot of overhead to the mix.
On Mar 3, 5:18 pm, luijar wrote:
> Thanks Toby,
>
> Can you point me to the threads you talk about?
>
> Thanks,
> Luijar
>
> On Mar 2, 4:15 am, Toby wrote:
>
> &
Thanks Toby,
Can you point me to the threads you talk about?
Thanks,
Luijar
On Mar 2, 4:15 am, Toby wrote:
> Hi luijar,
>
> I had the same problem -but no time-out- and I got some better
> performance by removing all autowire and annotation-scan stuff and
> also by putting
Thanks for the advice, I'll try that.
On Mar 1, 2:31 pm, Rusty Wright wrote:
> Try using the old way with xml configuration for wiring your beans together.
> The word on the street is that Spring's component scanning takes a lot of
> time.
>
>
>
> luijar wrote:
me know if your
> issue was resolved or reduced by using the above fix.
>
> On Feb 20, 12:05 am, luijar wrote:
>
> > I believe my development environment was on 1.3.0. That might be
> > something to look at, although it seems that probably it's a very
> > s
artmann wrote:
> > > The problem is that the initialization of your app takes longer than 30
> > > seconds.
> > > Pinging your app doesn't help when the app is restarted due to
> > redeployment
> > > or maintenance, or when high traffic de
is that you need to keep your app alive by simulating activity
> on it. Or go the non Spring route.
>
> Thanks
>
> On Feb 16, 4:14 pm, luijar wrote:
>
> > Hello Google App Engine forum,
>
> > We have been seeing ever since we deployed our applications
> > (
Hello Google App Engine forum,
We have been seeing ever since we deployed our applications
(currently 3 of them) that when our application instances become idle
(they have not been hit for x amount of seconds) subsequent requests
return with a 500 response. Logs show a hard deadline exceeded err
I was able to find the problem. I am not sure why this would happen.
In my GWT code, I had a HashMap mapping a String to a Serializable.
Removing this mapping (changed Serializable to String) fixes the
problem. Not quite sure why this would happen. If anyone can shed some
light, please free feel t
I am beginning to see this problem when uploading my application to
the AppEngine. Here is the stack trace:
com.google.appengine.tools.admin.AdminException: Unable to update app:
Error writing to server
at com.google.appengine.tools.admin.AppAdminImpl.update
(AppAdminImpl.java:62)
at com.google.a
17 matches
Mail list logo
