7yes, it is becouse xdoclet version i'm using don't take it off. I'll
take it by hand and see if this is the problem...
Jules Gosnell wrote:
> AFAIK, Jetty is compliant.
>
> Is your webapp ? - this would cause it to use my new
> distributable session manager, which may be the problem.
>
> As
AFAIK, Jetty is compliant.
Is your webapp ? - this would cause it to use my new
distributable session manager, which may be the problem.
As a workaround increase the session-timeout.
If, after testing you are convinced that Jetty is at fault, take your
problem to [EMAIL PROTECTED] - I'm away
Jules Gosnell wrote:
> Emerson,
>
> I am confused.
>
> I'm assuming that you are talking about the session-timeout clause in
> your web.xml.
>
> The declaration controls the timeout on an HttpSession.
>
> From your message it looks like you are expecting it to have some
> direct effect u
Emerson,
I am confused.
I'm assuming that you are talking about the session-timeout clause in
your web.xml.
The declaration controls the timeout on an HttpSession.
From your message it looks like you are expecting it to have some
direct effect upon a State[ful/less]Session EJB.
These two
We got this problem since 3.0.0 version, so we went to jboss-tomcat version.
We have a session bean that takes a long time (more than 30 seconds) to
load test data from a text file. The struts action sets a bean with a
success message and sends to a jsp page. In jetty version the message
doesn
