Description of problem: try to start the derby network server with fedora 17: $ derby-NetworkServerControl Error: Could not find or load main class org.apache.derby.drda.NetworkServerControl Version-Release number of selected component (if applicable): Installed Packages Name : derby Arch : noarch Version : 10.6.2.1 Release : 2.fc17 Size : 6.0 M Repo : installed From repo : fedora Summary : Relational database implemented entirely in Java URL : http://db.apache.org/derby/ License : ASL 2.0 Description : Apache Derby, an Apache DB sub-project, is a relational database : implemented entirely in Java. Some key advantages include a small : footprint, conformance to Java, JDBC, and SQL standards and : embedded JDBC driver. Additional info: The file /usr/share/java/derby/derbynet.jar seems to miss above class. Previous version derby-10.6.1.0-6.fc16 had above class in file derbynet.jar.
I can confirm the problem affects me too, I can't start derby network server with F17 as described above, same version. It just worked in F16. The installed /usr/share/java/derby/derbynet.jar file in F17 is only 75K in size while in F16 it is 231K, derbynet-10.6.1.0.jar. The classes in org.apache.derby.impl.* are missing in F17, compared to F16.
This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component.
Any news on this? Problem still exists.
Problem also exists in FC18 in "derby-10.6.2.1-4.fc18.noarch" Is this package actually supported by Fedora? The upstream version is at 10.9.1.0!
My apologies for letting this bug sit around. I volunteered to take this package when it was orphaned because I needed it as a BuildRequires of another package, but I have not had time to test its full functionality. I am looking into this issue in F18 today.
I have bumped to version 10.9.1.0 and attempted to fix the network server issue in this build: http://koji.fedoraproject.org/koji/taskinfo?taskID=5055311 Please test and let me know if it is acceptable.
Hi, thanks for working on this! 1.) Another class is missing in the derbynet.jar file: org/apache/derby/mbeans/drda/NetworkServerMBean --> $ derby-startNetworkServer Tue Feb 26 18:33:29 CET 2013 : Sicherheitsmanager mit einfacher Server-Sicherheitsrichtlinie installiert. Tue Feb 26 18:33:29 CET 2013 : Apache Derby Network Server 10.9.1.0 - (???) wurde gestartet und ist bereit, Verbindungen am Port 1527 zu akzeptieren. Exception in thread "main" java.lang.NoClassDefFoundError: org/apache/derby/mbeans/drda/NetworkServerMBean at java.lang.ClassLoader.defineClass1(Native Method) at java.lang.ClassLoader.defineClass(ClassLoader.java:791) at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:142) at java.net.URLClassLoader.defineClass(URLClassLoader.java:449) at java.net.URLClassLoader.access$100(URLClassLoader.java:71) at java.net.URLClassLoader$1.run(URLClassLoader.java:361) at java.net.URLClassLoader$1.run(URLClassLoader.java:355) at java.security.AccessController.doPrivileged(Native Method) at java.net.URLClassLoader.findClass(URLClassLoader.java:354) at java.lang.ClassLoader.loadClass(ClassLoader.java:423) at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:308) at java.lang.ClassLoader.loadClass(ClassLoader.java:356) at org.apache.derby.impl.drda.NetworkServerControlImpl.blockingStart(NetworkServerControlImpl.java:785) at org.apache.derby.impl.drda.NetworkServerControlImpl.executeWork(NetworkServerControlImpl.java:2243) at org.apache.derby.drda.NetworkServerControl.main(NetworkServerControl.java:351) Caused by: java.lang.ClassNotFoundException: org.apache.derby.mbeans.drda.NetworkServerMBean at java.net.URLClassLoader$1.run(URLClassLoader.java:366) at java.net.URLClassLoader$1.run(URLClassLoader.java:355) at java.security.AccessController.doPrivileged(Native Method) at java.net.URLClassLoader.findClass(URLClassLoader.java:354) at java.lang.ClassLoader.loadClass(ClassLoader.java:423) at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:308) at java.lang.ClassLoader.loadClass(ClassLoader.java:356) ... 15 more 2.) Thanks for including the systemd derby unit file 3.) The derby-ij shell script misses to include derbyclient.jar. Without this class you cannot use the derby-ij sql command interpreter, because it needs the derby JDBC driver which is included in the derbyclient.jar file! The shell script has this comment: 45 # Not loading all of derby, so that secure class loader 46 # can kick in 47 BASE_JARS="$BASE_JARS derby/derby" 48 BASE_JARS="$BASE_JARS derby/derbynet" 49 BASE_JARS="$BASE_JARS derby/derbytools" I'm not sure if it is a good idea to just include derbyclient.jar in this list, which makes derby-ij work...
This message is a reminder that Fedora 17 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 17. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '17'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 17's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 17 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior to Fedora 17's end of life. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
any news on this? did you fix the classpath in the shell script?
Fedora 17 changed to end-of-life (EOL) status on 2013-07-30. Fedora 17 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed.
derby-10.9.1.0-5.fc20 has been submitted as an update for Fedora 20. https://admin.fedoraproject.org/updates/derby-10.9.1.0-5.fc20
derby-10.9.1.0-5.fc19 has been submitted as an update for Fedora 19. https://admin.fedoraproject.org/updates/derby-10.9.1.0-5.fc19
Package derby-10.9.1.0-5.fc20: * should fix your issue, * was pushed to the Fedora 20 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing derby-10.9.1.0-5.fc20' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2013-18881/derby-10.9.1.0-5.fc20 then log in and leave karma (feedback).
derby-10.9.1.0-6.fc19 has been submitted as an update for Fedora 19. https://admin.fedoraproject.org/updates/derby-10.9.1.0-6.fc19
derby-10.9.1.0-6.fc20 has been submitted as an update for Fedora 20. https://admin.fedoraproject.org/updates/derby-10.9.1.0-6.fc20
derby-10.9.1.0-6.fc19 has been pushed to the Fedora 19 stable repository. If problems still persist, please make note of it in this bug report.
derby-10.9.1.0-6.fc20 has been pushed to the Fedora 20 stable repository. If problems still persist, please make note of it in this bug report.