Re: Request parameters getting lost

2004-04-13 Thread David Rees 
Frank W. Zammetti wrote, On 4/12/2004 4:50 PM:
So, my question is twofold... One, has anyone ever seen such an issue as
missing parameters before, and if so, what information can you share with me
about it?  Two, am I off my rocker to think that connector config is way out
of wack, and assuming it is, what suggestions would you guys have to fix it,
given the approximate load I've stated here?
Let me guess, you're using SSL, have keep-alive enabled, and are using 
MSIE with all the latest patches.  Right?

Turns out a patch released by MS around Feb 4 (KB832894) which causes 
MSIE to lose request parameters if the KeepAlive session expires, in 
other words, when the server drops the connection.

The fix is to either tell your users to use a different browser (like 
Mozilla) or to disable KeepAlive under SSL for all MSIE browsers.

See 
http://www.icdevgroup.org/pipermail/interchange-users/2004-February/037840.html

-Dave

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: Request parameters getting lost

2004-04-13 Thread Shapira, Yoav 

Hi,
Whatever the root cause of this issue is, your servlets should be
tolerant of these parameters not being specified, i.e. being null.  You
should never NPE in your own code due to improper input parameter
checking.

Yoav Shapira
Millennium Research Informatics


-Original Message-
From: Frank W. Zammetti [mailto:[EMAIL PROTECTED]
Sent: Monday, April 12, 2004 7:51 PM
To: [EMAIL PROTECTED]
Subject: Request parameters getting lost

I have a very odd situation...

I have an app running on Tomcat 5.0.1.8.  We're using it as both a web
server and servlet container.  What's happening is I'm getting
NullPointerExceptions in both JSP's and servlets that is a result of
request
parameters seemingly being lost somewhere along the way.  In other
words,
if
I submit a form to a servlet with a couple of fields, the parameters
are
not
showing up in the request object, hence I get NullPointerExceptions
trying
to access them.

This is an intermittent problem, in fact it's fairly rare (which has
saved
my a** at work thus far!), but I still have not been able to explain
it.
It
is happening at various points in my app, no consistent pattern that
I've
been able to discern, all of which should theoretically be impossible
to
have no parameters because the user is forced to enter things via
JavaScript, or clicking a button submits a hidden form, things like
that.
I've tried the best I can to get it to happen on my development
installation, but of course I've been unable to replicate it, but I
have
seen it on the production server so I know it's not just a stupid user
trick
(although I can't rule out them doing something stupid that I just
haven't
imagined).

I have a sneaking suspicion that it's a server tuning issue, and in
fact I
just did some reading and it looks like my predecessor in charge of
tuning
Tomcat really screwed up some things.  Here's his connector
configuration:

Connector
   allowTrace=true
   enableLookups=false
   redirectPort=8443
   secure=false
   acceptCount=100
   bufferSize=4096
   compression=off
   connectionLinger=-1
   connectionTimeout=6
   debug=0
   disableUploadTimeout=true
   maxHttpHeaderSize=8192
   maxKeepAliveRequests=200
   maxSpareThreads=175
   maxThreads=300
   minSpareThreads=100
   port=8181
   socketBuffer=12000
   tcpNoDelay=true
/

That looks incredibly wrong to me in terms of tuning.  The app has a
TOTAL
of 87 users, and not all of them are using the app at the same time,
and
the
requests are certainly not coming all at the same time.  I'm guessing
we're
talking about an average of maybe 20 concurrent requests at any given
time,
not a huge load by any stretch.

So, my question is twofold... One, has anyone ever seen such an issue
as
missing parameters before, and if so, what information can you share
with
me
about it?  Two, am I off my rocker to think that connector config is
way
out
of wack, and assuming it is, what suggestions would you guys have to
fix
it,
given the approximate load I've stated here?

Thanks in advance everyone!

Frank



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]




This e-mail, including any attachments, is a confidential business communication, and 
may contain information that is confidential, proprietary and/or privileged.  This 
e-mail is intended only for the individual(s) to whom it is addressed, and may not be 
saved, copied, printed, disclosed or used by anyone else.  If you are not the(an) 
intended recipient, please immediately delete this e-mail from your computer system 
and notify the sender.  Thank you.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: Request parameters getting lost

2004-04-13 Thread Allistair Crossley 
the only time i lost request parameters was because the form was multipart/form-data. 
In that case you need to use a form upload processer like commons FileUploader.

ADC

