geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Shiny Cheng (JIRA)" <>
Subject [jira] Created: (GERONIMO-4856) Some abnormal conditions with Tomcat NIO HTTPS Connector
Date Wed, 09 Sep 2009 02:41:57 GMT
Some abnormal conditions with Tomcat NIO HTTPS Connector

                 Key: GERONIMO-4856
             Project: Geronimo
          Issue Type: Bug
      Security Level: public (Regular issues)
          Components: Tomcat
    Affects Versions: 2.2
         Environment: win server 2008, jdk 1.6
            Reporter: Shiny Cheng
             Fix For: 2.2

These conditions happen when creating a new Tomcat NIO HTTPS Connector and trying to access

First of all, the basic path of "keystoreFile" will change during configuring. At the first
time, it's set to <geronimo_home>\var\catalina. Once your input can't help server to
find configured file, and you try to edit the connector. You will find this time, its basic
path is <geronimo_home> instead of the previous one. 

After set corresponding parameters, for instance, set UniqueName, keystoreFile, port and keystorePass,
then save the settings and try to access it via https://localhost:<prot>/console. You
will find the following error recorded in geronimo.log.
ERROR [NioEndpoint] java.lang.NullPointerException
And under some circumstances, this error will be shown in command line circularly and constantly
at a high speed that geronimo.log will be full within several seconds.  However, the latter
kind of condition is not stable reproduced. 

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message