#1707 Certificate operation cannot be completed: Unable to communicate with CMS (Service Unavailable))
Closed: Invalid None Opened 4 years ago by jstephen.

Steps to Reproduce:

1. Browse to IPA Client host in WebUI

Also

1. Run ipa cert-show 1

Actual results:

 ERROR: Certificate operation cannot be completed: Unable to communicate with
CMS (Service Unavailable))

Expected results:

Success

Additional info:

Took a look at the catalina.out log and I found this (disregard the line
numbers at the start of each line) ->

  13311 SEVERE: Error deploying web application directory ca
  13312 java.lang.UnsupportedClassVersionError:
com/netscape/cms/servlet/filter/AgentRequestFilter : Unsupported major.minor
version 51.0 (unable to load class
com.netscape.cms.servlet.filter.AgentRequestFilter)
  13313     at org.apache.catalina.loader.WebappClassLoader.findClassInternal(W
ebappClassLoader.java:2334)
  13314     at org.apache.catalina.loader.WebappClassLoader.findClass(WebappCla
ssLoader.java:976)
  13315     at org.apache.catalina.loader.WebappClassLoader.loadClass(WebappCla
ssLoader.java:1450)
  13316     at org.apache.catalina.loader.WebappClassLoader.loadClass(WebappCla
ssLoader.java:1329)
  13317     at org.apache.catalina.startup.WebAnnotationSet.loadClassAnnotation
(WebAnnotationSet.java:145)
  13318     at org.apache.catalina.startup.WebAnnotationSet.loadApplicationFilt
erAnnotations(WebAnnotationSet.java:84)
  13319     at org.apache.catalina.startup.WebAnnotationSet.loadApplicationAnno
tations(WebAnnotationSet.java:57)
  13320     at org.apache.catalina.startup.ContextConfig.applicationAnnotations
Config(ContextConfig.java:294)
  13321     at
org.apache.catalina.startup.ContextConfig.start(ContextConfig.java:1046)
  13322     at org.apache.catalina.startup.ContextConfig.lifecycleEvent(Context
Config.java:265)
  13323     at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(Lif
ecycleSupport.java:142)
  13324     at
org.apache.catalina.core.StandardContext.start(StandardContext.java:4616)
  13325     at
org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:791)
  13326     at
org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:771)
  13327     at
org.apache.catalina.core.StandardHost.addChild(StandardHost.java:526)
  13328     at
org.apache.catalina.startup.HostConfig.deployDirectory(HostConfig.java:1041)
  13329     at
org.apache.catalina.startup.HostConfig.deployDirectories(HostConfig.java:964)
  13330     at
org.apache.catalina.startup.HostConfig.deployApps(HostConfig.java:502)
  13331     at
org.apache.catalina.startup.HostConfig.start(HostConfig.java:1277)
  13332     at
org.apache.catalina.startup.HostConfig.lifecycleEvent(HostConfig.java:321)
  13333     at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(Lif
ecycleSupport.java:142)
  13334     at
org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1053)
  13335     at
org.apache.catalina.core.StandardHost.start(StandardHost.java:722)
  13336     at
org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1045)
  13337     at
org.apache.catalina.core.StandardEngine.start(StandardEngine.java:443)
  13338     at
org.apache.catalina.core.StandardService.start(StandardService.java:516)
  13339     at
org.apache.catalina.core.StandardServer.start(StandardServer.java:710)
  13340     at org.apache.catalina.startup.Catalina.start(Catalina.java:593)
  13341     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
  13342     at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
  13343     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethod
AccessorImpl.java:43)
  13344     at java.lang.reflect.Method.invoke(Method.java:622)
  13345     at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:289)
  13346     at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:414)

--- Additional comment from Ade Lee on 2015-11-30 21:26:03 EST ---

Checking whther or not we are executing with the right JVM by checking
alternatives is probably the right thing to do here.

Per discussions in the Dogtag 10.3 Triage meeting of 01/06/2016, it was determined that this bug was not valid on Fedora platforms.

Metadata Update from @jstephen:
- Issue set to the milestone: 10.3.0

3 years ago

Login to comment on this ticket.

Metadata