Am 27.11.2013 13:07, schrieb Karen Murphy: > > The event logs contained: > Error - Application Error - 14:28:52 > Faulting application name: JettyService.exe, version: 1.0.10.0, time stamp: > 0x4f4600a2 > Faulting module name: ntdll.dll, version: 6.1.7601.17725, time stamp: > 0x4ec4aa8e > Exception code: 0xc0000005 > Fault offset: 0x0000000000053210 > Faulting process id: 0x214 > Faulting application start time: 0x01cedf8048792d0c > Faulting application path: > c:\jetty-distribution-7.3.1.v20110307\bin\JettyService.exe > Faulting module path: C:\Windows\SYSTEM32\ntdll.dll > Report Id: 12552a2a-56a7-11e3-b01b-0050568b0d9a
Seems like the Operating System killed the Jetty-process. Look for a file hs_err_pid[number] in Jetty's working directory. That should contain more information. With your description, it seems that the operating system thought that it ran out of resources. During that time, the JVM tried to allocate more memory (or some other resource) and didn't handle the lack of it in a correct way and was killed by the OS. Regards, Lothar _______________________________________________ jetty-users mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/jetty-users
