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 <distributable/> ? - 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 for a few days, but > someone there will pick it up for you. > > Good luck, > > > Jules > > > Emerson Cargnin - SICREDI Servi�os wrote: > >> >> >> Jules Gosnell wrote: >> >>> Emerson, >>> >>> I am confused. >>> >>> I'm assuming that you are talking about the session-timeout clause in >>> your web.xml. >>> >>> The <session-timeout/> 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. >> >> >> >> sorry, i didn't mean that, i just was telling the context. >> >>> >>> These two types of Session are very different components - one >>> belonging to the the web-tier and the other the ejb-tier. >>> >>> Perhaps I am missing some indirect connection between your >>> HttpSession and your Session EJB ? >> >> >> >> The problem is that the sessionbean takes a long time to proccess the >> request. And in the way back (after 30.. seconds) it looses the >> javabean (not ejb) in the session : ) >> >>> >>> Perhaps you are not talking about a Session EJB at all ? >>> >>> >>> Please clarify, >> >> >> >>> >>> Jules >>> >>> >>> from the servlet spec DTD : >>> >>> <!-- The session-timeout element defines the default session timeout >>> interval for all sessions created in this web application. The >>> specified timeout must be expressed in a whole number of minutes. --> >>> >>> <!ELEMENT session-timeout (#PCDATA)> >>> >>> >>> >>> Emerson Cargnin - SICREDI Servi�os wrote: >>> >>>> 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't appear (in 3.0.1 tomcat version it >>>> does). It didn't in tomcat too, so we put the >>>> <session-config><session-timeout>30</session-timeout></session-config> >>>> tag. But in jetty it doesn't works. Would Jetty getting 30 as 30 >>>> seconds???? if i'm not crazy, the unit is in minutes, isn't? but in >>>> tomcat it works.... >>>> >>>> >>> >>> >>> >>> >>> >>> ------------------------------------------------------- >>> This sf.net email is sponsored by: OSDN - Tired of that same old >>> cell phone? Get a new here for FREE! >>> https://www.inphonic.com/r.asp?r=sourceforge1&refcode1=vs3390 >>> _______________________________________________ >>> JBoss-user mailing list >>> [EMAIL PROTECTED] >>> https://lists.sourceforge.net/lists/listinfo/jboss-user >>> >>> >> >> > > > > > > ------------------------------------------------------- > This sf.net email is sponsored by: OSDN - Tired of that same old > cell phone? Get a new here for FREE! > https://www.inphonic.com/r.asp?r=sourceforge1&refcode1=vs3390 > _______________________________________________ > JBoss-user mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/jboss-user > > -- Emerson Cargnin SICREDI - Tel : 3358-4860 ------------------------------------------------------- This sf.net email is sponsored by: OSDN - Tired of that same old cell phone? Get a new here for FREE! https://www.inphonic.com/r.asp?r=sourceforge1&refcode1=vs3390 _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
