Forum Moderators: phranque

Message Too Old, No Replies

Apache/Xampp crashes

         

dallascisco

6:24 pm on Dec 10, 2008 (gmt 0)

10+ Year Member



--------------------------------------------------------------------------------

My company is implementing a web database system for our finance department. The basic premise is to allow financial data to be uploaded from our users computers and stored in a server side database. The vendor who is designing this app for us is using apache inside of xampp and when we test the app it crashes during the upload process. it gives me a windows event id of 4096 and says the issue is with vsjitdebugger.

unhandled win32 exception in apache.exe (4280)

just in time debugging- the remote procedure call failed. I would upload a screenshot or the apache logs but I don't see an option to do that. Please help, I'm not a web admin.

jdMorgan

7:43 pm on Dec 10, 2008 (gmt 0)

WebmasterWorld Senior Member 10+ Year Member



Do you have the Visual Studio debugger installed on this test machine? If not, then such a crash would not be unexpected. It's possible that the test build delivered by your vendor was accidentally shipped with debugging options enabled, and that this is the problem.

The above is just a guess. I'm not a VS user, or even an Apache-on-Windows user. I would recommend beating on your vendor for support, or hiring an expert Visual Studio consultant locally.

Jim

dallascisco

1:55 pm on Dec 12, 2008 (gmt 0)

10+ Year Member



We have the Visual Stuio suite including the debugger on both the test and production environments.

gergoe

5:17 pm on Dec 20, 2008 (gmt 0)

10+ Year Member



Apache could crash (on Windows) for numerous reasons, but I never seen a case when it did it out of itself, it always happened because of third party modules like PHP, or modules of PHP. Remember that the Apache process hosts everything, so if a module, dll library or an executable which is involved in serving the response has a failure, then that will crash the Apache process.

But if I'd be you, I'd remove JIT from at least the production environment, debugging utilities and tools on a production environment is just asking for trouble (which is especially true for JIT).