Re: Struts 7.0.0 - JSP rendering is taking 3X time compare to struts 6.3.0.2

Kusal Kithul-Godage <[email protected]>
Newsgroups gmane.comp.jakarta.struts.devel
Message-ID <CAOG_=KwyqWz0g6RqapaiMyO5jxFcDsN6OcS_JGK686Be+3SJxA@mail.gmail.com>
Hi Dipak,

I don't believe the mailing lists support image attachments. Could you
try externally hosting them and linking them instead?

It would also be useful if you could additionally test with Struts
6.7.0 to further isolate when this potential regression may have been
introduced.

Kind regards,
Kusal


On Thu, Dec 26, 2024 at 11:31 PM Dipak Tank <[email protected]> wrote:
>
>
>
> ---------- Forwarded message ---------
> From: Dipak Tank <[email protected]>
> Date: Thu, Dec 26, 2024 at 12:34 PM
> Subject: Struts 7.0.0 - JSP rendering is taking 3X time compare to struts 6.3.0.2
> To: <[email protected]>
>
>
> Hi
>
> After upgrading to version 7.0.0, the JSP rendering time has significantly increased from around 500ms to approximately 1.5 seconds. Upon further investigation, it was discovered that the increase in time is primarily due to Ognl.getValue taking longer than it did in the previous version.
>
> Datadog Profiling screenshot:
>
>
>
>
> Sample JSP & Java Code as below:
>
>
>
>
> We have added following constant in struts.xml
>
> <constant name="struts.chaining.copyErrors" value="true" />
> <constant name="struts.chaining.copyMessages" value="true" />
> <constant name="struts.ui.checkbox.submitUnchecked" value="true"/>
> <constant name="struts.ognl.expressionMaxLength" value=""/>
> <constant name="struts.parameters.requireAnnotations" value="false"/>
> <constant name="struts.allowlist.enable" value="false"/>
> <constant name="struts.mapper.alwaysSelectFullNamespace" value="false"/>
> <constant name="struts.actionConfig.fallbackToEmptyNamespace" value="true"/>
>
> Can you please help with this ?
>
>
> --
> Thanks,
> Dipak Tank
>
>
> --
> Thanks,
> Dipak Tank
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.