Page 1 of 1

weird upgrade experience

PostPosted: Sun Oct 13, 2013 11:57 am
by dutchguy69
After upgrading my system to openSUSE 12.3 encountered the following issue when starting the serviio server

Exception in thread "main" java.lang.NoClassDefFoundError: org.serviio.MediaServer

Found message on board about adding all individual jars within the lib directory. Added all jars including path and the server started, only to fail with another error

WARN [DBConnectionPool] Can't create a new connection for jdbc:derby:db;create=true
java.sql.SQLException: No driver found for jdbc:derby:db;create=true

Found message on board about this as well which actually pointed out that the user was using java 1.5.0. As I already checked my version which was 1.7.0 I was sure to be correct here.

java -showversion
java version "1.7.0_40"
OpenJDK Runtime Environment (IcedTea 2.4.1) (suse-3.41.1-x86_64)
OpenJDK 64-Bit Server VM (build 24.0-b50, mixed mode)

But then when I checked the log file a bit closer found

2013-10-13 12:16:48,944 INFO [MediaServer] Serviio DLNA media streaming server v 1.3.1 (rev. f1fc8bc55657+)
2013-10-13 12:16:48,944 INFO [MediaServer] Petr Nejedly 2009-2013
2013-10-13 12:16:48,944 INFO [MediaServer] http://www.serviio.org
2013-10-13 12:16:48,944 INFO [MediaServer]
2013-10-13 12:16:48,944 INFO [MediaServer] Java 1.5.0-Free Software Foundation, Inc. <-- 1.5.0 java reference here was a bit of a surprise knowing I had 1.7.0 installed
2013-10-13 12:16:48,944 INFO [MediaServer] OS Linux x86_64 3.7.10-1.16-desktop
2013-10-13 12:16:48,944 INFO [MediaServer] File encoding: UTF-8
2013-10-13 12:16:48,944 INFO [MediaServer] Headless mode enabled: true

Here clearly it is showing 1.5.0 as well.

Via zypper (package manager on openSUSE) listed my java installs and found 2 references for 1.5.0 compatibility.

i | java-1_5_0-gcj-compat | package | 1.5.0.0-136.1 | x86_64 | Java-Repository
i | java-1_5_0-gcj-compat-devel | package | 1.5.0.0-136.1 | x86_64 | Java-Repository

Decided to remove these to verify whether that would resolve my issue and indeed it did.

Once this proofed to work I removed the individual jars from the classpath again moving back to original serviio.sh server script and that worked as well now.

Just wanted to make people aware of this as it does not seem straightforward and logical to me. :o