Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Message-ID: <1040941934.1129845171461.JavaMail.jira@ajax.apache.org>
Date: Thu, 20 Oct 2005 23:52:51 +0200 (CEST)
From: "Deepa Remesh (JIRA)" <derby-dev@db.apache.org>
To: derby-dev@db.apache.org
Subject: [jira] Updated: (DERBY-375) Specification of incomplete server
 properties on command line causes NPE with NetworkServerControl when starting
 the server.
In-Reply-To: <1695827227.1119165198678.JavaMail.jira@ajax.apache.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

     [ http://issues.apache.org/jira/browse/DERBY-375?page=all ]

Deepa Remesh updated DERBY-375:
-------------------------------

    Fix Version: 10.1.2.0

I merged this fix to my 10.1 codeline and ran derbyall with Sun JDK 1.4.2 on Windows XP. 2 failures:
derbyall/derbyall.fail:unit/T_Diagnosticable.unit (This test passed when I re-ran it)
derbyall/derbyall.fail:i18n/iepnegativetests_ES.sql (master update issue)

Merge command:
svn merge -r 321273:321274 https://svn.apache.org/repos/asf/db/derby/code/trunk
svn merge -r 326288:326289 https://svn.apache.org/repos/asf/db/derby/code/trunk

Please merge this to 10.1 branch. Thanks.


> Specification of incomplete server properties on command line causes NPE with NetworkServerControl when starting the server.
> ----------------------------------------------------------------------------------------------------------------------------
>
>          Key: DERBY-375
>          URL: http://issues.apache.org/jira/browse/DERBY-375
>      Project: Derby
>         Type: Bug
>   Components: Network Server
>     Versions: 10.2.0.0, 10.1.1.0
>  Environment: Running Derby Network Server and using command line API to start the server.
>     Reporter: A B
>     Assignee: Deepa Remesh
>      Fix For: 10.2.0.0, 10.1.2.0
>  Attachments: derby-375.diff, derby-375.status, derbyall_report.txt
>
> When using the command line to start the Network Server, there a couple of cases where if a property is specified on the command line but no value is given (ex. "-Dderby.drda.maxThreads" instead of "-Dderby.drda.maxThreads=3"), a Null Pointer Exception will result, when the correct behavior should be to use some kind of default.
> For example:
> > java -Dderby.drda.maxThreads org.apache.derby.drda.NetworkServerControl start -p 1528
> java.lang.NullPointerException
>         at org.apache.derby.impl.drda.NetworkServerControlImpl.localizeMessage(NetworkServerControlImpl.java)
>         at org.apache.derby.impl.drda.NetworkServerControlImpl.consolePropertyMessageWork(NetworkServerControlImpl.java)
>         at org.apache.derby.impl.drda.NetworkServerControlImpl.consolePropertyMessage(NetworkServerControlImpl.java)
>         at org.apache.derby.impl.drda.NetworkServerControlImpl.getIntPropVal(NetworkServerControlImpl.java)
>         at org.apache.derby.impl.drda.NetworkServerControlImpl.getPropertyInfo(NetworkServerControlImpl.java)
>         at org.apache.derby.impl.drda.NetworkServerControlImpl.<init>(NetworkServerControlImpl.java)
>         at org.apache.derby.drda.NetworkServerControl.main(NetworkServerControl.java)
> Note that even though we see this NPE, it appears that the server still starts up, although the startup may not be complete (subsequent attempts to connect  might lead to errors like "Invalid reply from network server: Insufficient data.").
> For other properties, this will just result in the default value being used, which is the correct behavior.  For example:
> > java -Dderby.drda.host org.apache.derby.drda.NetworkServerControl start -p 1528
> Server is ready to accept connections on port 1528.

-- 
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