Your post may have given me an idea, but the root cause isn't what you think. We always use a REST framework for all our services (the latest version of Jersey currently), so I am 100% certain an unexpected application level exception results in a 500 error and the stacktrace is logged by an Exception handler in Jersey. We never see anything in the logs except for the process death error when this happens.
It stands to reason that maybe an exception is being thrown in the Jersey layer before it reaches the HTTP layer, and somehow nothing is logged in this case. I'll investigate options with Jersey. Maybe there's a thread pool that needs reconfiguring or something. -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/google-appengine. To view this discussion on the web visit https://groups.google.com/d/msgid/google-appengine/2d928357-c828-43ab-a365-1d28e3566fde%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
