Uploaded image for project: 'jUDDI (Retired)'
  1. jUDDI (Retired)
  2. JUDDI-999

Issue with SQL Server Database with JUDDI 3.3.6 : The size (8192) given to the column 'instance_parms' exceeds the maximum allowed for any data type (8000)

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Closed
    • Major
    • Resolution: Fixed
    • 3.3.6
    • 3.3.7
    • juddi-tomcat

    Description

      We were using SQLServer with JUDDI 3.0.4. It is working fine so far.

      Now, we are trying to move to JUDDI version 3.3.6. We are encountering following issue on start-up.

      Caused by: <openjpa-2.3.0-r422266:1540826 nonfatal general error> org.apache.openjpa.persistence.PersistenceException: The size (8192) given to the column 'instance_parms' exceeds the maximum allowed for any data type (8000). {stmnt 1090863652 CREATE TABLE j3_tmodel_instance_info (id BIGINT NOT NULL, instance_parms VARCHAR(8192), tmodel_key VARCHAR(255) NOT NULL, entity_key VARCHAR(255) NOT NULL, PRIMARY KEY (id))} [code=131, state=S0002]Caused by: <openjpa-2.3.0-r422266:1540826 nonfatal general error> org.apache.openjpa.persistence.PersistenceException: The size (8192) given to the column 'instance_parms' exceeds the maximum allowed for any data type (8000). {stmnt 1090863652 CREATE TABLE j3_tmodel_instance_info (id BIGINT NOT NULL, instance_parms VARCHAR(8192), tmodel_key VARCHAR(255) NOT NULL, entity_key VARCHAR(255) NOT NULL, PRIMARY KEY (id))} [code=131, state=S0002] at org.apache.openjpa.jdbc.meta.MappingTool.record(MappingTool.java:559) at org.apache.openjpa.jdbc.meta.MappingTool.record(MappingTool.java:455) at org.apache.openjpa.jdbc.kernel.JDBCBrokerFactory.synchronizeMappings(JDBCBrokerFactory.java:160) at org.apache.openjpa.jdbc.kernel.JDBCBrokerFactory.synchronizeMappings(JDBCBrokerFactory.java:164) at org.apache.openjpa.jdbc.kernel.JDBCBrokerFactory.newBrokerImpl(JDBCBrokerFactory.java:122) at org.apache.openjpa.kernel.AbstractBrokerFactory.newBroker(AbstractBrokerFactory.java:209) at org.apache.openjpa.kernel.DelegatingBrokerFactory.newBroker(DelegatingBrokerFactory.java:155) at org.apache.openjpa.persistence.EntityManagerFactoryImpl.createEntityManager(EntityManagerFactoryImpl.java:226) at org.apache.openjpa.persistence.EntityManagerFactoryImpl.createEntityManager(EntityManagerFactoryImpl.java:153) at org.apache.openjpa.persistence.EntityManagerFactoryImpl.createEntityManager(EntityManagerFactoryImpl.java:59) at org.apache.juddi.config.PersistenceManager.getEntityManager(PersistenceManager.java:48) at org.apache.juddi.config.AppConfig.getPersistentConfiguration(AppConfig.java:174) at org.apache.juddi.config.AppConfig.loadConfiguration(AppConfig.java:160) at org.apache.juddi.config.AppConfig.<init>(AppConfig.java:82) at org.apache.juddi.config.AppConfig.getInstance(AppConfig.java:272) at org.apache.juddi.config.AppConfig.getConfiguration(AppConfig.java:298) at org.apache.juddi.api.impl.AuthenticatedService.<init>(AuthenticatedService.java:75) at org.apache.juddi.api.impl.UDDIInquiryImpl.<init>(UDDIInquiryImpl.java:88) at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at sun.reflect.NativeConstructorAccessorImpl.newInstance(Unknown Source) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(Unknown Source) at java.lang.reflect.Constructor.newInstance(Unknown Source) at org.springframework.beans.BeanUtils.instantiateClass(BeanUtils.java:142) ... 36 moreCaused by: org.apache.openjpa.lib.jdbc.ReportingSQLException: The size (8192) given to the column 'instance_parms' exceeds the maximum allowed for any data type (8000). {stmnt 1090863652 CREATE TABLE j3_tmodel_instance_info (id BIGINT NOT NULL, instance_parms VARCHAR(8192), tmodel_key VARCHAR(255) NOT NULL, entity_key VARCHAR(255) NOT NULL, PRIMARY KEY (id))} [code=131, state=S0002] at org.apache.openjpa.lib.jdbc.LoggingConnectionDecorator.wrap(LoggingConnectionDecorator.java:219) at org.apache.openjpa.lib.jdbc.LoggingConnectionDecorator.wrap(LoggingConnectionDecorator.java:203) at org.apache.openjpa.lib.jdbc.LoggingConnectionDecorator.access$700(LoggingConnectionDecorator.java:59) at org.apache.openjpa.lib.jdbc.LoggingConnectionDecorator$LoggingConnection$LoggingStatement.executeUpdate(LoggingConnectionDecorator.java:914) at org.apache.openjpa.lib.jdbc.DelegatingStatement.executeUpdate(DelegatingStatement.java:118) at org.apache.openjpa.jdbc.schema.SchemaTool.executeSQL(SchemaTool.java:1231) at org.apache.openjpa.jdbc.schema.SchemaTool.createTable(SchemaTool.java:976) at org.apache.openjpa.jdbc.schema.SchemaTool.add(SchemaTool.java:552) at org.apache.openjpa.jdbc.schema.SchemaTool.add(SchemaTool.java:364) at org.apache.openjpa.jdbc.schema.SchemaTool.run(SchemaTool.java:341) at org.apache.openjpa.jdbc.meta.MappingTool.record(MappingTool.java:505) ... 58 more
      

       

      The error is "The size (8192) given to the column 'instance_parms' exceeds the maximum allowed for any data type (8000)"

      Eventually the table "j3_tmodel_instance_info" failed to create. We are using SQLServer version 12.0.5207.0. It poses a limit on varchar fields to 8000.

      We have tried modifying the column length in class "TmodelInstanceInfo" and redeploying the app, however then it starts giving other issue.

      The type "class org.apache.juddi.model.TmodelInstanceInfo" has not been enhanced.

       

      Could anyone please help us. We are in RED flag and our application cease to work after update to JUDDI 3.3.6

      Any help be greatly appreciated. Kindly let me know if I need to provide more information to assist investigation.

      Thanks a lot

       

      Attachments

        1. catalina-log.txt
          10 kB
          Amol Bhonsle
        2. juddi-core-3.3.8-SNAPSHOT.jar
          626 kB
          Alex O'Ree
        3. juddi-core-openjpa-3.3.8-SNAPSHOT.jar
          843 kB
          Alex O'Ree
        4. tomcat-error.txt
          5 kB
          Amol Bhonsle

        Issue Links

          Activity

            People

              spyhunter99 Alex O'Ree
              rahul.winner Rahul S
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: