Hi all,
@Thomas: I will look into that, thank you. The way we generate our
pages in this framework, however, involves some interesting dynamic
generation of image URLs that are mounted within the application
itself. It ends up being a bit more complicated than just displaying
one string or another for the "src" attribute. Whether this is a good
practice on GAE is certainly up for debate, but I presume this
wouldn't help the frequent restart issue, correct? It just means that
fewer files would be able to trigger a restart?
@Tin: I'm not sure I understand what I will learn from this. From
what I understand, contextDestroyed() is never called so all I would
see is an additional log statement near GAE's loading request logging
line? I've never used a ServletContextListener, so perhaps it has
other features that I'm not aware of?
Thanks!
Jake
On Jun 7, 11:41 am, Tin <tin.c...@gmail.com> wrote:
> Hi Jack:
>
> I suggest that maybe you can write a ServletContextListener to monitor
> the web instance reloading issue, for our testing we just put a info
> logging in the contextInitialized(..) method:
>
> public void contextInitialized(ServletContextEvent evt) {
> log.info("Web context inited.");
>
> }
>
> And modify the DEFAULT logging level to INFO in the logging.properties
> file. If the web instance was reloaded, we could trace this in the
> logging messages.
--
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-appengine-java+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/google-appengine-java?hl=en.
