On Wed, 19 Oct 2011 12:43:49 +0200, Thomas Steinmaurer
<ts@...> wrote:

>> But I know from Jaybird for instance, that one needs to specify

specific

>> properties, see:
>> http://tracker.firebirdsql.org/browse/JDBC-118
>>
>> But I guess this is related to the thin driver not communicating via

the

>> client library.

Looking at it I do think that I will create a new task for Jaybird to
introduce a fallback mechanism if the user did not provide a PID and/or
processname. As far as I can see it should be possible to derive the PID
from ManagementFactory.getRuntimeMXBean().getName() and for Sun/Oracle JVMs
there should be a property called sun.java.launcher.pid.

I also know that the Oracle JDBC driver by default reports itself as 'JDBC
THIN CLIENT', something similar would be a good thing for Jaybird as well.

>> What access technology do you use and is your mentioned gds32.dll
>> version the one on the client or do we speak about a local installation
>> here anyway?
>
> Btw, the database parameter buffer (DPB) is called: isc_dpb_process_name

And isc_dpb_process_id for the pid.

Mark