11 Replies Latest reply on Jan 5, 2006 2:45 PM by glodo

    configuration jboss portal 2.2

    glodo

      Hi! i try to use the jboss portal 2.2 on jboss 4.0.3SP1, i configurate the deploy/setup/portal-oracle-ds.xml, and deploy/jboss-portal.sar/conf/hibernate/, i configurate every folder on this (instance, portal, security, user). is this right?
      but, still cannot deploy the the page of the portal.. when i type http://localhost:8080/portal show me this error: "The requested resource () is not available."
      and when i type http://localhost:8080/portal/login, shows the page of login but when i put user: admin, pass: admin, show that same error.

      aparently is something that is not configurate yet. anyone nows what can be the problem? any configuration that i forget?

      is one table of the database "jbp_object_node", and is empty, is necesary configurate something? and others tables is empty too, is this right?

      please help me... and thank for you help!

        • 1. Re: configuration jboss portal 2.2

          hi,

          I got exactly the same problem.

          JBP_OBJECT_NODE table is empty, except the first column, PK.

          it's seems that the content of the table can't be imported.

          I first think of a problem with hibernate configuration, but the table are create ...so.

          maybe a problem with the mapping files of hibernate ?

          regards,
          Lionel



          • 2. Re: configuration jboss portal 2.2
            glodo

            Hi cpage!! do you have any new?
            i still have the same problem, and i can not find de solutions to that..
            i dont now why show this error: "Invalid direct reference to form login page" description: The request sent by the client was syntactically incorrect
            do you find something?
            thanks!!

            • 3. Re: configuration jboss portal 2.2

              Hi,

              what my server.log says : (only warns and errors)

              2005-12-12 15:14:29,809 DEBUG [org.hibernate.util.JDBCExceptionReporter] could not execute query [select 1 as col_0_0_ from jbp_cms_repositoryentry repository0_ where FSENTRY_PATH=? and FSENTRY_NAME=?]
              java.sql.SQLException: ORA-00932: inconsistent datatypes: expected - got CLOB
              
              
              
              2005-12-12 15:14:29,825 ERROR [org.jboss.portal.cms.hibernate.HibernateStore] failed to check existence of file system entry: /meta
              
              
              2005-12-12 15:13:50,059 WARN [org.jboss.ejb3.cache.tree.PassivationTreeCache] No transaction manager lookup class has been defined. Transactions cannot be used
              
              2005-12-12 15:14:30,122 WARN [net.sf.ehcache.config.Configurator] No configuration found.
              
              2005-12-12 15:14:30,157 WARN [org.hibernate.cache.EhCacheProvider] Could not find configuration [org.jboss.portal.core.security.store.SecurityPolicy]; using defaults.
              2005-12-12 15:14:30,210 WARN [org.hibernate.cache.EhCacheProvider] Could not find configuration [org.jboss.portal.core.security.store.HbmSecurityConstraint]; using defaults.
              2005-12-12 15:14:30,282 WARN [org.hibernate.cache.EhCacheProvider] Could not find configuration [org.hibernate.cache.UpdateTimestampsCache]; using defaults.
              2005-12-12 15:14:30,291 WARN [org.hibernate.cache.EhCacheProvider] Could not find configuration [org.hibernate.cache.StandardQueryCache]; using defaults.
              2005-12-12 15:14:33,819 WARN [org.hibernate.cache.EhCacheProvider] Could not find configuration [org.jboss.portal.core.impl.role.RoleImpl]; using defaults.
              2005-12-12 15:14:33,855 WARN [org.hibernate.cache.EhCacheProvider] Could not find configuration [org.jboss.portal.core.impl.user.PreferenceImpl]; using defaults.
              2005-12-12 15:14:33,898 WARN [org.hibernate.cache.EhCacheProvider] Could not find configuration [org.jboss.portal.core.impl.user.UserImpl]; using defaults.
              2005-12-12 15:14:34,019 WARN [org.hibernate.cache.EhCacheProvider] Could not find configuration [org.jboss.portal.core.impl.user.PreferencesImpl]; using defaults.
              2005-12-12 15:14:34,127 WARN [org.hibernate.cache.EhCacheProvider] Could not find configuration [org.jboss.portal.core.impl.user.PreferencesGroupImpl]; using defaults.
              2005-12-12 15:14:34,160 WARN [org.hibernate.cache.EhCacheProvider] Could not find configuration [org.jboss.portal.core.impl.user.UserImpl.dynamic]; using defaults.
              2005-12-12 15:14:34,167 WARN [org.hibernate.cache.EhCacheProvider] Could not find configuration [org.jboss.portal.core.impl.role.RoleImpl.users]; using defaults.
              [...]
              2005-12-12 15:14:35,367 WARN [org.hibernate.cache.EhCacheProvider] Could not find configuration [org.jboss.portal.core.impl.model.portal.ObjectNode]; using defaults.
              
              
              2005-12-12 15:14:36,134 WARN [org.jboss.portal.core.deployment.jboss.PortalDeployment] Cannot create portal object null because the parent that the deployment descriptor references does not exist


              I really think to an hibernate configuration problem.

              regards,
              Lionel

              • 4. Re: configuration jboss portal 2.2

                is someone succeed with JBP 2.2 and Oracle 9i ?

                thanks,

                Lionel

                • 5. Re: configuration jboss portal 2.2

                  The error I see there is related to the CMS only. Are you seeing anything at the end of booting regarding some services that fail to start?

                  • 6. Re: configuration jboss portal 2.2
                    glodo

                    Hi everyone! i still have problem with the jboss portal 2.2, but the problem realy is the type of the attribute BLOB of oracle, because, when i install the jboss portal 2.0, i have the same problem, happens a error transactional with the database, and i resolve changing the type of attribute BLOB by CLOB, and in that moment work very fine..
                    is for that, that i think, the problem is this type of attribute, because now, show the same error.
                    if someone nows how i can change that or how configurate, i will feel so glad!!
                    thanks for your help.

                    • 7. Re: configuration jboss portal 2.2

                      I will change it as you say, and test it. I will let you know as the blob type is used in almost every CMS table now.

                      • 8. Re: configuration jboss portal 2.2

                        I'm surprised.

                        My DB, oracle9i worked fine with JBP 2.0 last week.

                        but i still can't deploy my portal 2.2 with the same DB.

                        • 9. Re: configuration jboss portal 2.2

                           

                          "roy.russo@jboss.com" wrote:
                          The error I see there is related to the CMS only. Are you seeing anything at the end of booting regarding some services that fail to start?


                          I have 2 errors. the first is a new one with JBP 2.2 but the second is an old error which was already raised with JBP 2.0 but didn't perturb the portal.

                          --- MBeans waiting for other MBeans ---
                          ObjectName: portal:service=CMS
                           State: FAILED
                           Reason: javax.jcr.RepositoryException: failed to create folder for repositorymeta data: failed to check existence of file system entry: /meta: could not execute query: failed to check existence of file system entry: /meta: could not execute query
                           I Depend On:
                           jboss.jca:service=DataSourceBinding,name=PortalDS
                           portal:service=JAASLoginModule
                           Depends On Me:
                           portal:mapper=CMSObject
                          
                          ObjectName: jboss:service=KeyGeneratorFactory,type=HiLo
                           State: CONFIGURED
                           I Depend On:
                           jboss:service=TransactionManager
                           jboss.jca:service=DataSourceBinding,name=DefaultDS
                          
                          --- MBEANS THAT ARE THE ROOT CAUSE OF THE PROBLEM ---
                          ObjectName: jboss.jca:service=DataSourceBinding,name=DefaultDS
                           State: NOTYETINSTALLED
                           Depends On Me:
                           jboss:service=KeyGeneratorFactory,type=HiLo
                          
                          ObjectName: portal:service=CMS
                           State: FAILED
                           Reason: javax.jcr.RepositoryException: failed to create folder for repositorymeta data: failed to check existence of file system entry: /meta: could not execute query: failed to check existence of file system entry: /meta: could not execute query
                           I Depend On:
                           jboss.jca:service=DataSourceBinding,name=PortalDS
                           portal:service=JAASLoginModule
                           Depends On Me:
                           portal:mapper=CMSObject


                          I have mentionned theses problems of datatypes :
                          2005-12-12 15:14:29,809 DEBUG [org.hibernate.util.JDBCExceptionReporter] could not execute query [se
                          lect 1 as col_0_0_ from jbp_cms_repositoryentry repository0_ where FSENTRY_PATH=? and FSENTRY_NAME=?
                          ]
                          java.sql.SQLException: ORA-00932: inconsistent datatypes: expected - got CLOB


                          but these problems are only on CMS, and I don't understand why the portal doesn't deploy ?

                          best regards,
                          Lionel.

                          • 10. Re: configuration jboss portal 2.2
                            ankursidana

                            Can any body suggest some soln. in case there is any?

                            Thanks
                            Ankur

                            • 11. Re: configuration jboss portal 2.2
                              glodo

                              You have to delete all rows of the table JBP_CMS_REPOSITORYENTRY and run again.. the portal set automatically all rows that it need...
                              if you have good solution.. please let me know..
                              regards
                              glodo