11 Replies Latest reply on Feb 28, 2012 12:28 PM by Brian Stansberry

    DeploymentUnitProcessingException: More than 1 component found for type

    hartnellg Newbie

      I'm new to JBoss and EJB

       

      I'm following a tutorial for Eclipse / EJB / Glassfish, but converting to JBoss AS7 as I go along - see

      http://programming.manessinger.com/tutorials/an-eclipse-glassfish-java-ee-6-tutorial/

       

      Ive got to the point where I'm adding a servet to access the EJB:

      http://programming.manessinger.com/tutorials/an-eclipse-glassfish-java-ee-6-tutorial/#heading_toc_j_37

       

      When I start JBoss AS7, I get the following error:

       

      16:53:23,084 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-3) MSC00001: Failed to start service jboss.deployment.subunit."cookbookEAR.ear"."cookbookServlets.war".INSTALL: org.jboss.msc.service.StartException in service jboss.deployment.subunit."cookbookEAR.ear"."cookbookServlets.war".INSTALL: Failed to process phase INSTALL of subdeployment "cookbookServlets.war" of deployment "cookbookEAR.ear"

          at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:121) [jboss-as-server-7.1.0.CR1b.jar:7.1.0.CR1b]

          at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1824) [jboss-msc-1.0.1.GA.jar:1.0.1.GA]

          at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1759) [jboss-msc-1.0.1.GA.jar:1.0.1.GA]

          at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [:1.6.0_24]

          at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [:1.6.0_24]

          at java.lang.Thread.run(Thread.java:662) [:1.6.0_24]

      Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: More than 1 component found for type 'com.hartnell.cookbook.service.CookbookBean' and bean name null for binding com.hartnell.cookbook.service.CountryList/cbBean

          at org.jboss.as.ejb3.deployment.processors.EjbInjectionSource.getResourceValue(EjbInjectionSource.java:85)

          at org.jboss.as.ee.component.deployers.ModuleJndiBindingProcessor.addJndiBinding(ModuleJndiBindingProcessor.java:213)

          at org.jboss.as.ee.component.deployers.ModuleJndiBindingProcessor$1.handle(ModuleJndiBindingProcessor.java:180)

          at org.jboss.as.ee.component.ClassDescriptionTraversal.run(ClassDescriptionTraversal.java:54)

          at org.jboss.as.ee.component.deployers.ModuleJndiBindingProcessor.processClassConfigurations(ModuleJndiBindingProcessor.java:148)

          at org.jboss.as.ee.component.deployers.ModuleJndiBindingProcessor.deploy(ModuleJndiBindingProcessor.java:141)

          at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:115) [jboss-as-server-7.1.0.CR1b.jar:7.1.0.CR1b]

          ... 5 more

       

       

      This has only occurred since I added the Servlet processing.

      As far as I can work out, there is a source class CookbookBean and it's referenced in the servlet as:

      @EJB CookbookBean cbBean;

       

      I've googled extensively for this, but can't find anything relevant.

      I've no idea where to look to try and identify what this means.

       

      I'd appreciate some pointers or a shove in the right direction to get me past this

      Thanks for reading and any suggestions

       

      Geoff

        • 1. Re: DeploymentUnitProcessingException: More than 1 component found for type
          hartnellg Newbie

          In addition to posting here, I also contacted the author of the tutorial at

          http://programming.manessinger.com/tutorials/an-eclipse-glassfish-java-ee-6-tutorial

           

          At his suggestion, I rebuilt/reran the application using Glasfish 3.1.1 instead of JBoss AS 7 and I was able to retrieve the expected results by navigating to a local location in browser

          There were no start up exceptions or anything equivalent to DeploymentUnitProcessingException.

           

          I'd appreciate any insight into what might be causing DeploymentUnitProcessingException within JBoss AS 7

          Thanks for reading and any suggestions

           

          Geoff

          • 2. Re: DeploymentUnitProcessingException: More than 1 component found for type
            jaikiran pai Master

            Can you give this a quick try against the recently released 7.1.0.Final and see if it works in that version? If not, please post the new exception stacktrace from that version.

            • 3. Re: DeploymentUnitProcessingException: More than 1 component found for type
              hartnellg Newbie

              Jaikiran,

               

              I originally used JBoss version 7.1.0.CR1b, but I also tried against 7.1.0 Final with exactly the same results - here is the full stack trace:

               

              10:51:27,329 INFO  [org.jboss.as.security] (ServerService Thread Pool -- 44) JBAS013101: Activating Security Subsystem

              10:51:27,344 INFO  [org.jboss.as.naming] (ServerService Thread Pool -- 38) JBAS011800: Activating Naming Subsystem

              10:51:27,405 INFO  [org.jboss.as.configadmin] (ServerService Thread Pool -- 26) JBAS016200: Activating ConfigAdmin Subsystem

              10:51:27,412 INFO  [org.jboss.as.webservices] (ServerService Thread Pool -- 48) JBAS015537: Activating WebServices Extension

              10:51:27,446 INFO  [org.jboss.as.osgi] (ServerService Thread Pool -- 39) JBAS011940: Activating OSGi Subsystem

              10:51:27,480 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 31) JBAS010280: Activating Infinispan subsystem.

              10:51:27,667 INFO  [org.jboss.as.connector] (MSC service thread 1-2) JBAS010408: Starting JCA Subsystem (JBoss IronJacamar 1.0.7.Final)

              10:51:27,807 INFO  [org.jboss.as.naming] (MSC service thread 1-3) JBAS011802: Starting Naming Service

              10:51:27,810 INFO  [org.jboss.as.security] (MSC service thread 1-3) JBAS013100: Current PicketBox version=4.0.6.final

              10:51:27,870 INFO  [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 27) JBAS010403: Deploying JDBC-compliant driver class org.h2.Driver (version 1.3)

              10:51:27,912 INFO  [org.jboss.as.mail.extension] (MSC service thread 1-2) JBAS015400: Bound mail session [java:jboss/mail/Default]

              10:51:28,163 INFO  [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 27) JBAS010403: Deploying JDBC-compliant driver class oracle.jdbc.OracleDriver (version 11.2)

              10:51:28,369 INFO  [org.jboss.ws.common.management.AbstractServerConfig] (MSC service thread 1-3) JBoss Web Services - Stack CXF Server 4.0.1.GA

              10:51:28,570 INFO  [org.apache.coyote.http11.Http11Protocol] (MSC service thread 1-2) Starting Coyote HTTP/1.1 on http--127.0.0.1-8080

              10:51:28,596 INFO  [org.jboss.as.server.deployment.scanner] (MSC service thread 1-4) JBAS015012: Started FileSystemDeploymentService for directory D:\WebContainers\JBoss\jboss-as-7.1.0.Final\standalone\deployments

              10:51:28,606 INFO  [org.jboss.as.remoting] (MSC service thread 1-4) JBAS017100: Listening on /127.0.0.1:9999

              10:51:28,614 INFO  [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) JBAS015003: Found cookbookEAR.ear in deployment directory. To trigger deployment create a file called cookbookEAR.ear.dodeploy

              10:51:28,618 INFO  [org.jboss.as.remoting] (MSC service thread 1-4) JBAS017100: Listening on /127.0.0.1:4447

              10:51:28,759 INFO  [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-1) JBAS010400: Bound data source [java:jboss/datasources/ExampleDS]

              10:51:28,773 INFO  [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-4) JBAS010400: Bound data source [java:jboss/datasources/JeeExample]

              10:51:28,910 INFO  [org.jboss.as] (MSC service thread 1-3) JBAS015874: JBoss AS 7.1.0.Final "Thunder" started in 3521ms - Started 139 of 211 services (70 services are passive or on-demand)

              10:51:28,920 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-4) JBAS015876: Starting deployment of "cookbookEAR.ear"

              10:51:28,982 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015876: Starting deployment of "cookbookServlets.war"

              10:51:28,983 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015876: Starting deployment of "cookbookEJB.jar"

              10:51:29,091 INFO  [org.jboss.as.jpa] (MSC service thread 1-2) JBAS011401: Read persistence.xml for cookbookEJB

              10:51:29,221 INFO  [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-3) JNDI bindings for session bean named Conversion in deployment unit subdeployment "cookbookEJB.jar" of deployment "cookbookEAR.ear" are as follows:

               

                  java:global/cookbookEAR/cookbookEJB/Conversion!com.hartnell.cookbook.util.Conversion

                  java:app/cookbookEJB/Conversion!com.hartnell.cookbook.util.Conversion

                  java:module/Conversion!com.hartnell.cookbook.util.Conversion

                  java:global/cookbookEAR/cookbookEJB/Conversion

                  java:app/cookbookEJB/Conversion

                  java:module/Conversion

               

              10:51:29,226 INFO  [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-3) JNDI bindings for session bean named CookbookBean in deployment unit subdeployment "cookbookEJB.jar" of deployment "cookbookEAR.ear" are as follows:

               

                  java:global/cookbookEAR/cookbookEJB/CookbookBean!com.hartnell.cookbook.service.CookbookBean

                  java:app/cookbookEJB/CookbookBean!com.hartnell.cookbook.service.CookbookBean

                  java:module/CookbookBean!com.hartnell.cookbook.service.CookbookBean

                  java:global/cookbookEAR/cookbookEJB/CookbookBean!com.hartnell.cookbook.service.CookbookInterface

                  java:app/cookbookEJB/CookbookBean!com.hartnell.cookbook.service.CookbookInterface

                  java:module/CookbookBean!com.hartnell.cookbook.service.CookbookInterface

                  java:jboss/exported/cookbookEAR/cookbookEJB/CookbookBean!com.hartnell.cookbook.service.CookbookInterface

               

              10:51:29,281 INFO  [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-3) JNDI bindings for session bean named CookbookEao in deployment unit subdeployment "cookbookEJB.jar" of deployment "cookbookEAR.ear" are as follows:

               

                  java:global/cookbookEAR/cookbookEJB/CookbookEao!com.hartnell.cookbook.eao.CookbookEao

                  java:app/cookbookEJB/CookbookEao!com.hartnell.cookbook.eao.CookbookEao

                  java:module/CookbookEao!com.hartnell.cookbook.eao.CookbookEao

                  java:global/cookbookEAR/cookbookEJB/CookbookEao

                  java:app/cookbookEJB/CookbookEao

                  java:module/CookbookEao

               

              10:51:29,401 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-3) MSC00001: Failed to start service jboss.deployment.subunit."cookbookEAR.ear"."cookbookServlets.war".INSTALL: org.jboss.msc.service.StartException in service jboss.deployment.subunit."cookbookEAR.ear"."cookbookServlets.war".INSTALL: Failed to process phase INSTALL of subdeployment "cookbookServlets.war" of deployment "cookbookEAR.ear"

                  at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:119) [jboss-as-server-7.1.0.Final.jar:7.1.0.Final]

                  at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]

                  at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]

                  at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [rt.jar:1.6.0_24]

                  at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [rt.jar:1.6.0_24]

                  at java.lang.Thread.run(Thread.java:662) [rt.jar:1.6.0_24]

              Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: More than 1 component found for type 'com.hartnell.cookbook.service.CookbookBean' and bean name null for binding com.hartnell.cookbook.service.CountryList/cbBean

                  at org.jboss.as.ejb3.deployment.processors.EjbInjectionSource.getResourceValue(EjbInjectionSource.java:88)

                  at org.jboss.as.ee.component.deployers.ModuleJndiBindingProcessor.addJndiBinding(ModuleJndiBindingProcessor.java:227)

                  at org.jboss.as.ee.component.deployers.ModuleJndiBindingProcessor$1.handle(ModuleJndiBindingProcessor.java:194)

                  at org.jboss.as.ee.component.ClassDescriptionTraversal.run(ClassDescriptionTraversal.java:54)

                  at org.jboss.as.ee.component.deployers.ModuleJndiBindingProcessor.processClassConfigurations(ModuleJndiBindingProcessor.java:162)

                  at org.jboss.as.ee.component.deployers.ModuleJndiBindingProcessor.deploy(ModuleJndiBindingProcessor.java:155)

                  at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:113) [jboss-as-server-7.1.0.Final.jar:7.1.0.Final]

                  ... 5 more

               

              10:51:29,682 INFO  [org.jboss.wsf.stack.cxf.metadata.MetadataBuilder] (MSC service thread 1-4) Add Service

              id=CookbookBean

              address=http://localhost:8080/cookbookEJB/CookbookBean

              implementor=com.hartnell.cookbook.service.CookbookBean

              invoker=org.jboss.wsf.stack.cxf.JBossWSInvoker

              serviceName={http://service.cookbook.hartnell.com/}CookbookBeanService

              portName={http://service.cookbook.hartnell.com/}CookbookBeanPort

              wsdlLocation=null

              mtomEnabled=false

              properties=[org.jboss.as.webservices.metadata.modelEjbComponentViewName -> service jboss.deployment.subunit."cookbookEAR.ear"."cookbookEJB.jar".component.CookbookBean.VIEW."com.hartnell.cookbook.service.CookbookBean".SERVICE_ENDPOINT]

              10:51:29,869 INFO  [org.apache.cxf.service.factory.ReflectionServiceFactoryBean] (MSC service thread 1-4) Creating Service {http://service.cookbook.hartnell.com/}CookbookBeanService from class com.hartnell.cookbook.service.CookbookBean

              10:51:30,413 INFO  [org.apache.cxf.endpoint.ServerImpl] (MSC service thread 1-4) Setting the server's publish address to be http://localhost:8080/cookbookEJB/CookbookBean

              10:51:30,523 INFO  [org.jboss.wsf.stack.cxf.deployment.WSDLFilePublisher] (MSC service thread 1-4) WSDL published to: file:/D:/WebContainers/JBoss/jboss-as-7.1.0.Final/standalone/data/wsdl/cookbookEAR.ear/cookbookEJB.jar/CookbookBeanService.wsdl

              10:51:30,531 INFO  [org.jboss.as.webservices] (MSC service thread 1-1) JBAS015539: Starting service jboss.ws.port-component-link

              10:51:30,543 INFO  [org.jboss.as.jpa] (MSC service thread 1-4) JBAS011402: Starting Persistence Unit Service 'cookbookEAR.ear/cookbookEJB.jar#cookbookEJB'

              10:51:30,661 INFO  [org.hibernate.annotations.common.Version] (MSC service thread 1-4) HCANN000001: Hibernate Commons Annotations {4.0.1.Final}

              10:51:30,666 INFO  [org.hibernate.Version] (MSC service thread 1-4) HHH000412: Hibernate Core {4.0.1.Final}

              10:51:30,668 INFO  [org.hibernate.cfg.Environment] (MSC service thread 1-4) HHH000206: hibernate.properties not found

              10:51:30,670 INFO  [org.hibernate.cfg.Environment] (MSC service thread 1-4) HHH000021: Bytecode provider name : javassist

              10:51:30,695 INFO  [org.hibernate.ejb.Ejb3Configuration] (MSC service thread 1-4) HHH000204: Processing PersistenceUnitInfo [

                  name: cookbookEJB

                  ...]

              10:51:30,867 INFO  [org.hibernate.service.jdbc.connections.internal.ConnectionProviderInitiator] (MSC service thread 1-4) HHH000130: Instantiating explicit connection provider: org.hibernate.ejb.connection.InjectedDataSourceConnectionProvider

              10:51:31,313 INFO  [org.hibernate.dialect.Dialect] (MSC service thread 1-4) HHH000400: Using dialect: org.hibernate.dialect.Oracle10gDialect

              10:51:31,330 INFO  [org.hibernate.engine.transaction.internal.TransactionFactoryInitiator] (MSC service thread 1-4) HHH000268: Transaction strategy: org.hibernate.engine.transaction.internal.jta.CMTTransactionFactory

              10:51:31,334 INFO  [org.hibernate.hql.internal.ast.ASTQueryTranslatorFactory] (MSC service thread 1-4) HHH000397: Using ASTQueryTranslatorFactory

              10:51:31,375 INFO  [org.hibernate.validator.util.Version] (MSC service thread 1-4) Hibernate Validator 4.2.0.Final

              10:51:31,646 INFO  [org.jboss.as.webservices] (MSC service thread 1-4) JBAS015539: Starting service jboss.ws.endpoint."cookbookEAR.ear"."cookbookEJB.jar".CookbookBean

              10:51:31,651 INFO  [org.jboss.ws.common.management.DefaultEndpointRegistry] (MSC service thread 1-4) register: jboss.ws:context=cookbookEJB,endpoint=CookbookBean

              10:51:31,653 INFO  [org.jboss.web] (MSC service thread 1-2) JBAS018210: Registering web context: /cookbookEJB

              10:51:31,857 INFO  [org.jboss.as.server] (DeploymentScanner-threads - 2) JBAS015870: Deploy of deployment "cookbookEAR.ear" was rolled back with failure message {"JBAS014671: Failed services" => {"jboss.deployment.subunit.\"cookbookEAR.ear\".\"cookbookServlets.war\".INSTALL" => "org.jboss.msc.service.StartException in service jboss.deployment.subunit.\"cookbookEAR.ear\".\"cookbookServlets.war\".INSTALL: Failed to process phase INSTALL of subdeployment \"cookbookServlets.war\" of deployment \"cookbookEAR.ear\""}}

              10:51:31,870 INFO  [org.jboss.as.webservices] (MSC service thread 1-3) JBAS015540: Stopping service jboss.ws.endpoint."cookbookEAR.ear"."cookbookEJB.jar".CookbookBean

              10:51:31,873 INFO  [org.jboss.ws.common.management.DefaultEndpointRegistry] (MSC service thread 1-3) remove: jboss.ws:context=cookbookEJB,endpoint=CookbookBean

              10:51:31,882 INFO  [org.jboss.as.jpa] (MSC service thread 1-1) JBAS011403: Stopping Persistence Unit Service 'cookbookEAR.ear/cookbookEJB.jar#cookbookEJB'

              10:51:31,893 INFO  [org.jboss.as.webservices] (MSC service thread 1-4) JBAS015540: Stopping service jboss.ws.port-component-link

              10:51:31,968 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-2) JBAS015877: Stopped deployment cookbookServlets.war in 106ms

              10:51:31,969 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-2) JBAS015877: Stopped deployment cookbookEJB.jar in 108ms

              10:51:31,976 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-2) JBAS015877: Stopped deployment cookbookEAR.ear in 118ms

              10:51:31,978 INFO  [org.jboss.as.controller] (DeploymentScanner-threads - 2) JBAS014774: Service status report

              JBAS014777:   Services which failed to start:      service jboss.deployment.subunit."cookbookEAR.ear"."cookbookServlets.war".INSTALL: org.jboss.msc.service.StartException in service jboss.deployment.subunit."cookbookEAR.ear"."cookbookServlets.war".INSTALL: Failed to process phase INSTALL of subdeployment "cookbookServlets.war" of deployment "cookbookEAR.ear"

               

              10:51:31,984 ERROR [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) {"JBAS014653: Composite operation failed and was rolled back. Steps that failed:" => {"Operation step-2" => {"JBAS014671: Failed services" => {"jboss.deployment.subunit.\"cookbookEAR.ear\".\"cookbookServlets.war\".INSTALL" => "org.jboss.msc.service.StartException in service jboss.deployment.subunit.\"cookbookEAR.ear\".\"cookbookServlets.war\".INSTALL: Failed to process phase INSTALL of subdeployment \"cookbookServlets.war\" of deployment \"cookbookEAR.ear\""}}}}

               

              Geoff

              • 4. Re: DeploymentUnitProcessingException: More than 1 component found for type
                jaikiran pai Master

                Just looked at that example. This is a bug in AS7 which is triggered by the use of @WebService on the stateless bean (CookbookBean in this case). I'll add a fix for this.

                • 6. Re: DeploymentUnitProcessingException: More than 1 component found for type
                  jaikiran pai Master

                  A fix for this is now available in the latest nightly build https://community.jboss.org/thread/167590. Please try it there and see if it fixes the issue for you.

                  • 7. Re: DeploymentUnitProcessingException: More than 1 component found for type
                    hartnellg Newbie

                    I've installed the fix obtained from the location as described by Jaikiran Pai above.
                    This fixes the original problem - the subject of this post, but I now see a further problem in the server log when JBoss AS 7 is starting:

                     

                    14:08:31,934 INFO  [org.jboss.as] (MSC service thread 1-3) JBAS015874: JBoss AS 7.1.1.Final-SNAPSHOT "Thunder" started in 5594ms - Started 240 of 319 services (77 services are passive or on-demand)

                    14:08:31,960 ERROR [org.jboss.as.controller.management-operation] (DeploymentScanner-threads - 2) JBAS014608: Failed to store configuration to standalone.xml: java.io.SyncFailedException: sync failed

                        at java.io.FileDescriptor.sync(Native Method) [rt.jar:1.6.0_24]

                        at org.jboss.as.controller.persistence.FilePersistenceResource.commit(FilePersistenceResource.java:83) [jboss-as-controller-7.1.1.Final-SNAPSHOT.jar:7.1.1.Final-SNAPSHOT]

                        at org.jboss.as.controller.persistence.ConfigurationFilePersistenceResource.commit(ConfigurationFilePersistenceResource.java:49) [jboss-as-controller-7.1.1.Final-SNAPSHOT.jar:7.1.1.Final-SNAPSHOT]

                        at org.jboss.as.controller.ModelControllerImpl$2.commit(ModelControllerImpl.java:389) [jboss-as-controller-7.1.1.Final-SNAPSHOT.jar:7.1.1.Final-SNAPSHOT]

                        at org.jboss.as.controller.AbstractOperationContext.doCompleteStep(AbstractOperationContext.java:342) [jboss-as-controller-7.1.1.Final-SNAPSHOT.jar:7.1.1.Final-SNAPSHOT]

                        at org.jboss.as.controller.AbstractOperationContext.completeStep(AbstractOperationContext.java:200) [jboss-as-controller-7.1.1.Final-SNAPSHOT.jar:7.1.1.Final-SNAPSHOT]

                        at org.jboss.as.controller.AbstractOperationContext.finishStep(AbstractOperationContext.java:451) [jboss-as-controller-7.1.1.Final-SNAPSHOT.jar:7.1.1.Final-SNAPSHOT]

                        at org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:438) [jboss-as-controller-7.1.1.Final-SNAPSHOT.jar:7.1.1.Final-SNAPSHOT]

                        at org.jboss.as.controller.AbstractOperationContext.doCompleteStep(AbstractOperationContext.java:272) [jboss-as-controller-7.1.1.Final-SNAPSHOT.jar:7.1.1.Final-SNAPSHOT]

                        at org.jboss.as.controller.AbstractOperationContext.completeStep(AbstractOperationContext.java:200) [jboss-as-controller-7.1.1.Final-SNAPSHOT.jar:7.1.1.Final-SNAPSHOT]

                        at org.jboss.as.server.deployment.DeploymentHandlerUtil$1.execute(DeploymentHandlerUtil.java:118) [jboss-as-server-7.1.1.Final-SNAPSHOT.jar:7.1.1.Final-SNAPSHOT]

                        at org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:385) [jboss-as-controller-7.1.1.Final-SNAPSHOT.jar:7.1.1.Final-SNAPSHOT]

                        at org.jboss.as.controller.AbstractOperationContext.doCompleteStep(AbstractOperationContext.java:272) [jboss-as-controller-7.1.1.Final-SNAPSHOT.jar:7.1.1.Final-SNAPSHOT]

                        at org.jboss.as.controller.AbstractOperationContext.completeStep(AbstractOperationContext.java:200) [jboss-as-controller-7.1.1.Final-SNAPSHOT.jar:7.1.1.Final-SNAPSHOT]

                        at org.jboss.as.server.deployment.DeploymentDeployHandler.execute(DeploymentDeployHandler.java:73) [jboss-as-server-7.1.1.Final-SNAPSHOT.jar:7.1.1.Final-SNAPSHOT]

                        at org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:385) [jboss-as-controller-7.1.1.Final-SNAPSHOT.jar:7.1.1.Final-SNAPSHOT]

                        at org.jboss.as.controller.AbstractOperationContext.doCompleteStep(AbstractOperationContext.java:272) [jboss-as-controller-7.1.1.Final-SNAPSHOT.jar:7.1.1.Final-SNAPSHOT]

                        at org.jboss.as.controller.AbstractOperationContext.completeStep(AbstractOperationContext.java:200) [jboss-as-controller-7.1.1.Final-SNAPSHOT.jar:7.1.1.Final-SNAPSHOT]

                        at org.jboss.as.server.deployment.DeploymentAddHandler.execute(DeploymentAddHandler.java:174) [jboss-as-server-7.1.1.Final-SNAPSHOT.jar:7.1.1.Final-SNAPSHOT]

                        at org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:385) [jboss-as-controller-7.1.1.Final-SNAPSHOT.jar:7.1.1.Final-SNAPSHOT]

                        at org.jboss.as.controller.AbstractOperationContext.doCompleteStep(AbstractOperationContext.java:272) [jboss-as-controller-7.1.1.Final-SNAPSHOT.jar:7.1.1.Final-SNAPSHOT]

                        at org.jboss.as.controller.AbstractOperationContext.completeStep(AbstractOperationContext.java:200) [jboss-as-controller-7.1.1.Final-SNAPSHOT.jar:7.1.1.Final-SNAPSHOT]

                        at org.jboss.as.controller.CompositeOperationHandler.execute(CompositeOperationHandler.java:85) [jboss-as-controller-7.1.1.Final-SNAPSHOT.jar:7.1.1.Final-SNAPSHOT]

                        at org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:385) [jboss-as-controller-7.1.1.Final-SNAPSHOT.jar:7.1.1.Final-SNAPSHOT]

                        at org.jboss.as.controller.AbstractOperationContext.doCompleteStep(AbstractOperationContext.java:272) [jboss-as-controller-7.1.1.Final-SNAPSHOT.jar:7.1.1.Final-SNAPSHOT]

                        at org.jboss.as.controller.AbstractOperationContext.completeStep(AbstractOperationContext.java:200) [jboss-as-controller-7.1.1.Final-SNAPSHOT.jar:7.1.1.Final-SNAPSHOT]

                        at org.jboss.as.controller.CompositeOperationHandler.execute(CompositeOperationHandler.java:85) [jboss-as-controller-7.1.1.Final-SNAPSHOT.jar:7.1.1.Final-SNAPSHOT]

                        at org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:385) [jboss-as-controller-7.1.1.Final-SNAPSHOT.jar:7.1.1.Final-SNAPSHOT]

                        at org.jboss.as.controller.AbstractOperationContext.doCompleteStep(AbstractOperationContext.java:272) [jboss-as-controller-7.1.1.Final-SNAPSHOT.jar:7.1.1.Final-SNAPSHOT]

                        at org.jboss.as.controller.AbstractOperationContext.completeStep(AbstractOperationContext.java:200) [jboss-as-controller-7.1.1.Final-SNAPSHOT.jar:7.1.1.Final-SNAPSHOT]

                        at org.jboss.as.controller.ModelControllerImpl$DefaultPrepareStepHandler.execute(ModelControllerImpl.java:461) [jboss-as-controller-7.1.1.Final-SNAPSHOT.jar:7.1.1.Final-SNAPSHOT]

                        at org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:385) [jboss-as-controller-7.1.1.Final-SNAPSHOT.jar:7.1.1.Final-SNAPSHOT]

                        at org.jboss.as.controller.AbstractOperationContext.doCompleteStep(AbstractOperationContext.java:272) [jboss-as-controller-7.1.1.Final-SNAPSHOT.jar:7.1.1.Final-SNAPSHOT]

                        at org.jboss.as.controller.AbstractOperationContext.completeStep(AbstractOperationContext.java:200) [jboss-as-controller-7.1.1.Final-SNAPSHOT.jar:7.1.1.Final-SNAPSHOT]

                        at org.jboss.as.controller.ModelControllerImpl.execute(ModelControllerImpl.java:121) [jboss-as-controller-7.1.1.Final-SNAPSHOT.jar:7.1.1.Final-SNAPSHOT]

                        at org.jboss.as.controller.ModelControllerImpl$1.execute(ModelControllerImpl.java:304) [jboss-as-controller-7.1.1.Final-SNAPSHOT.jar:7.1.1.Final-SNAPSHOT]

                        at org.jboss.as.controller.ModelControllerImpl$1.execute(ModelControllerImpl.java:294) [jboss-as-controller-7.1.1.Final-SNAPSHOT.jar:7.1.1.Final-SNAPSHOT]

                        at org.jboss.as.server.deployment.scanner.FileSystemDeploymentService$DeploymentTask.call(FileSystemDeploymentService.java:1251)

                        at org.jboss.as.server.deployment.scanner.FileSystemDeploymentService$DeploymentTask.call(FileSystemDeploymentService.java:1241)

                        at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) [rt.jar:1.6.0_24]

                        at java.util.concurrent.FutureTask.run(FutureTask.java:138) [rt.jar:1.6.0_24]

                        at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:98) [rt.jar:1.6.0_24]

                        at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:206) [rt.jar:1.6.0_24]

                        at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [rt.jar:1.6.0_24]

                        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [rt.jar:1.6.0_24]

                        at java.lang.Thread.run(Thread.java:662) [rt.jar:1.6.0_24]

                        at org.jboss.threads.JBossThread.run(JBossThread.java:122) [jboss-threads-2.0.0.GA.jar:2.0.0.GA]

                     

                    14:08:32,057 INFO  [org.jboss.as.server] (DeploymentScanner-threads - 2) JBAS018559: Deployed "cookbookEAR_gf.ear"

                     

                     

                    This does not seem to affect the operation of theJBoss AS as I can send a Soap request via SoapUI and get back the expected response.

                    I've tried removing the read-only properties from standalone.xml (in Windows 7), and the file no longer reports read only.

                    Indeed if standalone.xml is open in a text editor, then following the JBoss AS7 start, the editor reports a change to the file.

                    Any idea if this is specific to my installation or a more general problem.

                     

                    Thanks for reading and any suggestions

                    Geoff

                    • 8. Re: DeploymentUnitProcessingException: More than 1 component found for type
                      jaikiran pai Master

                      hartnellg wrote:

                       

                      I've tried removing the read-only properties from standalone.xml (in Windows 7), and the file no longer reports read only.

                      Indeed if standalone.xml is open in a text editor, then following the JBoss AS7 start, the editor reports a change to the file.

                      Any idea if this is specific to my installation or a more general problem.

                       

                      Do you see that error when the file is write enabled before starting the server? By the way, what made it read-only in first place?

                      • 9. Re: DeploymentUnitProcessingException: More than 1 component found for type
                        hartnellg Newbie

                        jaikiran pai wrote:

                        Do you see that error when the file is write enabled before starting the server? By the way, what made it read-only in first place?

                         

                        I'm not convinced the file was ever read only, but Windows 7 properties for the installation root directory shows read only, and that was my first thought.

                        The application was installed as for the previous versions, i.e. by just unzipping the downloaded zip file, so there should not be any reason for it to be read only.

                         

                        The Windows 7 properties for my previous two installations root directories - jboss-as-7.1.0.CR1b and jboss-as-7.1.0.Final - also show as read only

                        However, the Windows 7 properties for the individual standalone.xml files in those installations do NOT show read only  .

                        This may be a peculiarity of Windows 7, as the file property itself for the SNAPSHOT installation does NOT show read only.

                         

                        When standalone.xml is loaded in a text editor prior to starting JBoss AS 7, the text editor reports a change to the standalone.xml file after starting JBoss AS 7 (SNAPSHOT) - do I want to reload it ?

                         

                        Not sure that has really answered your question and I acknowledge that there is not a lot to work with.

                        Geoff

                        • 10. Re: DeploymentUnitProcessingException: More than 1 component found for type
                          jaikiran pai Master

                          I haven't seen that

                          14:08:31,960 ERROR [org.jboss.as.controller.management-operation] (DeploymentScanner-threads - 2) JBAS014608: Failed to store configuration to standalone.xml: java.io.SyncFailedException: sync failed

                              at java.io.FileDescriptor.sync(Native Method) [rt.jar:1.6.0_24]

                              at org.jboss.as.controller.persistence.FilePersistenceResource.commit(FilePersistenceResource.java:83) [jboss-as-controller-7.1.1.Final-SNAPSHOT.jar:7.1.1.Final-SNAPSHOT]

                          error before. I'll check with someone who have more knowledge about this and see if they have any idea.

                          • 11. Re: DeploymentUnitProcessingException: More than 1 component found for type
                            Brian Stansberry Master

                            Is this a build of the latest upstream master? I don't think so based on the line numbers. I introduced a bug into upstream for a few hours at about 5 PM EST on Feb 22, and those line numbers correspond to the buggy code.

                             

                            If you still see this with a build of the latest upstream, please open a bug report in JIRA and assign it to me. Thanks!