db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Halley Pacheco de Oliveira (JIRA)" <derby-...@db.apache.org>
Subject [jira] Commented: (DERBY-1293) Derby Server and Administration Guide - derby.drda.startNetworkServer
Date Fri, 05 May 2006 20:11:28 GMT
    [ http://issues.apache.org/jira/browse/DERBY-1293?page=comments#action_12378129 ] 

Halley Pacheco de Oliveira commented on DERBY-1293:
---------------------------------------------------

In my opinion John H. Embretsen's sentence could be longer, something like:

"In this context, Derby Network Server will start when the embedded driver is loaded, unless
it has already been started, and it will shutdown when the application ends, even if other
applications are connected to Derby Network Server, in the case it was started by the application."

That was my conclusion after adding derby.drda.startNetworkServer=true to derby.properties
file, and using the command

java -Dij.driver=org.apache.derby.jdbc.EmbeddedDriver -Dderby.system.home=$DERBY_INSTALL/frameworks/NetworkServer/bin
org.apache.derby.tools.ij

in two terminals in derby.system.home directory.

Terminal 1:

java -Dij.driver=org.apache.derby.jdbc.EmbeddedDriver -Dderby.system.home=$DERBY_INSTALL/frameworks/NetworkServer/bin
org.apache.derby.tools.ij
ij version 10.1
ij> connect 'jdbc:derby:sample';
ij>

Terminal 2:

java -Dij.driver=org.apache.derby.jdbc.EmbeddedDriver -Dderby.system.home=$DERBY_INSTALL/frameworks/NetworkServer/bin
org.apache.derby.tools.ij
ij version 10.1
ij> connect 'jdbc:derby:sample';
ERROR XJ040: Failed to start database 'sample', see the next exception for details.
ERROR XSDB6: Another instance of Derby may have already booted the database /usr/local/derby/frameworks/NetworkServer/bin/sample.
ij> connect 'jdbc:derby://localhost/sample';
ij> SELECT current_timestamp FROM sysibm.sysdummy1;
1
--------------------------
2006-05-05 16:52:19.196

1 row selected

Terminal 1:

ij> exit;

Terminal 2:

ij> SELECT current_timestamp FROM sysibm.sysdummy1;
ERROR (no SQLState): A communication error has been detected. Communication protocol being
used: Reply.fill(). Communication API being used: InputStream.read(). Location where the error
was detected: insufficient data. Communication function detecting the error: *. Protocol specific
error codes(s) TCP/IP SOCKETS


> Derby Server and Administration Guide - derby.drda.startNetworkServer
> ---------------------------------------------------------------------
>
>          Key: DERBY-1293
>          URL: http://issues.apache.org/jira/browse/DERBY-1293
>      Project: Derby
>         Type: Bug

>   Components: Documentation
>     Versions: 10.1.2.3
>  Environment: DITA-sourced documentation
>     Reporter: Halley Pacheco de Oliveira
>     Priority: Minor
>      Fix For: 10.1.2.3
>  Attachments: radminconfigstartnetworkserver.diff, radminconfigstartnetworkserver.diff.html,
radminconfigstartnetworkserver.html
>
> In this page is written:
> When you set derby.drda.startNetworkServer, the Network Server will automatically start
when you start Derby.
> but I think that
> When you set derby.drda.startNetworkServer to true, the Network Server will automatically
start when you start Derby.
> would be better, because "to true" should be explicit instead of implicit as it is in
the original text.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


Mime
View raw message