[esb-issues] [JBoss JIRA] Commented: (JBESB-1722) MSSQL: Unable to populate JBPM_ID_... tables

[Darrin Mison (JIRA)]

    [ https://jira.jboss.org/jira/browse/JBESB-1722?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12422470#action_12422470 ] 

Darrin Mison commented on JBESB-1722:
-------------------------------------

Proposed SOA 4.2 TP02 Release Note:
MSSQL: Initialisation of example data has been removed

> MSSQL: Unable to populate JBPM_ID_... tables
> --------------------------------------------
>
>                 Key: JBESB-1722
>                 URL: https://jira.jboss.org/jira/browse/JBESB-1722
>             Project: JBoss ESB
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Configuration, Deployment, Process flow
>    Affects Versions: 4.2.1 CP2
>            Reporter: Martin Vecera
>            Assignee: Kevin Conner
>            Priority: Blocker
>             Fix For: 4.2.1 CP3
>
>
> deploy/jbpm.esb/jbpm-sql/jbpm.jpdl.mssql.sql creates the MSSQL tables in a way that prevents direct (concrete value) primary key insertion.
> This makes SQL statements in deploy/jbpm.esb/jbpm-sql/import.sql fail:
> 08:40:01,503 WARN  [ServiceController] Problem starting service jboss.esb:service=JBPMDatabaseInitializer
> com.microsoft.sqlserver.jdbc.SQLServerException: Cannot insert explicit value for identity column in table 'JBPM_ID_USER' when IDENTITY_INSERT is set to OFF.
>         at com.microsoft.sqlserver.jdbc.SQLServerException.makeFromDatabaseError(Unknown Source)
>         at com.microsoft.sqlserver.jdbc.IOBuffer.processPackets(Unknown Source)
>         at com.microsoft.sqlserver.jdbc.SQLServerStatement.getNextResult(Unknown Source)
>         at com.microsoft.sqlserver.jdbc.SQLServerStatement.doExecuteStatement(Unknown Source)
>         at com.microsoft.sqlserver.jdbc.SQLServerStatement$StatementExecutionRequest.executeStatement(Unknown Source)
>         at com.microsoft.sqlserver.jdbc.CancelableRequest.execute(Unknown Source)
>         at com.microsoft.sqlserver.jdbc.SQLServerConnection.executeRequest(Unknown Source)
>         at com.microsoft.sqlserver.jdbc.SQLServerStatement.executeUpdate(Unknown Source)
>         at org.jboss.resource.adapter.jdbc.WrappedStatement.executeUpdate(WrappedStatement.java:186)
>         at org.jboss.internal.soa.esb.dependencies.DatabaseInitializer.executeSql(DatabaseInitializer.java:145)
>         at org.jboss.internal.soa.esb.dependencies.DatabaseInitializer.initDatabase(DatabaseInitializer.java:122)
>         at org.jboss.internal.soa.esb.dependencies.DatabaseInitializer.startService(DatabaseInitializer.java:159)
>         at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:289)
>         at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:245)
> ...

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira