Re: 6.0.24 Pid [file] Problem

2010-03-10 Thread Christopher Schultz
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Emerson, On 3/10/2010 4:59 AM, emerson cargnin wrote: > We have a wrapper script that is in charge of starting and stopping tomcat. > > Since we moved from 6.0.20 to 6.0.24 we started to get a few issues > with the pid not been removed properly makin

Re: 6.0.24 Pid Problem

2010-03-10 Thread emerson cargnin
That is an script we use for a while already, as after restarting, there is a one or two things that need to be done. The thing is that the wrapper worked before until 6.0.20. It was on 6.0.24 that the pid started to be left after stop. It seems like tomcat is taking longer to stop, and the standa

Re: 6.0.24 Pid Problem

2010-03-10 Thread Pid
On 10/03/2010 09:59, emerson cargnin wrote: We have a wrapper script that is in charge of starting and stopping tomcat. Since we moved from 6.0.20 to 6.0.24 we started to get a few issues with the pid not been removed properly making the start script to fail and never starting tomcat. I know of

Re: 6.0.24 SSL Session always New

2010-02-21 Thread Christopher Schultz
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Iain, On 2/19/2010 1:45 PM, iainmac wrote: >> 1. When do you set the "userName" attribute in the session? >> On validation of the user. Do you mean "identification" or the user (that is, somehow they enter their username without attempting to authent

Re: 6.0.24 SSL Session always New

2010-02-20 Thread André Warnier
iainmac wrote: 3. This page is made up of a parent frame and 2 sub-frames. 4. The parent frame (the named page that the redirect is to) does that check above i.e. tries to get the Username from the session object- This works successfully. This page begins to load. 5. The first sub-frame begins

Re: 6.0.24 SSL Session always New

2010-02-19 Thread iainmac
Hi yes you are right, but I add it when I get a new validated session, so it should be there, in effect for my code, it's he same thing. This worked fine for all browsers with 5.0.28, stopped working for all but MSIE from 6.0.20. I think its a change as mentioned by the other kind respondent, al

Re: 6.0.24 SSL Session always New

2010-02-19 Thread iainmac
Thanks I think it must be something to do with that. Eric Lenio-5 wrote: > > On Fri, Feb 19, 2010 at 12:02:18PM +, iainmac wrote: >> >> Hi, >> >> I have just moved from 5.0.18 to 6.0.24 using JSSE for SSL. >> >> I have a web application that checks for a current session, and if there >> i

Re: 6.0.24 SSL Session always New

2010-02-19 Thread iainmac
Christopher Schultz-2 wrote: > > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > Iain, > > On 2/19/2010 7:02 AM, iainmac wrote: >> I have just moved from 5.0.18 to 6.0.24 using JSSE for SSL. >> >> I have a web application that checks for a current session, and if there >> isn't one it se

Re: 6.0.24 SSL Session always New

2010-02-19 Thread Christopher Schultz
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Iain, On 2/19/2010 7:02 AM, iainmac wrote: > I have just moved from 5.0.18 to 6.0.24 using JSSE for SSL. > > I have a web application that checks for a current session, and if there > isn't one it sends the user to a login screen. This is working fi

Re: 6.0.24 SSL Session always New

2010-02-19 Thread Eric Lenio
On Fri, Feb 19, 2010 at 12:02:18PM +, iainmac wrote: > > Hi, > > I have just moved from 5.0.18 to 6.0.24 using JSSE for SSL. > > I have a web application that checks for a current session, and if there > isn't one it sends the user to a login screen. This is working fine from > Explorer as

Re: 6.0.24 SSL Session always New

2010-02-19 Thread André Warnier
iainmac wrote: Hi, I have just moved from 5.0.18 to 6.0.24 using JSSE for SSL. I have a web application that checks for a current session, and if there isn't one it sends the user to a login screen. This is working fine from Explorer as it did before in the previous version of Tomcat, but it k

Re: 6.0.24

2010-01-22 Thread Konstantin Kolinko
2010/1/22 Pid : > Just a quick FYI > > Looks like there's some errors on the mirrors at the moment. > I got a couple of 404s and a 500 from different servers. > It might happen, though according to the mirror status monitor page, most mirrors are up-to-date and running. http://www.apache.org/mirr