Return-Path: Delivered-To: apmail-db-derby-dev-archive@www.apache.org Received: (qmail 69931 invoked from network); 15 Mar 2005 11:30:49 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur-2.apache.org with SMTP; 15 Mar 2005 11:30:49 -0000 Received: (qmail 24578 invoked by uid 500); 15 Mar 2005 11:30:47 -0000 Delivered-To: apmail-db-derby-dev-archive@db.apache.org Received: (qmail 24538 invoked by uid 500); 15 Mar 2005 11:30:47 -0000 Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: List-Post: List-Id: Reply-To: "Derby Development" Delivered-To: mailing list derby-dev@db.apache.org Received: (qmail 24521 invoked by uid 99); 15 Mar 2005 11:30:47 -0000 X-ASF-Spam-Status: No, hits=0.1 required=10.0 tests=HTML_50_60,HTML_MESSAGE X-Spam-Check-By: apache.org Received-SPF: pass (hermes.apache.org: local policy) Received: from smtp.tele.fi (HELO smtp.tele.fi) (192.89.123.25) by apache.org (qpsmtpd/0.28) with ESMTP; Tue, 15 Mar 2005 03:30:44 -0800 Received: from amon (seth.inet.fi [193.210.21.197]) by smtp.tele.fi (Postfix) with SMTP id EAC9130E83 for ; Tue, 15 Mar 2005 13:30:39 +0200 (EET) Received: from mail.sysline.com[194.137.15.10]:3503 (EHLO mail.sysline.com) by amon ([192.168.100.3]:25) (F-Secure Anti-Virus for Internet Mail 6.41.150 Release) with SMTP; Tue, 15 Mar 2005 11:30:37 -0000 To: derby-dev@db.apache.org Subject: Re: Experimental JSR 169 patch and build instructions MIME-Version: 1.0 X-Mailer: Lotus Notes Release 6.5.2 June 01, 2004 Message-ID: From: "=?ISO-8859-1?Q?Niemel=E4_Jouni_=28Sysline=29?=" Date: Tue, 15 Mar 2005 13:32:44 +0200 X-MIMETrack: Serialize by Router on CINDY1/SYSLINE(Release 6.5.2|June 01, 2004) at 15.03.2005 13:32:45, Serialize complete at 15.03.2005 13:32:45 Content-Type: multipart/alternative; boundary="=_alternative 003F3795C2256FC5_=" X-Virus-Checked: Checked X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N This is a multipart message in MIME format. --=_alternative 003F3795C2256FC5_= Content-Type: text/plain; charset="US-ASCII" First of all I want to thank for the instructions and patch. I managed to patch Derby (revision 154375) by using using patch commands -l switch (patch -p0 -l experimental_jsr_169.patch). Some testing results: 1) Environment: Windows XP, IBM J9 (Foundation Frofile) - SimpleAppJSR169 example seems to work fine. - No significant problems with other simple test applications. 2) Environment: Linux (Fedora Core 3), J2ME CDC and Foundation Profile reference implementation ( http://www.sun.com/software/communitysource/j2me/cdc/download.xml). - SimpleAppJSR169 example failes in database creation. The last output lines on console I got were: WARNING - Experimental J2ME/CDC/Foundation/JSR 169 Derby implementation WARNING - NOT FOR USE IN PRODUCTION Process #16135 received signal 11 Process #16135 being suspended - Used CVM command line arguments with root access: bin/cvm -Xms64m -Xss4m -Xbootclasspath/a:/CDC/derby/lib/jdbc-cdc10.jar:/CDC/derby/lib/jce1_2_2.jar -Djava.class.path=derby.jar:SimpleAppJSR169.jar SimpleAppJSR169 - I realized that Derby created a log file called derby.log. According to log files content, there might be some problems with derby.database.classpath ? ---------------------------------------------------------------- 2005-03-15 09:11:58.929 GMT: Booting Derby version The Apache Software Foundation - Apache Derby - 10.1.0.0 alpha - (???): instance c013800d-0102-a57b-d263-000000326b8c on database directory /CDC/cdcfoundation/build/linux-i686/bin/derbyDB Database Class Loader started - derby.database.classpath='' - Also, the derbyDB directory was created after runnig the SimpleAppJSR169 example. The content of derbyDB: derbyDB/db.lck (size 38 bytes) derbyDB/dbex.lck (size 0 bytes) derbyDB/log/log.ctrl (size 48 bytes) derbyDB/log/log1.dat (size 492 bytes) derbyDB/log/logmirror.ctrl (size 48 bytes) derbyDB/seg0/c10.dat (size 4096 bytes) derbyDB/seg0/c20.dat (size 4096 bytes) derbyDB/seg0/c31.dat (size 4096 bytes) - After debuging for awhile, I'm rather sure the problem occurs on createDatabase method on class EmbedConnection. Probably class loading failes on BaseMonitor... private Database createDatabase(String dbname, Properties info) throws SQLException { info = filterProperties(info); try { if (Monitor.createPersistentService(Property.DATABASE_MODULE, dbname, info) == null) { // service already exists, create a warning addWarning(EmbedSQLWarning.newEmbedSQLWarning(SQLState.DATABASE_EXISTS, dbname)); } } catch (StandardException mse) { ... } Is there's any ideas what can done to solve the problem above? -- Jouni >I've managed to get Derby running with a simple test in >J2ME/CDC/Foundation/JSR 169. As promised here are the instructions and >patches to allow early testing. > >1) Obtain a J2ME/CDC/Foundation environment with JSR 169 libraries. > I used IBM's WCTME 5.7 (I'm employeed by IBM). > http://www.ibm.com/software/wireless/wctme/ > > I also found through google another J2ME CDC environment by Emsertec. > I have no experience with it. > http://www.esmertec.com/company/downloads/Jbed_CDC.pdf --=_alternative 003F3795C2256FC5_= Content-Type: text/html; charset="US-ASCII"
First of all I want to thank for the instructions and patch. I managed
to patch Derby (revision 154375) by using using patch commands -l switch
(patch -p0 -l experimental_jsr_169.patch).

Some testing results:

1) Environment: Windows XP, IBM J9 (Foundation Frofile)
   - SimpleAppJSR169 example seems to work fine.
   - No significant problems with other simple test applications.

