7 Replies Latest reply on Mar 26, 2012 7:14 AM by mstruk

    GateIn 3.2.0.Final on existing jboss-as-7.1.0.Final installation?

    bussien

      Is there a package available I can import import via 'Import/Existing Maven Project' into 'JBoss Developer Studio' and then 'Add and Remove...'  'Publish to the server'?

        • 1. Re: GateIn 3.2.0.Final on existing jboss-as-7.1.0.Final installation?
          theute

          You should deploy to GateIn so you can treat GateIn as a standard AS 7.1 installation and you can deploy your portlets, skins, portals to that "special" server.

          • 2. Re: GateIn 3.2.0.Final on existing jboss-as-7.1.0.Final installation?
            bussien

            Thanks Tom - the problem is fixed:

            I installed again 'GateIn-3.2.0.Final-jbossas7-preview' and this time was able to add a user.

             

            Now I have to install:

            • gatein
            • gatein-sample-extension
            • gatein-sample-portal
            • gatein-sample-skin

            into 'JBoss Developer Studio' ?

            • 3. Re: GateIn 3.2.0.Final on existing jboss-as-7.1.0.Final installation?
              bussien

              and what that means?

              18:16:33,402 INFO  [org.jboss.as] JBAS015899: JBoss AS 7.1.0.Final "Thunder" starting

              18:16:33,885 INFO  [org.jboss.as] JBAS015950: JBoss AS 7.1.0.Final "Thunder" stopped in 5ms

              18:16:33,885 ERROR [org.jboss.as.controller] JBAS014601: Error booting the container: java.lang.RuntimeException: org.jboss.as.controller.persistence.ConfigurationPersistenceException: JBAS014676: Failed to parse configuration

                        at org.jboss.as.controller.AbstractControllerService$1.run(AbstractControllerService.java:161) [jboss-as-controller-7.1.0.Final.jar:7.1.0.Final]

                        at java.lang.Thread.run(Unknown Source) [rt.jar:1.7.0_04-ea]

              Caused by: org.jboss.as.controller.persistence.ConfigurationPersistenceException: JBAS014676: Failed to parse configuration

              • 4. Re: GateIn 3.2.0.Final on existing jboss-as-7.1.0.Final installation?
                mstruk

                Marcel Bussien wrote:

                 

                Now I have to install:

                • gatein
                • gatein-sample-extension
                • gatein-sample-portal
                • gatein-sample-skin

                into 'JBoss Developer Studio' ?

                 

                These are deployment archives. What you want to install into your IDE are libraries that your project requires. I guess there must be a wizard for creating a new portlet project, that automatically adds dependencies on javax.portlet, javax.servlet ... maven artifacts.

                • 5. Re: GateIn 3.2.0.Final on existing jboss-as-7.1.0.Final installation?
                  mstruk

                  Marcel Bussien wrote:

                   

                  and what that means?

                  18:16:33,402 INFO  [org.jboss.as] JBAS015899: JBoss AS 7.1.0.Final "Thunder" starting

                  18:16:33,885 INFO  [org.jboss.as] JBAS015950: JBoss AS 7.1.0.Final "Thunder" stopped in 5ms

                  18:16:33,885 ERROR [org.jboss.as.controller] JBAS014601: Error booting the container: java.lang.RuntimeException: org.jboss.as.controller.persistence.ConfigurationPersistenceException: JBAS014676: Failed to parse configuration

                            at org.jboss.as.controller.AbstractControllerService$1.run(AbstractControllerService.java:161) [jboss-as-controller-7.1.0.Final.jar:7.1.0.Final]

                            at java.lang.Thread.run(Unknown Source) [rt.jar:1.7.0_04-ea]

                  Caused by: org.jboss.as.controller.persistence.ConfigurationPersistenceException: JBAS014676: Failed to parse configuration

                  A broken standalone.xml maybe? But there should be a more verbose stacktrace ...  How do you start your JBoss AS?

                  • 6. Re: GateIn 3.2.0.Final on existing jboss-as-7.1.0.Final installation?
                    bussien

                    Thanks Marco - no, its the standard standalone.xml comming out of the box:

                     

                    WARNING: -logmodule is deprecated. Please use the system property 'java.util.logging.manager' or the 'java.util.logging.LogManager' service loader.

                    10:41:56,128 INFO  [org.jboss.modules] JBoss Modules version 1.1.1.GA

                    10:41:57,682 INFO  [org.jboss.msc] JBoss MSC version 1.0.2.GA

                    10:41:57,745 INFO  [org.jboss.as] JBAS015899: JBoss AS 7.1.0.Final "Thunder" starting

                    10:42:03,263 INFO  [org.jboss.as] JBAS015950: JBoss AS 7.1.0.Final "Thunder" stopped in 7ms

                    10:42:03,257 ERROR [org.jboss.as.controller] JBAS014601: Error booting the container: java.lang.RuntimeException: org.jboss.as.controller.persistence.ConfigurationPersistenceException: JBAS014676: Failed to parse configuration

                              at org.jboss.as.controller.AbstractControllerService$1.run(AbstractControllerService.java:161) [jboss-as-controller-7.1.0.Final.jar:7.1.0.Final]

                              at java.lang.Thread.run(Unknown Source) [rt.jar:1.7.0_04-ea]

                    Caused by: org.jboss.as.controller.persistence.ConfigurationPersistenceException: JBAS014676: Failed to parse configuration

                              at org.jboss.as.controller.persistence.XmlConfigurationPersister.load(XmlConfigurationPersister.java:125) [jboss-as-controller-7.1.0.Final.jar:7.1.0.Final]

                              at org.jboss.as.controller.AbstractControllerService.boot(AbstractControllerService.java:187) [jboss-as-controller-7.1.0.Final.jar:7.1.0.Final]

                              at org.jboss.as.server.ServerService.boot(ServerService.java:261) [jboss-as-server-7.1.0.Final.jar:7.1.0.Final]

                              at org.jboss.as.controller.AbstractControllerService$1.run(AbstractControllerService.java:155) [jboss-as-controller-7.1.0.Final.jar:7.1.0.Final]

                              ... 1 more

                    Caused by: javax.xml.stream.XMLStreamException: Failed to load module org.jboss.as.web

                              at org.jboss.as.controller.parsing.ExtensionXml.parseExtensions(ExtensionXml.java:154) [jboss-as-controller-7.1.0.Final.jar:7.1.0.Final]

                              at org.jboss.as.server.parsing.StandaloneXml.readServerElement_1_1(StandaloneXml.java:304) [jboss-as-server-7.1.0.Final.jar:7.1.0.Final]

                              at org.jboss.as.server.parsing.StandaloneXml.readElement(StandaloneXml.java:126) [jboss-as-server-7.1.0.Final.jar:7.1.0.Final]

                              at org.jboss.as.server.parsing.StandaloneXml.readElement(StandaloneXml.java:100) [jboss-as-server-7.1.0.Final.jar:7.1.0.Final]

                              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:117) [jboss-as-controller-7.1.0.Final.jar:7.1.0.Final]

                              ... 4 more

                    Caused by: java.util.concurrent.ExecutionException: javax.xml.stream.XMLStreamException: JBAS014674: Failed to load module

                              at java.util.concurrent.FutureTask$Sync.innerGet(Unknown Source) [rt.jar:1.7.0_04-ea]

                              at java.util.concurrent.FutureTask.get(Unknown Source) [rt.jar:1.7.0_04-ea]

                              at org.jboss.as.controller.parsing.ExtensionXml.parseExtensions(ExtensionXml.java:146) [jboss-as-controller-7.1.0.Final.jar:7.1.0.Final]

                              ... 10 more

                    Caused by: javax.xml.stream.XMLStreamException: JBAS014674: Failed to load module

                              at org.jboss.as.controller.parsing.ExtensionXml.loadModule(ExtensionXml.java:195) [jboss-as-controller-7.1.0.Final.jar:7.1.0.Final]

                              at org.jboss.as.controller.parsing.ExtensionXml.access$000(ExtensionXml.java:68) [jboss-as-controller-7.1.0.Final.jar:7.1.0.Final]

                              at org.jboss.as.controller.parsing.ExtensionXml$1.call(ExtensionXml.java:126) [jboss-as-controller-7.1.0.Final.jar:7.1.0.Final]

                              at org.jboss.as.controller.parsing.ExtensionXml$1.call(ExtensionXml.java:123) [jboss-as-controller-7.1.0.Final.jar:7.1.0.Final]

                              at java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source) [rt.jar:1.7.0_04-ea]

                              at java.util.concurrent.FutureTask.run(Unknown Source) [rt.jar:1.7.0_04-ea]

                              at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) [rt.jar:1.7.0_04-ea]

                              at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) [rt.jar:1.7.0_04-ea]

                              at java.lang.Thread.run(Unknown Source) [rt.jar:1.7.0_04-ea]

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

                    Caused by: org.jboss.modules.ModuleNotFoundException: Module org.gatein.wci:main is not found in local module loader @253ac14a (roots: C:\GateIn-3.2.0.Final-jbossas7-preview\modules)

                              at org.jboss.modules.LocalModuleLoader.findModule(LocalModuleLoader.java:126) [jboss-modules.jar:1.1.1.GA]

                              at org.jboss.modules.ModuleLoader.loadModuleLocal(ModuleLoader.java:275) [jboss-modules.jar:1.1.1.GA]

                              at org.jboss.modules.ModuleLoader.preloadModule(ModuleLoader.java:222) [jboss-modules.jar:1.1.1.GA]

                              at org.jboss.modules.LocalModuleLoader.preloadModule(LocalModuleLoader.java:94) [jboss-modules.jar:1.1.1.GA]

                              at org.jboss.modules.Module.addPaths(Module.java:841) [jboss-modules.jar:1.1.1.GA]

                              at org.jboss.modules.Module.link(Module.java:1181) [jboss-modules.jar:1.1.1.GA]

                              at org.jboss.modules.Module.relinkIfNecessary(Module.java:1207) [jboss-modules.jar:1.1.1.GA]

                              at org.jboss.modules.ModuleLoader.loadModule(ModuleLoader.java:208) [jboss-modules.jar:1.1.1.GA]

                              at org.jboss.as.controller.parsing.ExtensionXml.loadModule(ExtensionXml.java:177) [jboss-as-controller-7.1.0.Final.jar:7.1.0.Final]

                              ... 9 more

                    • 7. Re: GateIn 3.2.0.Final on existing jboss-as-7.1.0.Final installation?
                      mstruk

                      It looks as if you're either (a) not using bin\standalone.bat to run gatein or - more likely - (b) that your JBOSS_HOME env variable points to a different location that your GateIn-3.2.0.Final-jboss-as7-preview directory, or (c) that there is no JBOSS_HOME\gatein\modules directory.

                       

                      In standalone.bat there is a command that starts java executable. It receives the parameter:

                       

                          -mp "%MODULEPATH%;%JBOSS_HOME%\gatein\modules" ^

                       

                       

                      Make sure the second path element points to the correct location.

                       

                      This should work out of the box if you simply unzip the downloaded release and unset any JBOSS_HOME env variable. Go to bin folder and run standalone.bat.