Uploaded image for project: 'Proxy'
  1. Proxy
  2. PROXY-183

Error when deploying proxy, jdbc driver

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 4.4.3
    • Fix Version/s: 4.5.0
    • Labels:
      None
    • Environment:
      strech + Postgresql 9.6
    • Account:
      Maintenance 2018 (MAINTENANCE2018)

      Description

      The error is under the installation of Luxembourg: https://gazelle.agence-esante.lu/
      If you do gazelle@debian-gazelle[PROD: LUXEMBOURG]:~$ touch /usr/local/jboss7-tm/standalone/deployments/gazelle-proxy.ear
      you will have the same error

      2017-10-21 22:52:11,348 ERROR () [org.hibernate.engine.jdbc.spi.SqlExceptionHelper] (ServerService Thread Pool -- 115 ) ERROR: column am.amcanorder does not exist
        Position: 427
      2017-10-21 22:52:11,349 ERROR () [org.hibernate.tool.hbm2ddl.SchemaUpdate] (ServerService Thread Pool -- 115 ) HHH000299: Could not complete schema update: java.lang.NullPointerException
      at org.hibernate.engine.jdbc.spi.SqlExceptionHelper.convert(SqlExceptionHelper.java:124) [hibernate-core-4.2.20.Final.jar:4.2.20.Final]
      at org.hibernate.engine.jdbc.spi.SqlExceptionHelper.convert(SqlExceptionHelper.java:109) [hibernate-core-4.2.20.Final.jar:4.2.20.Final]
      at org.hibernate.tool.hbm2ddl.DatabaseMetadata.getTableMetadata(DatabaseMetadata.java:157) [hibernate-core-4.2.20.Final.jar:4.2.20.Final]
      at org.hibernate.cfg.Configuration.generateSchemaUpdateScriptList(Configuration.java:1173) [hibernate-core-4.2.20.Final.jar:4.2.20.Final]
      at org.hibernate.tool.hbm2ddl.SchemaUpdate.execute(SchemaUpdate.java:237) [hibernate-core-4.2.20.Final.jar:4.2.20.Final]
      at org.hibernate.tool.hbm2ddl.SchemaUpdate.execute(SchemaUpdate.java:203) [hibernate-core-4.2.20.Final.jar:4.2.20.Final]
      at org.hibernate.internal.SessionFactoryImpl.<init>(SessionFactoryImpl.java:509) [hibernate-core-4.2.20.Final.jar:4.2.20.Final]
      at org.hibernate.cfg.Configuration.buildSessionFactory(Configuration.java:1799) [hibernate-core-4.2.20.Final.jar:4.2.20.Final]
      at org.hibernate.ejb.EntityManagerFactoryImpl.<init>(EntityManagerFactoryImpl.java:96) [hibernate-entitymanager-4.2.20.Final.jar:4.2.20.Final]
      at org.hibernate.ejb.Ejb3Configuration.buildEntityManagerFactory(Ejb3Configuration.java:915) [hibernate-entitymanager-4.2.20.Final.jar:4.2.20.Final]
      at org.hibernate.ejb.Ejb3Configuration.buildEntityManagerFactory(Ejb3Configuration.java:900) [hibernate-entitymanager-4.2.20.Final.jar:4.2.20.Final]
      at org.hibernate.ejb.HibernatePersistence.createContainerEntityManagerFactory(HibernatePersistence.java:76) [hibernate-entitymanager-4.2.20.Final.jar:4.2.20.Final]
      at org.jboss.as.jpa.service.PersistenceUnitServiceImpl.createContainerEntityManagerFactory(PersistenceUnitServiceImpl.java:200) [jboss-as-jpa-7.2.0.Final.jar:7.2.0.Final]
      at org.jboss.as.jpa.service.PersistenceUnitServiceImpl.access$600(PersistenceUnitServiceImpl.java:57) [jboss-as-jpa-7.2.0.Final.jar:7.2.0.Final]
      at org.jboss.as.jpa.service.PersistenceUnitServiceImpl$1.run(PersistenceUnitServiceImpl.java:99) [jboss-as-jpa-7.2.0.Final.jar:7.2.0.Final]
      at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_75]
      at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_75]
      at java.lang.Thread.run(Thread.java:745) [rt.jar:1.7.0_75]
      at org.jboss.threads.JBossThread.run(JBossThread.java:122)

      2017-10-21 22:52:12,525 WARNING () [org.richfaces.log.Application] (ServerService Thre

        Attachments

          Activity

            People

            • Assignee:
              gthomazon Guillaume Thomazon
              Reporter:
              aboufahj Abderrazek Boufahja (Inactive)
            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Time Tracking

                Estimated:
                Original Estimate - 2 hours Original Estimate - 2 hours
                2h
                Remaining:
                Remaining Estimate - 0 minutes
                0m
                Logged:
                Time Spent - 2 hours, 30 minutes
                2h 30m

                  Potential Duplicates