# How to see facelet template errors?

**URL:** <https://forum.payara.fish/t/how-to-see-facelet-template-errors/1806>\
**Category:** Technical Discussion\
**Created:** [August 14, 2026, 3:31pm UTC](https://forum.payara.fish/t/how-to-see-facelet-template-errors/1806 "2026-08-14T15:31:19Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![rdelaplante](https://avatars.discourse-cdn.com/v4/letter/r/bc8723/32.png) [@rdelaplante](https://forum.payara.fish/u/rdelaplante)\
**Post date:** [August 14, 2026, 3:31pm UTC](https://forum.payara.fish/t/how-to-see-facelet-template-errors/1806/1 "2026-08-14T15:31:19Z")

</div>

I’m using JSF on Payara 7. When there is something wrong with a facelet template such as a syntax error or an issue with EL, I used to see a stack dump in Payara’s server.log. I’m not sure when this changed, but I no longer see that or any useful information about the error other than an HTTP 500 response.

I’ve tried setting jakarta.faces.PROJECT\_STAGE to Development in web.xml and also changing the log level of javax.enterprise.resource.webcontainer.jsf.facelets to FINE but still get no error details. Yes I redeployed and also restarted Payara. For now I have to delete chunks of my template until I the page renders again, then try to figure out what’s wrong. Sometimes there is nothing obviously wrong and I wish Payara would just show the error detail in the log.

Can anyone please help get facelet template error details to show in the server.log or on screen since the PROJECT\_STAGE is Development?

---

<div class="post-metadata">

**Author:** ![rdelaplante](https://avatars.discourse-cdn.com/v4/letter/r/bc8723/32.png) [@rdelaplante](https://forum.payara.fish/u/rdelaplante)\
**Post date:** [August 18, 2026, 2:16pm UTC](https://forum.payara.fish/t/how-to-see-facelet-template-errors/1806/2 "2026-08-18T14:16:34Z")

</div>

I opened a bug report:

> <https://github.com/payara/Payara/issues/8355>
>
> \### Brief Summary
> 
> I've been using GlassFish/Payara since it was Sun Java System… Application Server. While working with JSF templates, if there was invalid XHTML such as \<br\> instead of \<br/\>, a tag namespace wasn't defined, a tag syntax error, EL expression error, etc. I would be able to diagnose the problem by looking in server.log to see a stack dump with the exact error details. I'm not sure when that changed, but I no longer get any helpful information when there is something wrong with a template, only an HTTP 500 response with no content. Nothing in server.log. 
> 
> I tried setting jakarta.faces.PROJECT\_STAGE to Development in web.xml as well as changing log levels of JSF related namespaces to FINE - which shouldn't be necessary for errors. The only way I can diagnose these issues is by removing chunks of HTML from my templates and reloading until I eventually narrow it down to a specific tag. Then I have to guess about what might be wrong until I find the solution.
> 
> I'm using Payara 7.2026.7, but this has been an issue for a long time.
> 
> \### Expected Outcome
> 
> When there is a facelet template error, the stack dump or at least an error message should be written to server.log
> 
> \### Current Outcome
> 
> When there is a facelet error, I get an HTTP 500 response with no body and nothing is written to server.log
> 
> \### Reproducer
> 
> Add invalid XHTML to a template such as \<br\> with no closing tag. This will reproduce the issue. Then add the closing tag \<br/\> and try again. The page will now render.
> 
> \### Operating System
> 
> Windows 11 Pro
> 
> \### JDK Version
> 
> Temurin-21.0.11+10
> 
> \### Payara Distribution
> 
> Payara Server Full Profile