10 Replies Latest reply on Oct 5, 2012 6:47 PM by Brian Wallis

    3.0.0 Beta 3 JBoss as kit for 7.2 won't start

    Brian Wallis Master

      (starting a new discussion rather than continue in the announcement thread)

      Hi Randall,

       

      I re-downloaded the kit after you fixed the links but am getting the same error on startup.

       

      {noformat}

      % bin/standalone.sh -c standalone-modeshape.xml                     

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

       

       

        JBoss Bootstrap Environment

       

       

        JBOSS_HOME: /Users/bwallis/InfoMedix/JBoss/ModeShape/jboss-as-7.2.0.Alpha1-SNAPSHOT

       

       

        JAVA: java

       

       

        JAVA_OPTS: -d32 -client -Xms64m -Xmx512m -XX:MaxPermSize=256m -Djava.net.preferIPv4Stack=true -Dorg.jboss.resolver.warning=true -Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000 -Djboss.modules.system.pkgs=org.jboss.byteman -Djava.awt.headless=true -Djboss.server.default.config=standalone.xml

       

       

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

       

       

      10:19:53,737 INFO  [org.jboss.modules] JBoss Modules version 1.1.3.GA

      10:19:53,937 INFO  [org.jboss.msc] JBoss MSC version 1.0.2.GA

      10:19:53,995 INFO  [org.jboss.as] JBAS015899: JBoss AS 7.2.0.Alpha1-SNAPSHOT "Steropes" starting

      10:19:54,493 ERROR [org.jboss.as.controller] JBAS014601: Error booting the container: java.lang.NoSuchMethodError: org.jboss.as.controller.SimpleListAttributeDefinition$Builder.<init>(Ljava/lang/String;Lorg/jboss/as/controller/SimpleAttributeDefinition;)V

                at org.modeshape.jboss.subsystem.MappedListAttributeDefinition$Builder.<init>(MappedListAttributeDefinition.java:388)

                at org.modeshape.jboss.subsystem.MappedListAttributeDefinition$Builder.of(MappedListAttributeDefinition.java:393)

                at org.modeshape.jboss.subsystem.ModelAttributes.<clinit>(ModelAttributes.java:150)

                at org.modeshape.jboss.subsystem.ModeShapeSubsystemXMLReader_1_0.parseWorkspaces(ModeShapeSubsystemXMLReader_1_0.java:266)

                at org.modeshape.jboss.subsystem.ModeShapeSubsystemXMLReader_1_0.parseRepository(ModeShapeSubsystemXMLReader_1_0.java:154)

                at org.modeshape.jboss.subsystem.ModeShapeSubsystemXMLReader_1_0.readElement(ModeShapeSubsystemXMLReader_1_0.java:70)

                at org.modeshape.jboss.subsystem.ModeShapeSubsystemXMLReader_1_0.readElement(ModeShapeSubsystemXMLReader_1_0.java:42)

                at org.jboss.staxmapper.XMLMapperImpl.processNested(XMLMapperImpl.java:110) [staxmapper-1.1.0.Final.jar:1.1.0.Final]

                at org.jboss.staxmapper.XMLExtendedStreamReaderImpl.handleAny(XMLExtendedStreamReaderImpl.java:69) [staxmapper-1.1.0.Final.jar:1.1.0.Final]

                at org.jboss.as.server.parsing.StandaloneXml.parseServerProfile(StandaloneXml.java:922) [jboss-as-server-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT]

                at org.jboss.as.server.parsing.StandaloneXml.readServerElement_1_1(StandaloneXml.java:339) [jboss-as-server-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT]

                at org.jboss.as.server.parsing.StandaloneXml.readElement(StandaloneXml.java:135) [jboss-as-server-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT]

                at org.jboss.as.server.parsing.StandaloneXml.readElement(StandaloneXml.java:104) [jboss-as-server-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT]

                at org.jboss.staxmapper.XMLMapperImpl.processNested(XMLMapperImpl.java:110) [staxmapper-1.1.0.Final.jar:1.1.0.Final]

                at org.jboss.staxmapper.XMLMapperImpl.parseDocument(XMLMapperImpl.java:69) [staxmapper-1.1.0.Final.jar:1.1.0.Final]

                at org.jboss.as.controller.persistence.XmlConfigurationPersister.load(XmlConfigurationPersister.java:133) [jboss-as-controller-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT]

                at org.jboss.as.server.ServerService.boot(ServerService.java:289) [jboss-as-server-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT]

                at org.jboss.as.controller.AbstractControllerService$1.run(AbstractControllerService.java:156) [jboss-as-controller-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT]

                at java.lang.Thread.run(Thread.java:680) [classes.jar:1.6.0_33]

       

       

      10:19:54,498 INFO  [org.jboss.as] JBAS015950: JBoss AS 7.2.0.Alpha1-SNAPSHOT "Steropes" stopped in 5ms

      {noformat}

        • 1. Re: 3.0.0 Beta 3 JBoss as kit for 7.2 won't start
          Brian Wallis Master

          I rebuilt JBoss 7.2.0 from a recent update from the master branch and then rebuilt modeshape 3.0.0-Beta3 after a small change to the pom to disable the javadoc generation (that seems to break for me for reasons unknown).

           

          I installed the modeshape 7.2 kit that I just built into the jboss 7.2.0 that I also had just built and it is starting up OK now.

           

          Looking into the jboss source it seems that the class SimpleAttributeDefinition has been renamed/replaced with AttributeDefinition. The kit in the Beta3 may be built against an older verion. The reason it works for me with a build is that  AS7-4767 re-introduced the missing method for backward compatibility reasons (for exactly the sort of problem we are seeing here). I think that change was commited to the jboss-as repository on the 18th July.

          1 of 1 people found this helpful
          • 2. Re: 3.0.0 Beta 3 JBoss as kit for 7.2 won't start
            Randall Hauch Master

            I rebuilt JBoss 7.2.0 from a recent update from the master branch and then rebuilt modeshape 3.0.0-Beta3 after a small change to the pom to disable the javadoc generation (that seems to break for me for reasons unknown).

            For future reference, "mvn clean install -Pintegration" should build the kits without the JavaDoc, while "mvn clean install -Passembly" will build the kits with the JavaDoc. (This isn't intuitive, but there is some logic behind it: we need the AS7 kits for the "modeshape-jbossas-integration-tests" but don't want/need these builds to produce the JavaDoc, while we use the "assembly" profile to generate the various assemblies -- including JavaDoc -- needed for a release.)

             

             

            I installed the modeshape 7.2 kit that I just built into the jboss 7.2.0 that I also had just built and it is starting up OK now.

             

            Looking into the jboss source it seems that the class SimpleAttributeDefinition has been renamed/replaced with AttributeDefinition. The kit in the Beta3 may be built against an older verion. The reason it works for me with a build is that  AS7-4767 re-introduced the missing method for backward compatibility reasons (for exactly the sort of problem we are seeing here). I think that change was commited to the jboss-as repository on the 18th July.

            This is one of the challenges we have with supporting both AS7.1 and 7.2. Currently, we're using the same codebase for both, but each fo the AS7 kits has slightly different modules and "standalone-modeshape.xml" configuration files.

             

            When I did the work for the 7.2 kits (MODE-1605) on August 22, I pulled the latest 7.2.0.Alpha1-SNAPSHOT code from 'master' branch of the JBoss AS Git repository, built locally, and then used that distribution in all of my tests. Per your notes, that already included the correction for AS7-4767.

             

            I guess the moral of the story is to try to use the latest 7.2 code as much as possible, at least until they start issuing releases.

            • 3. Re: 3.0.0 Beta 3 JBoss as kit for 7.2 won't start
              Brian Wallis Master

              Just a note that the problem persists with the 3.0.0.CR1 kit against the latest nightly build of JBoss AS7 7.2.0.Alpha1. I downloaded both today, unpacked the jboss distribution, unpaced the modeshape 7.2 kit on top of it and tried to start it up.

               

              I'll just try what I did last time and rebuild jboss followed by a build of modeshape 3.0.0.CR1

              • 4. Re: 3.0.0 Beta 3 JBoss as kit for 7.2 won't start
                Brian Wallis Master

                Nope, this is a slightly different problem.

                 

                AS7-4784 committed a month ago has removed the method setAlternates (amongst others) from the Builder class in

                 

                {noformat}controller/src/main/java/org/jboss/as/controller/SimpleListAttributeDefinition.java{noformat}

                 

                and this method is referenced from

                 

                {noformat}deploy/jbossas/modeshape-jbossas-subsystem/src/main/java/org/modeshape/jboss/subsystem/MappedListAttributeDefinition.java{noformat}

                 

                so when I build modeshape with the following command line:

                 

                {noformat}mvn clean install -s settings.xml -Pintegration,as72{noformat}

                 

                (after having built/installed the latest jboss-as-7.2.0.Alpha1-SNAPSHOT) I get an error

                 

                {code}

                [ERROR] Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:2.3.2:compile (default-compile) on project modeshape-jbossas-subsystem: Compilation failure

                [ERROR] /users/bwallis/InfoMedix/JBoss/ModeShape/workspace/modeshape-src/modeshape/deploy/jbossas/modeshape-jbossas-subsystem/src/main/java/org/modeshape/jboss/subsystem/MappedListAttributeDefinition.java:[408,19] cannot find symbol

                [ERROR] symbol  : method setAlternates(java.lang.String[])

                [ERROR] location: class org.jboss.as.controller.SimpleListAttributeDefinition.Builder

                {code}

                 

                The method setAlternates(String[]) is now on the superclass of Builder and is renamed to setAlternatives(String[])

                 

                They seem to be making it hard to keep a single AS7 integration module, AS 7.1 and 7.2 seem to be diverging a bit...

                • 5. Re: 3.0.0 Beta 3 JBoss as kit for 7.2 won't start
                  Randall Hauch Master

                  Ah, crap. I've logged this as MODE-1665 and will have a fix shortly that will be in 3.0.0.CR2.

                  • 6. Re: 3.0.0 Beta 3 JBoss as kit for 7.2 won't start
                    Randall Hauch Master

                    I've committed a fix to the 'master' branch. If you have time, grab the latest code, build the ModeShape kit for AS 7.2.0.Alpha1-SNAPSHOT, and give it a whirl. If not, the fix will be in CR2.

                     

                    Note that I'm getting several errors in the AS7 log that appear to be benign or are possibly bugs within the AS7.2 codebase (see MODE-1665 for details). That's not too farfetched, given that the AS7.2 code is not even Alpha ready. However, if you think they are issues with the ModeShape code, please let us know.

                    • 7. Re: 3.0.0 Beta 3 JBoss as kit for 7.2 won't start
                      Brian Wallis Master

                      I have updated to the latest code, built modeshape, installed in jboss 7.2.0 and it starts up ok (with the errors that you mentioned). I'll get on with rebuilding, deploying and running my load tests and see what happens. With the fixes to the configuration so i can get the indexes and binaries into the DB, this is getting exciting!

                      1 of 1 people found this helpful
                      • 8. Re: 3.0.0 Beta 3 JBoss as kit for 7.2 won't start
                        Brian Wallis Master

                        It seems to be running OK now with that fix for 7.2.0. The problem of the indexes and binaries not going into the cache and/or database still occurs and I've reopened MODE-1609 with a bit more info on the problem.

                        • 9. Re: 3.0.0 Beta 3 JBoss as kit for 7.2 won't start
                          Ted Jones Master

                          Brian,

                           

                          I am trying to reproduce MODE-1609. At what point do you see the index directories getting created? I am accessing the repo via the REST app and see this:

                           

                           

                           

                          09:19:20,211 INFO  [org.infinispan.factories.GlobalComponentRegistry] (http--127.0.0.1-8080-1) ISPN000128: Infinispan version: Infinispan 'Brahma' 5.1.2.FINAL
                          09:19:20,356 INFO  [org.jboss.as.clustering.infinispan] (http--127.0.0.1-8080-1) JBAS010281: Started testRepositoryCache cache from modeshapeCache container
                          09:19:20,414 INFO  [org.jboss.as.clustering.infinispan] (http--127.0.0.1-8080-1) JBAS010281: Started testRepository/system cache from modeshapeCache container
                          
                          • 10. Re: 3.0.0 Beta 3 JBoss as kit for 7.2 won't start
                            Brian Wallis Master

                            You will not see the creation message if the directories are already there. I clean out before each run, deleting the contents of standalone/data/modeshape and removing any database tables that were created. standalone/data/modeshape/testRepository is recreated when the server starts up again and I access http://localhost:8080/modeshape-rest/testRepository

                             

                            The complete log is

                             

                            {code}

                            08:32:58,460 INFO  [org.jboss.modules] JBoss Modules version 1.1.1.GA

                            08:32:58,705 INFO  [org.jboss.msc] JBoss MSC version 1.0.2.GA

                            08:32:58,760 INFO  [org.jboss.as] JBAS015899: JBoss AS 7.1.1.Final "Brontes" starting

                            08:32:59,745 INFO  [org.xnio] XNIO Version 3.0.3.GA

                            08:32:59,745 INFO  [org.jboss.as.server] JBAS015888: Creating http management service using socket-binding (management-http)

                            08:32:59,756 INFO  [org.xnio.nio] XNIO NIO Implementation Version 3.0.3.GA

                            08:32:59,764 INFO  [org.jboss.remoting] JBoss Remoting version 3.2.3.GA

                            08:32:59,781 INFO  [org.jboss.as.logging] JBAS011502: Removing bootstrap log handlers

                            08:32:59,785 INFO  [org.jboss.as.configadmin] (ServerService Thread Pool -- 27) JBAS016200: Activating ConfigAdmin Subsystem

                            08:32:59,792 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 32) JBAS010280: Activating Infinispan subsystem.

                            08:32:59,829 INFO  [org.jboss.as.naming] (ServerService Thread Pool -- 40) JBAS011800: Activating Naming Subsystem

                            08:32:59,840 INFO  [org.jboss.as.security] (ServerService Thread Pool -- 46) JBAS013101: Activating Security Subsystem

                            08:32:59,847 INFO  [org.jboss.as.osgi] (ServerService Thread Pool -- 41) JBAS011940: Activating OSGi Subsystem

                            08:32:59,852 INFO  [org.jboss.as.security] (MSC service thread 1-4) JBAS013100: Current PicketBox version=4.0.7.Final

                            08:32:59,869 INFO  [org.jboss.as.webservices] (ServerService Thread Pool -- 50) JBAS015537: Activating WebServices Extension

                            08:32:59,915 INFO  [org.jboss.as.connector] (MSC service thread 1-2) JBAS010408: Starting JCA Subsystem (JBoss IronJacamar 1.0.9.Final)

                            08:32:59,996 INFO  [org.jboss.as.naming] (MSC service thread 1-3) JBAS011802: Starting Naming Service

                            08:33:00,035 INFO  [org.jboss.as.mail.extension] (MSC service thread 1-3) JBAS015400: Bound mail session [java:jboss/mail/Default]

                            08:33:00,036 INFO  [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 28) JBAS010403: Deploying JDBC-compliant driver class org.h2.Driver (version 1.3)

                            08:33:00,094 INFO  [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 28) JBAS010404: Deploying non-JDBC-compliant driver class org.modeshape.jdbc.LocalJcrDriver (version 3.0)

                            08:33:00,108 INFO  [org.jboss.ws.common.management.AbstractServerConfig] (MSC service thread 1-7) JBoss Web Services - Stack CXF Server 4.0.2.GA

                            08:33:00,226 INFO  [org.apache.coyote.http11.Http11Protocol] (MSC service thread 1-1) Starting Coyote HTTP/1.1 on http-localhost-127.0.0.1-8080

                            08:33:00,947 INFO  [org.modeshape.jcr.JcrRepository] (MSC service thread 1-7) Initializing ModeShape version 3.0.0.CR1

                            08:33:00,962 INFO  [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-2) JBAS010400: Bound data source [java:/datasources/ModeShapeDS]

                            08:33:00,968 INFO  [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-3) JBAS010400: Bound data source [java:jboss/datasources/ExampleDS]

                            08:33:01,066 INFO  [org.jboss.as.remoting] (MSC service thread 1-3) JBAS017100: Listening on localhost/127.0.0.1:4447

                            08:33:01,067 INFO  [org.jboss.as.remoting] (MSC service thread 1-5) JBAS017100: Listening on /127.0.0.1:9999

                            08:33:01,074 INFO  [org.jboss.as.server.deployment.scanner] (MSC service thread 1-4) JBAS015012: Started FileSystemDeploymentService for directory /Users/bwallis/InfoMedix/JBoss/ModeShape/jboss-as-7.1.1.Final/standalone/deployments

                            08:33:01,086 INFO  [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) JBAS015003: Found modeshape-webdav.war in deployment directory. To trigger deployment create a file called modeshape-webdav.war.dodeploy

                            08:33:01,088 INFO  [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) JBAS015003: Found modeshape-rest.war in deployment directory. To trigger deployment create a file called modeshape-rest.war.dodeploy

                            08:33:01,194 INFO  [org.jboss.as] (Controller Boot Thread) JBAS015951: Admin console listening on http://127.0.0.1:9990

                            08:33:01,195 INFO  [org.jboss.as] (Controller Boot Thread) JBAS015874: JBoss AS 7.1.1.Final "Brontes" started in 3155ms - Started 146 of 250 services (101 services are passive or on-demand)

                            08:33:01,207 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-6) JBAS015876: Starting deployment of "modeshape-rest.war"

                            08:33:01,207 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-4) JBAS015876: Starting deployment of "modeshape-webdav.war"

                            08:33:01,666 INFO  [org.jboss.web] (MSC service thread 1-6) JBAS018210: Registering web context: /modeshape-webdav

                            08:33:01,793 INFO  [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-5) Deploying javax.ws.rs.core.Application: class org.modeshape.web.jcr.rest.JcrApplication

                            08:33:01,804 WARN  [org.jboss.resteasy.spi.ResteasyDeployment] (MSC service thread 1-5) Application.getClasses() returned unknown class type: org.modeshape.web.jcr.rest.form.FileUploadForm

                            08:33:01,938 INFO  [org.jboss.web] (MSC service thread 1-5) JBAS018210: Registering web context: /modeshape-rest

                            08:33:02,030 INFO  [org.jboss.as.server] (DeploymentScanner-threads - 2) JBAS018559: Deployed "modeshape-webdav.war"

                            08:33:02,031 INFO  [org.jboss.as.server] (DeploymentScanner-threads - 2) JBAS018559: Deployed "modeshape-rest.war"

                            08:34:25,640 INFO  [org.infinispan.factories.GlobalComponentRegistry] (http-localhost-127.0.0.1-8080-1) ISPN000128: Infinispan version: Infinispan 'Brahma' 5.1.2.FINAL

                            08:34:25,890 INFO  [org.infinispan.jmx.CacheJmxRegistration] (http-localhost-127.0.0.1-8080-1) ISPN000031: MBeans were successfully registered to the platform mbean server.

                            08:34:25,893 INFO  [org.jboss.as.clustering.infinispan] (http-localhost-127.0.0.1-8080-1) JBAS010281: Started testRepositoryCache cache from modeshapeCache container

                            08:34:26,464 INFO  [org.jboss.as.clustering.infinispan] (http-localhost-127.0.0.1-8080-1) JBAS010281: Started testRepository/system cache from modeshapeCache container

                            08:34:26,972 WARNING [org.modeshape.jcr.RepositoryConfiguration] (http-localhost-127.0.0.1-8080-1) The field name is not present on org.modeshape.jcr.security.ServletProvider or any of its super types

                            08:34:27,182 INFO  [org.hibernate.search.Version] (http-localhost-127.0.0.1-8080-1) HSEARCH000034: Hibernate Search 4.1.1.Final

                            08:34:27,244 INFO  [org.hibernate.annotations.common.Version] (http-localhost-127.0.0.1-8080-1) HCANN000001: Hibernate Commons Annotations {4.0.1.Final}

                            08:34:27,374 WARN  [org.hibernate.search.store.impl.DirectoryProviderHelper] (http-localhost-127.0.0.1-8080-1) HSEARCH000041: Index directory not found, creating: '/Users/bwallis/InfoMedix/JBoss/ModeShape/jboss-as-7.1.1.Final/standalone/data/modeshape/testRepository/testRepository/indexes'

                            08:34:27,376 WARN  [org.hibernate.search.store.impl.DirectoryProviderHelper] (http-localhost-127.0.0.1-8080-1) HSEARCH000041: Index directory not found, creating: '/Users/bwallis/InfoMedix/JBoss/ModeShape/jboss-as-7.1.1.Final/standalone/data/modeshape/testRepository/testRepository/indexes/nodeinfo'

                            08:34:27,591 INFO  [org.hibernate.search.indexes.serialization.avro.impl.AvroSerializationProvider] (http-localhost-127.0.0.1-8080-1) HSEARCH000079: Serialization protocol version 1.0

                            08:34:28,293 INFO  [org.jboss.as.clustering.infinispan] (http-localhost-127.0.0.1-8080-1) JBAS010281: Started testRepository/default cache from modeshapeCache container

                            {code}

                            You can see the point where the index directories are recreated in the 4th and 3rd last lines

                             

                            The directory for the binary storage isn't created until you add a property with a value greater than 4096 bytes. At this point the directory standalone/data/modeshape/testRepository/testRepository/binaries will be created as well despite the coinfiguration to put it into a cache.

                             

                            If I examine what caches exist via Naming (jndi) in the jboss admin panel I see only two caches created, the repository one and the binary one. The index cache as configured never makes it into the naming service and I assume is never accessed/initialised. The Binary cache is created but I don't think it is used since the binary directories are created and content is put in there (large amounts for my test application).

                             

                            Naming.jpg