Component hangs when uploading large file to Globa - WeOnlyDo Discussion board

Component hangs when uploading large file to Globa (wodHttpDLX)

by Kyle Johnson, Thursday, March 15, 2007, 18:21 (6261 days ago)

When using the HttpDLX component to perform a PUT over an HTTPS connection, it hangs when uploading large files (somewhere in the neighborhood of 3MB) to a GlobalScape EFT HTTPS server. Now, this certainly could be related to a problem on the server side, but it seems to me that the component should at least time out instead of hanging.

After traipsing through some assembler, I found out the following information:
- The component seems to be held up in some infinite loop where it uses a Windows API call, PeekMessage(), to get new messages from the hidden socket window.
- It grabs a user-defined message, (WM_USER + 1, 401h), and does something with it.
- During the loop, a call is made to a Windows API call, PostMessage(), to post another message to the hidden window message queue (message ID: WM_USER + 1).
- It then goes back to the top of the loop and checks for another message, repeating the process.

Hopefully that helps. If you have any more questions for me (memory offsets of code chunks, etc.), please let me know.

Thanks!

Kyle Johnson

Re: Component hangs when uploading large file to G

by wodDamir, Thursday, March 15, 2007, 18:49 (6261 days ago) @ Kyle Johnson

Hi Kyle,

Does this happen only on this specific server? Could you try that on any other server? How big files are we talking about?

Also, what is your version of wodHttpDLX?

Could you prepare a sample which we could simply run on our side and duplicate the issue? You can send it to techsupport@weonlydo.com

Regards,
Damba

Re: Component hangs when uploading large file to G

by Kyle Johnson, Thursday, March 15, 2007, 19:14 (6261 days ago) @ wodDamir

Damir -

I tried performing the same thing on a local server and found that uploading a 3MB file worked properly, so it seems that there's a problem with that server specifically. Unfortunately, we don't own the server, but it's owned by one of our clients, so we will need their permission in order to attempt replication.

If I am able to get permission, I will send an email to tech support.

Kyle Johnson