1 2 Previous Next 22 Replies Latest reply on May 2, 2006 5:09 PM by edwinjaufmann

    Portal 2.2 Clustering

    martymaar

      I try to get the portal 2.2 clustering to work. Downloaded the JBoss Portal + JBoss AS 4.0.3SP1 2.2.1RC2. By following the instructions in the Wikki I get an error starting with:

      5:02:32,185 ERROR [MainDeployer] Could not create deployment: file:/opt/jboss/server/default/deploy/jboss-portal.sar/portal-cms.sar/
      org.jboss.deployment.DeploymentException: no protocol: org/jboss/portal/cms/impl/jcr/ha/HAJCRCMS.xml; - nested throwable: (java.net.MalformedURLException: no protocol: org/jboss/portal/cms/impl/jcr/ha/HAJCRCMS.xml)

      If I skip the configuration in the portal-cms META-INF directory I also receive errors. This time it's:


      java.lang.UnsupportedOperationException: TreeCache is a fully transactional cache: org/jboss/portal/core/impl/model/portal/PortalObjectImpl
      at org.hibernate.cache.TreeCache.unlock(TreeCache.java:137)
      at org.hibernate.cache.ReadWriteCache.put(ReadWriteCache.java:176)
      at org.hibernate.engine.TwoPhaseLoad.initializeEntity(TwoPhaseLoad.java:153)
      at org.hibernate.loader.Loader.initializeEntitiesAndCollections(Loader.java:842)
      at org.hibernate.loader.Loader.doQuery(Loader.java:717)
      at org.hibernate.loader.Loader.doQueryAndInitializeNonLazyCollections(Loader.java:223)
      at org.hibernate.loader.Loader.loadEntity(Loader.java:1782)
      at org.hibernate.loader.entity.AbstractEntityLoader.load(AbstractEntityLoader.java:93)
      at org.hibernate.loader.entity.AbstractEntityLoader.load(AbstractEntityLoader.java:81)
      at org.hibernate.persister.entity.AbstractEntityPersister.load(AbstractEntityPersister.java:2729)
      at org.hibernate.event.def.DefaultLoadEventListener.loadFromDatasource(DefaultLoadEventListener.java:365)
      at org.hibernate.event.def.DefaultLoadEventListener.doLoad(DefaultLoadEventListener.java:346)


      Obviously I missed some instructions on how to configure the cluster. Are there additional tasks besides the stuff described in the wikki? Maybe the version of the portal I got is not "prepared" for clustering?

      thankful for any help
      Martin

        • 1. Re: Portal 2.2 Clustering
          noicangi

          i read the wiki, and it said i can build the portal clustered changing the properties.xml but i need to bluid it? how i do that?


          the other thing is that in jboss forum says i need the all server...but in bundled id only the default directory.....the server/all is too small.


          the wiki doesn't explain how i set the master and the slaves.


          please if you can detail the explanaiton of clusterin jboss portal it would be great. thanks

          • 2. Re: Portal 2.2 Clustering
            noicangi

            working with mysql 4.1 connector 3.1, winxp and redhat 9 and the bundled version of portal and jboss 4.03+2.2.1rc2

            the same happened to me, i guess that the wiki part that said
            The file you need to edit are :

            - jboss-portal.sar/META-INF/jboss-service.xml
            - jboss-portal.sar/META-INF/portal-cms.sar/META-INF/jboss-service.xml
            - jboss-portal.sar/portal-server.war/WEB-INF/web.xml
            - jboss-portal.sar/conf/hibernate/instance/hibernate.cfg.xml
            - jboss-portal.sar/conf/hibernate/instance/portal.cfg.xml-->C:\JBoss\server\default\deploy\jboss-portal.sar\conf\hibernate\portal\hibernate.cfg.xml

            - jboss-portal.sar/conf/hibernate/instance/user.cfg.xml -->C:\JBoss\server\default\deploy\jboss-portal.sar\conf\hibernate\user\hibernate.cfg.xml

            but it doesn't work....here the error
            1098, backlog=50, bindAddress=/0.0.0.0, Client SocketFactory=null, Server Socket
            Factory=org.jboss.net.sockets.DefaultSocketFactory@ad093076
            17:40:14,420 ERROR [MainDeployer] Could not create deployment: file:/C:/JBoss/se
            rver/default/deploy/jboss-portal.sar/portal-cms.sar/
            org.jboss.deployment.DeploymentException: no protocol: org/jboss/portal/cms/impl
            /jcr/ha/HAJCRCMS.xml; - nested throwable: (java.net.MalformedURLException: no pr
            otocol: org/jboss/portal/cms/impl/jcr/ha/HAJCRCMS.xml)
             at org.jboss.system.ServiceConfigurator.install(ServiceConfigurator.java
            :178)
             at org.jboss.system.ServiceController.install(ServiceController.java:215
            )
             at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
             at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
            java:39)
             at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
            sorImpl.java:25)
             at java.lang.reflect.Method.invoke(Method.java:585)
             at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatch
            er.java:141)
             at org.jboss.mx.server.Invocation.dispatch(Invocation.java:80)
             at org.jboss.mx.server.Invocation.invoke(Invocation.java:72)
             at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.
            java:245)
             at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:644)
             at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:176)
             at $Proxy4.install(Unknown Source)
             at org.jboss.deployment.SARDeployer.create(SARDeployer.java:232)
             at org.jboss.deployment.MainDeployer.create(MainDeployer.java:935)
             at org.jboss.deployment.MainDeployer.create(MainDeployer.java:925)
             at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:789)
             at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:753)
             at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
             at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
            java:39)
             at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
            sorImpl.java:25)
             at java.lang.reflect.Method.invoke(Method.java:585)
             at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatch
            er.java:141)
             at org.jboss.mx.server.Invocation.dispatch(Invocation.java:80)
             at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractIntercept
            or.java:118)
             at org.jboss.mx.server.Invocation.invoke(Invocation.java:74)
             at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelM
            BeanOperationInterceptor.java:127)
             at org.jboss.mx.server.Invocation.invoke(Invocation.java:74)
             at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.
            java:245)
             at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:644)
             at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:176)
             at $Proxy9.deploy(Unknown Source)
             at org.jboss.deployment.scanner.URLDeploymentScanner.deploy(URLDeploymen
            tScanner.java:319)
             at org.jboss.deployment.scanner.URLDeploymentScanner.scan(URLDeploymentS
            canner.java:507)
             at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.
            doScan(AbstractDeploymentScanner.java:192)
             at org.jboss.deployment.scanner.AbstractDeploymentScanner.startService(A
            bstractDeploymentScanner.java:265)
             at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanS
            upport.java:274)
             at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMB
            eanSupport.java:230)
             at sun.reflect.GeneratedMethodAccessor2.invoke(Unknown Source)
             at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
            sorImpl.java:25)
             at java.lang.reflect.Method.invoke(Method.java:585)
             at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatch
            er.java:141)
             at org.jboss.mx.server.Invocation.dispatch(Invocation.java:80)
             at org.jboss.mx.server.Invocation.invoke(Invocation.java:72)
             at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.
            java:245)
             at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:644)
             at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceControl
            ler.java:943)
             at $Proxy0.start(Unknown Source)
             at org.jboss.system.ServiceController.start(ServiceController.java:428)
             at sun.reflect.GeneratedMethodAccessor9.invoke(Unknown Source)
             at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
            sorImpl.java:25)
             at java.lang.reflect.Method.invoke(Method.java:585)
             at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatch
            er.java:141)
             at org.jboss.mx.server.Invocation.dispatch(Invocation.java:80)
             at org.jboss.mx.server.Invocation.invoke(Invocation.java:72)
             at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.
            java:245)
             at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:644)
             at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:176)
             at $Proxy4.start(Unknown Source)
             at org.jboss.deployment.SARDeployer.start(SARDeployer.java:285)
             at org.jboss.deployment.MainDeployer.start(MainDeployer.java:989)
             at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:790)
             at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:753)
             at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:737)
             at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
             at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
            java:39)
             at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
            sorImpl.java:25)
             at java.lang.reflect.Method.invoke(Method.java:585)
             at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatch
            er.java:141)
             at org.jboss.mx.server.Invocation.dispatch(Invocation.java:80)
             at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractIntercept
            or.java:118)
             at org.jboss.mx.server.Invocation.invoke(Invocation.java:74)
             at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelM
            BeanOperationInterceptor.java:127)
             at org.jboss.mx.server.Invocation.invoke(Invocation.java:74)
             at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.
            java:245)
             at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:644)
             at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:176)
             at $Proxy5.deploy(Unknown Source)
             at org.jboss.system.server.ServerImpl.doStart(ServerImpl.java:453)
             at org.jboss.system.server.ServerImpl.start(ServerImpl.java:330)
             at org.jboss.Main.boot(Main.java:187)
             at org.jboss.Main$1.run(Main.java:438)
             at java.lang.Thread.run(Thread.java:595)
            Caused by: java.net.MalformedURLException: no protocol: org/jboss/portal/cms/imp
            l/jcr/ha/HAJCRCMS.xml
             at java.net.URL.<init>(URL.java:567)
             at java.net.URL.<init>(URL.java:464)
             at java.net.URL.<init>(URL.java:413)
             at org.jboss.system.ServiceCreator.install(ServiceCreator.java:173)
             at org.jboss.system.ServiceConfigurator.internalInstall(ServiceConfigura
            tor.java:431)
             at org.jboss.system.ServiceConfigurator.install(ServiceConfigurator.java
            :153)
             ... 82 more
            
            
            
            please if anyone has the portal clustered xplain me,
            i tried to bluid source of portal to config local.properties without success,
            anybody there to teach me how to build?


            • 3. Re: Portal 2.2 Clustering
              noicangi

              i get it...!!! this is to cluster de portal but not jboss,

              the bundled version comes only with the default server, download the jboss AS4.03sp1 ALONE!! copy the ALL directory under the same directory \server of your bundled version and read this:

              http://docs.jboss.org/jbossas/clustering/JBossClustering7.pdf

              ;)

              when i finish reading i post....any news please post

              • 4. Re: Portal 2.2 Clustering

                can you try to use JBoss Portal head of branch 2.2 ?

                I fixed the issue with java.net.MalformedURLException: no protocol: org/jboss/portal/cms/impl/jcr/ha/HAJCRCMS.xml

                • 5. Re: Portal 2.2 Clustering
                  noicangi

                  sorry julien i'm newbie to the portal.....i'm just a learning user/admin of the portal, can you pecify me waht do you mean with the portal head of branch?

                  i unziped the bundled version....next i copy the server/all from the jboss as 4.0.3SP1.zip to the server/ directory of my bundled version to have all functions...then like the pdf says.../jboss/bin>run -c all with the portal.sar copied to the all/deploy .....and funtions well

                  the thing i don't understand well....is that to have the portal clustered i must cluster jboss and follow the wiki instructions or just follow wiki steps to only cluster the portal.


                  what fix? i must download something¿ or copy a file to the .jar where hajcrcms.xml don't exist?

                  thanks julien....and sorry, there are some terms in english i don't handle :P

                  • 6. Re: Portal 2.2 Clustering

                    you should download jboss portal 2.2 branch
                    copy build/etc/local.properties-example to build/local.properties
                    edit the property file and set portal.clustered=true
                    build jboss portal
                    deploy it in all configuration in the servers that belong to the same cluster

                    • 7. Re: Portal 2.2 Clustering
                      noicangi

                      hi, i delete de portal.sar from the deploy (bundled), i download the source and in the cmd y go to the directory build where i copied the local.properties to make clustering, i type build in many form to make it work in windows without results, this is must be done in linux? i have a redhat machine but i prefer to don't touch it because i want it to be the master server.


                      • 8. Re: Portal 2.2 Clustering
                        noicangi

                        here the trouble building..

                        
                        cd jboss-portal-2.2.1RC2-src/build/
                        [root@poseidon build]# ll
                        total 52
                        -rwxrwxr-x 1 root root 1283 Jan 29 08:59 build.bat
                        -rwxrwxr-x 1 root root 1214 Jan 29 08:59 build.sh
                        -rwxrwxr-x 1 root root 13107 Jan 29 08:58 build.xml
                        -rwxrwxr-x 1 root root 9491 Jan 29 08:58 distrib.xml
                        drwxrwxr-x 2 root root 4096 Feb 17 13:57 etc
                        drwxrwxr-x 3 root root 4096 Jan 29 08:58 ide
                        drwxrwxr-x 2 root root 4096 Feb 17 13:57 licences
                        drwxrwxr-x 2 root root 4096 Feb 17 13:57 misc
                        [root@poseidon build]# ./build.sh deploy
                        : command not foundportal-2.2.1RC2-src/tools/bin/build.sh: line 7:
                        : command not foundportal-2.2.1RC2-src/tools/bin/build.sh: line 9:
                        /home/npavez/jboss-portal-2.2.1RC2-src/tools/bin/build.sh: /home/npavez/jboss-portal-2.2.1RC2-src/tools/bin/common.shlib: line 11: syntax error near unexpected 'oken `{
                        /home/npavez/jboss-portal-2.2.1RC2-src/tools/bin/build.sh: /home/npavez/jboss-po'tal-2.2.1RC2-src/tools/bin/common.shlib: line 11: `{
                        xset: unable to open display ""
                        xset: unable to open display ""
                        /home/npavez/jboss-portal-2.2.1RC2-src/tools/bin/build.sh: line 38: check_os: command not found
                        /home/npavez/jboss-portal-2.2.1RC2-src/tools/bin/build.sh: line 1: convertpath: command not found
                        /home/npavez/jboss-portal-2.2.1RC2-src/tools/bin/build.sh: line 1: convertpath: command not found
                        /home/npavez/jboss-portal-2.2.1RC2-src/tools/bin/build.sh: line 42: debug: command not found
                        /home/npavez/jboss-portal-2.2.1RC2-src/tools/bin/build.sh: line 43: debug: command not found
                        xset: unable to open display ""
                        xset: unable to open display ""
                        /home/npavez/jboss-portal-2.2.1RC2-src/tools/bin/build.sh: line 51: warn: command not found
                        /home/npavez/jboss-portal-2.2.1RC2-src/tools/bin/build.sh: line 1: convertpath: command not found
                        /home/npavez/jboss-portal-2.2.1RC2-src/tools/bin/build.sh: line 54: debug: command not found
                        xset: unable to open display ""
                        /home/npavez/jboss-portal-2.2.1RC2-src/tools/bin/build.sh: line 62: debug: command not found
                        /home/npavez/jboss-portal-2.2.1RC2-src/tools/bin/build.sh: line 67: maybe_source: command not found
                        /home/npavez/jboss-portal-2.2.1RC2-src/tools/bin/build.sh: line 70: [: =: unary operator expected
                        /home/npavez/jboss-portal-2.2.1RC2-src/tools/bin/build.sh: line 90: die: command not found
                        /home/npavez/jboss-portal-2.2.1RC2-src/tools/bin/build.sh: line 94: debug: command not found
                        /home/npavez/jboss-portal-2.2.1RC2-src/tools/bin/build.sh: line 107: die: command not found
                        xset: unable to open display ""
                        /home/npavez/jboss-portal-2.2.1RC2-src/tools/bin/build.sh: line 120: debug: command not found
                        xset: unable to open display ""
                        /home/npavez/jboss-portal-2.2.1RC2-src/tools/bin/build.sh: line 133: debug: command not found
                        /home/npavez/jboss-portal-2.2.1RC2-src/tools/bin/build.sh: line 136: notice: command not found
                        /home/npavez/jboss-portal-2.2.1RC2-src/tools/bin/build.sh: line 140: /bin/ant: No such file or directory
                        /home/npavez/jboss-portal-2.2.1RC2-src/tools/bin/build.sh: line 140: exec: /bin/ant: cannot execute: No such file or directory
                        
                        
                        


                        • 9. Re: Portal 2.2 Clustering
                          noicangi

                          sorry for bothering again but it has being imposible to me to run the build.sh from the source, i have tried all...please helpme

                          i tried xp and redhat with sh build.sh deploy, build, ./buils.sh etc etc

                          • 10. Re: Portal 2.2 Clustering
                            noicangi

                            hi, i build the cvs version 2.2 and then i deploy it to the server/all (all server of the jboss i copied from the jboss4.0.3SP1 because the bundled doesn't have the direcoty) but it doesn't work.


                            please help

                            the file
                            HAJCRCMS.xml is not created.

                            • 11. Re: Portal 2.2 Clustering

                              have you tried the latest version from branch 2.2 ?

                              • 12. Re: Portal 2.2 Clustering
                                noicangi

                                yes i think so, i followed the steps of using eclipse in the wiki, i download the jboss-portal-2.2 and build that version but it doesn't works, i start the server but the portal don't starts. i tried to buield other version called jboss-portal but i could't build it.

                                at this moment i'am stuck, i tried to build the portal ( i suppose i'm building the branch, if not can you tell me please?)

                                and triyng to configure from the xml files ( clustering2_2) but doen'st work :P

                                for the record i copied the server/all directory from the jboss as 403sp1 to the bundled version of the portal because this version doesn't brings the .jar to make clustering. and when i install or copy the jboss AS the portal doesn't work.

                                notice i'm just a begginer in jboss, i following every step of the user/reference wiki and forum.

                                thanks for the help

                                • 13. Re: Portal 2.2 Clustering
                                  noicangi

                                  hi, this is not the right topic but its refered to clustering.

                                  i download the cvs ((jboss-portal-2.2)) ( i suppose the branch) to build with clustering=true and change the portal instance name to /portal to / , it builds but when i run the jboss the portal doesn't apears. because i'm using bundled version i copy the server/all from the jbosss as 403sp1 to the bundled and copy the builded portal.sar to the server/all/deploy at the bundled to make clustering but it doesn't work.

                                  please tell me if i'm doing the right thing with cvs and also if bundled + all directory its able for clustering because instaling or unzipping jboss and adding the portal.sar don't works.

                                  ----------------
                                  i downloaded the jboss as 4.0.4rc1 with his installer and make a full(all) install but it claims a that policy bla bla bla.... the same i post some topics ago....

                                  • 14. Re: Portal 2.2 Clustering
                                    noicangi

                                    hi, thomas in the topic about a zip file in cms for download post that he uses the cvs head of portal 2.4, i need to know if that version ( not stable i know) has the option of clustering, i don't know if i'am usign the 2.2 branch of the portal, but setting true at local.properties at cvs i download with eclipse don't works.

                                    i will post the error...

                                    1 2 Previous Next