Re: Win32 hard crash problem

On 6-Sep-06, at 3:27 AM, Magnus Hagander wrote:

>>>>>> Yes they are using a connection pool. A java based one.
>>>>> Since java has it's own protocol implementation, this is
>> totally
>>>>> unrelated to any libpq error messages.
>>>> Another important point that we've not been given information
>> on:
>>>> when pgAdmin/libpq starts failing like this, exactly what is
>>>> happening with the connection pool? Is it still able to issue
>>>> queries, and if not what happens exactly?
>>>
>>> No, when this happens everything stops. The only thing they get
>> back
>>> is that message until they reboot the server. The web app (via
>>> java/connection pool), pgAdmin both give the same error.
>>>
>>> Which now that I think about it, seems odd if the message is
>> coming
>>> from libpq yes?
>> Yes, this is very odd, AFICS, this message does not exist in the
>> java driver. So.... it would be interesting to get the actual logs
>> from the client.
>
> Definitly - that error msg showing up in the web app really doesn't
> make
> sense. However, are we sure that the error message is *exactly* the
> same, word for word, or is it possible that it's just "the same in
> what
> it says" but with different words? I assume there are screendumps to
> verify this ;-)

I looked at the code in the jdbc driver and it doesn't even do this
check

>
>
> Another point that at least I don't know - what kind of connection
> pool
> is it? Is it an external one (like pgpool) to which the java app
> connects (using FE/BE protocol, emulating a "proper postmaster" but
> pooling access to the database), or is it running inside the app
> server
> (like for example .net connection pooling does, which simply means
> that
> when you run the Open() method on the connection object it will pick
> something off an *internal* pool)?
It's an internal pool, and the client has told me off list they have
removed it and are using the jdbc driver pool.

At this point I'm confused as to what they really are using, but as
they have contracted Command Prompt to fix this for them, I am no
longer in the private loop.

Dave
>
> //Magnus
>
>
> ---------------------------(end of
> broadcast)---------------------------
> TIP 2: Don't 'kill -9' the postmaster
>