If it runs again then look at the logic where it's gotta decide whether this is
the initial call or if the job is already running and this is just a status
check. Is it looking at the request to figure that out? If so, and the
expected info isn't found, walk the data path to figure out where
I am attempting to implement a centralized session store to an existing
application using Spring Session (Redis) and Struts. I have everything
working on a basic level, but I am running into an issue when a Struts
Action uses ExecuteAndWait. The refresh attempts don't seem to pick up
the
2 matches
Mail list logo
