Comments by MikeTheDebugger

MikeTheDebugger 16-Aug-13 14:44pm View

Resetting the Internet Settings seems to have fixed the issue, client hasn't experienced any failure since.

MikeTheDebugger 23-Jul-13 16:38pm View

Thank you very much for all the help! I couldn't have done this without hearing your explaination of just what's going on with the code & events and your suggestions! You said you may write something about this and/or do some further testing, I would be interested in hearing about whatever you come up with. Let me know! Cheers again!

MikeTheDebugger 23-Jul-13 12:07pm View

I posted something that I am working on as a solution.

MikeTheDebugger 22-Jul-13 11:57am View

I don't but I might be able to change that. I feel like that would probably solve everything. It was brought up in a meeting but someone shut that down. "They wouldn't go for that" or something. I don't know if he was refering to the Web Service Admin guys or what (???). When this was originally written, it wasn't meant to update a substantial number of tasks but things have changed.

MikeTheDebugger 22-Jul-13 11:23am View

I've posted the code below. Taking the event creation out didn't seem to make any difference :(

MikeTheDebugger 21-Jul-13 16:33pm View

I'll try these things when I'm back at work tomorrow.

I should add that I did not write this code. It was created by a contractor whom is no longer available for answering questions.

The AssignCrewAsync(task, guid) method (which is a call to the proxy invoke async method) is called in a foreach loop which loops through a list of tasks to change. Right before this a completed method + event is set up.

foreach(AssignCrewTask task in TaskList){
.....
AssignCrewComplete += AssignCrewCompleteEvent; (I know this line probably looks wrong but I'm just going off of memory)
AssignCrewAsync(task, this.userstate);
.....
}

Is there a more correct way of doing this? I'll post the actual code here tomorrow.

Threading limit makes sense... I believe the call + loop combo will try to create 2000+ threads which seems a little excessive.

MikeTheDebugger 19-Jul-13 18:29pm View

Yeah we're definitely on the same page :) I have a question about Fiddler: it seems to only capture about 440ish packets during my BeginInvoke (it starts failing after about 500-600). I might get some other activity captured but I no longer get anything from the application. The rest of the BeginInvokes do not show up and nothing from EndInvoke. I can't seem to find any limits on it... seems really odd. Otherwise, it looks really clean compared to Wireshark, I'll definitely be using Fiddler again.

MikeTheDebugger 19-Jul-13 15:10pm View

I believe I understand what you are saying... I am just calling one method that is in the proxy class and passing in a task and an ID. So, there is no further logic that is being created on my part. This is correct? Sounds awesome, I'll send you a PM, working on installing this program right now.

Comments by MikeTheDebugger (Top 8 by date)