Thats interesting. In our case the cron is not even getting trigerred :( Is
there anything we have to do other that updating the capabilities.xml and
writing a update servlet?
<w:crons>
<w:cron path="/_wave/robot/fetchupdate" timerinseconds="10" />
</w:crons>
I have some log statements in the update servlet and I never see them on my
dashboard. Have tried all sorts of debugging and my brain is fried now :(
Google?
thanks
On Mon, Sep 21, 2009 at 1:09 AM, Thomas Beverley <
[email protected]> wrote:
>
> from what I can tell it appears to be a global issue-- hence tweety
> isn't working. However my crons jobs do get called. They just fail to
> update the wave. For example if I had the code...
>
>
> if (bundle.getEvents().size() == 0) {
> bundle.getWavelet(waveId, waveletId).appendBlip().getDocument
> ().append("testing 123");
> count++;
> }
>
> that fires on a cron event. Count would be incremented, but
> "testing123" would not be posted to the wave. I have submitted an
> issue to google but have heard no word back yet...
>
> http://code.google.com/p/google-wave-resources/issues/detail?id=205&start=100
>
> On Sep 20, 10:33 am, HP <[email protected]> wrote:
> > Cron job is not getting started at all for us also. Is it a global
> > issue that everyone is facing or is there something wrong with our
> > configuration?
> >
> > Here is the capabilities.xml
> >
> > <w:crons>
> > <w:cron path="/_wave/robot/fetchupdate" timerinseconds="10" />
> > </w:crons>
> >
> > and web.xml
> >
> > <servlet>
> > <servlet-name>update</servlet-name>
> > <servlet-class>com.google.wave.poppy.PoppyUpdateServlet</servlet-
> > class>
> > </servlet>
> > <servlet-mapping>
> > <servlet-name>update</servlet-name>
> > <url-pattern>/_wave/robot/fetchupdate</url-pattern>
> > </servlet-mapping>
> >
> > Thanks.
> > On Sep 17, 2:00 am, Thomas Beverley <[email protected]>
> > wrote:
> >
> >
> >
> > > Tweety is non-responsive. It relies oncronjobs. Perhaps this is a
> > > bug seeing that it effects the google robots too. Most of their
> > > gadgets were well prepared for the update...
> >
> > > On Sep 17, 9:55 am, Thomas Beverley <[email protected]>
> > > wrote:
> >
> > > > Yep.Cronjobs broken. Two of mine have gone down in flames!
> >
> > > > Wave Live Messenger and Rssybot both rely oncronjobs, were working a-
> > > > ok yesterday afternoon and are now failing to retrieve updates. No
> fix
> > > > as yet however when I find one I will update the thread!
> >
> > > > On Sep 16, 8:18 pm, Piers Finlayson <[email protected]> wrote:
> >
> > > > > Hi,
> >
> > > > > I assume the upgrade has happened and is now complete. Cronjobs
> now
> > > > > seem to be broken:
> >
> > > > > - My robot registers (capabilities.xml) for acronnotification
> every
> > > > > 5s.
> > > > > - I see in appengine that it's now actually getting called every
> > > > > 40ms.
> > > > > - Although my robot isn't throwing an exception, when it posts a
> new
> > > > > blip (when called by acronjob) this isn't appearing in the wave.
> > > > > I've tried old waves (pre upgrade) and new waves (post upgrade).
> >
> > > > > Can anyone else confirm/deny this is happening for them?
> >
> > > > > Piers
> >
>
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Google Wave API" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/google-wave-api?hl=en
-~----------~----~----~----~------~----~------~--~---