-Original Message-
From: Shapira, Yoav [mailto:[EMAIL PROTECTED]
Sent: 13 April 2004 13:49
To: Tomcat Users List
Subject: RE: Request parameters getting lost



Hi,
Whatever the root cause of this issue is, your servlets should be
tolerant of these parameters not being specified, i.e. being null.  You
should never NPE in your own code due to improper input parameter
checking.

Yoav Shapira
Millennium Research Informatics


-Original Message-
From: Frank W. Zammetti [mailto:[EMAIL PROTECTED]
Sent: Monday, April 12, 2004 7:51 PM
To: [EMAIL PROTECTED]
Subject: Request parameters getting lost

I have a very odd situation...

I have an app running on Tomcat 5.0.1.8.  We're using it as both a web
server and servlet container.  What's happening is I'm getting
NullPointerExceptions in both JSP's and servlets that is a result of
request
parameters seemingly being lost somewhere along the way.  In other
words,
if
I submit a form to a servlet with a couple of fields, the parameters
are
not
showing up in the request object, hence I get NullPointerExceptions
trying
to access them.

This is an intermittent problem, in fact it's fairly rare (which has
saved
my a** at work thus far!), but I still have not been able to explain
it.
It
is happening at various points in my app, no consistent pattern that
I've
been able to discern, all of which should theoretically be impossible
to
have no parameters because the user is forced to enter things via
JavaScript, or clicking a button submits a hidden form, things like
that.
I've tried the best I can to get it to happen on my development
installation, but of course I've been unable to replicate it, but I
have
seen it on the production server so I know it's not just a stupid user
trick
(although I can't rule out them doing something stupid that I just
haven't
imagined).

I have a sneaking suspicion that it's a server tuning issue, and in
fact I
just did some reading and it looks like my predecessor in charge of
tuning
Tomcat really screwed up some things.  Here's his connector
configuration:

Connector
   allowTrace=true
   enableLookups=false
   redirectPort=8443
   secure=false
   acceptCount=100
   bufferSize=4096
   compression=off
   connectionLinger=-1
   connectionTimeout=6
   debug=0
   disableUploadTimeout=true
   maxHttpHeaderSize=8192
   maxKeepAliveRequests=200
   maxSpareThreads=175
   maxThreads=300
   minSpareThreads=100
   port=8181
   socketBuffer=12000
   tcpNoDelay=true
/

That looks incredibly wrong to me in terms of tuning.  The app has a
TOTAL
of 87 users, and not all of them are using the app at the same time,
and
the
requests are certainly not coming all at the same time.  I'm guessing
we're
talking about an average of maybe 20 concurrent requests at any given
time,
not a huge load by any stretch.

So, my question is twofold... One, has anyone ever seen such an issue
as
missing parameters before, and if so, what information can you share
with
me
about it?  Two, am I off my rocker to think that connector config is
way
out
of wack, and assuming it is, what suggestions would you guys have to
fix
it,
given the approximate load I've stated here?

Thanks in advance everyone!

Frank



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]




This e-mail, including any attachments, is a confidential business communication, and 
may contain information that is confidential, proprietary and/or privileged.  This 
e-mail is intended only for the individual(s) to whom it is addressed, and may not be 
saved, copied, printed, disclosed or used by anyone else.  If you are not the(an) 
intended recipient, please immediately delete this e-mail from your computer system 
and notify the sender.  Thank you.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



FONT SIZE=1 FACE=VERDANA,ARIAL COLOR=BLUE 
---
QAS Ltd.
Developers of QuickAddress Software
a href=http://www.qas.com;www.qas.com/a
Registered in England: No 2582055
Registered in Australia: No 082 851 474
---
/FONT


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Request parameters getting lost

2004-04-13 Thread David Rees 
David Rees wrote:

 Let me guess, you're using SSL, have keep-alive enabled, and are using
 MSIE with all the latest patches.  Right?

 Turns out a patch released by MS around Feb 4 (KB832894) which causes
 MSIE to lose request parameters if the KeepAlive session expires, in
 other words, when the server drops the connection.

 The fix is to either tell your users to use a different browser (like
 Mozilla) or to disable KeepAlive under SSL for all MSIE browsers.

Looks like Microsoft released a patch today to fix the above bug.  See:
http://support.microsoft.com/default.aspx?kbid=831167

-Dave

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: Request parameters getting lost

2004-04-12 Thread Daniel Huang 
You mentioned you have javascript to enforce user to enter values. Have you
considered the possibility that user has disabled javascript from browser?
That way they will be able to submit a null value to the server.

Regards,
Daniel

