You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by "Halley Pacheco de Oliveira (JIRA)" <de...@db.apache.org> on 2006/05/05 15:54:27 UTC

[jira] Created: (DERBY-1293) Derby Server and Administration Guide - derby.drda.startNetworkServer

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


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


[jira] Commented: (DERBY-1293) Derby Server and Administration Guide - derby.drda.startNetworkServer

Posted by "John H. Embretsen (JIRA)" <de...@db.apache.org>.
    [ http://issues.apache.org/jira/browse/DERBY-1293?page=comments#action_12378418 ] 

John H. Embretsen commented on DERBY-1293:
------------------------------------------

Halley Pacheco de Oliveira commented:
 
> 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."

I think this is too much to include in one sentence. 
Is it really necessary to say "unless it has already been started"? Isn't that obvious?
I also think "When you set derby.drda.startNetworkServer, the Network Server will automatically start when you start Derby. In this context, Derby Network Server will start when the embedded driver is loaded..." sounds a bit strange. I guess the two sentences will have to be merged. Anyway, the point of my suggestion was merely to indicate more clearly to the reader how to start Derby, since this was mentioned in the previous sentence. 

Besides, if we really want to include information about when the network server shuts down, I think we need to be a bit more careful with the wording, and put it in a separate paragraph.

Yes, it is true that the Network Server will shut down when the embedding application ends. However, the server also shuts down if 

a) the Derby system is shut down, for example:

ij> connect 'jdbc:derby:;shutdown=true';

or
b) the NetworkServerControl shutdown command is executed from the command line, for example:

$ java org.apache.derby.drda.NetworkServerControl shutdown

or
c) the NetworkServerControl shutdown method is invoked from a Java application, for example:

NetworkServerControl server = new NetworkServerControl();
server.shutdown();

Perhaps there are even more ways to do this...

So, things are more complicated than they seem at first glance. We can make it even more complicated by including some text about restarting the server after it has been shut down using a), b) ,c) or the end-of-application approach. With a) you can restart the server simply by reloading the embedded driver, with b) and c) you cannot do that (that is, until you actually "unload" the embedded driver first).

Unless we can come up with some generic statement which covers all shutdown options, I recommend not mentioning shutdown in this context. Having said that, I think it would be good to have a separate doc page with examples and explanations of things in this category. I think this is largely related to the new document that Stanley Bradbury is working on, see 
http://www.nabble.com/Re%3A-WWD-Review-of-Final-Chapters-%285-and-6%29-p4218805.html


> 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


Re: [jira] Commented: (DERBY-1293) Derby Server and Administration Guide - derby.drda.startNetworkServer

Posted by John Embretsen <Jo...@Sun.COM>.
Hi Jeff,

thanks for commenting; now let me recap and respond to your suggestions 
below...

derby@mylevita.com wrote:

> Hi John,  
> 
> This looks good to me.  Just from a consistency standpoint, having written almost all of the other documentation, there are a couple cosmetic changes I'd recommend to keep this similar to the rest of the writing:

Just to clarify a bit, can you give me a link to some manual pages 
justifying this consistency argument?

So you basically suggest:

1) removing the first paragraph:

"Use the derby.drda.startNetworkServer property to simplify embedding 
the Network Server in your Java application."

This sentence is part of the original manual page, I just added the word 
"Java". So I guess you are the original writer? Anyway, I thought this 
would help users understand why such a property exists, but the removal 
is OK with me if it helps preserving doc consistency.

> When you set derby.drda.startNetworkServer to true, the Network Server
> will automatically start with Derby (in this context, Derby
> will start when the embedded driver is loaded). Only one Network Server
> can be started in a JVM.

2) replacing "will automatically start when you start Derby" with "will 
automatically start with Derby".

Again, you suggest changing the original wording. I'm OK with it, 
although I think your suggestion is a tiny bit less clear to the reader 
than the original. Please justify why this is better, consistency-wise.

> 
> 
> NOTE:
> If you start the Network Server with this
> property, the Network Server will stop when your application ends or
> when you stop it by other means (e.g. by using the Java API or the
> command line interface, or by shutting down the Derby system, whichever
>  comes first).

3) changing "Please be aware that if the Network Server is started using 
this property" with "If you start the Network Server with this property".

Your suggestion is shorter and still sends the same message. I agree 
with this change.


4) moving ", whichever comes first" into the parenthesis.

This change does not make sense to me. The intention was to say that the 
server is stopped either when your application ends or when you stop the 
server by other means, whichever comes first. What is inside the 
parenthesis is just examples of other ways to stop an embedded Network 
Server (could be removed entirely, if it is a cause of confusion).



-- 
John

