1 Reply Latest reply on Sep 16, 2013 1:42 AM by Maciej Swiderski

    JBPM 6.0.0CR2 fails to deploy

    Mark Yang Newbie

      Hi, I just attempted clean install of JBPM 6.0.0CR2. When I tried to start it, the .war failed to deploy, so I took a look at server.log and noticed this:

      0:50:03,135 INFO  [org.hibernate.tool.hbm2ddl.TableMetadata] (MSC service thread 1-14) HHH000108: Foreign keys: [fk61f475a52ff04688, fk61f475a5f510cb46, fk61f475a5b35e68f5]

      10:50:03,138 INFO  [org.hibernate.tool.hbm2ddl.TableMetadata] (MSC service thread 1-14) HHH000126: Indexes: [fk61f475a5b35e68f5_index_e, fk61f475a52ff04688_index_e, primary_key_e8]

      10:50:03,317 ERROR [org.hibernate.tool.hbm2ddl.SchemaUpdate] (MSC service thread 1-14) HHH000388: Unsuccessful: alter table I18NText add column I18NTextId bigint not null

      10:50:03,326 ERROR [org.hibernate.tool.hbm2ddl.SchemaUpdate] (MSC service thread 1-14) NULL not allowed for column "I18NTEXTID"; SQL statement:

      alter table I18NText add column I18NTextId bigint not null [23502-161]

      10:50:03,358 ERROR [org.hibernate.tool.hbm2ddl.SchemaUpdate] (MSC service thread 1-14) HHH000388: Unsuccessful: alter table Task add column TaskId bigint not null

      10:50:03,363 ERROR [org.hibernate.tool.hbm2ddl.SchemaUpdate] (MSC service thread 1-14) NULL not allowed for column "TASKID"; SQL statement:

      alter table Task add column TaskId bigint not null [23502-161]

      10:50:03,440 ERROR [org.hibernate.tool.hbm2ddl.SchemaUpdate] (MSC service thread 1-14) HHH000388: Unsuccessful: alter table Attachment add constraint FK1C9354333CA892A foreign key (TaskData_Attachments_Id) references Task

      10:50:03,445 ERROR [org.hibernate.tool.hbm2ddl.SchemaUpdate] (MSC service thread 1-14) Constraint "FK1C9354333CA892A" already exists; SQL statement:

      ....

      Looks like altering the table is unsuccessful every time, and this causes a bunch of nullpointerexpections when deploying jbpm-console. Any recommendations on how to proceed?

        • 1. Re: JBPM 6.0.0CR2 fails to deploy
          Maciej Swiderski Master

          these unsuccessful hibernate errors do not impact the application deployment but indeed there is an issue with building demo environment on application startup. Would you mind trying CR3 version to see if that is resolved there and if not please file a jira issue (and describe your environment) as it looks like it might be OS specific - assuming you ran on windows.

           

          HTH