-Original Message-
From: Frank W. Zammetti [mailto:[EMAIL PROTECTED]
Sent: Monday, April 12, 2004 4:51 PM
To: [EMAIL PROTECTED]
Subject: Request parameters getting lost

I have a very odd situation...

I have an app running on Tomcat 5.0.1.8.  We're using it as both a web
server and servlet container.  What's happening is I'm getting
NullPointerExceptions in both JSP's and servlets that is a result of request
parameters seemingly being lost somewhere along the way.  In other words, if
I submit a form to a servlet with a couple of fields, the parameters are not
showing up in the request object, hence I get NullPointerExceptions trying
to access them.

This is an intermittent problem, in fact it's fairly rare (which has saved
my a** at work thus far!), but I still have not been able to explain it.  It
is happening at various points in my app, no consistent pattern that I've
been able to discern, all of which should theoretically be impossible to
have no parameters because the user is forced to enter things via
JavaScript, or clicking a button submits a hidden form, things like that.
I've tried the best I can to get it to happen on my development
installation, but of course I've been unable to replicate it, but I have
seen it on the production server so I know it's not just a stupid user trick
(although I can't rule out them doing something stupid that I just haven't
imagined).

I have a sneaking suspicion that it's a server tuning issue, and in fact I
just did some reading and it looks like my predecessor in charge of tuning
Tomcat really screwed up some things.  Here's his connector configuration:

Connector
   allowTrace=true
   enableLookups=false
   redirectPort=8443
   secure=false
   acceptCount=100
   bufferSize=4096
   compression=off
   connectionLinger=-1
   connectionTimeout=6
   debug=0
   disableUploadTimeout=true
   maxHttpHeaderSize=8192
   maxKeepAliveRequests=200
   maxSpareThreads=175
   maxThreads=300
   minSpareThreads=100
   port=8181
   socketBuffer=12000
   tcpNoDelay=true
/

That looks incredibly wrong to me in terms of tuning.  The app has a TOTAL
of 87 users, and not all of them are using the app at the same time, and the
requests are certainly not coming all at the same time.  I'm guessing we're
talking about an average of maybe 20 concurrent requests at any given time,
not a huge load by any stretch.

So, my question is twofold... One, has anyone ever seen such an issue as
missing parameters before, and if so, what information can you share with me
about it?  Two, am I off my rocker to think that connector config is way out
of wack, and assuming it is, what suggestions would you guys have to fix it,
given the approximate load I've stated here?

Thanks in advance everyone!

Frank



-
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]

Re: Request parameters getting lost

2004-04-12 Thread QM 
On Mon, Apr 12, 2004 at 07:50:55PM -0400, Frank W. Zammetti wrote:
: So, my question is twofold... One, has anyone ever seen such an issue as
: missing parameters before, and if so, what information can you share with me
: about it?  Two, am I off my rocker to think that connector config is way out
: of wack, and assuming it is, what suggestions would you guys have to fix it,
: given the approximate load I've stated here?

The params may never reach Tomcat:

- do your end-users use a different browser than you?
- does the app rely on javascript to set any params?

See what I mean?

Maybe you could use a servlet filter, to track params as they enter the
container?  You mentioned this is an intermittent problem, though, so
you could burn a lot of log space in the hopes of tracking down the
bug...

-QM

-- 

software  -- http://www.brandxdev.net
tech news -- http://www.RoarNetworX.com


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Request Parameters Getting Lost

2000-11-10 Thread Stefan Woithe 

Hi Jason,

I use Tomcat 3.1final and in an JSP the implicit object "request". If you know the 
name of the parameter use request.getParameter(name). Where is the method 
"getRequestParameters()" located -- for sure not in javax.servlet.ServletRequest?

Regards

Stefan

 "Voegele, Jason" wrote:
 
 We've run across some problems using request parameters in our JSP.  We decided to 
create a JSP that does nothing but print out request parms and values, just to ensure 
that they are being passed with the request.
 
 We invoke the JSP like so:  http://localhost:8080/dwstatus?page_id=TEST_PAGE
 
 Our JSP simply prints out the value of the page_id parameter, and enumerates the 
names of all parameters sent.
 
 The value we get for the page_id parameter is always null.  There are no parameters 
present in the Enumeration returned by getRequestParameters().
 
 Can anyone explain what's happening to our request parameters?  We're using Tomcat 
standalone on Windows NT Server 4.0.
 
 Thanks,
 Jason Voegele

RE: Request Parameters Getting Lost

2000-11-10 Thread Keith McNeill 
Title: RE: Request Parameters Getting Lost



We've 
had the same problem dealing with wireless apps  WAP gateways. Our 
theory is that the request params are being sent in UTF-8 not ascii and Tomcat 
can't deal with it. We do not have any problems when using JRun or 
Websphere.

