[RESOLVED] Error during process migration to 7.4.1 from 7.3.0

Submitted by 3Fred9 on Mon, 01/23/2017 - 10:55
1
0
-1

Hi,

I'm migrating Bonita version 7.3.0 to 7.4.1 and I have an error during the process definition migration with the bonita-migration-distrib-2.19.0 tool. The last lines in log are :

....
[INFO] Execute migration to version 7.3.3
[INFO] Updating platform version in the database ...
[INFO] Platform version in database changed to 7.3.3
[INFO] Execute migration to version 7.4.0
[INFO] ---------------
[INFO] | Execute migration step: Update process definition xml to the new 7.4 format
Exception in thread "main" org.xml.sax.SAXParseException; lineNumber: 8; columnNumber: 52; cvc-id.2 : Occurrences multiples de la valeur d'ID '_65537'.
at com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.createSAXParseException(ErrorHandlerWrapper.java:203)
at com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.error(ErrorHandlerWrapper.java:134)
at com.sun.org.apache.xerces.internal.impl.XMLErrorReporter.reportError(XMLErrorReporter.java:396)
at com.sun.org.apache.xerces.internal.impl.XMLErrorReporter.reportError(XMLErrorReporter.java:327)
at com.sun.org.apache.xerces.internal.impl.XMLErrorReporter.reportError(XMLErrorReporter.java:284)
...

Thanks for any body help...

migration
Process
Definition
7.4

Comments

Submitted by 3Fred9 on Mon, 01/23/2017 - 17:19

The problem seems to be during the tranformation of the xml for the process definition.
I can't find the source of the bonita-migration-distrib-2.19.0. These are stopping at 7.3.2 here. Anybody knows where are the next ?

Permalink
Submitted by 3Fred9 on Mon, 01/30/2017 - 11:14

And another !!!! Is this transformation is all right ?

Exception in thread "main" org.xml.sax.SAXParseException; lineNumber: 9; columnNumber: 18; cvc-datatype-valid.1.2.1 : '' n'est pas une valeur valide pour 'NCName'.

Permalink
Submitted by 3Fred9 on Tue, 01/24/2017 - 17:43

Another problem :

Exception in thread "main" org.xml.sax.SAXParseException; lineNumber: 595; columnNumber: 21; cvc-complex-type.2.4.a : Contenu non valide trouvé à partir de l'élément 'incomingTransition'. L'une des valeurs '{displayDescription, displayName, displayDescriptionAfterCompletion, defaultTransition, throwMessageEventTrigger, throwSignalEventTrigger}' est attendue.

Permalink
Submitted by 3Fred9 on Mon, 01/30/2017 - 11:12

This problem is due to the order of the tags :

   <intermediateThrowEvent id="-8587563552856333760" name="Msg renvoi affaire">
      <description>BlaBla</description>
      <incomingTransition>2335833872676702296</incomingTransition>
      <outgoingTransition>8241998588891019719</outgoingTransition>

incomingTransition must be the first tag between description

Permalink
Submitted by 3Fred9 on Tue, 01/24/2017 - 16:11

This first problem is due to actors that are present twice in the process definition xml... Why ? I don't know ?

` <actors>
<actor name="Acteur">
<description/>
</actor>
<actor name="Acteur"/>
</actors>
`

I found the raison with XML Tools (Notepad++) by transforming with them and control with the files **ProcessDefinition.xml** and **ProcessDefiniton.xsd** present in **bonita-migration-distrib-2.19.0.jar**.

The message issue to the xsd validation is : ERROR: Element 'actor', attribute 'id': 'idm1596941468' is not a valid value of the atomic type 'xs:ID'.

I can bypass this problem migration with modify the content (xml process definition) in the **process_content** table of the bonita schema.

Permalink
Submitted by Sean McP on Mon, 01/23/2017 - 21:26

This looks like a bug, I would open a report here:

https://bonita.atlassian.net

regards
Seán

*PS: I realise this may not be the answer you are looking for but it's the best we can do for this type of error on the community forum, please mark as resolved so others don't have to reply.*

Permalink
Submitted by 3Fred9 on Tue, 01/24/2017 - 09:32

Thanks Sean,

Maybe it could be a problem with my process particularity, if I could get the migration source project, i coul'd debug it and try to find where is the problem and help you for resolving the issue...

Permalink
Submitted by Sean McP on Mon, 01/30/2017 - 11:20

As I said report it as a bug...

Finding one then another when you don't have any source is Bonitasoft problem...

Regards
Seán

Permalink
Submitted by 3Fred9 on Mon, 01/30/2017 - 11:31

I would but I can't

Permalink
1 answer

Submitted by 3Fred9 on Mon, 01/30/2017 - 16:32
1
0
-1
This one is the BEST answer!

Reported as bugs in JIRA here BBPMC-451 and BBPMC-452

Comments

Submitted by antoine.mottier on Thu, 02/02/2017 - 13:47

