-
Bug
-
Resolution: Done
-
Major
-
27.0.1.Final
-
None
We are in the process of switching from Wildfly26 to Wildfly27.
We have made the changeover to Jakarta EE 10. When starting Wildfly27, an error occurs under Wildfly 26, the service worked without problems.
When starting the MBean /SAR, the error occurs:
Caused by: java.lang.RuntimeException: Provider for jakarta.activation.spi.MailcapRegistryProvider cannot be found.
Logging output:
2023-04-03 12:47:56,453 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-3) MSC000001: Failed to start service jboss.mbean.service."com.myservice.iface.jco.server.qac:service=QAC".registration: org.jboss.msc.service.StartException in service jboss.mbean.service."com.myservice.iface.jco.server.qac:service=QAC".registration: WFLYSAR0015: Failed to register mbean [com.myservice.iface.jco.server.qac:service=QAC]
at org.jboss.as.sar@27.0.1.Final//org.jboss.as.service.MBeanRegistrationService.start(MBeanRegistrationService.java:84)
at org.jboss.msc@1.4.13.Final//org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1739)
at org.jboss.msc@1.4.13.Final//org.jboss.msc.service.ServiceControllerImpl$StartTask.execute(ServiceControllerImpl.java:1701)
at org.jboss.msc@1.4.13.Final//org.jboss.msc.service.ServiceControllerImpl$ControllerTask.run(ServiceControllerImpl.java:1559)
at org.jboss.threads@2.4.0.Final//org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35)
at org.jboss.threads@2.4.0.Final//org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1990)
at org.jboss.threads@2.4.0.Final//org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1486)
at org.jboss.threads@2.4.0.Final//org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1377)
at java.base/java.lang.Thread.run(Unknown Source)
Caused by: javax.management.RuntimeErrorException: Error thrown in postRegister method: rethrowing <java.lang.ExceptionInInitializerError>, but keeping the MBean registered
at java.management/com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.postRegister(Unknown Source)
at java.management/com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerDynamicMBean(Unknown Source)
at java.management/com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerObject(Unknown Source)
at java.management/com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerMBean(Unknown Source)
at java.management/com.sun.jmx.mbeanserver.JmxMBeanServer.registerMBean(Unknown Source)
at org.jboss.as.jmx@19.0.1.Final//org.jboss.as.jmx.PluggableMBeanServerImpl$TcclMBeanServer.registerMBean(PluggableMBeanServerImpl.java:1517)
at org.jboss.as.jmx@19.0.1.Final//org.jboss.as.jmx.PluggableMBeanServerImpl.registerMBean(PluggableMBeanServerImpl.java:873)
at org.jboss.as.sar@27.0.1.Final//org.jboss.as.service.MBeanRegistrationService.start(MBeanRegistrationService.java:82)
... 8 more
Caused by: java.lang.ExceptionInInitializerError
at org.apache.cxf@3.5.2.jbossorg-4//org.apache.cxf.interceptor.AttachmentOutInterceptor.handleMessage(AttachmentOutInterceptor.java:66)
at org.apache.cxf@3.5.2.jbossorg-4//org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:307)
at org.apache.cxf@3.5.2.jbossorg-4//org.apache.cxf.endpoint.ClientImpl.doInvoke(ClientImpl.java:528)
at org.apache.cxf@3.5.2.jbossorg-4//org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:439)
at org.apache.cxf@3.5.2.jbossorg-4//org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:354)
at org.apache.cxf@3.5.2.jbossorg-4//org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:312)
at org.apache.cxf.impl//org.apache.cxf.frontend.ClientProxy.invokeSync(ClientProxy.java:96)
at org.apache.cxf.impl//org.apache.cxf.jaxws.JaxWsClientProxy.invoke(JaxWsClientProxy.java:140)
at deployment.mbeanService.ear.mbeanService_qac.sar//com.sun.proxy.$Proxy68.getSystemInformation(Unknown Source)
at deployment.mbeanService.ear.mbeanService_qac.sar//com.myservice.iface.jco.server.QACService.createRoutingTableInternal(QACService.java:662)
at deployment.mbeanService.ear.mbeanService_qac.sar//com.myservice.iface.jco.server.QACService.createRoutingTable(QACService.java:170)
at deployment.mbeanService.ear.mbeanService_qac.sar//com.myservice.iface.jco.server.QACService.startService(QACService.java:109)
at org.jboss.as.system-jmx@27.0.1.Final//org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:255)
at org.jboss.as.system-jmx@27.0.1.Final//org.jboss.system.ServiceMBeanSupport.start(ServiceMBeanSupport.java:162)
at org.jboss.as.system-jmx@27.0.1.Final//org.jboss.system.ServiceMBeanSupport.jbossInternalCreate(ServiceMBeanSupport.java:233)
at org.jboss.as.system-jmx@27.0.1.Final//org.jboss.system.ServiceMBeanSupport.create(ServiceMBeanSupport.java:158)
at org.jboss.as.system-jmx@27.0.1.Final//org.jboss.system.ServiceMBeanSupport.postRegister(ServiceMBeanSupport.java:372)
at java.management/com.sun.jmx.mbeanserver.MBeanSupport.postRegister(Unknown Source)
... 16 more
Caused by: java.lang.RuntimeException: Provider for jakarta.activation.spi.MailcapRegistryProvider cannot be found
at jakarta.activation.api@2.1.1.jbossorg-1//jakarta.activation.FactoryFinder.find(FactoryFinder.java:90)
at jakarta.activation.api@2.1.1.jbossorg-1//jakarta.activation.MailcapCommandMap.getImplementation(MailcapCommandMap.java:705)
at jakarta.activation.api@2.1.1.jbossorg-1//jakarta.activation.MailcapCommandMap.loadFile(MailcapCommandMap.java:284)
at jakarta.activation.api@2.1.1.jbossorg-1//jakarta.activation.MailcapCommandMap.<init>(MailcapCommandMap.java:154)
at jakarta.activation.api@2.1.1.jbossorg-1//jakarta.activation.CommandMap.getDefaultCommandMap(CommandMap.java:60)
at org.apache.cxf@3.5.2.jbossorg-4//org.apache.cxf.attachment.AttachmentUtil.<clinit>(AttachmentUtil.java:81)
... 34 more
2023-04-03 12:47:56,535 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("deploy") failed - address: ([("deployment" => "mbeanService.ear")]) - failure description: {"WFLYCTL0080: Failed services" => {"jboss.mbean.service.\"com.myservice.iface.jco.server.qac:service=QAC\".registration" => "WFLYSAR0015: Failed to register mbean [com.myservice.iface.jco.server.qac:service=QAC]
Caused by: javax.management.RuntimeErrorException: Error thrown in postRegister method: rethrowing <java.lang.ExceptionInInitializerError>, but keeping the MBean registered
Caused by: java.lang.ExceptionInInitializerError
Caused by: java.lang.RuntimeException: Provider for jakarta.activation.spi.MailcapRegistryProvider cannot be found"}}
2023-04-03 12:47:56,720 ERROR [org.jboss.as] (Controller Boot Thread) WFLYSRV0026: WildFly Full 27.0.1.Final (WildFly Core 19.0.1.Final) started (with errors) in 19285ms - Started 717 of 975 services (1 services failed or missing dependencies, 407 services are lazy, passive or on-demand) - Server configuration file in use: standalone-full.xml
2023-04-03 12:47:56,724 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0060: Http management interface listening on http://127.0.0.1:9990/management
2023-04-03 12:47:56,724 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0051: Admin console listening on http://127.0.0.1:9990
2023-04-03 12:56:27,568 DEBUG [com.myservice.iface.jco.server.QACService] (ServerService Thread Pool – 94) Ignoring stop call; current state is Starting
2023-04-03 12:56:27,594 DEBUG [com.myservice.iface.jco.server.QACService] (ServerService Thread Pool – 97) Ignoring destroy call; current state is Starting
2023-04-03 12:56:28,201 INFO [org.jboss.as] (MSC service thread 1-3) WFLYSRV0050: WildFly Full 27.0.1.Final (WildFly Core 19.0.1.Final) stopped in 772ms
Thanks and BR
- is caused by
-
WFCORE-6470 Unexpected classloader when registering MBeans that are part of a deployment
- Resolved
- is related to
-
WFLY-18370 Remove org.eclipse.angus.activation dependency from sar module, and add test that the App CL is being used
- Closed