Hi all,
Following is a rough test report with the latest JServ on Win95.
I cannot spend more time on it, not even finding the right person to
send this to but I wish to share the info hoping someone will pick it
up and use it:

Installation attempt 15/06/99 reveals:
- In automatic operation, class JServ does not start successfully
  - Consequently(?), no errors originating from class JServ were
    visible in the error log file.
- In standalone mode operation, NullPointer Exception on
  security.secretKey file although the setting in
conf\jserv.properties
  is security.authentication=false as per default and the
configuration
  line security.secretKey=... was commented out as per default.
- Consequent Java Source code changes ("bt-test")
  in JServ.java in start()
    if (authenticate) {
        if (log.active) log.log(CH_INIT, "Enable connection
authentication");
  to:
    if (false) {//bt-test
        if (log.active) log.log(CH_INIT, "Enable connection
authentication");

  reveal that file jserv.properties
  was not processed correctly and the search for the
security.secretKey file
  was a consequence of a default setting that could not be overridden
  by the missing config information. So why is there no error message
for
  this situation?
  
  Further up at the beginning of start() I modified code:
  
      // Load configuration parameters
    try {
        confs = new Configurations(new ExtendedProperties(confFile));
    } catch (IOException e) {
        System.out.println("Error while reading configuration
file");//bt-test
        fail("Error while reading configuration file", e);
    }
    
    //bt-test start: Dump configutration
    Hashtable testRep=confs.getRepository();
    Enumeration repEnum=testRep.elements();
    while(repEnum.hasMoreElements()){
        System.out.println(repEnum.nextElement());
    }
    //bt-test end: Dump configutration

  
  That revealed that the configuration file was found but no
configuration
  data was available because the hashtable repEnum is empty.
  
  
  Further down in the code I modified the test that looks for servlet
zones:
  
    //if (zones == null) {//original
        fail("No servlet zones defined in configuration
file");//original
    }//original

    if (zones != null && zones.hasMoreElements()) {//bt-test
    }else{//bt-test
        fail("No servlet zones defined in configuration
file");//bt-test
    }//bt-test
    
    
  The modified code prints the error.
  Similar code would be needed earlier in the process to report
missing
  configuration - for whatever reason - not known at this stage.



--
--------------------------------------------------------------
To subscribe:        [EMAIL PROTECTED]
To unsubscribe:      [EMAIL PROTECTED]
READ THE FAQ!!!!     <http://java.apache.org/faq/>
Archives and Other:  <http://java.apache.org/main/mail.html/>
Problems?:           [EMAIL PROTECTED]

Reply via email to