Experiencing Upload Problems

[xscottehx]

On our server we have many file uploads per day however whenever a user uploads a document they get a webspeed error or the page fails to load. However when checked the documents have uploaded perfectly and there are no messages in the log file. This has only recently started happening but i cannot trace back to when. Is this a problem with progress as my code has not changed?

Any feedback would be appreciated

 

[Cecil]

What is the webspeed Error message?
Are the WebSpeed agents crashing and automatically restarting?
Are the files being uploaded particularly big?
Can you reproduce the error/problem in a testing environment?
Oh and the big question is What version of OpenEdge+Service Packs are you using, plus Windows or Linux?

 

[xscottehx]

What is the webspeed Error message?

WebSpeed error from messenger process (6019)
WebSpeed Agent Error: OCTO error receiving page from Agent = % (6532)

Are the WebSpeed agents crashing and automatically restarting?

Not crashing or locking ... nothing written to broker or server log files to say there has been a problem.

Are the files being uploaded particularly big?

Only effecting binary files. Can load 4Mb .csv without problems but failed with a 700K jpg

Can you reproduce the error/problem in a testing environment?

Yep. On our dev system we have 3 agents running and roughly 50% of requests fail when re-posting the same form using F5

Oh and the big question is What version of OpenEdge+Service Packs are you using, plus Windows or Linux?

10.2b 64bit enterprise service pack 01
Redhat Openserver 5 64bit with all the latest package updates applied.

 

[Cecil]

I guessing you have Already checked the Progress KB. If not here is one possible solution:
Status: Unverified

FACT(s) (Environment):

OpenEdge 10.x

SYMPTOM(s):

Errors 6019 and 6532 displays on the browser intermittently

WebSpeed error from messenger process (6019)

WebSpeed Agent Error: OCTO error receiving page from Agent = % (6532)

WebSpeed Agent Error: OCTO error receiving page from Agent
=<errorcode> (6532)

The error is apparent when the request is served by the first agent on
the WebSpeed broker status list

The WebSpeed agents port range is set to default from 3202 to 3502

CAUSE:

The exact cause is unknown at this time of this writing

FIX:

Change the srvrMinPort to a higher number then 3202 but lower then the
srvrMaxport number and restart the broker.

 

[xscottehx]

Hi Cecil,

We do not currently use the standard ports anyway.

Thanks for your help though. Back to the drawing board

 

[chrisadam2]

Users in several dozen metro areas scattered across the country, including Boston, New York City, Washington DC, Houston, Phoenix, Las Vegas, and Seattle among others, have reported the issue. The issue does not appear to be nationwide, however, as users in a number of locations including Atlanta, Richmond, and Raleigh, as well as some customers even in markets where other users are affected, are not experiencing slow upload speeds.

_________________________________________________________

Want to get-on Google's first page and loads of traffic to your website? Hire a SEO Specialist from Ocean Groups seo pecialist

 

[Cecil]

Hi Cecil,

We do not currently use the standard ports anyway.

Thanks for your help though. Back to the drawing board

Are you doing any post-processing of the file after it has been received? I.E. if a JPEG file has been uploaded and it's creating a thumbnail image using something like ImageMagick?

Or, storing the the binary/text information into a LOB field on the database. From my testing/development if the database structure is not correctly configured right it can take time for the blob to be saved into the database.

The reason I ask is because I was having similar problem where I was doing some post processing on an uploaded file and it was taking too long to process and the browser/messenger was timing out. All because I was not sending any information back down the wire to the browser/messenger in a expect reasonable time.

Also I've noted that pressing the F5 (refresh) key can also cause problems because the form is being re-submitted for the nth time. If the the first form submission is processing the first file uploaded and you re-submit the same file by pressing the F5 key. You could potentially end up with two (or more) WebSpeed Agents running a posted process on the exactly the same file. This might be causing you problems.

But since I don't know how you are handling each web request I'm only guessing.

Is it possible to have a high-level step-by-step process flow of what happens when the a user submits a form from the browser and what happens to that web request on the server.

I quite keen on helping you resolve your problem.

Also using Firefox (with Firebug add-on) it also possible to monitor each form submissions, check to see no other conflicting web requests could be screwing thing up like AJAX request.