Bug 1231002

Created attachment 1037871 [details]
whole log file

Description of problem:

when upgrade to BPMS 6.1 GA ,our old process was gone.

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1. use old server backup  data, include 
   database
   maven repo(kie.maven.settings.custom): .m2
   bpms repo (org.uberfire.metadata.index.dir) :repo
   git server data(org.uberfire.nio.git.dir).niogit
   and .index 
2. start server
3. run sql script 
  update Task t set name = (select shorttext from I18NText where task_names_id = t.id);
update Task t set subject = (select shorttext from I18NText where task_subjects_id = t.id);
update Task t set description = (select shorttext from I18NText where task_descriptions_id = t.id);
INSERT INTO AuditTaskImpl (activationTime, actualOwner, createdBy, createdOn, deploymentId, description, dueDate, name, parentId, priority, processId, processInstanceId, processSessionId, status, taskId)
SELECT activationTime, actualOwner_id, createdBy_id, createdOn, deploymentId, description, expirationTime, name, parentId, priority,processId, processInstanceId, processSessionId, status, id 
FROM Task;


Actual results:
i find tables DeploymentStore just have org.guvnor:guvnor-asset-mgmt-project:6.2.0.Final-redhat-4 , do not have any old process deployment information and i find master branch of system.git don't have any old process deployment information.
If i restart bpms6.1 server , i can not get any process definition of old process and  process instance of old process and deployment unit of old process. 

Expected results:
All old process can be work.

Additional info:
Last month , i get successful migration for BPMS 6.0.1 to  BPMS 6.1.ER4 .
I debug this issue , i find some code change from 6.1.CR4 to 6.1 GA in here
https://github.com/droolsjbpm/jbpm/blob/master/jbpm-services/jbpm-kie-services/src/main/java/org/jbpm/kie/services/impl/store/DeploymentStore.java#L152.
In 6.1.CR4 , don't have this code.
Our old process don't have Attributes.so there will throw runtimeexception.

Please refer to whole log  in the attachment.