Server eating up all cpu

[Cesar]

The db connection management was one of my first guesses of the problem,

myDac automatically handles the connection pooling, (in the code i gave you i had it disabled because i was testing)

But even with pooling disabled it never goes higher than 50 active connections. also MyDAc handles when you have exahusted your connections and raise an Error.

And the destructor of the connection handles the closing. anyways I'm making the changes, to manually close them before freeing them.

[Cesar]

I just made a new test with interesting results.

I logged every time i enter in the PosEx Function

i discovered it doesn't get stuck in it, but instead, when the cpu spikes, it gets called again and again with the same parameters and length.

now im running a new test logging the contents of InBuffer in the internalRead to see what exactly is sending. unfortunately, my users are already logging out and my traffic might not be enough to make another spike until tomorrow

[D.Tkalcec (RTC)]

I've analyzed the code responsible for reading data with Chunked Transfer encoding and found a possible scenario which could result in an endless loop, calling InternalRead over and over again. I am working on an update now, will be releasing it shortly.

Best Regards,
Danijel Tkalcec

[Cesar]

Thanks Danijiel,

let me know if you need to test anything, i'll gladly be your guinea pig

[D.Tkalcec (RTC)]

I've uploaded the RTC SDK v6.15 to the "RTC SDK Downloads" area.
Please let me know if this update has resolved your issue with 100% CPU drain.

Best Regards,
Danijel Tkalcec

[D.Tkalcec (RTC)]

Is my "guinea pig" dead? Or how should I interpret the long silence?

[Cesar]

hehehe sorry,

i made the changes yesterday and the server has not spiked up again, it's almost 24 hours since the change so I'll say its officially working now.

Thank you very much this bug was cracking my head for the last 3 weeks

[D.Tkalcec (RTC)]

I'm glad you've decided to report this issue. Any RTC Server hosting content for mobile phones could have ended up with the same problem. I'm surprised it wasn't happening more often. Anyway ... I'm going to send an E-Mail now for everyone to download this update, because it's a bug I would rather not have in a production Server.

Best Regards,
Danijel Tkalcec