[jira] [Commented] (DERBY-7063) Cannot connect using squirrel 3.3.0
[ https://issues.apache.org/jira/browse/DERBY-7063?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17008364#comment-17008364 ] Richard N. Hillegas commented on DERBY-7063: Thanks for raising the topic of a Derby release. I will move this discussion over to the dev list. > Cannot connect using squirrel 3.3.0 > --- > > Key: DERBY-7063 > URL: https://issues.apache.org/jira/browse/DERBY-7063 > Project: Derby > Issue Type: Bug > Components: JDBC, Network Server >Affects Versions: 10.15.1.3 >Reporter: sagar >Priority: Major > Fix For: 10.15.1.3 > > > The derbyclient.jar file does not have the > org.apache.derby.jdbc.ClientDriver.class > > When I add the jar file in squirrel, ssquirrel automatically detects the > driver but since this class is missing it does not detect it. > Till now I was using 10.11.1.1 database. Now I have decided to upgrade and > this issue cropped up. > > Yes Derby has switched to the module system from 10.15.1.3 but the derby > documentation mentions connection to Network Server similar to previous as > using the > org.apache.derby.jdbc.ClientDriver and this class is missing from the new > derbyclient.jar. > > > Squirrel is running on Java 1.8 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (DERBY-7063) Cannot connect using squirrel 3.3.0
[ https://issues.apache.org/jira/browse/DERBY-7063?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17008130#comment-17008130 ] sagar commented on DERBY-7063: -- Ok so managed to connect to 10.15.1.3 using squirrel. Put derbyClient derbyTools and derbyshared jar files in the squirrel lib folder. So that closes this report. Also the network server runs well with the startNetworkServer scripts ... upgraded and old database and tried out an existing application ... all well ... Just wanted to know if a new derby release is coming up by March, since its will be a year since the 10.15.1.3 has released. > Cannot connect using squirrel 3.3.0 > --- > > Key: DERBY-7063 > URL: https://issues.apache.org/jira/browse/DERBY-7063 > Project: Derby > Issue Type: Bug > Components: JDBC, Network Server >Affects Versions: 10.15.1.3 >Reporter: sagar >Priority: Major > > The derbyclient.jar file does not have the > org.apache.derby.jdbc.ClientDriver.class > > When I add the jar file in squirrel, ssquirrel automatically detects the > driver but since this class is missing it does not detect it. > Till now I was using 10.11.1.1 database. Now I have decided to upgrade and > this issue cropped up. > > Yes Derby has switched to the module system from 10.15.1.3 but the derby > documentation mentions connection to Network Server similar to previous as > using the > org.apache.derby.jdbc.ClientDriver and this class is missing from the new > derbyclient.jar. > > > Squirrel is running on Java 1.8 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (DERBY-7063) Cannot connect using squirrel 3.3.0
[ https://issues.apache.org/jira/browse/DERBY-7063?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17006149#comment-17006149 ] Bryan Pendleton commented on DERBY-7063: If you are using the scripts to start the Network Server, then I don't think you need to manage the classpath manually. If you find that is not true, and classpath is still a problem even with the scripts, please let us know. > Cannot connect using squirrel 3.3.0 > --- > > Key: DERBY-7063 > URL: https://issues.apache.org/jira/browse/DERBY-7063 > Project: Derby > Issue Type: Bug > Components: JDBC, Network Server >Affects Versions: 10.15.1.3 >Reporter: sagar >Priority: Major > > The derbyclient.jar file does not have the > org.apache.derby.jdbc.ClientDriver.class > > When I add the jar file in squirrel, ssquirrel automatically detects the > driver but since this class is missing it does not detect it. > Till now I was using 10.11.1.1 database. Now I have decided to upgrade and > this issue cropped up. > > Yes Derby has switched to the module system from 10.15.1.3 but the derby > documentation mentions connection to Network Server similar to previous as > using the > org.apache.derby.jdbc.ClientDriver and this class is missing from the new > derbyclient.jar. > > > Squirrel is running on Java 1.8 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (DERBY-7063) Cannot connect using squirrel 3.3.0
[ https://issues.apache.org/jira/browse/DERBY-7063?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17005416#comment-17005416 ] sagar commented on DERBY-7063: -- Bryan my slip of eye ... Did not read reference to derbytools.jar in the release notes in Remote Client section. Though will report again tomorrow. By the way I start the NetworkServer using the StartNetworkServer script ... In it I have set JAVA_HOME and DERBY_HOME path variables ... So I think now there is no necessitiy to set classpath manually or run NetworkServer usong derbyrun.jar. Is it? > Cannot connect using squirrel 3.3.0 > --- > > Key: DERBY-7063 > URL: https://issues.apache.org/jira/browse/DERBY-7063 > Project: Derby > Issue Type: Bug > Components: JDBC, Network Server >Affects Versions: 10.15.1.3 >Reporter: sagar >Priority: Major > > The derbyclient.jar file does not have the > org.apache.derby.jdbc.ClientDriver.class > > When I add the jar file in squirrel, ssquirrel automatically detects the > driver but since this class is missing it does not detect it. > Till now I was using 10.11.1.1 database. Now I have decided to upgrade and > this issue cropped up. > > Yes Derby has switched to the module system from 10.15.1.3 but the derby > documentation mentions connection to Network Server similar to previous as > using the > org.apache.derby.jdbc.ClientDriver and this class is missing from the new > derbyclient.jar. > > > Squirrel is running on Java 1.8 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (DERBY-7063) Cannot connect using squirrel 3.3.0
[ https://issues.apache.org/jira/browse/DERBY-7063?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17005399#comment-17005399 ] sagar commented on DERBY-7063: -- Thanks. Will chk tomorrow morning IST and report success or failure. I checked Derby Developer guide and moat of the other guides too but all examples mentioned the driver class name same but did not find if there was any reference to derbytools.jar. Will double check again and report back. > Cannot connect using squirrel 3.3.0 > --- > > Key: DERBY-7063 > URL: https://issues.apache.org/jira/browse/DERBY-7063 > Project: Derby > Issue Type: Bug > Components: JDBC, Network Server >Affects Versions: 10.15.1.3 >Reporter: sagar >Priority: Major > > The derbyclient.jar file does not have the > org.apache.derby.jdbc.ClientDriver.class > > When I add the jar file in squirrel, ssquirrel automatically detects the > driver but since this class is missing it does not detect it. > Till now I was using 10.11.1.1 database. Now I have decided to upgrade and > this issue cropped up. > > Yes Derby has switched to the module system from 10.15.1.3 but the derby > documentation mentions connection to Network Server similar to previous as > using the > org.apache.derby.jdbc.ClientDriver and this class is missing from the new > derbyclient.jar. > > > Squirrel is running on Java 1.8 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (DERBY-7063) Cannot connect using squirrel 3.3.0
[ https://issues.apache.org/jira/browse/DERBY-7063?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17005329#comment-17005329 ] Richard N. Hillegas commented on DERBY-7063: As part of the modularization work, the JDBC drivers moved into derbytools.jar. The release notes do not make this clear. Please include derbyclient.jar, derbyshared.jar, and derbytools.jar on your client-side classpath. > Cannot connect using squirrel 3.3.0 > --- > > Key: DERBY-7063 > URL: https://issues.apache.org/jira/browse/DERBY-7063 > Project: Derby > Issue Type: Bug > Components: JDBC, Network Server >Affects Versions: 10.15.1.3 >Reporter: sagar >Priority: Major > > The derbyclient.jar file does not have the > org.apache.derby.jdbc.ClientDriver.class > > When I add the jar file in squirrel, ssquirrel automatically detects the > driver but since this class is missing it does not detect it. > Till now I was using 10.11.1.1 database. Now I have decided to upgrade and > this issue cropped up. > > Yes Derby has switched to the module system from 10.15.1.3 but the derby > documentation mentions connection to Network Server similar to previous as > using the > org.apache.derby.jdbc.ClientDriver and this class is missing from the new > derbyclient.jar. > > > Squirrel is running on Java 1.8 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (DERBY-7063) Cannot connect using squirrel 3.3.0
[ https://issues.apache.org/jira/browse/DERBY-7063?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17005327#comment-17005327 ] Bryan Pendleton commented on DERBY-7063: See : [https://stackoverflow.com/a/57221011/193453] Have you tried adding derbyshared.jar as an additional jar file in your Squirrel driver configuration? Where do you recommend we should document this new behavior? It is documented here: [http://db.apache.org/derby/releases/release-10.15.1.3.cgi] Note that if you are running Java 1.8, you can also consider just using Derby 10.14, rather than Derby 10.15. > Cannot connect using squirrel 3.3.0 > --- > > Key: DERBY-7063 > URL: https://issues.apache.org/jira/browse/DERBY-7063 > Project: Derby > Issue Type: Bug > Components: JDBC, Network Server >Affects Versions: 10.15.1.3 >Reporter: sagar >Priority: Major > > The derbyclient.jar file does not have the > org.apache.derby.jdbc.ClientDriver.class > > When I add the jar file in squirrel, ssquirrel automatically detects the > driver but since this class is missing it does not detect it. > Till now I was using 10.11.1.1 database. Now I have decided to upgrade and > this issue cropped up. > > Yes Derby has switched to the module system from 10.15.1.3 but the derby > documentation mentions connection to Network Server similar to previous as > using the > org.apache.derby.jdbc.ClientDriver and this class is missing from the new > derbyclient.jar. > > > Squirrel is running on Java 1.8 -- This message was sent by Atlassian Jira (v8.3.4#803005)
