3 Replies Latest reply on Dec 11, 2012 4:10 AM by Nicklas Karlsson

    https error under jboss 7

    mike just Master

      Hi all,

       

      I have met an issue related to https.

       

      I used below configuration for the https setting.

       

      <connector name="https" protocol="HTTP/1.1" scheme="https" socket-binding="https" secure="true">
                      <ssl key-alias="demo" password="Password1" certificate-key-file="${jboss.server.config.dir}/demo.keystore"/>
      </connector>
      
      

       

      Now I have got such error when starting jboss:

       

      2012-12-11 08:05:08,647;[MSC service thread 1-5];ERROR;org.apache.coyote.http11.Http11Protocol;Error initializing endpoint: java.io.IOException: Alias name demo does not identify a key entry
                at org.apache.tomcat.util.net.jsse.JSSESocketFactory.getKeyManagers(JSSESocketFactory.java:517)
                at org.apache.tomcat.util.net.jsse.JSSESocketFactory.init(JSSESocketFactory.java:452)
                at org.apache.tomcat.util.net.jsse.JSSESocketFactory.createSocket(JSSESocketFactory.java:168)
                at org.apache.tomcat.util.net.JIoEndpoint.init(JIoEndpoint.java:977)
                at org.apache.coyote.http11.Http11Protocol.init(Http11Protocol.java:190)
                at org.apache.catalina.connector.Connector.init(Connector.java:983)
                at org.jboss.as.web.WebConnectorService.start(WebConnectorService.java:267)
                at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811)
                at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746)
                at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
                at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
                at java.lang.Thread.run(Thread.java:662)
      
      
      2012-12-11 08:05:08,663;[MSC service thread 1-5];ERROR;org.jboss.msc.service.fail;MSC00001: Failed to start service jboss.web.connector.https: org.jboss.msc.service.StartException in service jboss.web.connector.https: JBAS018007: Error starting web connector
                at org.jboss.as.web.WebConnectorService.start(WebConnectorService.java:271)
                at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811)
                at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746)
                at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
                at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
                at java.lang.Thread.run(Thread.java:662)
      Caused by: LifecycleException:  Protocol handler initialization failed: java.io.IOException: Alias name demo does not identify a key entry
                at org.apache.catalina.connector.Connector.init(Connector.java:985)
                at org.jboss.as.web.WebConnectorService.start(WebConnectorService.java:267)
                ... 5 more
      
      

       

      Is it related to the "key-alias" attribute use?

       

      I checked the older version Jboss (4) which used to be working and found the configuration is like this

       

       

      <Connector port="444" address="${jboss.bind.address}"
                 maxThreads="100" minSpareThreads="5" maxSpareThreads="15"
                 scheme="https" secure="true" clientAuth="false"
                 keystoreFile="${jboss.server.home.dir}/conf/demo.keystore"
                 keystorePass="Password1" sslProtocol = "TLS" />
      
      

       

      Any thoughts on this case?