2) Environment: Linux (Fedora Core 3), J2ME CDC and Foundation Profile reference implementation (http://www.sun.com/software/communitysource/j2me/cdc/download.xml).
   - SimpleAppJSR169 example failes in database creation. The last output lines on console I got were:
WARNING - Experimental J2ME/CDC/Foundation/JSR 169 Derby implementation
WARNING - NOT FOR USE IN PRODUCTION
Process #16135 received signal 11
Process #16135 being suspended
   - Used CVM command line arguments with root access:
     bin/cvm -Xms64m -Xss4m -Xbootclasspath/a:/CDC/derby/lib/jdbc-cdc10.jar:/CDC/derby/lib/jce1_2_2.jar -Djava.class.path=derby.jar:SimpleAppJSR169.jar SimpleAppJSR169
   - I realized that Derby created a log file called derby.log. According to log files content, there might be some problems with derby.database.classpath ?

<log file>
----------------------------------------------------------------
2005-03-15 09:11:58.929 GMT:
 Booting Derby version The Apache Software Foundation - Apache Derby - 10.1.0.0 alpha - (???): instance c013800d-0102-a57b-d263-000000326b8c
on database directory /CDC/cdcfoundation/build/linux-i686/bin/derbyDB

Database Class Loader started - derby.database.classpath=''
</log file>

   - Also, the derbyDB directory was created after runnig the SimpleAppJSR169 example.
     The content of derbyDB:
       derbyDB/db.lck             (size 38 bytes)
       derbyDB/dbex.lck           (size 0 bytes)
       derbyDB/log/log.ctrl       (size 48 bytes)
       derbyDB/log/log1.dat       (size 492 bytes)
       derbyDB/log/logmirror.ctrl (size 48 bytes)
       derbyDB/seg0/c10.dat       (size 4096 bytes)
       derbyDB/seg0/c20.dat       (size 4096 bytes)
       derbyDB/seg0/c31.dat       (size 4096 bytes)
   - After debuging for awhile, I'm rather sure the problem occurs on createDatabase method
     on class EmbedConnection. Probably class loading failes on BaseMonitor...

<EmbedConnection class>
        private Database createDatabase(String dbname, Properties info)
                throws SQLException {
                info = filterProperties(info);

                try {
                        if (Monitor.createPersistentService(Property.DATABASE_MODULE, dbname, info) == null)
                        {
                                // service already exists, create a warning
                                addWarning(EmbedSQLWarning.newEmbedSQLWarning(SQLState.DATABASE_EXISTS, dbname));
                        }
                } catch (StandardException mse) {
         ...
         }    
</EmbedConnection class>


Is there's any ideas what can done to solve the problem above?

-- Jouni
   

>I've managed to get Derby running with a simple test in
>J2ME/CDC/Foundation/JSR 169. As promised here are the instructions and
>patches to allow early testing.
>
>1) Obtain a J2ME/CDC/Foundation environment with JSR 169 libraries.
>   I used IBM's WCTME 5.7 (I'm employeed by IBM).
>    http://www.ibm.com/software/wireless/wctme/
>
>   I also found through google another J2ME CDC environment by Emsertec.
>   I have no experience with it.
>    http://www.esmertec.com/company/downloads/Jbed_CDC.pdf
--=_alternative 003F3795C2256FC5_=--