Thread: RE: [Squirrel-sql-develop] Connection to database over VPN fails?
A Java SQL client for any JDBC compliant database
Brought to you by:
colbell,
gerdwagner
From: Colin B. <Col...@as...> - 2004-07-25 23:07:17
|
Hi Maury, > -----Original Message----- > From: Maury Hammel [mailto:ml1...@sh...] > Sent: Monday, 26 July 2004 2:15 AM > To: SQuirreL SQL Developers > Subject: [Squirrel-sql-develop] Connection to database over VPN fails? > oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:545) > at java.sql.DriverManager.getConnection(DriverManager.java:512) > at java.sql.DriverManager.getConnection(DriverManager.java:140) > at > net.sourceforge.squirrel_sql.fw.sql.SQLDriverManager.getConnec > tion(SQLDriverManager.java:135) > at > net.sourceforge.squirrel_sql.client.mainframe.action.OpenConne > ctionCommand.execute(OpenConnectionCommand.java:97) The SQuirreL class SQLDriverManager doesn't use java.sql.DriverManager because DriverManager assumes that the JDBC drivers are loaded by the system classloader which isn't the case in SQuirreL. I don't think I've used DriverManager since one of the betas for version 1.0 so it looks like you're using a very old version of SQuirreL. Could you try this with the latest beta 1.2beta6. If it doesn't work with beta6 try running the following code. Its closer to the way SQuirreL opens a connection than your test case. import java.sql.*; import java.util.*; public final class Test { public static void main(String[] args) { try { final Properties myProps = new Properties(); myProps.put("user", "USER"); myProps.put("password", "PASSWORD"); final Class clazz = Class.forName("oracle.jdbc.driver.OracleDriver"); final Driver driver = (Driver)clazz.newInstance(); final Connection conn = driver.connect("jdbc:oracle:thin:@<SERVER>:1521:<DB>", myProps); try { System.out.println("Success"); } finally { conn.close(); } } catch (Throwable th) { th.printStackTrace(); } } } If this works but beta6 doesn't then it looks like an issue with the classloader in SQuirreL. Let me know and I'll take a further look. Col |
From: <co...@in...> - 2004-07-26 21:06:31
|
> Actually, this was with a copy of the latest in CVS (as of > Saturday). Very strange. I'll clean everything out, do > a fresh check-out and try again, just in case something > got messed up somewhere. Make sure that you're using the sql12 module from CVS. squirrelsql module is a copy of the 1.1 version. Col |
From: Maury H. <ml1...@sh...> - 2004-07-26 22:10:22
|
Colin: > Make sure that you're using the sql12 module from CVS. > squirrelsql module is a copy of the 1.1 version. I thought I was using sql12, but you never know. :-( Maury... |
From: Maury H. <ml1...@sh...> - 2004-08-02 15:43:59
|
> Make sure that you"re using the sql12 module from CVS. > squirrelsql module is a copy of the 1.1 version. Yes, that was what I was using (at least I thought I was...). Anyway, I removed all instances of SQuirreL off my machine, downloaded a fresh copy of 1.2 beta 6, and also did a new checkout of the current 1.2 beta 7 source. I still cannot connect with the either version, but the error is identical in both (and it appears to be slightly different than what I was getting before): java.sql.SQLException: Io exception: The Network Adapter could not establish the connection at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:125) at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:162) at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:274) at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:319) at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java:344) at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:148) at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtension.java:32) at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:545) at net.sourceforge.squirrel_sql.fw.sql.SQLDriverManager.getConnection(SQLDriverManager.java:124) at net.sourceforge.squirrel_sql.client.mainframe.action.OpenConnectionCommand.execute(OpenConnectionCommand.java:97) at net.sourceforge.squirrel_sql.client.mainframe.action.ConnectToAliasCommand$SheetHandler.run(ConnectToAliasCommand.java:368) at net.sourceforge.squirrel_sql.fw.util.TaskExecuter.run(TaskExecuter.java:82) at java.lang.Thread.run(Thread.java:534) The example code Colin posted does work, so there must be something in SQuirreL that is having a problem. I'll keep puzzling over it, but if anyone has any ideas..... Thanks... Maury. |
From: Colin B. <co...@in...> - 2004-08-05 09:39:39
|
On Mon, Aug 02, 2004 at 09:33:07AM -0600, Maury Hammel wrote: > Anyway, I removed all instances of SQuirreL off my machine, downloaded a > fresh copy of 1.2 beta 6, and also did a new checkout of the current 1.2 > beta 7 source. I still cannot connect with the either version, but the > error is identical in both (and it appears to be slightly different than > what I was getting before): > > java.sql.SQLException: Io exception: The Network Adapter could not > establish the connection <snip /> > > The example code Colin posted does work, so there must be something in > SQuirreL that is having a problem. I'll keep puzzling over it, but if > anyone has any ideas..... The only other real difference is that the drivers aren't loaded using the system classloader, but rather by a custom classloader. I can't see that causing this problem but you never know. Let me have another look at the code and I'll see if I can see anything. -- Colin Bell http://www.squirrelsql.org |
From: Neil G. <ne...@as...> - 2004-09-01 06:55:29
|
Nice to have feature, On the SQL-Output (sql results) it would be nice to have a 'close all' button which closes all the resultsets. Or like with Eclipse, 'Close all', 'Close others' |
From: Colin B. <co...@in...> - 2004-09-06 12:35:59
|
Hi Neil, On Wed, Sep 01, 2004 at 08:29:32AM +0200, Neil Gordon wrote: > Nice to have feature, > > On the SQL-Output (sql results) it would be nice to have a 'close all' > button which closes all the resultsets. Or like with Eclipse, 'Close > all', 'Close others' Could you please add an RFE for this. That way I won't forget abut it. http://sourceforge.net/tracker/?atid=393417&group_id=28383 -- Colin Bell http://www.squirrelsql.org |
From: Neil G. <ne...@as...> - 2004-09-09 13:58:28
|
Colin, Have written a little plugin which shows Compiere (see http://www.compiere.org) meta-info on the table info section. Any chance of reserving the namespace 'compiereplugin?' (package net.sourceforge.squirrel_sql.plugins.compiereplugin) Thanks Neil |
From: Maury H. <ml1...@sh...> - 2004-07-26 15:27:48
|
Colin: > The SQuirreL class SQLDriverManager doesn't use java.sql.DriverManager > because DriverManager assumes that the JDBC drivers are loaded by the > system classloader which isn't the case in SQuirreL. I don't think > I've used DriverManager since one of the betas for version 1.0 so it > looks like you're using a very old version of SQuirreL. Could > you try this with the latest beta 1.2beta6. Actually, this was with a copy of the latest in CVS (as of Saturday). Very strange. I'll clean everything out, do a fresh check-out and try again, just in case something got messed up somewhere. > If it doesn't work with beta6 try running the following code. Its > closer to the way SQuirreL opens a connection than your test case. [snip] > If this works but beta6 doesn't then it looks like an issue with the > classloader > in SQuirreL. Let me know and I'll take a further look. Okay, I give the code a try. Thanks again... Maury. |