8.2.3: Server crashes on Windows using Eclipse/Junit

On Mon, 15 Oct 2007, Laurent Duperval wrote:

I have a large amount of tests I run in Eclipse to test my application.
Many of them create and delete a lot of information in PG and at some
point, PG will crash and restart.

I get en error in the logs that state:

Server process exited with exit code -1073741502

This is likely a server bug. If you can isolate the failing test and
extract a self contained example someone can probably fix it.

Kris Jurka

On Mon, 15 Oct 2007 15:06:37 -0400, Kris Jurka wrote:

I get en error in the logs that state:

Server process exited with exit code -1073741502

This is likely a server bug. If you can isolate the failing test and
extract a self contained example someone can probably fix it.

It seems to be some sort of interaction between Eclipse and Junit/Postgres
driver. When I run my tests, just before the server crash, I have dozens
and dozens of spawned Postgres processes. When the crash occurs, all
processes are killed and restarted again. And this process continues until
the tests complete.

When I run the tests from an ant script I also see some spawned processes,
but nothing like running it in Eclipse.

If I run each test case separately, I don't see this issue. But when I run
them as a whole (i.e. run all tests defined in my application) I get the
same error every time.

L

Kris Jurka

---------------------------(end of broadcast)---------------------------
TIP 6: explain analyze is your friend

--
Prenez la parole en public en étant Speak to an audience while being
moins nerveux et plus convaincant! less nervous and more convincing!
Éveillez l'orateur en vous! Bring out the speaker in you!

Information: laurent@duperval.com http://www.duperval.com (514) 902-0186

I will add that speed may be a factor also. When I increase the amount of
logging by the PG server, I see the problem less often.

L

On Mon, 15 Oct 2007 17:58:48 +0000, Laurent Duperval wrote:

Hi,

I have a large amount of tests I run in Eclipse to test my application.
Many of them create and delete a lot of information in PG and at some
point, PG will crash and restart.

I get en error in the logs that state:

Server process exited with exit code -1073741502
.
.
.
Terminating connection because of crash of another server process

If it helps:

- I am using Windows XP
- I have 2 GB of memory
- I am using JPA/Hibernate3 and the Postgres Java driver

Any ideas?

L

--
Prenez la parole en public en étant Speak to an audience while being
moins nerveux et plus convaincant! less nervous and more convincing!
Éveillez l'orateur en vous! Bring out the speaker in you!

Information: laurent@duperval.com http://www.duperval.com (514) 902-0186

Laurent Duperval wrote:

On Mon, 15 Oct 2007 15:06:37 -0400, Kris Jurka wrote:

I get en error in the logs that state:

Server process exited with exit code -1073741502

This is likely a server bug. If you can isolate the failing test and
extract a self contained example someone can probably fix it.

It seems to be some sort of interaction between Eclipse and Junit/Postgres
driver. When I run my tests, just before the server crash, I have dozens
and dozens of spawned Postgres processes. When the crash occurs, all
processes are killed and restarted again. And this process continues until
the tests complete.

The fact that all Postgres processes disappear is normal. Postgres
itself (more precisely, the postmaster process) kills all server
processes when one of them dies unexpectedly.

When I run the tests from an ant script I also see some spawned processes,
but nothing like running it in Eclipse.

If I run each test case separately, I don't see this issue. But when I run
them as a whole (i.e. run all tests defined in my application) I get the
same error every time.

Maybe Eclipse is trying to run more of them at a time than ant, and the
extra concurrency is killing the server for some reason. Was this
compiled with Cygwin, or is it the native (mingw) version?

--
Alvaro Herrera http://www.amazon.com/gp/registry/DXLWNGRJD34J
"La vida es para el que se aventura"

Alvaro Herrera <alvherre@commandprompt.com> writes:

Maybe Eclipse is trying to run more of them at a time than ant, and the
extra concurrency is killing the server for some reason. Was this
compiled with Cygwin, or is it the native (mingw) version?

Don't both those builds have some hard-wired upper limit on the number of
child processes? I wonder what Laurent has max_connections set to...
if it's larger than the build could actually support, perhaps this
behavior would be the result.

regards, tom lane

On 10/16/07, Alvaro Herrera <alvherre@commandprompt.com> wrote:

Laurent Duperval wrote:

I get en error in the logs that state:

Server process exited with exit code -1073741502

FYI, this exit code means a DLL's initialization routine indicated
failure during process startup.

If I run each test case separately, I don't see this issue. But when I run
them as a whole (i.e. run all tests defined in my application) I get the
same error every time.

Maybe Eclipse is trying to run more of them at a time than ant, and the
extra concurrency is killing the server for some reason.

Sounds likely.

Hi,

Sorry for top-posting but since I am answering questions that don't all
appear in this message:

- I installed the default download of Postgres. I didn't compile myself,
so it's probably the mingw version

- Max_connections is set to 500. I did that originally because I kept
seeing a message about no connection available and I thought it was
because I was not allocating enough connections. My machine has 2GB of RAM.

- How do I determine what DLL is failing and what is causing it to fail in
its initialization routine?

Thanks,

L

On Tue, 16 Oct 2007 16:02:32 -0700, Trevor Talbot wrote:

On 10/16/07, Alvaro Herrera <alvherre@commandprompt.com> wrote:

Laurent Duperval wrote:

I get en error in the logs that state:

Server process exited with exit code -1073741502

FYI, this exit code means a DLL's initialization routine indicated
failure during process startup.

If I run each test case separately, I don't see this issue. But when I run
them as a whole (i.e. run all tests defined in my application) I get the
same error every time.

Maybe Eclipse is trying to run more of them at a time than ant, and the
extra concurrency is killing the server for some reason.

Sounds likely.

---------------------------(end of broadcast)---------------------------
TIP 5: don't forget to increase your free space map settings

--
Prenez la parole en public en étant Speak to an audience while being
moins nerveux et plus convaincant! less nervous and more convincing!
Éveillez l'orateur en vous! Bring out the speaker in you!

Information: laurent@duperval.com http://www.duperval.com (514) 902-0186