Keith 
McNeill
[EMAIL PROTECTED]

  -Original Message-From: Voegele, Jason 
  [mailto:[EMAIL PROTECTED]]Sent: Friday, November 10, 
  2000 1:14 PMTo: '[EMAIL PROTECTED]'Subject: 
  RE: Request Parameters Getting Lost
  My apologies, we're actually using 
  request.getParameter("page_id"), as well as the getParameterNames and 
  getParameterValues as you've said. I just wrote the wrong method name in 
  my original email.
  Given that we are using the proper methods, is there any way 
  to explain this behavior? 
  Thanks, Jason Voegele 
  -Original Message- From: CPC 
  Livelink Admin [mailto:[EMAIL PROTECTED]] 
  Sent: Friday, November 10, 2000 12:37 PM To: [EMAIL PROTECTED] Subject: RE: 
  Request Parameters Getting Lost 
  Actually, the functions are getParameterNames and 
  getParameterValues 
  -Original Message- From: 
  Stefan Woithe [mailto:[EMAIL PROTECTED]] 
  Sent: Friday, November 10, 2000 12:25 PM To: [EMAIL PROTECTED] Subject: Re: 
  Request Parameters Getting Lost 
  Hi Jason, 
  I use Tomcat 3.1final and in an JSP the implicit object 
  "request". If you know the name of the parameter use 
  request.getParameter(name). Where is the 
  method "getRequestParameters()" located -- for sure not in javax.servlet.ServletRequest? 
  Regards 
  Stefan 
   "Voegele, Jason" wrote:   We've run across some problems using 
  request parameters in our JSP. We decided to 
  create a JSP that does nothing but print out request parms and 
  values, just to ensure that they are being passed with the 
  request.   We invoke 
  the JSP like so: http://localhost:8080/dwstatus?page_id=TEST_PAGE 
Our JSP simply prints out 
  the value of the page_id parameter, and enumerates the 
  names of all parameters sent.   The value we get for the page_id parameter is always null. 
  There are no parameters present in the Enumeration 
  returned by getRequestParameters().  
   Can anyone explain what's happening to our request 
  parameters? We're using Tomcat standalone on 
  Windows NT Server 4.0.   Thanks,  Jason Voegele

RE: Request Parameters Getting Lost

2000-11-10 Thread Voegele, Jason 
Title: RE: Request Parameters Getting Lost



Thanks 
for the pointer. We're accessing the JSP with IE 5.5, which has an option 
to send URLs as UTF-8. I turned this option off, but alas the request 
parameters are still not there. Any further advice?

Thanks,
Jason 
Voegele


  -Original Message-From: Keith McNeill 
  [mailto:[EMAIL PROTECTED]]Sent: Friday, November 10, 2000 2:54 
  PMTo: [EMAIL PROTECTED]Cc: 
  [EMAIL PROTECTED]Subject: RE: Request Parameters 
  Getting Lost
  We've had the same problem dealing with wireless apps 
   WAP gateways. Our theory is that the request params are being sent 
  in UTF-8 not ascii and Tomcat can't deal with it. We do not have any 
  problems when using JRun or Websphere.
  
  Keith McNeill
  [EMAIL PROTECTED]
  
-Original Message-From: Voegele, Jason 
[mailto:[EMAIL PROTECTED]]Sent: Friday, November 10, 
2000 1:14 PMTo: 
'[EMAIL PROTECTED]'Subject: RE: Request Parameters 
Getting Lost
My apologies, we're actually using 
request.getParameter("page_id"), as well as the getParameterNames and 
getParameterValues as you've said. I just wrote the wrong method name 
in my original email.
Given that we are using the proper methods, is there any way 
to explain this behavior? 
Thanks, Jason Voegele 

-Original Message- From: CPC 
Livelink Admin [mailto:[EMAIL PROTECTED]] 
Sent: Friday, November 10, 2000 12:37 PM To: [EMAIL PROTECTED] Subject: 
RE: Request Parameters Getting Lost 
Actually, the functions are getParameterNames and 
getParameterValues 
-Original Message- From: 
Stefan Woithe [mailto:[EMAIL PROTECTED]] 
Sent: Friday, November 10, 2000 12:25 PM To: [EMAIL PROTECTED] Subject: 
Re: Request Parameters Getting Lost 
Hi Jason, 
I use Tomcat 3.1final and in an JSP the implicit object 
"request". If you know the name of the parameter use 
request.getParameter(name). Where is the 
method "getRequestParameters()" located -- for sure not in javax.servlet.ServletRequest? 
Regards 
Stefan 
 "Voegele, Jason" wrote:   We've run across some problems 
using request parameters in our JSP. We decided to create a JSP that does nothing but print out request parms 
and values, just to ensure that they are being 
passed with the request.   We invoke the JSP like so: http://localhost:8080/dwstatus?page_id=TEST_PAGE 
  Our JSP simply prints out 
the value of the page_id parameter, and enumerates 
the names of all parameters sent.  
 The value we get for the page_id parameter is always 
null. There are no parameters present in the 
Enumeration returned by getRequestParameters().   Can anyone explain what's happening 
to our request parameters? We're using Tomcat 
standalone on Windows NT Server 4.0.  
 Thanks,  Jason 
Voegele