10 Replies Latest reply on May 17, 2006 11:39 AM by johnpoole

    JDP_SECURITY POLICY doesn't exist

    johnpoole

      I?m using:
      JBoss 4.0.3SP1, which starts up okay by itself

      I?m trying to start up JBoss Portal from the files in:
      jboss-portal-2.2.1.zip

      Using: MySQL, version: 4.0.15 with this connector: mysql-connector-java-3.0.17-ga-bin.jar

      It manages to connect to mysql and create and populate some tables,( All with ?cms? in the name)

      But it fails to create any of the user tables.

      The first error msg is this:

      11:10:43,571 ERROR [JDBCExceptionReporter] General error message from server: "Table 'jbossportal.JBP_SECURITY_POLICY' doesn't exist"
      11:10:43,606 WARN [ServiceController] Problem starting service portal:service=TreeCache,type=persistent
      org.hibernate.exception.GenericJDBCException: could not execute query

      The only ?odd? thing I?m doing is using jdk1.6.0. Would this JDK cause a problem?

      Thanks for any advice,
      John

        • 1. Re: JDP_SECURITY POLICY doesn't exist

          We have not tested with jdk6. So it is likely the problem... try using 1.4 or 5.

          • 2. Re: JDP_SECURITY POLICY doesn't exist
            johnpoole

            I get the same result using 5

            cat run.log | grep -i jdk
            JAVA: /usr/java/jdk1.5.0_05/bin/java
            CLASSPATH: /jboss/jboss-4.0.3SP1/bin/run.jar:/usr/java/jdk1.5.0_05/lib/tools.jar
            12:04:22,019 INFO [Environment] using JDK 1.4 java.sql.Timestamp handling


            cat run.log | grep -i error
            12:04:01,799 ERROR [LocaleUtils] Locale name null or empty, ignoring
            12:04:31,788 WARN [JDBCExceptionReporter] SQL Error: 1146, SQLState: S1000
            12:04:31,788 ERROR [JDBCExceptionReporter] General error message from server: "Table 'jbossportal.JBP_SECURITY_POLICY' doesn't exist"
            Caused by: java.sql.SQLException: General error message from server: "Table 'jbossportal.JBP_SECURITY_POLICY' doesn't exist"
            at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:2001)
            12:04:32,671 WARN [JDBCExceptionReporter] SQL Error: 1146, SQLState: S1000
            12:04:32,671 ERROR [JDBCExceptionReporter] General error message from server: "Table 'jbossportal.jbp_users' doesn't exist"
            Caused by: java.sql.SQLException: General error message from server: "Table 'jbossportal.jbp_users' doesn't exist"
            at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:2001)
            12:04:33,402 WARN [JDBCExceptionReporter] SQL Error: 1146, SQLState: S1000
            12:04:33,402 ERROR [JDBCExceptionReporter] General error message from server: "Table 'jbossportal.JBP_INSTANCE' doesn't exist"
            Caused by: java.sql.SQLException: General error message from server: "Table 'jbossportal.JBP_INSTANCE' doesn't exist"
            at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:2001)
            12:04:33,880 WARN [JDBCExceptionReporter] SQL Error: 1146, SQLState: S1000
            12:04:33,880 ERROR [JDBCExceptionReporter] General error message from server: "Table 'jbossportal.JBP_PORTAL_OBJECT' doesn't exist"
            Caused by: java.sql.SQLException: General error message from server: "Table 'jbossportal.JBP_PORTAL_OBJECT' doesn't exist"
            at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:2001)
            12:04:34,448 ERROR [URLDeploymentScanner] Incomplete Deployment listing:

            • 3. Re: JDP_SECURITY POLICY doesn't exist

              If this is hapenning on the initial boot, its normal. Portal checks to see if the tables exist, if they do not, it creates them.

              After the startup, are the tables created?

              • 4. Re: JDP_SECURITY POLICY doesn't exist
                johnpoole

                just these ones:

                mysql> show tables;
                +-------------------------+
                | Tables_in_jbossportal |
                +-------------------------+
                | jbp_cms_cmsentry |
                | jbp_cms_repositoryentry |
                | jbp_cms_version_binval |
                | jbp_cms_version_node |
                | jbp_cms_version_prop |
                | jbp_cms_version_refs |
                | jbp_cms_versionentry |
                | jbp_cms_wsp_binval |
                | jbp_cms_wsp_node |
                | jbp_cms_wsp_prop |
                | jbp_cms_wsp_refs |
                +-------------------------+
                11 rows in set (0.00 sec)

                • 5. Re: JDP_SECURITY POLICY doesn't exist

                  ok. Do this:

                  I want to do a clean install/upgrade over my existing one. What are the steps?

                  Shut down JBoss AS
                  Delete JBOSS_HOME/server/default/data/portal
                  Delete all JBoss Portal tables from your database
                  Start JBoss AS.

                  Tell me what happens. This is a clean install procedure.

                  • 6. Re: JDP_SECURITY POLICY doesn't exist
                    johnpoole

                    I get the exact same result.

                    • 7. Re: JDP_SECURITY POLICY doesn't exist
                      johnpoole

                      This error shows up in server.log:

                      2006-05-16 12:45:57,388 DEBUG [org.jboss.mx.server.AbstractMBeanInvoker] Setter not found: setObjectName(class javax.management.ObjectName)
                      java.lang.NoSuchMethodException: org.jboss.portal.security.impl.jacc.JBossSecurityProviderImpl.setObjectName(javax.management.ObjectName)

                      • 8. Re: JDP_SECURITY POLICY doesn't exist

                        Do a clean install and please email the server.log.

                        • 9. Re: JDP_SECURITY POLICY doesn't exist
                          johnpoole

                          cleaned and sent

                          • 10. Re: JDP_SECURITY POLICY doesn't exist
                            johnpoole

                            As Roy suspected, the problem turned out to be the version of mysql. I upgraded to 5 and it works now.