Unable to access HTTPS URL of Publisher after SP13 installation | Community
Skip to main content
G
gspatil11-1
Level 2
December 8, 2022
Solved

Unable to access HTTPS URL of Publisher after SP13 installation

  • December 8, 2022
  • 1 reply
  • 1750 views

Hi Team,


We are not able to access HTTPS URL of Publisher but HTTP URL is accessible fine. This issue has started after Service Pack13(SP 13) installation on AEM 6.5.5.0 version.

We have enabled debug logging for org.apache.felix.http and able to see below syntax issue. But no much pointers on how to resolve this issue.

28.11.2022 04:20:53.352 *ERROR* [CM Configuration Updater (ManagedService Update: pid=[org.apache.felix.http])] org.apache.felix.http.jetty Failed to start Connector: ServerConnector@3385e5bc{SSL, (ssl, http/1.1)}{0.0.0.0:7706} (java.util.regex.PatternSyntaxException: Unclosed character class near index 7
["SSLv3"
^)
java.util.regex.PatternSyntaxException: Unclosed character class near index 7
["SSLv3"
^
at java.util.regex.Pattern.error(Pattern.java:1969)
at java.util.regex.Pattern.clazz(Pattern.java:2562)
at java.util.regex.Pattern.sequence(Pattern.java:2077)
at java.util.regex.Pattern.expr(Pattern.java:2010)
at java.util.regex.Pattern.compile(Pattern.java:1702)
at java.util.regex.Pattern.<init>(Pattern.java:1352)
at java.util.regex.Pattern.compile(Pattern.java:1028)
at org.eclipse.jetty.util.ssl.SslContextFactory.processIncludeExcludePatterns(SslContextFactory.java:1437)
at org.eclipse.jetty.util.ssl.SslContextFactory.selectProtocols(SslContextFactory.java:1372)
at org.eclipse.jetty.util.ssl.SslContextFactory.load(SslContextFactory.java:396)
at org.eclipse.jetty.util.ssl.SslContextFactory.doStart(SslContextFactory.java:244)
at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:73)
at org.eclipse.jetty.util.component.ContainerLifeCycle.start(ContainerLifeCycle.java:169)
at org.eclipse.jetty.util.component.ContainerLifeCycle.doStart(ContainerLifeCycle.java:117)
at org.eclipse.jetty.server.SslConnectionFactory.doStart(SslConnectionFactory.java:97)
at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:73)
at org.eclipse.jetty.util.component.ContainerLifeCycle.start(ContainerLifeCycle.java:169)
at org.eclipse.jetty.util.component.ContainerLifeCycle.doStart(ContainerLifeCycle.java:117)
at org.eclipse.jetty.server.AbstractConnector.doStart(AbstractConnector.java:321)
at org.eclipse.jetty.server.AbstractNetworkConnector.doStart(AbstractNetworkConnector.java:81)
at org.eclipse.jetty.server.ServerConnector.doStart(ServerConnector.java:234)
at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:73)
at org.apache.felix.http.jetty.internal.JettyService.startConnector(JettyService.java:619)
at org.apache.felix.http.jetty.internal.JettyService.initializeHttps(JettyService.java:498)
at org.apache.felix.http.jetty.internal.JettyService.initializeJetty(JettyService.java:352)
at org.apache.felix.http.jetty.internal.JettyService.startJetty(JettyService.java:192)
at org.apache.felix.http.jetty.internal.JettyService.updated(JettyService.java:184)
at org.apache.felix.http.jetty.internal.JettyManagedService.updated(JettyManagedService.java:38)
at org.apache.felix.cm.impl.helper.ManagedServiceTracker.updated(ManagedServiceTracker.java:189)
at org.apache.felix.cm.impl.helper.ManagedServiceTracker.updateService(ManagedServiceTracker.java:152)
at org.apache.felix.cm.impl.helper.ManagedServiceTracker.provideConfiguration(ManagedServiceTracker.java:85)
at org.apache.felix.cm.impl.ConfigurationManager$ManagedServiceUpdate.provide(ConfigurationManager.java:1113)
at org.apache.felix.cm.impl.ConfigurationManager$ManagedServiceUpdate.run(ConfigurationManager.java:1069)
at org.apache.felix.cm.impl.UpdateThread.run0(UpdateThread.java:138)
at org.apache.felix.cm.impl.UpdateThread.run(UpdateThread.java:105)
at java.lang.Thread.run(Thread.java:750)

Please help us with any hints to resolve this issue.

Regards,
G Patil

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by Nikita___Garg

Hi @nikita___garg,

Have you configured SSL from org.apache.felix.http with truststore and keystore values?
I have built fresh Publisher instance and then installed SP13 on it, but I am able to reproduce the same issue.

Regards,

G Patil


hi @gspatil11-1 ,

 

Please raise adobe support ticket as I didn't find this issue as known issues in AEM 6.5 SP13 or higher version.

 

Thanks,

Nikita Garg

1 reply

N
Adobe Employee
Nikita___GargAdobe Employee
Adobe Employee
December 8, 2022

hi @gspatil11-1,

 

Is there any specific reason you are using SP13, as SP15 is already out on Dec 2. 

 

https://experienceleague.adobe.com/docs/experience-manager-65/release-notes/release-notes.html?lang=en#sites-6515

 

I would recommend to download SP15 and install and validate whether you are still facing the same issue. You can download from https://experience.adobe.com/#/downloads/content/software-distribution/en/aem.html

 

Thanks,

Nikita Garg

 

 

 

    G
    gspatil11-1Author
    Level 2
    December 8, 2022

    Hi @nikita___garg 

    There is no specific reason for installing SP13, but the syntax issue is the one blocking us to access HTTPS URL. Do you see any pointers for syntax issue from org.apache.felix.http configuration?

     

    Regards,

    G Patil

      G
      gspatil11-1Author
      Level 2
      December 9, 2022

      hi @gspatil11-1 ,

       

      Please raise adobe support ticket as I didn't find this issue as known issues in AEM 6.5 SP13 or higher version.

       

      Thanks,

      Nikita Garg


      Yes @nikita___garg, I have logged case for the same with Adobe and working with them for resolution.

       

      Regards,

      G Patil

        Terms & ConditionsAccessibility statement

        Loading footer...