Is the error occuring before or after your code is called.

If its after could you use a synchroniser token, to ignore any duplicate


-----Original Message-----
From: Joe Pluta [mailto:joepluta@xxxxxxxxxxxxxxxxx] 
Sent: 07 December 2003 23:13
To: 'Web Enabling the AS400 / iSeries'
Subject: RE: [WEB400] Errors in WebSphere Express

> From: David Gibbs
> I'm not an expert in this stuff ... but perhaps the servlet isn't
> to receive input until the previous request has finished rendering ... 
> and you are clicking the button before it's finished?

It's the fact that I'm getting a double POST request.  I don't know if it's
the browser sending two requests or WAS burping, but two requests are being
passed to the servlet within milliseconds of one another.

This has to do with the parsePostData error, I think.  The timings are
perfect.  I get a POST request, a parsePostData error occurs way in the
bowels of WAS, and then I get another POST request, all within milliseconds.
It's as if WAS senses the error and tries to resend the data to me.

I'm going to try to ignore any request that doesn't have the right data.
That's probably not a valid fix long term, but it will test the proposition.


This is the Web Enabling the AS400 / iSeries (WEB400) mailing list To post a
message email: WEB400@xxxxxxxxxxxx To subscribe, unsubscribe, or change list
or email: WEB400-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives

For the latest on Bertram Books products and services and for up-to-the-minute 
book news visit

This e-mail and any attachments may contain information that is confidential 
and privileged and is solely for the use of the intended recipient. If you are 
not the intended recipient please notify the sender and delete this e-mail and 
any attachments immediately

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2022 by and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.