From: whalesuit at bonbon.net (Eric E)
Date: Fri, 10 Jun 2005 12:55:16 -0400
Subject: [Pljava-dev] Re: PL/Java example queries don't respond
In-Reply-To: <thhal-0ayyCAxl9zjYClEHkc4u3FOFiTkcLuc@mailblocks.com>
References: <429F4535.90803@bonbon.net> <42A693E8.7080409@mailblocks.com>
	<thhal-0ayyCAxl9zjYClEHkc4u3FOFiTkcLuc@mailblocks.com>
Message-ID: <42A9C5F4.5060004@bonbon.net>

Hi Thomas,
    Thanks for the advice - I'll hang on to this.  Since I installed 
Postgres from binaries, and didn't build it, I'm gonna hold off on 
recompiling with debugging symbols in the interest of getting my project 
done.  Turns out I got PL/Java working on Postgres 8.0 under windows, so 
I think I'll migrate my Linux installation to 8.0 as well.  Thanks again 
for all the advice.

Cheers,

Eric


Thomas Hallgren wrote:

> Eric E wrote:
>
>> Hi,
>>    Thanks for the previous help with LD_LIBRARY_PATH and LD_PRELOAD.  
>> I will post shortly on some tricks for making these changes when 
>> launching postgres from RedHat-style init scrips.
>>
>>    I'm working with PL/JAVA on a postgres 7.4 instance on Suse 9.2 
>> Pro.  I've successfully installed pl-java, and when go to run the 
>> examples.jar file with:
>> SELECT 
>> sqlj.install_jar('file:///usr/lib/postgresql/pljava/examples.jar', 
>> 'samples',  true);
>>
>> the query runs indefinitely, and basically cannot be canceled, except 
>> via a SIGQUIT to postmaster.
>>
>> LD_LIBRARY_PATH is set to use java, and LD_PRELOAD points zlib at the 
>> version used by the JVM.  From the log (see below), the JVM is 
>> initializing, but nothing further is happening.
>>
>> Any insight?
>>
> Can you please try the following:
> 1. Reconfigure and recompile your PostgreSQL installation:
>
> ./configure --enable-cassert --enable-debug
> make
>
> 2. Recompile your PL/Java using make CFLAGS=-g (make clean first).
>
> Start your app again. Once it hangs, attach gdb to the postgres 
> process that corresponds to your session, i.e.:
>
> gdb <pid of process> <full path to postgres executable>
>
> Once in gdb, print a stack backtrace and see where it's hung.
>
> Regards,
> Thomas Hallgren
>
>
>