Necro problem related to packet floods?

[psychoninja]

I work for an ISP in Texas. We do FIXED wireless broadband... Not that satellite stuff. On some of our 2.4 ghz systems we had some lower end switches at one time and those switches used to get "Packet flooding". This would cause the system to reboot. Would cause a minute of downtime or so as well.

I was thinking this could relate to the random server reboots. I was 2 of 5 players online the other night... And every time I'd start MASS pulling the server would restart back to the exact point that I logged in almost... Almost like it was me that was restarting it. So I heard it could be necros causing these problems. So I stopped playing my servant necro. So I rolled a Cab lol. Went matter spec and I made a larger than average pull the other day with focus shield up. As the 20-30 mobs were hitting the pet I started spamming DoT on them and right as I was casting both my chat windows wiped clean then seconds later I was DC'd.

I was thinking with this many things attacking and going on at once at one time that it could cause some kind of packet jam? All those mobs getting hit at once from DoT and focus shield would be sending an extreme amount of packets at once right? I'm not THAT great with networking but I think it sounds right.

Perhaps you've already found the problem and are fixing it - but I thought they could relate b/c the server kept doing it while I was playing Necro then it started to do it when I rolled the cabalist.

I'm Ohdad, Creature, and Fightmaster btw.

[loen2]

Well at the time of the last server crash I was mass pulling on my cave shaman. I hope it wasn't me There was 1 necro on as well.
Staff here said that the sever had a power outage and that there is a bad storm in the area of the server.

[IStandAloneToo]

Here's what appears to happen. A spell is 'queued' for the pet to cast (stores the target, spell, spell line). The target dies before the spell is casted giving you the 'You must select a target for this spell'. Now, under normal circumstances the spell will be removed from the queue (and it works 99% of the time). However, due to some strange circumstances (possibly lag?) the spell is not removed from the queue. In fact it appears to become 'stuck' in the queue which then creates a stack loop. Basically the error is this:
A calls B calls C calls A calls B calls C calls A and so on until the computer says ENOUGH! and completely kills the executable. So, the loop goes like:
CastSpell calls Notify calls CheckQueue calls CastSpell calls Notify calls CheckQueue.

Like I said, under normal circumstances that works because if nothing is in the queue, CheckQueue doesn't reach CastSpell... But if there is a pesky little spell that gets stuck in the queue... You can see where this is going .

[IStandAloneToo]

Oh, you guys pulling a lot of mobs doesn't cause it . Well, indirectly. The necro apparently had the nice little incident happen .