Whoever caused this regression, please fix it ASAP. It does not look
good that the error page points user to non-existent logs and even worse
does not tell user about GlassFish.
Sahoo
Sahoo wrote:
> Is this an after effect of any recent change? While accessing a
> servlet, I got "HTTP Status 500" and the page contained the following
> line:
>
> *note The full stack traces of the exception and its root causes are
> available in the Grizzly logs.*
>
> Why is it saying Grizzly logs instead of GlassFish logs?
>
> Thanks,
> Sahoo
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe_at_glassfish.dev.java.net
> For additional commands, e-mail: dev-help_at_glassfish.dev.java.net
>