From derby-user-return-428-apmail-db-derby-user-archive=db.apache.org@db.apache.org Tue Dec 28 17:57:58 2004 Return-Path: Delivered-To: apmail-db-derby-user-archive@www.apache.org Received: (qmail 53641 invoked from network); 28 Dec 2004 17:57:57 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur-2.apache.org with SMTP; 28 Dec 2004 17:57:57 -0000 Received: (qmail 4751 invoked by uid 500); 28 Dec 2004 17:57:45 -0000 Delivered-To: apmail-db-derby-user-archive@db.apache.org Received: (qmail 4694 invoked by uid 500); 28 Dec 2004 17:57:44 -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 4633 invoked by uid 99); 28 Dec 2004 17:57:43 -0000 X-ASF-Spam-Status: No, hits=1.7 required=10.0 tests=DNS_FROM_RFC_ABUSE,DNS_FROM_RFC_POST,SPF_HELO_PASS,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (hermes.apache.org: domain of natgross.rentalsystems@verizon.net designates 206.46.170.106 as permitted sender) Received: from out006pub.verizon.net (HELO out006.verizon.net) (206.46.170.106) by apache.org (qpsmtpd/0.28) with ESMTP; Tue, 28 Dec 2004 09:57:06 -0800 Received: from [192.168.1.100] ([68.237.94.67]) by out006.verizon.net (InterMail vM.5.01.06.06 201-253-122-130-106-20030910) with ESMTP id <20041228175656.VLMJ7873.out006.verizon.net@[192.168.1.100]> for ; Tue, 28 Dec 2004 11:56:56 -0600 Message-ID: <41D19E6C.6070104@verizon.net> Date: Tue, 28 Dec 2004 12:57:00 -0500 From: Nat Gross Reply-To: Derby Discussion Organization: Easy Systems International User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7) Gecko/20040616 X-Accept-Language: en-us, he MIME-Version: 1.0 To: Derby Discussion Subject: Re: Sun 8.0.1 Appserver pooling References: <41CF305C.9080903@verizon.net> <41CF3A46.2040803@Golux.Com> <41D0404B.5000709@verizon.net> <41D0A0DB.2040606@Golux.Com> <41D18DAA.6000406@verizon.net> <41D18F25.9080409@sun.com> In-Reply-To: <41D18F25.9080409@sun.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Authentication-Info: Submitted using SMTP AUTH at out006.verizon.net from [68.237.94.67] at Tue, 28 Dec 2004 11:56:56 -0600 X-Virus-Checked: Checked X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N Lance J. Andersen wrote: > Nat, > I have had this working successfully with 8.0 and early beta of 8.1. Thanks. Music to my ears. I prefer Derby over HSQLDB, and this info helps my decision. > > Where did you install your derby classes? Normally I put them in > domains/domain1/lib/ext. I put them into "domains/domain1/lib". But even if that was wrong, I also configured sjsaas (jvm options--->paths) to add derby.jar to the classpath, which it correctly did, since it finally changed from the 'class not found' error to the gui framework error. Also, it automatically gave me Derby relevant properties to set, so I assume that it did properly see the Derby classes. > > Can you post your domain.xml entry that you used with the embedded driver? To be honest, I don't know what this is. But I am just finishing up the install of sjsas8.1 RC, and will attempt everything again. > Are you sure you did not have another process that already had the > DB open outside of SJSAS? Huh? What? WOA. Maybe this was it. I have Eclipse/MyEclipse with dbExplorer connecting to it at times, and it *might* have been using a connection as well. (But I also think, yes only think, that I tried it many times with the Eclipse ide closed altogether.) BUT, does this mean, that I cannot use any type of db tool to view/alter the database if I have that db open from appserver? Or, can I administer/manage (my dba hat on now) the db via some tool VIA a pooled connection from sjsas? Thanks a mill; -nat > > Regards > Lance > > Nat Gross wrote: > >> myrnap wrote: >> >>> Nat Gross wrote: >>> >>>> myrnap wrote: >>>> >>>>> Nat Gross wrote: >>>>> >>>>>> Hi; >>>>>> Although I have no problems connecting to my new Derby, via jdbc, >>>>>> I cannot get a 'ping' when setting up a j2ee pool and jndi >>>>>> connector in the Sun app server. I followed the instructions on >>>>>> the java.net blog,for embedded, the classpath is set, have tried >>>>>> various javax connectors, the xa version and non xa version, to >>>>>> no avail. >>>>>> Your help will be appreciated. >>>>>> Thanks >>>>>> -nat >>>>>> >>>>> Nat, >>>>> >>>>> What's the error you see? >>>>> What's in the server.log? >>>>> Does a derby.log get created? If so, is it where you expect it to be? >>>>> >>>>> Myrna >>>>> >>>> Progress.... For some reason the sdk's bin directory wasn't in the >>>> PATH. I didn't dream that the gui admin uses the cmdline stuff >>>> behind the scenes. Anyhow, now there is a new error when pinging. >>>> The first exception sais that it couldn't open the database and the >>>> next exception has the details why. But the next exception list >>>> some gui framework error, for the ping button. Here it is.: >>>> >>> Hm, I like the classnot found problem more - at least then we know >>> it's the classpath, somehow. :-) >>> I would've checked whether derby.jar was in the lib, or lib/ext dir... >>> >>> The 'Failed to start database ...' error can be caused by a number >>> of situations...Unfortunately, I think the app server gobbles up the >>> nested (i.e. 'next') exception... >>> Perhaps someone else knows more about the framework error... >>> >>> The situation I'm thinking you might be hitting is somehow 2 >>> jvms/processes trying to get hold of the same database. >>> >>> In that case, you would see a derby.log that looks completely fine >>> and healthy (because of the first jvm starting the database), but >>> still get this error. And of course, you'd see an extra (java or >>> javaw) process after the ping. >>> >>> To see more, I suggest you add the following derby.properties file >>> to the derby.system.home dir (practically speaking, that would be >>> where derby.log gets created.): >>> derby.infolog.append=true >>> derby.language.logStatementText=true >>> derby.stream.error.logSeverityLevel=0 >>> >>> If it is the multiple jvm situation, then you will see a neat >>> starting message in derby.log & still get this error. If it's >>> something else, then possibly the database does not get opened at >>> all, and your derby.log would be an empty file even after >>> infolog.append is picked up from derby.properties. >>> >>> Now, why there would be 2 jvms trying to start the database - I >>> don't know...Does the ping start a second process/jvm? >>> >>> Another area to look at is the policy files. This is really a wild >>> guess....But make sure the following permissions are set for the >>> derby database: >>> grant codeBase "file:///derby.jar" { >>> permission java.lang.RuntimePermission "createClassLoader"; >>> permission java.util.PropertyPermission "derby.*", "read"; >>> permission java.io.FilePermission "${derby.system.home}${/} -", >>> "read,write,delete"; >>> >>> I hope this helps any.... >>> >>> Myrna >>> >>> >> Thank you much. I am sure that this is a bug on the Sun Appserver >> 8.0.1. A search of the Sun forum revealed that many users have seen >> the same Sun error with other products (non-Derby, or even db >> related). So, I guess I'll try their RC of the next version, to >> verify this. I am also thinking of using the Jonas (objectweb.org) >> appserver, but I don't know how to embed Derby within it. >> If anyone has used Jonas replacing HSQLDB (that comes with it) with >> Derby, please let me know. >> TA >> -nat > > >