Re: [jira] Commented: (DERBY-1293) Derby Server and Administration Guide - derby.drda.startNetworkServer

Posted by de...@mylevita.com.
----- Original Message ----
From: John H. Embretsen (JIRA) <de...@db.apache.org>
To: derby-dev@db.apache.org
Sent: Wednesday, May 24, 2006 7:49:30 AM
Subject: [jira] Commented: (DERBY-1293) Derby Server and Administration Guide - derby.drda.startNetworkServer

    [ http://issues.apache.org/jira/browse/DERBY-1293?page=comments#action_12413131 ] 

John H. Embretsen commented on DERBY-1293:
------------------------------------------

Adding the most recent proposal from the derby-dev list (http://www.nabble.com/-jira-+Created%3A+%28DERBY-1293%29+Derby+Server+and+Administration+Guide+-+derby.drda.startNetworkServer-t1564099.html#a4247615) to this Jira-issue for review:

== START ==

Use the derby.drda.startNetworkServer property to simplify embedding the
Network Server in your Java application.

When you set derby.drda.startNetworkServer to true, the Network Server
will automatically start when you start Derby (in this context, Derby
will start when the embedded driver is loaded). Only one Network Server
can be started in a JVM.

NOTE:
Please be aware that if the Network Server is started using this
property, the Network Server will stop when your application ends or
when you stop it by other means (e.g. by using the Java API or the
command line interface, or by shutting down the Derby system), whichever
comes first.

== END ==


Hi John,  

This looks good to me.  Just from a consistency standpoint, having written almost all of the other documentation, there are a couple cosmetic changes I'd recommend to keep this similar to the rest of the writing:

When you set derby.drda.startNetworkServer to true, the Network Server
will automatically start with Derby (in this context, Derby
will start when the embedded driver is loaded). Only one Network Server
can be started in a JVM.


NOTE:
If you start the Network Server with this
property, the Network Server will stop when your application ends or
when you stop it by other means (e.g. by using the Java API or the
command line interface, or by shutting down the Derby system, whichever
 comes first).




[jira] Commented: (DERBY-1293) Derby Server and Administration Guide - derby.drda.startNetworkServer

Posted by "John H. Embretsen (JIRA)" <de...@db.apache.org>.
    [ http://issues.apache.org/jira/browse/DERBY-1293?page=comments#action_12413131 ] 

John H. Embretsen commented on DERBY-1293:
------------------------------------------

Adding the most recent proposal from the derby-dev list (http://www.nabble.com/-jira-+Created%3A+%28DERBY-1293%29+Derby+Server+and+Administration+Guide+-+derby.drda.startNetworkServer-t1564099.html#a4247615) to this Jira-issue for review:

== START ==

Use the derby.drda.startNetworkServer property to simplify embedding the
Network Server in your Java application.

When you set derby.drda.startNetworkServer to true, the Network Server
will automatically start when you start Derby (in this context, Derby
will start when the embedded driver is loaded). Only one Network Server
can be started in a JVM.

NOTE:
Please be aware that if the Network Server is started using this
property, the Network Server will stop when your application ends or
when you stop it by other means (e.g. by using the Java API or the
command line interface, or by shutting down the Derby system), whichever
comes first.

== END ==



> 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.2.0.0, 10.1.3.0
>  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


[jira] Updated: (DERBY-1293) Derby Server and Administration Guide - derby.drda.startNetworkServer

Posted by "Andrew McIntyre (JIRA)" <de...@db.apache.org>.
     [ http://issues.apache.org/jira/browse/DERBY-1293?page=all ]

Andrew McIntyre updated DERBY-1293:
-----------------------------------

    Fix Version: 10.2.0.0
                 10.1.3.0
                     (was: 10.1.2.3)

> 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.2.0.0, 10.1.3.0
>  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


[jira] Commented: (DERBY-1293) Derby Server and Administration Guide - derby.drda.startNetworkServer

Posted by "Halley Pacheco de Oliveira (JIRA)" <de...@db.apache.org>.
    [ http://issues.apache.org/jira/browse/DERBY-1293?page=comments#action_12413145 ] 

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

For me, it's perfect.

> 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.2.0.0, 10.1.3.0
>  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


[jira] Commented: (DERBY-1293) Derby Server and Administration Guide - derby.drda.startNetworkServer

Posted by "John H. Embretsen (JIRA)" <de...@db.apache.org>.
    [ http://issues.apache.org/jira/browse/DERBY-1293?page=comments#action_12415828 ] 

John H. Embretsen commented on DERBY-1293:
------------------------------------------

Thanks, Jean, for committing! :)
Halley, please close this issue if you are happy with the result...

> 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
>     Assignee: John H. Embretsen
>     Priority: Minor
>      Fix For: 10.2.0.0, 10.1.3.0
>  Attachments: DERBY-1293_v2.diff, radminconfigstartnetworkserver.diff, radminconfigstartnetworkserver.diff.html, radminconfigstartnetworkserver.html, radminconfigstartnetworkserver_v2.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


[jira] Assigned: (DERBY-1293) Derby Server and Administration Guide - derby.drda.startNetworkServer

Posted by "John H. Embretsen (JIRA)" <de...@db.apache.org>.
     [ http://issues.apache.org/jira/browse/DERBY-1293?page=all ]

John H. Embretsen reassigned DERBY-1293:
----------------------------------------

    Assign To: John H. Embretsen

> 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
>     Assignee: John H. Embretsen
>     Priority: Minor
>      Fix For: 10.2.0.0, 10.1.3.0
>  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


[jira] Resolved: (DERBY-1293) Derby Server and Administration Guide - derby.drda.startNetworkServer

Posted by "Jean T. Anderson (JIRA)" <de...@db.apache.org>.
     [ http://issues.apache.org/jira/browse/DERBY-1293?page=all ]
     
Jean T. Anderson resolved DERBY-1293:
-------------------------------------

    Resolution: Fixed
    Derby Info:   (was: [Patch Available])

I think the patch looks fine, definitely improves the wording. 
Committed DERBY-1293_v2.diff, revision 412634. Merged fix to 10.1 branch, revision 412636.

> 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
>     Assignee: John H. Embretsen
>     Priority: Minor
>      Fix For: 10.2.0.0, 10.1.3.0
>  Attachments: DERBY-1293_v2.diff, radminconfigstartnetworkserver.diff, radminconfigstartnetworkserver.diff.html, radminconfigstartnetworkserver.html, radminconfigstartnetworkserver_v2.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


Re: [jira] Commented: (DERBY-1293) Derby Server and Administration Guide - derby.drda.startNetworkServer

Posted by John Embretsen <Jo...@Sun.COM>.
Halley Pacheco de Oliveira (JIRA) wrote:

>     [ http://issues.apache.org/jira/browse/DERBY-1293?page=comments#action_12378433 ] 
> 
> Halley Pacheco de Oliveira commented on DERBY-1293:
> ---------------------------------------------------
> 
> The point I would like to emphasize is that the Network Server is linked to the application. 

So by "the application" you mean some Java application that is embedding
the Derby Network Server, right? (since you are mentioning loading the
embedded driver next)

> When the application starts (embedded driver is loaded), the Network Server starts, and when the application ends, the Network Server ends, but it only happens if the Network Server was not started before starting the application.

I still think we should treat starting and stopping the server
separately, or it will quickly become confusing and complicated. Yes,
the server will only be started if it was not already started before
starting the embedding application - that is obvious. And yes, the
server will probably not be stopped when the embedding application ends
if that particular application did not start the server in the first
place - that is less obvious, so I agree that it could be mentioned
somewhere.

However, this is already covered by the following statement under
"Static or dynamic" on the manual page in question:

"You must shut down the Network Server and restart Derby for this change
to take effect."

> People like me that all their lives used DB2, Oracle, SQL Server or even PostgreSQL are not used to this behavior. When one of these servers is started, it continues running after the application ends, and usually they start when the operating system boots. 

Hmm, ok, I understand. But Derby is pure Java, and Java programs do not
live longer than the JVM in which they run. When you embed a network
server in your Java application, it should not come as a surprise that
the server will stop when your application ends. A stand-alone network
server may be something else, but that is not what we are discussing
here. Anyway, I think we don't really disagree much here, so we should
be able to come up with a result we're all happy with pretty soon :)

By the way, I believe someone on derby-user has expressed a need to run
the Derby Network Server as a service in the OS, but I don't remember
the result of that inquiry.

> This dependency between the Network Server and an application is not natural for me, and in this case we are talking about a Network Server, not about an embedded server.

I am (and have been) talking about the Network Server as an embedded
server, since we are discussing the manual page for the
derby.drda.startNetworkServer property. I think we should limit this
discussion to that particular scenario.


Here is what I suggest:

== START ==

Use the derby.drda.startNetworkServer property to simplify embedding the
Network Server in your Java application.

When you set derby.drda.startNetworkServer to true, the Network Server
will automatically start when you start Derby (in this context, Derby
will start when the embedded driver is loaded). Only one Network Server
can be started in a JVM.

NOTE:
Please be aware that if the Network Server is started using this
property, the Network Server will stop when your application ends or
when you stop it by other means (e.g. by using the Java API or the
command line interface, or by shutting down the Derby system), whichever
comes first.

== END ==

Does this capture the points you wanted to make, Halley? I tried to keep
it as simple as possible...

I think the point that "It will only start if it has not already been
started by other means" is covered by the "Static or Dynamic" statement
at the bottom of the page.


-- 
John





[jira] Commented: (DERBY-1293) Derby Server and Administration Guide - derby.drda.startNetworkServer

Posted by "Halley Pacheco de Oliveira (JIRA)" <de...@db.apache.org>.
    [ http://issues.apache.org/jira/browse/DERBY-1293?page=comments#action_12378433 ] 

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

The point I would like to emphasize is that the Network Server is linked to the application. When the application starts (embedded driver is loaded), the Network Server starts, and when the application ends, the Network Server ends, but it only happens if the Network Server was not started before starting the application. People like me that all their lives used DB2, Oracle, SQL Server or even PostgreSQL are not used to this behavior. When one of these servers is started, it continues running after the application ends, and usually they start when the operating system boots. This dependency between the Network Server and an application is not natural for me, and in this case we are talking about a Network Server, not about an embedded server.

> 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


[jira] Updated: (DERBY-1293) Derby Server and Administration Guide - derby.drda.startNetworkServer

Posted by "Halley Pacheco de Oliveira (JIRA)" <de...@db.apache.org>.
     [ http://issues.apache.org/jira/browse/DERBY-1293?page=all ]

Halley Pacheco de Oliveira updated DERBY-1293:
----------------------------------------------

    Attachment: radminconfigstartnetworkserver.diff
                radminconfigstartnetworkserver.diff.html
                radminconfigstartnetworkserver.html

The diff file, the HTMLized diff file and the new manual page.

> 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


[jira] Updated: (DERBY-1293) Derby Server and Administration Guide - derby.drda.startNetworkServer

Posted by "John H. Embretsen (JIRA)" <de...@db.apache.org>.
     [ http://issues.apache.org/jira/browse/DERBY-1293?page=all ]

John H. Embretsen updated DERBY-1293:
-------------------------------------

    Attachment: DERBY-1293_v2.diff
                radminconfigstartnetworkserver_v2.html

Attaching patch (and resulting html output) to function as a compromise between most comments to this issue so far, with hopes that this issue can eventually be resolved and closed. Please review, and commit if all is well:

DERBY-1293_v2.diff
radminconfigstartnetworkserver_v2.html

I have not seen any response to http://article.gmane.org/gmane.comp.apache.db.derby.devel/20833, so I have not included all the consistency-related suggestions in the patch.



> 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
>     Assignee: John H. Embretsen
>     Priority: Minor
>      Fix For: 10.2.0.0, 10.1.3.0
>  Attachments: DERBY-1293_v2.diff, radminconfigstartnetworkserver.diff, radminconfigstartnetworkserver.diff.html, radminconfigstartnetworkserver.html, radminconfigstartnetworkserver_v2.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


[jira] Commented: (DERBY-1293) Derby Server and Administration Guide - derby.drda.startNetworkServer

Posted by "John H. Embretsen (JIRA)" <de...@db.apache.org>.
    [ http://issues.apache.org/jira/browse/DERBY-1293?page=comments#action_12378041 ] 

John H. Embretsen commented on DERBY-1293:
------------------------------------------

Would adding

"In this context, Derby will start when the embedded driver is loaded."

be a good idea? This was not obvious to me the first time I read about that property, so I'm just thinking that the additional info might be useful to others.

I assume there is no other way of starting Derby in the embedded-server-using-properties scenario. Please speak up if my assumption is wrong.


> 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


[jira] Commented: (DERBY-1293) Derby Server and Administration Guide - derby.drda.startNetworkServer

Posted by "Halley Pacheco de Oliveira (JIRA)" <de...@db.apache.org>.
    [ 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


[jira] Closed: (DERBY-1293) Derby Server and Administration Guide - derby.drda.startNetworkServer

Posted by "Halley Pacheco de Oliveira (JIRA)" <de...@db.apache.org>.
     [ http://issues.apache.org/jira/browse/DERBY-1293?page=all ]
     
Halley Pacheco de Oliveira closed DERBY-1293:
---------------------------------------------


Hi John,
I'm happy with the result. This issue is closed.
Thanks,
Halley

> 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
>     Assignee: John H. Embretsen
>     Priority: Minor
>      Fix For: 10.2.0.0, 10.1.3.0
>  Attachments: DERBY-1293_v2.diff, radminconfigstartnetworkserver.diff, radminconfigstartnetworkserver.diff.html, radminconfigstartnetworkserver.html, radminconfigstartnetworkserver_v2.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