13 Replies Latest reply on Jun 11, 2011 8:25 PM by John Ulmer

    Jboss 5.1 Failed to load profile: Summary of incomplete deployments

    Prakash M Novice

      Hi,

      I am getting the following ERROR while while starting the jboss 5.1 server. I have copied the relevant error messages from the log file and paced in the attached txt file.

       

      Could you please assist on resolving these error messages?

       

      Note: Attched txt file contains different chunk of error messages, which I  have copied from the original log file.

       

      15:39:55,916 ERROR [ProfileServiceBootstrap] Failed to load profile: Summary of incomplete deployments (SEE PREVIOUS ERRORS FOR DETAILS):

       

      DEPLOYMENTS MISSING DEPENDENCIES:
        Deployment "JBossTimerServiceFactory" is missing the following dependencies:
          Dependency "jboss.ejb:service=EJBTimerService" (should be in state "Create", but is actually in state "Configured")
        Deployment "jboss.ejb:persistencePolicy=database,service=EJBTimerService" is missing the following dependencies:
          Dependency "jboss.jca:name=DefaultDS,service=DataSourceBinding" (should be in state "Create", but is actually in state "** NOT FOUND Depends on 'jboss.jca:name=DefaultDS,service=DataSourceBinding' **")
          Dependency "jboss.jdbc:datasource=DefaultDS,service=metadata" (should be in state "Create", but is actually in state "** NOT FOUND Depends on 'jboss.jdbc:datasource=DefaultDS,service=metadata' **")
        Deployment "jboss.ejb:service=EJBTimerService" is missing the following dependencies:
          Dependency "jboss.ejb:persistencePolicy=database,service=EJBTimerService" (should be in state "Create", but is actually in state "Configured")
        Deployment "jboss.j2ee:jar=profileservice-secured.jar,name=SecureDeploymentManager,service=EJB3" is missing the following dependencies:
          Dependency "<UNKNOWN jboss.j2ee:jar=profileservice-secured.jar,name=SecureDeploymentManager,service=EJB3>" (should be in state "Described", but is actually in state "** UNRESOLVED Demands 'jboss.ejb:service=EJBTimerService' **")
        Deployment "jboss.j2ee:jar=profileservice-secured.jar,name=SecureDeploymentManager,service=EJB3_endpoint" is missing the following dependencies:
          Dependency "jboss.j2ee:jar=profileservice-secured.jar,name=SecureDeploymentManager,service=EJB3" (should be in state "Configured", but is actually in state "PreInstall")
        Deployment "jboss.j2ee:jar=profileservice-secured.jar,name=SecureManagementView,service=EJB3" is missing the following dependencies:
          Dependency "<UNKNOWN jboss.j2ee:jar=profileservice-secured.jar,name=SecureManagementView,service=EJB3>" (should be in state "Described", but is actually in state "** UNRESOLVED Demands 'jboss.ejb:service=EJBTimerService' **")
        Deployment "jboss.j2ee:jar=profileservice-secured.jar,name=SecureManagementView,service=EJB3_endpoint" is missing the following dependencies:
          Dependency "jboss.j2ee:jar=profileservice-secured.jar,name=SecureManagementView,service=EJB3" (should be in state "Configured", but is actually in state "PreInstall")
        Deployment "jboss.j2ee:jar=profileservice-secured.jar,name=SecureProfileService,service=EJB3" is missing the following dependencies:
          Dependency "<UNKNOWN jboss.j2ee:jar=profileservice-secured.jar,name=SecureProfileService,service=EJB3>" (should be in state "Described", but is actually in state "** UNRESOLVED Demands 'jboss.ejb:service=EJBTimerService' **")
          Dependency "<UNKNOWN jboss.j2ee:jar=profileservice-secured.jar,name=SecureProfileService,service=EJB3>" (should be in state "Described", but is actually in state "** UNRESOLVED Demands 'jndi:SecureManagementView/remote-org.jboss.deployers.spi.management.ManagementView' **")
        Deployment "jboss.j2ee:jar=profileservice-secured.jar,name=SecureProfileService,service=EJB3_endpoint" is missing the following dependencies:
          Dependency "jboss.j2ee:jar=profileservice-secured.jar,name=SecureProfileService,service=EJB3" (should be in state "Configured", but is actually in state "PreInstall")
        Deployment "jboss:service=KeyGeneratorFactory,type=HiLo" is missing the following dependencies:
          Dependency "jboss.jca:name=DefaultDS,service=DataSourceBinding" (should be in state "Create", but is actually in state "** NOT FOUND Depends on 'jboss.jca:name=DefaultDS,service=DataSourceBinding' **")

       

      DEPLOYMENTS IN ERROR:
        Deployment "<UNKNOWN jboss.j2ee:jar=profileservice-secured.jar,name=SecureProfileService,service=EJB3>" is in error due to the following reason(s): ** UNRESOLVED Demands 'jboss.ejb:service=EJBTimerService' **, ** UNRESOLVED Demands 'jndi:SecureManagementView/remote-org.jboss.deployers.spi.management.ManagementView' **
        Deployment "jboss.jca:name=DefaultDS,service=DataSourceBinding" is in error due to the following reason(s): ** NOT FOUND Depends on 'jboss.jca:name=DefaultDS,service=DataSourceBinding' **
        Deployment "<UNKNOWN jboss.j2ee:jar=profileservice-secured.jar,name=SecureManagementView,service=EJB3>" is in error due to the following reason(s): ** UNRESOLVED Demands 'jboss.ejb:service=EJBTimerService' **
        Deployment "<UNKNOWN jboss.j2ee:jar=profileservice-secured.jar,name=SecureDeploymentManager,service=EJB3>" is in error due to the following reason(s): ** UNRESOLVED Demands 'jboss.ejb:service=EJBTimerService' **
        Deployment "jboss.jdbc:datasource=DefaultDS,service=metadata" is in error due to the following reason(s): ** NOT FOUND Depends on 'jboss.jdbc:datasource=DefaultDS,service=metadata' **

       

      Thanks,

      Prakash

        • 1. Re: Jboss 5.1 Failed to load profile: Summary of incomplete deployments
          Timothy Landon Newbie

          Have you found a solution to this issue?  I am now getting the same error.

          • 2. Re: Jboss 5.1 Failed to load profile: Summary of incomplete deployments
            Prakash M Novice

            Not yet Tim, still am working on resolving other issues. if you could provide some hints, it would be helpful.

             

            Thanks,

            Prakash

            • 3. Re: Jboss 5.1 Failed to load profile: Summary of incomplete deployments
              Vanitha Palanichamy Newbie

              Hi,

               

              Did you find the solution for this problem.  If yes, could you please post it. I am running into the same issue.

               

               

              Thanks

              Vanitha

              • 4. Re: Jboss 5.1 Failed to load profile: Summary of incomplete deployments
                jaikiran pai Master

                For those posting "me too" in this thread - Not all "Failed to load profile" errors are the same. So please open separate threads with the details about the version of JBoss and the exception stacktrace to discuss your issues.

                • 5. Re: Jboss 5.1 Failed to load profile: Summary of incomplete deployments
                  Brent Craig Newbie

                  Was this problem resolved? I am running into the same situation. Thx

                  • 6. Re: Jboss 5.1 Failed to load profile: Summary of incomplete deployments
                    jaikiran pai Master

                    Brent Craig wrote:

                     

                    Was this problem resolved? I am running into the same situation. Thx

                     

                    As I said in my previous reply:

                     

                    For those posting "me too" in this thread - Not all "Failed to load profile" errors are the same. So please open separate threads with the details about the version of JBoss and the exception stacktrace to discuss your issues.

                    • 7. Re: Jboss 5.1 Failed to load profile: Summary of incomplete deployments
                      Umesh R Newbie

                      While everything was working fine on 5.1 GA and I got similar error after one deployment

                      DEPLOYMENTS IN ERROR:
                        Deployment "jboss.ejb:service=EJBTimerService" is in error due to the following reason(s): Configured

                       

                      I looke at the logs carefully and found out the root following root cause:

                      java.io.FileNotFoundException: /apps/jboss-5.1.0.GA/server/default/data/tx-object-store/HashedActionStore/defaultStore/Recovery/TransactionStatusManager/#107#/7f000001_575b_4c9295b8_0 (Permission denied)

                       

                      The reason I found was: The server was started by one userid and I deployed the ear with different userid. After changing the permissions to respective directory, the server started working fine as before.

                      • 8. Re: Jboss 5.1 Failed to load profile: Summary of incomplete deployments
                        Srinivas Nandina Newbie

                        I got something similar error on 5.1 GA:

                         

                        Dependency "jboss.jca:name=MyDS,service=DataSourceBinding" (should be in state "Create", but is actually in state "** NOT FOUND Depends on 'jboss.jca:name=MyDS,service=DataSourceBinding' **")

                         

                        I found the problem to be with the improper naming of datasource xml file. I changed the name of the file from my-db.xml to my-db-ds.xml and it started working. Only files ending with -ds.xml will be deployed.

                        • 9. Re: Jboss 5.1 Failed to load profile: Summary of incomplete deployments
                          Derya Altuntas Newbie

                          I have same problem.Error message is below.I could not find data source xml file to change.Where is it?

                           

                          DEPLOYMENTS MISSING DEPENDENCIES:
                            Deployment "persistence.unit:unitName=SiguardEJB.jar#SiguardEJBPU" is missing the following dependencies:
                              Dependency "jboss.jca:name=SiguardEJBJNDI,service=DataSourceBinding" (should be in state "Create", but is actually in state "** NOT FOUND Depends on 'jboss.jca:name=SiguardEJBJNDI,service=DataSourceBinding' **")

                          DEPLOYMENTS IN ERROR:
                            Deployment "jboss.jca:name=SiguardEJBJNDI,service=DataSourceBinding" is in error due to the following reason(s): ** NOT FOUND Depends on 'jboss.jca:name=SiguardEJBJNDI,service=DataSourceBinding' **

                          at org.jboss.deployers.plugins.deployers.DeployersImpl.checkComplete(DeployersImpl.java:1228) [:2.2.0.GA]
                          at org.jboss.deployers.plugins.main.MainDeployerImpl.checkComplete(MainDeployerImpl.java:905) [:2.2.0.GA]
                          at org.jboss.system.server.profileservice.deployers.MainDeployerPlugin.checkComplete(MainDeployerPlugin.java:87) [:6.0.0.Final]
                          at org.jboss.profileservice.deployment.ProfileDeployerPluginRegistry.checkAllComplete(ProfileDeployerPluginRegistry.java:107) [:0.2.2]
                          at org.jboss.system.server.profileservice.bootstrap.BasicProfileServiceBootstrap.start(BasicProfileServiceBootstrap.java:135) [:6.0.0.Final]
                          at org.jboss.system.server.profileservice.bootstrap.BasicProfileServiceBootstrap.start(BasicProfileServiceBootstrap.java:56) [:6.0.0.Final]
                          at org.jboss.bootstrap.impl.base.server.AbstractServer.startBootstraps(AbstractServer.java:827) [jboss-bootstrap-impl-base.jar:2.1.0-alpha-5]
                          at org.jboss.bootstrap.impl.base.server.AbstractServer$StartServerTask.run(AbstractServer.java:417) [jboss-bootstrap-impl-base.jar:2.1.0-alpha-5]

                          • 10. Jboss 5.1 Failed to load profile: Summary of incomplete deployments
                            Wolfgang Knauf Master

                            The "-ds.xml" files are normally found in %JBOSS_HOME%\server\default\deploy - but I think they might also be part of a deployed app.

                             

                            Hope this helps

                             

                            Wolfgang

                            • 11. Jboss 5.1 Failed to load profile: Summary of incomplete deployments
                              Derya Altuntas Newbie

                              Thanks Woolfgang.But I could not find any xml file about db in specified folder.

                              • 12. Jboss 5.1 Failed to load profile: Summary of incomplete deployments
                                Wolfgang Knauf Master

                                Hi,

                                 

                                as Jaikiran wrote above: please start a new thread about this issue. In this new thread, provide us with more details about your app:

                                -how does "persistence.xml" look like?

                                -is it a new app or some older stuff?

                                 

                                Best regards

                                 

                                Wolfgang

                                • 13. Re: Jboss 5.1 Failed to load profile: Summary of incomplete deployments
                                  John Ulmer Newbie

                                  Hello:

                                  I had a similar problem in a JPA project, because in my persistence.xml file I specified the wrong data source binding. Here's the log from before and after and details on the solution:

                                   

                                  ======================================

                                  DEPLOYMENTS MISSING DEPENDENCIES:

                                    Deployment "persistence.unit:unitName=ProjectEAR.ear/Project.jar#example-pu" is missing the following dependencies:

                                      Dependency "jboss.jca:name=JavaFinalDS,service=DataSourceBinding" (should be in state "Create", but is actually in state "** NOT FOUND Depends on 'jboss.jca:name=JavaFinalDS,service=DataSourceBinding' **")

                                   

                                  DEPLOYMENTS IN ERROR:

                                    Deployment "jboss.jca:name=JavaFinalDS,service=DataSourceBinding" is in error due to the following reason(s): ** NOT FOUND Depends on 'jboss.jca:name=JavaFinalDS,service=DataSourceBinding' **

                                   

                                      at org.jboss.deployers.plugins.deployers.DeployersImpl.checkComplete(DeployersImpl.java:863)

                                      at org.jboss.deployers.plugins.main.MainDeployerImpl.checkComplete(MainDeployerImpl.java:806)

                                      at org.jboss.system.server.profileservice.hotdeploy.HDScanner.scan(HDScanner.java:293)

                                      at org.jboss.system.server.profileservice.hotdeploy.HDScanner.run(HDScanner.java:221)

                                      at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)

                                      at java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java:317)

                                      at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:150)

                                      at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:98)

                                      at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.runPeriodic(ScheduledThreadPoolExecutor.java:180)

                                      at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:204)

                                      at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)

                                      at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)

                                      at java.lang.Thread.run(Thread.java:680)

                                   

                                  =============================

                                  At this point, I compared this project's persistence.xml file with that of another project, and found a difference:

                                  In this project's persistence.xml, the following lines specify the data source as "JavaFinalDS" (highlighted above in red):

                                   

                                          <jta-data-source>java:/JavaFinalDS</jta-data-source>

                                          <non-jta-data-source>java:/JavaFinalDS</non-jta-data-source>

                                   

                                  In the other project, that deploys correctly, the data source is specified as "DefaultDS":

                                   

                                          <jta-data-source>java:/DefaultDS</jta-data-source>

                                          <non-jta-data-source>java:/DefaultDS</non-jta-data-source>

                                   

                                  So I changed it to "DefaultDS" and redeployed successfully.

                                  =============================