Hi Adam,
I don't think a blank artifact can replicate the issue, in
our app action consist of many spring beans dependency and so on. As i said
this is happening only while first time a page loads from a web context,
later on any pages from the same web context loads normal. I guess struts
is doing some warming up wrt spring bean injection or something similar.
On Thu, Jul 21, 2016 at 2:45 AM, Adam Brin <ab...@digitalantiquity.org>
wrote:
> Hi,
> Have you tried this on a blank artifact? Seems like it might be a local
> configuration issue as opposed to a struts issue. If the former, addressing
> it might depend on your own initialization sequence and perhaps setting up
> your own Servlet init method
>
>
> > On Jul 20, 2016, at 1:46 PM, Sreekanth S. Nair <
> sreekanth.n...@egovernments.org> wrote:
> >
> > It seems like struts2 takes very long time while loading page for the
> first
> > time within a webcontext, this will definitely save deployment time but
> > result in less responsive for enduser for the first time. I guess this is
> > struts's default behavior, is there anyway we can instruct struts2 to
> load
> > in advance, like at deployment time itself ?
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: user-unsubscr...@struts.apache.org
> For additional commands, e-mail: user-h...@struts.apache.org
>
>
