On Sun, 26 May 2013, Wolfgang Kluge wrote:
> Good evening.
>
> I will be grateful if sombody could tell me what is wrong with the
> following connection string:
>
> jdbc:firebirdsql:localhost:3050:c:\fbdata\frontdesk.fdb
>
> Firebird 1.5.6 on Win XP SP3
>
> I found may contradicting versions but could not get any one to work.
Did you try forward slashes?
Also, here's an example I found online:
jdbc:firebirdsql://localhost:3050/C:/FirebirdDB/EMPLOYEEDB.fdb
Did you try slashes before localhost and instead of the colon separating
the port number and the database file path?
--
John Hardin KA7OHZ http://www.impsec.org/~jhardin/
jhardin@... FALaholic #11174 pgpk -a jhardin@...
key: 0xB8732E79 -- 2D8C 34F4 6411 F507 136C AF76 D822 E6E6 B873 2E79
-----------------------------------------------------------------------
Maxim XXIX: The enemy of my enemy is my enemy's enemy. No more.
No less.
-----------------------------------------------------------------------
Tomorrow: Memorial Day - honor those who sacrificed for our liberty

On Sun, 26 May 2013, Drav Sloan wrote:
> urbanmojo wrote:
>> I'm working with Squirrel 3.4.0 connecting to Oracle over a shaky VPN
>> connection using the Oracle Thin JDBC driver.
>>
>> I've noticed that even if Squirrel is sitting idle for some time and, during
>> that time, I lose connection to the database and then come back and try to
>> run a query that it doesn't run and I get something like a "closed
>> connection error". (even though I currently do have connectivity when
>> attempting to run it).
>>
>> The only way I see is to close my query window and reconnect to the alias.
>>
>> Question 1:
>> 1. Is this an issue with Squirrel, the driver, or Oracle?
>
> A thin driver connection is a tcp connection (and therefore stateful) which relies
> on a permanent net connection. If this fails then the connection will drop.
One important piece of that is: if your IP address changes. If the VPN
connection drops, gets restored, and you get assigned the same IP address,
the TCP connection *should* recover unless the timeouts have been set
fairly short.
>> 2. Any way around this?
>
> You can issue the "reconnect" command Session > Reconnect (quick shortcut of
> Crtl-Alt-T), which will save you having to reopen the window. You may or may
> have some success with a "keepalive" command. Right click on the Alias and
> goto Alias Properties, select the connection tab, enable keep alive and set
> some sql to run (select sysdate from dual as an example). However this may
> make your connection drop more quickly.
--
John Hardin KA7OHZ http://www.impsec.org/~jhardin/
jhardin@... FALaholic #11174 pgpk -a jhardin@...
key: 0xB8732E79 -- 2D8C 34F4 6411 F507 136C AF76 D822 E6E6 B873 2E79
-----------------------------------------------------------------------
Maxim XXIX: The enemy of my enemy is my enemy's enemy. No more.
No less.
-----------------------------------------------------------------------
Tomorrow: Memorial Day - honor those who sacrificed for our liberty

Good evening.
I will be grateful if sombody could tell me what is wrong with the
following connection string:
jdbc:firebirdsql:localhost:3050:c:\fbdata\frontdesk.fdb
Firebird 1.5.6 on Win XP SP3
I found may contradicting versions but could not get any one to work.
Thanks in advance.
Wolfgang Kluge

urbanmojo wrote:
> I'm working with Squirrel 3.4.0 connecting to Oracle over a shaky VPN
> connection using the Oracle Thin JDBC driver.
>
> I've noticed that even if Squirrel is sitting idle for some time and, during
> that time, I lose connection to the database and then come back and try to
> run a query that it doesn't run and I get something like a "closed
> connection error". (even though I currently do have connectivity when
> attempting to run it).
>
> The only way I see is to close my query window and reconnect to the alias.
>
> Question 1:
> 1. Is this an issue with Squirrel, the driver, or Oracle?
A thin driver connection is a tcp connection (and therefore stateful) which relies
on a permanent net connection. If this fails then the connection will drop.
> 2. Any way around this?
You can issue the "reconnect" command Session > Reconnect (quick shortcut of
Crtl-Alt-T), which will save you having to reopen the window. You may or may
have some success with a "keepalive" command. Right click on the Alias and
goto Alias Properties, select the connection tab, enable keep alive and set
some sql to run (select sysdate from dual as an example). However this may
make your connection drop more quickly.
Regards
D.