Issue should be fixed in next maintenance version of migration tools. Thanks for your report.

Permalink
Submitted by claudio.carvalh... on Wed, 05/08/2019 - 16:33

I'm having a problem similar to the one submitted by 3Fred9 on Tue, 01/24/2017 - 17:43:

[INFO] Execute migration to version 7.4.0
[INFO] ---------------
[INFO] | Execute migration step: Update process definition xml to the new 7.4 format
[ERROR]
failed to migrate process definition due to cvc-complex-type.2.4.a: Foi detectado um conteúdo inválido começando com o elemento 'displayDescription'. Era esperado um dos '{displayDescriptionAfterCompletion, defaultTransition}'.

I'm using the bonita-migration-distrib-2.40.0 (04/18/2019 - 15:37) to migrate from 7.3.3 to 7.4.0, since the similar problem was reported as a bug in 2017, I was wondering if this one could be a bug as well?

Regards.
Claudio Carvalho

Permalink
Submitted by antoine.mottier on Thu, 05/09/2019 - 14:26

I just give a try to a migration from 7.3.0 to 7.4.1 having a process definition that includes a "display description after completion" for a task and also a transition set as "default" and I manage to successfully do it.

So I think that in order to reproduce your issue I would need your process definition. Can you share your process .bar file for Bonita 7.3.0? And also maybe the content of your workspace as a .bos file? Can you put all that in an new issue on the Bonita Community Edition bug tracker: https://bonita.atlassian.net/projects/BBPMC/issues/

Thanks.

Permalink
Submitted by claudio.carvalh... on Thu, 05/09/2019 - 19:20

Acctually, I'm migrating from 6.4.2 to 7.8.4.
The migration from 6.4.2 to 7.0.0 worked fine and the migration from 7.0.0 to 7.3.3 also worked fine. The problem I mentioned has occured in the migration from 7.3.3 to 7.4.0.
In order to create a new issue on the Bonita Community Edition bug tracker, I tried to import my .bos (6.4.2), using the Studio 7.3.0 but it didn't work. I tried doing this in other versions as welll, but it only worked in Studio 7.8. Could you help me with that? I Can share my .bos if you want, just let me know how.

Thanks in advance.

Permalink
Submitted by antoine.mottier on Thu, 05/09/2019 - 20:41

Yes I can definitively help with that but I think it will be more efficient to use the issue tracker (https://bonita.atlassian.net/projects/BBPMC/issues/).

Can you open an issue there and I'll try to reproduce the issue and find a fix. Thanks.

Permalink
Submitted by antoine.mottier on Thu, 05/09/2019 - 20:41

Yes I can definitively help with that but I think it will be more efficient to use the issue tracker (https://bonita.atlassian.net/projects/BBPMC/issues/).

Can you open an issue there and I'll try to reproduce the issue and find a fix. Thanks.

Permalink
Submitted by claudio.carvalh... on Thu, 05/09/2019 - 21:29

Done! BBPMC-552.
Please let me know if you need anything else.
Regards.

Permalink
Submitted by claudio.carvalh... on Tue, 05/21/2019 - 16:36

reported by mistake

Permalink
Submitted by antoine.mottier on Tue, 05/21/2019 - 19:23

Sorry I didn't had time yet to take a look at the issue you report (https://bonita.atlassian.net/browse/BBPMC-552).

But can you clarify the meaning of your last comment? Is it an accidental comment? Or did you mean that you managed to solved the issue?

Permalink
Submitted by claudio.carvalh... on Tue, 05/21/2019 - 20:31

Actually it was a mistake, my mistake. But thanks anyway and sorry for bothering you guys.
However, I'm still working in the migration here and I'd like to know if can report any issue I might have along the process.

Permalink
Submitted by antoine.mottier on Wed, 05/22/2019 - 09:24

Thanks for the feedback. Can I ask you to put a comment on the Jira issue explaining what was the mistake?

Of you course feel free to post a question if you need help with the migration process or open a Jira issue if you face a bug (such contribution are really appreciated).

Permalink
Submitted by claudio.carvalh... on Wed, 05/22/2019 - 16:06

It was mostly a typo, i don't think it will be of any help on the Jira issue, but again, thank you very much I really appreciated your help. I'll let you know if anything else come along during my migration process. Regards.

Permalink
Submitted by claudio.carvalh... on Wed, 05/22/2019 - 17:25

Sorry, but i think we're having a little misunderstanding here. The issue BBPMC-552 was not suposed to be closed. When I submit the comment "reported by mistake" on Tue, 05/21/2019 - 11:36, I was reffering to a totally diferent issue. The original issue BBPMC-552 is a bug and still happening. The one I reported by mistake was about the bonita.home directory is no longer be used in version 7.3.3 and above. It is possible to reopen the issue BBPMC-552?

Permalink
Submitted by antoine.mottier on Wed, 05/22/2019 - 17:49

Sorry about the misunderstanding. Issue is reopened and I will investigate it.

Permalink
Notifications