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
[EMAIL PROTECTED]
rwin.com
To
10/16/2006 01:42 "Derby Discussion"
PM <[email protected]>
cc
Please respond to Subject
"Derby Re: Derby 10.1.3.1 Embedded+Network
Discussion"
<[EMAIL PROTECTED]
ache.org>
Then you want to run NetWorkServer mode and not Embedded mode.
[EMAIL PROTECTED]
10/16/2006 01:58 PM
Please respond to "Derby Discussion"
To: [email protected]
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).
