10 Replies Latest reply on Jan 3, 2006 5:55 AM by Hassnain Badami

    jbp2.2 deploy error

    peter Apprentice


      when i deploy jp2.2rc2, i found there is a error message
      my enviroment is :

      jboss4.0.3SP1+linux+postgresql 8.1

      a in jboss.security:service=JaccPolicyProvider
      2005-12-15 10:13:29,220 DEBUG [org.jboss.system.ServiceCreator] About to create xmbean object: portal:service=SecurityProvid
      er with code: org.jboss.portal.security.impl.jacc.JBossSecurityProviderImpl with embedded descriptor
      2005-12-15 10:13:29,258 DEBUG [org.jboss.mx.server.AbstractMBeanInvoker] Setter not found: setObjectName(class javax.managem
      java.lang.NoSuchMethodException: org.jboss.portal.security.impl.jacc.JBossSecurityProviderImpl.setObjectName(javax.managemen
      at java.lang.Class.getMethod(Class.java:986)
      at org.jboss.mx.server.AbstractMBeanInvoker.inject(AbstractMBeanInvoker.java:929)
      at org.jboss.mx.server.AbstractMBeanInvoker.preRegister(AbstractMBeanInvoker.java:643)
      at org.jboss.mx.server.registry.BasicMBeanRegistry.invokePreRegister(BasicMBeanRegistry.java:678)
      at org.jboss.mx.server.registry.BasicMBeanRegistry.registerMBean(BasicMBeanRegistry.java:196)
      at sun.reflect.GeneratedMethodAccessor1.invoke(Unknown Source)
      at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
      at java.lang.reflect.Method.invoke(Method.java:324)
      at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:141)

        • 1. Re: jbp2.2 deploy error
          peter Apprentice

          this is another error:

          2005-12-15 10:13:52,669 DEBUG [org.hibernate.util.JDBCExceptionReporter] could not insert: [org.jboss.portal.cms.hibernate.R
          epositoryEntry] [insert into jbp_cms_repositoryentry (FSENTRY_NAME, FSENTRY_PATH, FSENTRY_DATA, FSENTRY_LASTMOD, FSENTRY_LEN
          GTH, PK) values (?, ?, ?, ?, ?, ?)]
          org.postgresql.util.PSQLException: Unknown Types value.
          at org.postgresql.jdbc2.AbstractJdbc2Statement.setNull(AbstractJdbc2Statement.java:1003)
          at org.postgresql.jdbc3.AbstractJdbc3Statement.setNull(AbstractJdbc3Statement.java:1445)
          at org.jboss.resource.adapter.jdbc.WrappedPreparedStatement.setNull(WrappedPreparedStatement.java:252)
          at org.hibernate.type.BlobType.set(BlobType.java:33)
          at org.hibernate.type.BlobType.nullSafeSet(BlobType.java:117)
          at org.hibernate.persister.entity.AbstractEntityPersister.dehydrate(AbstractEntityPersister.java:1825)
          at org.hibernate.persister.entity.AbstractEntityPersister.dehydrate(AbstractEntityPersister.java:1802)
          at org.hibernate.persister.entity.AbstractEntityPersister.insert(AbstractEntityPersister.java:2058)
          at org.hibernate.persister.entity.AbstractEntityPersister.insert(AbstractEntityPersister.java:2426)
          at org.hibernate.action.EntityInsertAction.execute(EntityInsertAction.java:51)
          at org.hibernate.engine.ActionQueue.execute(ActionQueue.java:243)
          at org.hibernate.engine.ActionQueue.executeActions(ActionQueue.java:227)
          at org.hibernate.engine.ActionQueue.executeActions(ActionQueue.java:140)
          at org.hibernate.event.def.AbstractFlushingEventListener.performExecutions(AbstractFlushingEventListener.java:296)
          at org.hibernate.event.def.DefaultFlushEventListener.onFlush(DefaultFlushEventListener.java:27)
          at org.hibernate.impl.SessionImpl.flush(SessionImpl.java:905)
          at org.jboss.portal.cms.hibernate.HibernateStore.safeFlush(HibernateStore.java:1704)
          at org.jboss.portal.cms.hibernate.HibernateStore.createDeepFolder(HibernateStore.java:1585)
          at org.jboss.portal.cms.hibernate.HibernateStore.createDeepFolder(HibernateStore.java:1552)

          • 2. Re: jbp2.2 deploy error
            Woodler Expert

            hmm, the first stack is strange.
            I'd focus on the database problem (the second stack) first. I'm on 4.03 SP1 and linux (SuSE9) and don't see the issue (I'm using MySQL)

            Any chance you could configure to use MySQL to see if that fixes the issue ?

            • 3. Re: jbp2.2 deploy error
              gressho Newbie


              I saw the second stack trace, too with the same environment (RHEL 4,
              Postgres 8.1.0). There was an earlier error, when Postgres couldn't build
              the CMS tables: an error with some LOB's.



              • 4. Re: jbp2.2 deploy error
                cpage cpage Novice

                same problem with Oracle9i and the CLOBs

                • 5. Re: jbp2.2 deploy error
                  Roy Russo Master

                  The fix for postgres is committed in CVS.

                  • 6. Re: jbp2.2 deploy error
                    Steve Moyer Newbie

                    This eliminated the problem that I described in the post titled "Hibernate problems" (http://www.jboss.com/index.html?module=bb&op=viewtopic&t=73561), but I'm wondering about actually fixing the problem. I'm still interested in saving all my content in PostgreSQL and all this seemed to do was move the page storage to the file system.

                    Is there a permanent incompatibility between Hibernate3 and PostgreSQL8? If you can't store BLOBs or CLOBs any more, this will probably affect quite a few other projects that use Hibernate for their OR mapping.

                    I certainly do appreciate being able to try out JBP2.2 without resorting to a different database (and what I see so far looks great). Hopefully I'll be able to donate some portlets.


                    • 7. Re: jbp2.2 deploy error
                      Roy Russo Master

                      The fix for storing everything in postgres is in CVS. Did you check it out? You may need to wipe your DB and /data/portal directory so it doesn't read the old repository config.

                      • 8. Re: jbp2.2 deploy error
                        Steve Moyer Newbie

                        I deleted the project from Eclipse, then created a new project from CVS (so I'm sure that I have the latest sources). I also deleted the the entire data directory and the old portal files from the deploy directory before I started the build. I also dropped the entire database and recreated it so that I could verify it was automatic.

                        I changed local.properties file to select postgresql, but did not edit the hibernate.cfg.xml files (as described in my other post). Is there anything else I need to configure first? I know there is a mechanism for having content in the filesystem and portal data in the database, but I haven't found the switch for this.

                        I'm also still curious about the problem with large objects ... what was the cause? How can I avoid it in other problems?

                        Thanks for all your help!

                        • 9. Re: jbp2.2 deploy error
                          Roy Russo Master

                          You don't need to modify the local.properties, just make sure you deploy the postgres database descriptor.

                          If you want 100% filesystem storage:

                          Essentially, you're commenting out the HibernateStore and HibernatePM nodes and telling jackrabbit to use the LocalFSStore and the XMLPM. Are you still experiencing the problems with postgres with a clean CVS checkout?

                          So many problems with postgres, I encountered:


                          #2 http://forum.hibernate.org/viewtopic.php?t=927552

                          • 10. Re: jbp2.2 deploy error
                            Hassnain Badami Newbie

                            I am having the same problem i.e. Large objects may not be used in auto-commit mode.
                            I took a fresh checkout of hibernate3 from the CVS, built it and replaced the old hibernate3.jar with the new one. But it doesnt resolve the issue.

                            I am using jboss 4.0.3 with postgres 8.0

                            The exception dump is

                            Caused by: org.postgresql.util.PSQLException: Large Objects may not be used in auto-commit mode.
                            at org.postgresql.largeobject.LargeObjectManager.open(LargeObjectManager.java:172)
                            at org.postgresql.largeobject.LargeObjectManager.open(LargeObjectManager.java:158)
                            at org.postgresql.jdbc2.AbstractJdbc2BlobClob.(AbstractJdbc2BlobClob.java:39)
                            at org.postgresql.jdbc2.AbstractJdbc2Blob.(AbstractJdbc2Blob.java:23)
                            at org.postgresql.jdbc3.AbstractJdbc3Blob.(AbstractJdbc3Blob.java:22)
                            at org.postgresql.jdbc3.Jdbc3Blob.(Jdbc3Blob.java:20)
                            at org.postgresql.jdbc3.Jdbc3ResultSet.getBlob(Jdbc3ResultSet.java:54)
                            at org.postgresql.jdbc2.AbstractJdbc2ResultSet.getBlob(AbstractJdbc2ResultSet.java:312)
                            at org.jboss.resource.adapter.jdbc.WrappedResultSet.getBlob(WrappedResultSet.java:208)
                            at org.hibernate.type.BlobType.get(BlobType.java:57)
                            at org.hibernate.type.BlobType.nullSafeGet(BlobType.java:111)
                            at org.hibernate.type.AbstractType.hydrate(AbstractType.java:81)
                            at org.hibernate.persister.entity.AbstractEntityPersister.hydrate(AbstractEntityPersister.java:1899)
                            at org.hibernate.loader.Loader.loadFromResultSet(Loader.java:1372)
                            at org.hibernate.loader.Loader.instanceNotYetLoaded(Loader.java:1300)
                            at org.hibernate.loader.Loader.getRow(Loader.java:1197)
                            at org.hibernate.loader.Loader.getRowFromResultSet(Loader.java:569)
                            at org.hibernate.loader.Loader.doQuery(Loader.java:689)
                            at org.hibernate.loader.Loader.doQueryAndInitializeNonLazyCollections(Loader.java:224)
                            at org.hibernate.loader.Loader.loadEntity(Loader.java:1785)