I don't think your going crazy, I have been seeing the same thing too... I have an app that has been in production for about a year. Yes, there have been changes along the way, but it's been more or less rock-solid stable... except that the past few months I've seen occassional NPE's caused by incoming request parameters being null.
I have never been able to replicate this in test or development. It's not frequent, maybe 5-10 times per 50,000 requests, which is 5-10 times too many, but not too bad (I haven't been yelled at, let's put it that way :) ). But, it's been bugging me. I see it in similar places as you... Doing a database query, where the SQL is constructed based on incoming parameters, and they wind up being null, causing SQL exceptions. Because of the way the front-end works, it should be entirely impossible for a user to ever not submit these requests (you'll have to trust me on this... if it's not impossible, they'd have to go out of their way and try to do this). So, yes, I'm seeing the same thing. Also, it's been a number of Tomcat versions now, all in the 5.0.x branch. We're at 5.0.29 now. I've also seen some bizarre exceptions caused by session problems... Trying to set an attribute and it's telling me the session is invalid (IllegalStateException), except that the line of code DIRECTLY BEFORE THAT ONE verified that the session is valid! We are moving to WebSphere in the next few weeks, so I'll know pretty quickly if this is a Tomcat issue or not, but I strongly suspect it is (not meant as a knock, I absolutely adore Tomcat). -- Frank W. Zammetti Founder and Chief Software Architect Omnytex Technologies http://www.omnytex.com On Wed, December 22, 2004 3:51 pm, Roberto Rios said: > Hi, > > I know that my subject sounds crazy, but I'm going nuts... > > I have an application, 100% java (jsp 1.2 and servlet 2.3). This > application has more or less 1,5 years. So it is stable. I always used > tomcat as my web server (without apache because I don't have static html > to be served) with no problem. > > We are using TC 4.1.31, with J2SDK1.4.2_03 on a W2K/SP4 box (Xeon 3.0Ghz > with 2GB mem). > > At this time we had more or less 25 concurrent users. We were happy... > > Recently, another department in company started to use the application. > So now we have more or less 100 concurrent users. > > Since then the problems began raising. Most of then when we try to > insert/update data in database. Generally we receive errors telling that > we tried to insert null values into a not null field (BTW we are using > oracle 8.1.7 with JDBC - classes12.jar). > > My point is that application was working. Nothing changed (except the > number of users). So, I'm sure that the fields are being properly > filled. > > What I would like to ask you, is if someone has experienced this kind of > problem. I was wondering if tomcat could lost request parameters under > heavy traffic... > > I don't have any prove that it actually lost something. As I said, I'm > just wondering. Maybe the JDBC... > > Searching into the mailing list archive, I found a thread about > performance. I have changed the connector maxProcessors to 150 and also > add maxKeepAliveRequests="1" to it after reading it. Nothing change. > > Does someone has some advice? I know that my posting is vague, but I > don't where to look anymore... > > I was thinking about to do a tomcat upgrade (to 5.0.X). > > TIA, > > Bob > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
