4 Replies Latest reply on Aug 9, 2010 3:39 AM by Ales Justin

    MC - Better error reporting?

    jaikiran pai Master

      While trying out an application deployment on AS, MC threw this error message: {code:java} 15:49:18,031 ERROR [org.jboss.system.server.profileservice.ProfileServiceBootstrap] Failed to load profile: Summary of incomplete deployments (SEE PREVIOUS ERRORS FOR DETAILS): DEPLOYMENTS MISSING DEPENDENCIES:   Deployment "jboss.ejb3:module=myapp,component=MyNoInterfaceSFSB,service=EjbEncFactory" is missing the following dependencies:     Dependency "jboss.naming:component=MyNoInterfaceSFSB,module=myapp" (should be in state "Installed", but is actually in state "** NOT FOUND Depends on 'jboss.naming:component=MyNoInterfaceSFSB,module=myapp' **")   Deployment "jboss.ejb3:module=myapp,component=MyNoInterfaceSLSB,service=EjbEncFactory" is missing the following dependencies:     Dependency "jboss.naming:component=MyNoInterfaceSLSB,module=myapp" (should be in state "Installed", but is actually in state "** NOT FOUND Depends on 'jboss.naming:component=MyNoInterfaceSLSB,module=myapp' **")   Deployment "jboss.j2ee:jar=myapp.war,name=MyNoInterfaceSFSB,service=EJB3" is missing the following dependencies:     Dependency "jboss.ejb3:component=MyNoInterfaceSFSB,module=myapp,service=EjbEncFactory" (should be in state "Installed", but is actually in state "Described")   Deployment "jboss.j2ee:jar=myapp.war,name=MyNoInterfaceSFSB,service=EJB3_endpoint" is missing the following dependencies:     Dependency "jboss.j2ee:jar=myapp.war,name=MyNoInterfaceSFSB,service=EJB3" (should be in state "Installed", but is actually in state "Instantiated")   Deployment "jboss.j2ee:jar=myapp.war,name=MyNoInterfaceSLSB,service=EJB3" is missing the following dependencies:     Dependency "jboss.ejb3:component=MyNoInterfaceSLSB,module=myapp,service=EjbEncFactory" (should be in state "Installed", but is actually in state "Described")   Deployment "jboss.j2ee:jar=myapp.war,name=MyNoInterfaceSLSB,service=EJB3_endpoint" is missing the following dependencies:     Dependency "jboss.j2ee:jar=myapp.war,name=MyNoInterfaceSLSB,service=EJB3" (should be in state "Installed", but is actually in state "Instantiated") DEPLOYMENTS IN ERROR:   Deployment "jboss.naming:component=MyNoInterfaceSLSB,module=myapp" is in error due to the following reason(s): ** NOT FOUND Depends on 'jboss.naming:component=MyNoInterfaceSLSB,module=myapp' **   Deployment "jboss.naming:component=MyNoInterfaceSFSB,module=myapp" is in error due to the following reason(s): ** NOT FOUND Depends on 'jboss.naming:component=MyNoInterfaceSFSB,module=myapp' **   Deployment "jboss.ejb3:component=MyNoInterfaceSLSB,module=myapp,service=EjbEncFactory" is in error due to the following reason(s): Described   Deployment "jboss.ejb3:component=MyNoInterfaceSFSB,module=myapp,service=EjbEncFactory" is in error due to the following reason(s): Described     {code}     I had a very hard time trying to figure out what that message was trying to convey. Could these error messages be better reported to make it more understandable?   

        • 1. Re: MC - Better error reporting?
          Ales Justin Master
          Could these error messages be better reported to make it more understandable?

          Sure. What do you suggest?

          • 2. Re: MC - Better error reporting?
            jaikiran pai Master

            I haven't (yet) looked at the code responsible for logging this, so I can't propose any changes on that front. But I can make some general suggestions about the messages (with the previously posted logs as an example): 1) {code} DEPLOYMENTS MISSING DEPENDENCIES:   Deployment "jboss.ejb3:module=myapp,component=MyNoInterfaceSFSB,service=EjbEncFactory" is missing the following dependencies:     Dependency "jboss.naming:component=MyNoInterfaceSFSB,module=myapp" (should be in state "Installed", but is actually in state "** NOT FOUND Depends on 'jboss.naming:component=MyNoInterfaceSFSB,module=myapp' **") {code} So this is saying that a service is missing a dependency which was expected to be in Installed state but is actually in "** NOT FOUND Depends on 'jboss.naming:component=MyNoInterfaceSFSB,module=myapp' **" What does "** NOT FOUND Depends on 'jboss.naming:component=MyNoInterfaceSFSB,module=myapp' **" mean in the context of that message? Maybe it should be: {code} Dependency "jboss.naming:component=MyNoInterfaceSFSB,module=myapp" (should be in state "Installed", but is actually missing) {code} 2) This one is more of formatting the error messages - In its current form multiple deployments which are missing dependencies are logged together like: {code} DEPLOYMENTS MISSING DEPENDENCIES:   Deployment "jboss.ejb3:module=myapp,component=MyNoInterfaceSFSB,service=EjbEncFactory" is missing the following dependencies:     Dependency "jboss.naming:component=MyNoInterfaceSFSB,module=myapp" (should be in state "Installed", but is actually in state "** NOT FOUND Depends on 'jboss.naming:component=MyNoInterfaceSFSB,module=myapp' **")   Deployment "jboss.ejb3:module=myapp,component=MyNoInterfaceSLSB,service=EjbEncFactory" is missing the following dependencies:     Dependency "jboss.naming:component=MyNoInterfaceSLSB,module=myapp" (should be in state "Installed", but is actually in state "** NOT FOUND Depends on 'jboss.naming:component=MyNoInterfaceSLSB,module=myapp' **")   Deployment "jboss.j2ee:jar=myapp.war,name=MyNoInterfaceSFSB,service=EJB3" is missing the following dependencies:     Dependency "jboss.ejb3:component=MyNoInterfaceSFSB,module=myapp,service=EjbEncFactory" (should be in state "Installed", but is actually in state "Described")   Deployment "jboss.j2ee:jar=myapp.war,name=MyNoInterfaceSFSB,service=EJB3_endpoint" is missing the following dependencies:     Dependency "jboss.j2ee:jar=myapp.war,name=MyNoInterfaceSFSB,service=EJB3" (should be in state "Installed", but is actually in state "Instantiated") ... {code} When this gets logged, it's very difficult to distinguish the different deployments. It just "appears" like some random text dumped out on the console. Maybe each deployment should be separated by an empty line, so that each one stands out: {code} DEPLOYMENTS MISSING DEPENDENCIES:   Deployment "jboss.ejb3:module=myapp,component=MyNoInterfaceSFSB,service=EjbEncFactory" is missing the following dependencies:     Dependency "jboss.naming:component=MyNoInterfaceSFSB,module=myapp" (should be in state "Installed", but is actually in state "** NOT FOUND Depends on 'jboss.naming:component=MyNoInterfaceSFSB,module=myapp' **")       Deployment "jboss.ejb3:module=myapp,component=MyNoInterfaceSLSB,service=EjbEncFactory" is missing the following dependencies:     Dependency "jboss.naming:component=MyNoInterfaceSLSB,module=myapp" (should be in state "Installed", but is actually in state "** NOT FOUND Depends on 'jboss.naming:component=MyNoInterfaceSLSB,module=myapp' **")       Deployment "jboss.j2ee:jar=myapp.war,name=MyNoInterfaceSFSB,service=EJB3" is missing the following dependencies:     Dependency "jboss.ejb3:component=MyNoInterfaceSFSB,module=myapp,service=EjbEncFactory" (should be in state "Installed", but is actually in state "Described")   Deployment "jboss.j2ee:jar=myapp.war,name=MyNoInterfaceSFSB,service=EJB3_endpoint" is missing the following dependencies:     Dependency "jboss.j2ee:jar=myapp.war,name=MyNoInterfaceSFSB,service=EJB3" (should be in state "Installed", but is actually in state "Instantiated") {code} 3) The other section "Deployments in ERROR": {code} DEPLOYMENTS IN ERROR:   Deployment "jboss.naming:component=MyNoInterfaceSLSB,module=myapp" is in error due to the following reason(s): ** NOT FOUND Depends on 'jboss.naming:component=MyNoInterfaceSLSB,module=myapp' **   Deployment "jboss.naming:component=MyNoInterfaceSFSB,module=myapp" is in error due to the following reason(s): ** NOT FOUND Depends on 'jboss.naming:component=MyNoInterfaceSFSB,module=myapp' **   Deployment "jboss.ejb3:component=MyNoInterfaceSLSB,module=myapp,service=EjbEncFactory" is in error due to the following reason(s): Described   Deployment "jboss.ejb3:component=MyNoInterfaceSFSB,module=myapp,service=EjbEncFactory" is in error due to the following reason(s): Described {code} This section (atleast in this specific deployment) is confusing and redundant. The message: {code}   Deployment "jboss.naming:component=MyNoInterfaceSLSB,module=myapp" is in error due to the following reason(s): ** NOT FOUND Depends on 'jboss.naming:component=MyNoInterfaceSLSB,module=myapp' ** {code} is trying to say that jboss.naming:component=MyNoInterfaceSLSB,module=myapp has not been deployed (i.e. is missing). This was already conveyed in the earlier "Deployments missing dependencies" section. Why repeat it again? Also the ** NOT FOUND Depends...", as in the earlier case, is confusing. The other message: {code} Deployment "jboss.ejb3:component=MyNoInterfaceSLSB,module=myapp,service=EjbEncFactory" is in error due to the following reason(s): Described {code} This too has already been conveyed (in a slightly different form) in the earlier "Deployments missing dependencies" section. So why repeat again? :)

            • 3. Re: MC - Better error reporting?
              Michael Schuetz Novice

              Hi,

               

              I ran into same troubles. Is this one scheduled? Is there a JIRA ticket, already?

               

               

              Thanks and regards

              Michael

              • 4. Re: MC - Better error reporting?
                Ales Justin Master
                Is this one scheduled? Is there a JIRA ticket, already?

                It's on my TODO list, but not with a high priority.