1 Reply Latest reply on May 28, 2013 6:01 AM by jaikiran

    Jboss 4.3.GA to Jboss 6.1.0.alpha migration - JBAS015893: Encountered invalid class name

    georgesg

      I saw the below warning in the server console log. Should it be considered seriously or can be ignored ?  Complete Server logs attached.

       

      16:38:44,915 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-3) JBAS015893: Encountered invalid class name 'org.springframework.context.ApplicationContext,org.springframework.beans.BeansException' for service type 'org.apache.cxf.bus.factory'

        • 1. Re: Jboss 4.3.GA to Jboss 6.1.0.alpha migration - JBAS015893: Encountered invalid class name
          jaikiran

          ANAND KUMAR GEORGE PREM KUMAR wrote:

           

           

           

          16:38:44,915 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-3) JBAS015893: Encountered invalid class name 'org.springframework.context.ApplicationContext,org.springframework.beans.BeansException' for service type 'org.apache.cxf.bus.factory'

          That's definitely a invalid class name (notice the comma separation in there). It looks like whoever is exposing those services through service loader mechanism isn't following the rules defined here http://docs.oracle.com/javase/6/docs/api/java/util/ServiceLoader.html

           

          A service provider is identified by placing a provider-configuration file in the resource directory META-INF/services. The file's name is the fully-qualified binary name of the service's type. The file contains a list of fully-qualified binary names of concrete provider classes, one per line