From derby-user-return-13253-apmail-db-derby-user-archive=db.apache.org@db.apache.org Fri Dec 03 12:20:38 2010 Return-Path: Delivered-To: apmail-db-derby-user-archive@www.apache.org Received: (qmail 68820 invoked from network); 3 Dec 2010 12:20:38 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 3 Dec 2010 12:20:38 -0000 Received: (qmail 64739 invoked by uid 500); 3 Dec 2010 12:20:38 -0000 Delivered-To: apmail-db-derby-user-archive@db.apache.org Received: (qmail 64435 invoked by uid 500); 3 Dec 2010 12:20:35 -0000 Mailing-List: contact derby-user-help@db.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: List-Post: List-Id: Reply-To: "Derby Discussion" Delivered-To: mailing list derby-user@db.apache.org Received: (qmail 64423 invoked by uid 99); 3 Dec 2010 12:20:34 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 03 Dec 2010 12:20:34 +0000 X-ASF-Spam-Status: No, hits=1.2 required=10.0 tests=FORGED_HOTMAIL_RCVD2,FREEMAIL_FROM,SPF_HELO_PASS,SPF_PASS,T_TO_NO_BRKTS_FREEMAIL X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of lists@nabble.com designates 216.139.236.158 as permitted sender) Received: from [216.139.236.158] (HELO kuber.nabble.com) (216.139.236.158) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 03 Dec 2010 12:20:29 +0000 Received: from isper.nabble.com ([192.168.236.156]) by kuber.nabble.com with esmtp (Exim 4.63) (envelope-from ) id 1POUcS-0005pl-EM for derby-user@db.apache.org; Fri, 03 Dec 2010 04:20:08 -0800 Message-ID: <30366541.post@talk.nabble.com> Date: Fri, 3 Dec 2010 04:20:08 -0800 (PST) From: BeNdErR To: derby-user@db.apache.org Subject: Re: Derby : No suitable driver found for jdbc:derby:db;create=true In-Reply-To: <4CF7F7FC.8040707@oracle.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Nabble-From: bendertheoffender_87@hotmail.com References: <30335341.post@talk.nabble.com> <4CF436D4.7080101@gmail.com> <30339246.post@talk.nabble.com> <30347946.post@talk.nabble.com> <4CF65ABC.7090803@gmail.com> <30352053.post@talk.nabble.com> <4CF6FDEF.7020201@gmail.com> <30359597.post@talk.nabble.com> <4CF7F7FC.8040707@oracle.com> For the login I use an activatable server (this app uses java rmi), then, once I'm done with this derby problem, I'll use another "normal" server that extends UnicastRemoteObject. If I haven't answered your question properly, tell me :) Kristian Waagan-2 wrote: > > On 02.12.10 16:35, BeNdErR wrote: >> I modifyed as you told me, that's the error print I get in the client >> window: >> >> SQLState:08001 >> Error Code:0 >> Message:No suitable driver found for jdbc:derby:db;create=true >> >> >> The rmid window, for the activatable server, shows this error: > > Maybe you already said, but what kind of server are you using? > > I have experienced that if you include a jar-file ([1]) on the classpath > from two different locations, things will go crazy. This was using an > appserver, where the jar was loaded both from a system-wide lib > directory and a domain-specific lib directory. > > > -- > Kristian > > [1] Not sure if this is a general problem, or a Derby-specific problem. > >> >> Thu Dec 02 16:22:34 CET 2010:ExecGroup-0:out: DBMS.java >> ClassNotFoundException Error: org.apache.derby.jdbc.EmbeddedDriver >> Thu Dec 02 16:22:34 CET >> 2010:ExecGroup-0:err:java.lang.ClassNotFoundException: >> org.apache.derby.jdbc.EmbeddedDriver >> Thu Dec 02 16:22:34 CET 2010:ExecGroup-0:err: at >> java.net.URLClassLoader$1.run(URLClassLoader.java:202) >> Thu Dec 02 16:22:34 CET 2010:ExecGroup-0:err: at >> java.security.AccessController.doPrivileged(Native Method) >> Thu Dec 02 16:22:34 CET 2010:ExecGroup-0:err: at >> java.net.URLClassLoader.findClass(URLClassLoader.java:190) >> Thu Dec 02 16:22:34 CET 2010:ExecGroup-0:err: at >> java.lang.ClassLoader.loadClass(ClassLoader.java:307) >> Thu Dec 02 16:22:34 CET 2010:ExecGroup-0:err: at >> java.lang.ClassLoader.loadClass(ClassLoader.java:248) >> Thu Dec 02 16:22:34 CET 2010:ExecGroup-0:err: at >> java.lang.Class.forName0(Native Method) >> Thu Dec 02 16:22:34 CET 2010:ExecGroup-0:err: at >> java.lang.Class.forName(Class.java:169) >> Thu Dec 02 16:22:34 CET 2010:ExecGroup-0:err: at >> tmp.DBMS.(DBMS.java:24) >> Thu Dec 02 16:22:34 CET 2010:ExecGroup-0:out:Apro la connessione con il >> DB. >> Thu Dec 02 16:22:34 CET 2010:ExecGroup-0:err: at >> tmp.AuthServer.register(AuthServer.java:79) >> Thu Dec 02 16:22:34 CET 2010:ExecGroup-0:err: at >> sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) >> Thu Dec 02 16:22:34 CET 2010:ExecGroup-0:err: at >> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) >> Thu Dec 02 16:22:34 CET 2010:ExecGroup-0:err: at >> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) >> Thu Dec 02 16:22:34 CET 2010:ExecGroup-0:err: at >> java.lang.reflect.Method.invoke(Method.java:597) >> Thu Dec 02 16:22:34 CET 2010:ExecGroup-0:err: at >> sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:305) >> Thu Dec 02 16:22:34 CET 2010:ExecGroup-0:err: at >> sun.rmi.transport.Transport$1.run(Transport.java:159) >> Thu Dec 02 16:22:34 CET 2010:ExecGroup-0:err: at >> java.security.AccessController.doPrivileged(Native Method) >> Thu Dec 02 16:22:34 CET 2010:ExecGroup-0:err: at >> sun.rmi.transport.Transport.serviceCall(Transport.java:155) >> Thu Dec 02 16:22:34 CET 2010:ExecGroup-0:err: at >> sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:535) >> Thu Dec 02 16:22:34 CET 2010:ExecGroup-0:err: at >> sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run0(TCPTransport.java:790) >> Thu Dec 02 16:22:34 CET 2010:ExecGroup-0:err: at >> sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:649) >> Thu Dec 02 16:22:34 CET 2010:ExecGroup-0:err: at >> java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) >> Thu Dec 02 16:22:34 CET 2010:ExecGroup-0:err: at >> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) >> Thu Dec 02 16:22:34 CET 2010:ExecGroup-0:err: at >> java.lang.Thread.run(Thread.java:662) >> >> the first error is thrown when he enters the DBMS constructor. In the >> setup >> code of the activatable server I used this setting to tell him where he >> can >> find *.class he needs: >> prop.put("java.class.path", "/home/user/app/lib/"); >> because rmid does not accept a -classpath option, I assume that putting >> the >> classpath into the code is an alternative method.. >> I never mentioned before this error because, sincerely and stupidly, I >> never >> watched the rmid window, focusing only on the client error. >> >> I have a question: does the fact that I run every piece of the app >> (server, >> rmid, client) in different shells? I mean, running (or trying) derby in >> one >> shell, lets the others interact with it? >> Another question: my scope is to build this app with a database, then >> move >> ALL the codes into another pc, without installing derby (I can't because >> on >> that pc I'm not the admin). I thought was enough to move all the derby >> libraries in a folder, and then run everywhere I need my application.. Am >> I >> all abroad? >> >> Hoping I'm not wasting your time in a useless thing, thanks a lot > > > -- View this message in context: http://old.nabble.com/Derby-%3A-No-suitable-driver-found-for-jdbc%3Aderby%3Adb-create%3Dtrue-tp30335341p30366541.html Sent from the Apache Derby Users mailing list archive at Nabble.com.