You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is inconsistent, but happens sometimes in an installation and in the IT suite. That makes me think it's some sort of timing issue, though I'm not sure where that would be. Could be related to whatever is going on with #542
org.jboss.weld.exceptions.DeploymentException: WELD-001408: Unsatisfied dependencies for type MetricRegistry with qualifiers @RegistryType
at injection point [UnbackedAnnotatedField] @Inject @RegistryType io.smallrye.faulttolerance.metrics.MicroProfileMetricsProvider.registry
at io.smallrye.faulttolerance.metrics.MicroProfileMetricsProvider.registry(MicroProfileMetricsProvider.java:0)
at org.jboss.weld.bootstrap.Validator.validateInjectionPointForDeploymentProblems(Validator.java:379)
at org.jboss.weld.bootstrap.Validator.validateInjectionPoint(Validator.java:294)
at org.jboss.weld.bootstrap.Validator.validateGeneralBean(Validator.java:141)
at org.jboss.weld.bootstrap.Validator.validateRIBean(Validator.java:163)
at org.jboss.weld.bootstrap.Validator.validateBean(Validator.java:533)
at org.jboss.weld.bootstrap.Validator.validateBeans(Validator.java:518)
at org.jboss.weld.bootstrap.Validator.validateDeployment(Validator.java:493)
at org.jboss.weld.bootstrap.WeldStartup.validateBeans(WeldStartup.java:497)
at org.jboss.weld.bootstrap.WeldBootstrap.validateBeans(WeldBootstrap.java:94)
at org.jboss.weld.environment.se.Weld.initialize(Weld.java:856)
at org.openntf.xsp.jakarta.cdi.util.ContainerUtil.lambda$7(ContainerUtil.java:341)
at java.base/java.security.AccessController.doPrivileged(AccessController.java:692)
at org.openntf.xsp.jakarta.cdi.util.ContainerUtil.lambda$6(ContainerUtil.java:318)
at org.openntf.xsp.jakarta.cdi.util.ContainerUtil.withLock(ContainerUtil.java:426)
at org.openntf.xsp.jakarta.cdi.util.ContainerUtil.getContainer(ContainerUtil.java:275)
at org.openntf.xsp.jakarta.cdi.impl.ContainerUtilProvider.getContainer(ContainerUtilProvider.java:33)
at java.base/java.util.Optional.map(Optional.java:260)
at org.openntf.xsp.jakarta.cdi.provider.ComponentModuleCDIContainerLocator.getContainer(ComponentModuleCDIContainerLocator.java:43)
at org.openntf.xsp.jakarta.cdi.provider.DominoCDIProvider.getCDI(DominoCDIProvider.java:52)
at jakarta.enterprise.inject.spi.CDI.getCDIProvider(CDI.java:78)
at jakarta.enterprise.inject.spi.CDI.current(CDI.java:65)
at org.openntf.xsp.jakarta.rest.impl.JakartaRestServlet.initCdi(JakartaRestServlet.java:132)
at org.openntf.xsp.jakarta.rest.impl.JakartaRestServlet.service(JakartaRestServlet.java:74)
at jakarta.servlet.http.HttpServlet.service(HttpServlet.java:614)
at org.openntf.xsp.jakartaee.servlet.NewHttpServletWrapper.service(NewHttpServletWrapper.java:112)
at com.ibm.designer.runtime.domino.adapter.ComponentModule.invokeServlet(ComponentModule.java:599)
at com.ibm.domino.xsp.module.nsf.NSFComponentModule.invokeServlet(NSFComponentModule.java:1359)
at com.ibm.designer.runtime.domino.adapter.ComponentModule$AdapterInvoker.invokeServlet(ComponentModule.java:886)
at com.ibm.designer.runtime.domino.adapter.ComponentModule$ServletInvoker.doService(ComponentModule.java:829)
at com.ibm.designer.runtime.domino.adapter.ComponentModule.doService(ComponentModule.java:588)
at com.ibm.domino.xsp.module.nsf.NSFComponentModule.doService(NSFComponentModule.java:1343)
at com.ibm.domino.xsp.module.nsf.NSFService.doServiceInternal(NSFService.java:725)
at com.ibm.domino.xsp.module.nsf.NSFService.doService(NSFService.java:515)
at com.ibm.designer.runtime.domino.adapter.LCDEnvironment.doService(LCDEnvironment.java:371)
at com.ibm.designer.runtime.domino.adapter.LCDEnvironment.service(LCDEnvironment.java:327)
at com.ibm.domino.xsp.bridge.http.engine.XspCmdManager.service(XspCmdManager.java:302)
The text was updated successfully, but these errors were encountered:
This is inconsistent, but happens sometimes in an installation and in the IT suite. That makes me think it's some sort of timing issue, though I'm not sure where that would be. Could be related to whatever is going on with #542
The text was updated successfully, but these errors were encountered: