Uploaded image for project: 'WildFly'
  1. WildFly
  2. WFLY-17662

Errors with upgrade to Spring Boot 3.0.3

    XMLWordPrintable

Details

    • Bug
    • Resolution: Unresolved
    • Major
    • None
    • 27.0.1.Final
    • Mail
    • None
    • ---
    • ---

    Description

      I have an application based on Spring Boot 3.0.2 which works fine with Wildfly 27.

      When upgrading to Spring Boot 3.0.3, however, we start getting the following error:

      java.util.ServiceConfigurationError: jakarta.activation.spi.MailcapRegistryProvider: com.sun.activation.registries.MailcapRegistryProviderImpl not a subtype
              at java.util.ServiceLoader.fail(ServiceLoader.java:593) ~[?:?]
              at java.util.ServiceLoader$LazyClassPathLookupIterator.hasNextService(ServiceLoader.java:1244) ~[?:?]
              at java.util.ServiceLoader$LazyClassPathLookupIterator.hasNext(ServiceLoader.java:1273) ~[?:?]
              at java.util.ServiceLoader$2.hasNext(ServiceLoader.java:1309) ~[?:?]
              at java.util.ServiceLoader$3.hasNext(ServiceLoader.java:1393) ~[?:?]
              at jakarta.activation.ServiceLoaderUtil.firstByServiceLoader(ServiceLoaderUtil.java:33) ~[jakarta.activation-api-2.1.1.jbossorg-1.jar!/:2.1.1.jbossorg-1]
              at jakarta.activation.FactoryFinder.find(FactoryFinder.java:77) ~[jakarta.activation-api-2.1.1.jbossorg-1.jar!/:2.1.1.jbossorg-1]
              at jakarta.activation.MailcapCommandMap.getImplementation(MailcapCommandMap.java:705) ~[jakarta.activation-api-2.1.1.jbossorg-1.jar!/:2.1.1.jbossorg-1]
              at jakarta.activation.MailcapCommandMap.loadFile(MailcapCommandMap.java:284) ~[jakarta.activation-api-2.1.1.jbossorg-1.jar!/:2.1.1.jbossorg-1]
              at jakarta.activation.MailcapCommandMap.<init>(MailcapCommandMap.java:154) ~[jakarta.activation-api-2.1.1.jbossorg-1.jar!/:2.1.1.jbossorg-1]
              at jakarta.activation.CommandMap.getDefaultCommandMap(CommandMap.java:60) ~[jakarta.activation-api-2.1.1.jbossorg-1.jar!/:2.1.1.jbossorg-1]
      

      We had the same error with Tomcat deployment, which was fixed by avoiding some dependencies to pull angus-activation-1.0.0.jar as angus-activation-2.0.0.jar comes via Spring Boot 3.0.3.

      For this reason, we have added the following exclusions to our jboss-deployment-structure.xml:

            <module name="jakarta.activation.api"/>
            <module name="org.eclipse.angus.activation"/>
            <module name="org.eclipse.angus.mail"/> 
      

      Nothing seems to change, however: any idea?

      Attachments

        Issue Links

          Activity

            People

              yborgess1@redhat.com Yeray Borges Santana
              francesco.chicchiricco@tirasa.net Francesco Chicchiriccò
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated: