Return-Path: Delivered-To: apmail-db-derby-user-archive@www.apache.org Received: (qmail 80178 invoked from network); 16 Oct 2006 18:57:14 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 16 Oct 2006 18:57:14 -0000 Received: (qmail 12095 invoked by uid 500); 16 Oct 2006 18:57:13 -0000 Delivered-To: apmail-db-derby-user-archive@db.apache.org Received: (qmail 12069 invoked by uid 500); 16 Oct 2006 18:57:13 -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 12058 invoked by uid 99); 16 Oct 2006 18:57:13 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 16 Oct 2006 11:57:13 -0700 X-ASF-Spam-Status: No, hits=0.6 required=10.0 tests=NO_REAL_NAME X-Spam-Check-By: apache.org Received-SPF: pass (asf.osuosl.org: local policy) Received: from [12.14.247.132] (HELO www.oreillyauto.com) (12.14.247.132) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 16 Oct 2006 11:57:09 -0700 Received: from domlx2.oreillyauto.com ([192.168.0.3]) by www.oreillyauto.com (Lotus Domino Release 6.5.5) with ESMTP id 2006101613564723-4648 ; Mon, 16 Oct 2006 13:56:47 -0500 In-Reply-To: Subject: Re: Derby 10.1.3.1 Embedded+Network To: "Derby Discussion" X-Mailer: Lotus Notes Release 6.5.3 September 14, 2004 Message-ID: From: mballard@oreillyauto.com Date: Mon, 16 Oct 2006 13:57:46 -0500 MIME-Version: 1.0 X-MIMETrack: Serialize by Router on domlx2/OReilly(Release 6.5.5FP1 | May 17, 2006) at 10/16/2006 13:56:46, Itemize by SMTP Server on Domsvr/OReilly(Release 6.5.5|November 30, 2005) at 10/16/2006 13:56:47, Serialize by Router on Domsvr/OReilly(Release 6.5.5|November 30, 2005) at 10/16/2006 13:57:08, Serialize complete at 10/16/2006 13:57:08 Content-type: text/plain; charset=US-ASCII X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N However, based on various documentation I have read, it appears the best of both worlds is Embedded+Network mode, and, unless there is some other doc which says this is a limitation in this mode, then it seems this should be a workable solution. This should allow Tomcat5 to realize the benefits of embedded mode, while not restricting other (non-tomcat) users access to the derby system. Thanks, MikeB Mike Ballard Director of Internet Development and Networking O'Reilly Auto Parts (417) 874-7107 Ofc (417) 838-0271 Cell michael.mouer@she rwin.com To 10/16/2006 01:42 "Derby Discussion" PM cc Please respond to Subject "Derby Re: Derby 10.1.3.1 Embedded+Network Discussion" Then you want to run NetWorkServer mode and not Embedded mode. mballard@oreillyauto.com 10/16/2006 01:58 PM Please respond to "Derby Discussion" To: derby-user@db.apache.org cc: Subject: Derby 10.1.3.1 Embedded+Network I have configured Derby to run in embedded mode, including starting the Network Framework, within Tomcat5. Everything works fine, except that when I connect to the Network framework, ie, via ij or from another machine on the network, using a query tool, I seem to only get a Read-Only connection. If I drop Tomcat (& the embedded instance of Derby) and start a pure NetworkServer instance then I can get a read-write connection. My goal is to run Derby embedded in Tomcat, while still having the luxury of accessing Derby via the network for queries, maintenance, etc. Thanks for any help. -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean (415FBF6D63.53F1C).