You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@geronimo.apache.org by "Ghetolay (JIRA)" <ji...@apache.org> on 2012/05/16 11:05:02 UTC
[jira] [Created] (GERONIMO-6350) Edit TomcatHttpsConnector's
keystore configuration
Ghetolay created GERONIMO-6350:
----------------------------------
Summary: Edit TomcatHttpsConnector's keystore configuration
Key: GERONIMO-6350
URL: https://issues.apache.org/jira/browse/GERONIMO-6350
Project: Geronimo
Issue Type: Bug
Security Level: public (Regular issues)
Components: Tomcat, webservices
Affects Versions: 3.0-beta-1
Environment: Fresh geronimo 3.0-beta-1 with sun-java-6 on linux mint Lisa.
JAVA_HOME set to jdk.
Reporter: Ghetolay
Priority: Minor
Once you've edit the keystore configuration (file/alias/passphrase) of the TomcatHttpsConnector the server is unreachable for this specific port.
The only logs from both geronimo.log and .out are :
2012-05-16 10:42:43,162 ERROR [JIoEndpoint]
java.lang.NullPointerException
at org.apache.tomcat.util.net.JIoEndpoint.processSocket(JIoEndpoint.java:504)
at org.apache.tomcat.util.net.JIoEndpoint$Acceptor.run(JIoEndpoint.java:223)
at java.lang.Thread.run(Thread.java:662)
The only workaround I've found is delete the connector, restart geronimo and recreate the connector. It has to be done at each shutdown of geronimo.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (GERONIMO-6350) Edit TomcatHttpsConnector's
keystore configuration
Posted by "Ghetolay (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GERONIMO-6350?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13276659#comment-13276659 ]
Ghetolay commented on GERONIMO-6350:
------------------------------------
Ok. I did the change on /var/catalina/server.xml while the server was down and it worked.
Is there others values wich cannot be changed while the connector is running ?
> Edit TomcatHttpsConnector's keystore configuration
> --------------------------------------------------
>
> Key: GERONIMO-6350
> URL: https://issues.apache.org/jira/browse/GERONIMO-6350
> Project: Geronimo
> Issue Type: Bug
> Security Level: public(Regular issues)
> Components: Tomcat, webservices
> Affects Versions: 3.0-beta-1
> Environment: Fresh geronimo 3.0-beta-1 with sun-java-6 on linux mint Lisa.
> JAVA_HOME set to jdk.
> Reporter: Ghetolay
> Priority: Minor
> Labels: newbie
>
> Once you've edit the keystore configuration (file/alias/passphrase) of TomcatHttpsConnector through the webconsole, the server is unreachable for this specific port and protocol.
> The only logs from both geronimo.log and .out are :
> 2012-05-16 10:42:43,162 ERROR [JIoEndpoint]
> java.lang.NullPointerException
> at org.apache.tomcat.util.net.JIoEndpoint.processSocket(JIoEndpoint.java:504)
> at org.apache.tomcat.util.net.JIoEndpoint$Acceptor.run(JIoEndpoint.java:223)
> at java.lang.Thread.run(Thread.java:662)
> The only workaround I've found is delete the connector, restart geronimo and recreate the connector. It has to be done at each shutdown of geronimo.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Comment Edited] (GERONIMO-6350) Edit TomcatHttpsConnector's
keystore configuration
Posted by "Ghetolay (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GERONIMO-6350?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13276659#comment-13276659 ]
Ghetolay edited comment on GERONIMO-6350 at 5/16/12 10:56 AM:
--------------------------------------------------------------
Ok. I did the change on /var/catalina/server.xml while the server was down and it worked.
Is there others attributes wich cannot be changed while the connector is running ?
was (Author: ghetolay):
Ok. I did the change on /var/catalina/server.xml while the server was down and it worked.
Is there others values wich cannot be changed while the connector is running ?
> Edit TomcatHttpsConnector's keystore configuration
> --------------------------------------------------
>
> Key: GERONIMO-6350
> URL: https://issues.apache.org/jira/browse/GERONIMO-6350
> Project: Geronimo
> Issue Type: Bug
> Security Level: public(Regular issues)
> Components: Tomcat, webservices
> Affects Versions: 3.0-beta-1
> Environment: Fresh geronimo 3.0-beta-1 with sun-java-6 on linux mint Lisa.
> JAVA_HOME set to jdk.
> Reporter: Ghetolay
> Priority: Minor
> Labels: newbie
>
> Once you've edit the keystore configuration (file/alias/passphrase) of TomcatHttpsConnector through the webconsole, the server is unreachable for this specific port and protocol.
> The only logs from both geronimo.log and .out are :
> 2012-05-16 10:42:43,162 ERROR [JIoEndpoint]
> java.lang.NullPointerException
> at org.apache.tomcat.util.net.JIoEndpoint.processSocket(JIoEndpoint.java:504)
> at org.apache.tomcat.util.net.JIoEndpoint$Acceptor.run(JIoEndpoint.java:223)
> at java.lang.Thread.run(Thread.java:662)
> The only workaround I've found is delete the connector, restart geronimo and recreate the connector. It has to be done at each shutdown of geronimo.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (GERONIMO-6350) Edit TomcatHttpsConnector's
keystore configuration
Posted by "Forrest Xia (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GERONIMO-6350?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13276621#comment-13276621 ]
Forrest Xia commented on GERONIMO-6350:
---------------------------------------
You must want to change the connector which is currently in serve status, for example, 8443, we don't support to change the one in running status. To achieve that, you may need to shutdown server first, then update the https connector settings, and then start the server again.
> Edit TomcatHttpsConnector's keystore configuration
> --------------------------------------------------
>
> Key: GERONIMO-6350
> URL: https://issues.apache.org/jira/browse/GERONIMO-6350
> Project: Geronimo
> Issue Type: Bug
> Security Level: public(Regular issues)
> Components: Tomcat, webservices
> Affects Versions: 3.0-beta-1
> Environment: Fresh geronimo 3.0-beta-1 with sun-java-6 on linux mint Lisa.
> JAVA_HOME set to jdk.
> Reporter: Ghetolay
> Priority: Minor
> Labels: newbie
>
> Once you've edit the keystore configuration (file/alias/passphrase) of TomcatHttpsConnector through the webconsole, the server is unreachable for this specific port and protocol.
> The only logs from both geronimo.log and .out are :
> 2012-05-16 10:42:43,162 ERROR [JIoEndpoint]
> java.lang.NullPointerException
> at org.apache.tomcat.util.net.JIoEndpoint.processSocket(JIoEndpoint.java:504)
> at org.apache.tomcat.util.net.JIoEndpoint$Acceptor.run(JIoEndpoint.java:223)
> at java.lang.Thread.run(Thread.java:662)
> The only workaround I've found is delete the connector, restart geronimo and recreate the connector. It has to be done at each shutdown of geronimo.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (GERONIMO-6350) Edit TomcatHttpsConnector's
keystore configuration
Posted by "Ghetolay (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GERONIMO-6350?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ghetolay updated GERONIMO-6350:
-------------------------------
Description:
Once you've edit the keystore configuration (file/alias/passphrase) of TomcatHttpsConnector through the webconsole, the server is unreachable for this specific port and protocol.
The only logs from both geronimo.log and .out are :
2012-05-16 10:42:43,162 ERROR [JIoEndpoint]
java.lang.NullPointerException
at org.apache.tomcat.util.net.JIoEndpoint.processSocket(JIoEndpoint.java:504)
at org.apache.tomcat.util.net.JIoEndpoint$Acceptor.run(JIoEndpoint.java:223)
at java.lang.Thread.run(Thread.java:662)
The only workaround I've found is delete the connector, restart geronimo and recreate the connector. It has to be done at each shutdown of geronimo.
was:
Once you've edit the keystore configuration (file/alias/passphrase) of the TomcatHttpsConnector the server is unreachable for this specific port.
The only logs from both geronimo.log and .out are :
2012-05-16 10:42:43,162 ERROR [JIoEndpoint]
java.lang.NullPointerException
at org.apache.tomcat.util.net.JIoEndpoint.processSocket(JIoEndpoint.java:504)
at org.apache.tomcat.util.net.JIoEndpoint$Acceptor.run(JIoEndpoint.java:223)
at java.lang.Thread.run(Thread.java:662)
The only workaround I've found is delete the connector, restart geronimo and recreate the connector. It has to be done at each shutdown of geronimo.
> Edit TomcatHttpsConnector's keystore configuration
> --------------------------------------------------
>
> Key: GERONIMO-6350
> URL: https://issues.apache.org/jira/browse/GERONIMO-6350
> Project: Geronimo
> Issue Type: Bug
> Security Level: public(Regular issues)
> Components: Tomcat, webservices
> Affects Versions: 3.0-beta-1
> Environment: Fresh geronimo 3.0-beta-1 with sun-java-6 on linux mint Lisa.
> JAVA_HOME set to jdk.
> Reporter: Ghetolay
> Priority: Minor
> Labels: newbie
>
> Once you've edit the keystore configuration (file/alias/passphrase) of TomcatHttpsConnector through the webconsole, the server is unreachable for this specific port and protocol.
> The only logs from both geronimo.log and .out are :
> 2012-05-16 10:42:43,162 ERROR [JIoEndpoint]
> java.lang.NullPointerException
> at org.apache.tomcat.util.net.JIoEndpoint.processSocket(JIoEndpoint.java:504)
> at org.apache.tomcat.util.net.JIoEndpoint$Acceptor.run(JIoEndpoint.java:223)
> at java.lang.Thread.run(Thread.java:662)
> The only workaround I've found is delete the connector, restart geronimo and recreate the connector. It has to be done at each shutdown of geronimo.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (GERONIMO-6350) Edit TomcatHttpsConnector's
keystore configuration
Posted by "Ghetolay (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GERONIMO-6350?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13276636#comment-13276636 ]
Ghetolay commented on GERONIMO-6350:
------------------------------------
Yes, I'm editing the running connector. What's the edit menu made for so ?
> Edit TomcatHttpsConnector's keystore configuration
> --------------------------------------------------
>
> Key: GERONIMO-6350
> URL: https://issues.apache.org/jira/browse/GERONIMO-6350
> Project: Geronimo
> Issue Type: Bug
> Security Level: public(Regular issues)
> Components: Tomcat, webservices
> Affects Versions: 3.0-beta-1
> Environment: Fresh geronimo 3.0-beta-1 with sun-java-6 on linux mint Lisa.
> JAVA_HOME set to jdk.
> Reporter: Ghetolay
> Priority: Minor
> Labels: newbie
>
> Once you've edit the keystore configuration (file/alias/passphrase) of TomcatHttpsConnector through the webconsole, the server is unreachable for this specific port and protocol.
> The only logs from both geronimo.log and .out are :
> 2012-05-16 10:42:43,162 ERROR [JIoEndpoint]
> java.lang.NullPointerException
> at org.apache.tomcat.util.net.JIoEndpoint.processSocket(JIoEndpoint.java:504)
> at org.apache.tomcat.util.net.JIoEndpoint$Acceptor.run(JIoEndpoint.java:223)
> at java.lang.Thread.run(Thread.java:662)
> The only workaround I've found is delete the connector, restart geronimo and recreate the connector. It has to be done at each shutdown of geronimo.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Closed] (GERONIMO-6350) Edit TomcatHttpsConnector's
keystore configuration
Posted by "Ghetolay (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GERONIMO-6350?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ghetolay closed GERONIMO-6350.
------------------------------
Resolution: Not A Problem
> Edit TomcatHttpsConnector's keystore configuration
> --------------------------------------------------
>
> Key: GERONIMO-6350
> URL: https://issues.apache.org/jira/browse/GERONIMO-6350
> Project: Geronimo
> Issue Type: Bug
> Security Level: public(Regular issues)
> Components: Tomcat, webservices
> Affects Versions: 3.0-beta-1
> Environment: Fresh geronimo 3.0-beta-1 with sun-java-6 on linux mint Lisa.
> JAVA_HOME set to jdk.
> Reporter: Ghetolay
> Priority: Minor
> Labels: newbie
>
> Once you've edit the keystore configuration (file/alias/passphrase) of TomcatHttpsConnector through the webconsole, the server is unreachable for this specific port and protocol.
> The only logs from both geronimo.log and .out are :
> 2012-05-16 10:42:43,162 ERROR [JIoEndpoint]
> java.lang.NullPointerException
> at org.apache.tomcat.util.net.JIoEndpoint.processSocket(JIoEndpoint.java:504)
> at org.apache.tomcat.util.net.JIoEndpoint$Acceptor.run(JIoEndpoint.java:223)
> at java.lang.Thread.run(Thread.java:662)
> The only workaround I've found is delete the connector, restart geronimo and recreate the connector. It has to be done at each shutdown of geronimo.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (GERONIMO-6350) Edit TomcatHttpsConnector's
keystore configuration
Posted by "Ghetolay (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GERONIMO-6350?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ghetolay updated GERONIMO-6350:
-------------------------------
Comment: was deleted
(was: Yes, I'm editing the running connector. What's the edit menu made for so ?)
> Edit TomcatHttpsConnector's keystore configuration
> --------------------------------------------------
>
> Key: GERONIMO-6350
> URL: https://issues.apache.org/jira/browse/GERONIMO-6350
> Project: Geronimo
> Issue Type: Bug
> Security Level: public(Regular issues)
> Components: Tomcat, webservices
> Affects Versions: 3.0-beta-1
> Environment: Fresh geronimo 3.0-beta-1 with sun-java-6 on linux mint Lisa.
> JAVA_HOME set to jdk.
> Reporter: Ghetolay
> Priority: Minor
> Labels: newbie
>
> Once you've edit the keystore configuration (file/alias/passphrase) of TomcatHttpsConnector through the webconsole, the server is unreachable for this specific port and protocol.
> The only logs from both geronimo.log and .out are :
> 2012-05-16 10:42:43,162 ERROR [JIoEndpoint]
> java.lang.NullPointerException
> at org.apache.tomcat.util.net.JIoEndpoint.processSocket(JIoEndpoint.java:504)
> at org.apache.tomcat.util.net.JIoEndpoint$Acceptor.run(JIoEndpoint.java:223)
> at java.lang.Thread.run(Thread.java:662)
> The only workaround I've found is delete the connector, restart geronimo and recreate the connector. It has to be done at each shutdown of geronimo.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira