Bug 975820
| Summary: | Cannot start BPMS when any deployed project kmodule.xml set session as default | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Retired] JBoss BPMS Platform 6 | Reporter: | Ivo Bek <ibek> | ||||
| Component: | Business Central | Assignee: | Maciej Swiderski <mswiders> | ||||
| Status: | CLOSED WONTFIX | QA Contact: | Ivo Bek <ibek> | ||||
| Severity: | unspecified | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | 6.0.0 | CC: | mswiders, rrajasek, rzhang | ||||
| Target Milestone: | ER2 | ||||||
| Target Release: | 6.0.0 | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2013-09-23 11:56:17 UTC | Type: | Bug | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Embargoed: | |||||||
| Attachments: |
|
||||||
|
Description
Ivo Bek
2013-06-19 12:13:10 UTC
Created attachment 762904 [details]
the project with session set as default
Unfortunately the kjar attached does not produce valid KieModule - returns an empty KieModule but rebuild it manually to try it and all works as expected. It is completely fine (or even recommended) to have session marked as default as that simplifies deployment. In general there are two ways to deploy kjars in kie-wb: 1. auto deploy that is automatically attempted when you build project in project explorer 2. using Deployments screen where you specify details of the kjar to deploy The main difference between these two is that with second one you can provide the name of kbase and ksession that shall be used when deploying (creating runtime manager). In first case it relies on default kbase and ksession definitions. If they are not there then it won't be able to deploy as it cannot guess what kbase and ksession it shall use. Meaning auto deploy will fail but user can manually deploy it using Deployments screen where kbase and ksession names can be given. Hi Maciej, Yes I understand that but the user should be only warned about the missing default kbase and ksession, because in the current situation we aren't able to deploy the business central to fix this "mistake", and change the project kmodule.xml or create the default kbase, and ksession. BTW I didn't figure out how to create the default kbase and ksession. Is it possible to create them in the business central or how is this done? For now I would recommend to not use the default kbase, and ksession, because we weren't able to fix it without removing .niogit, repository, data and tmp folders but then the BPMS will never be the same as before; so, it's even better to install the new BPMS again and clone the user's repositories from .niogit. Thank you Ivo, in most of the cases you should not create any kbase or ksession in kmodule.xml at all as that would make default being generated for you. So leaving blank kmodule.xml when authoring should make the deployment works just fine. In Beta3 there was an issue that authoring tool was adding one ksession there by default (was already removed so it keeps clean kmodule.xml) and that might cause issues as it was not marked as default. Removing it from kmodule.xml made all works ok. Moreover there is no need to remove entire .niogit if you want to clean up runtime environment, in fact there are two ways: 1. remove only system.git from .niogit folder 2. clone system.git repository and make the required changes - all system configuration is stored as files, for example each deployment unit is stored as independent file in the system repository and can be manipulated. So once cloned you can delete given deployment unit and push the changes back to the origin repository. Another thing is that when deployment fails it is not stored in the system repository so on restart it will not be deployed as only successful deployed units are stored in system repo. Thank you for the clarification; it's very helpful when there isn't any documentation about that. Well it would be nice to have the default generated kbase and kmodule present in the Project Editor because I thought there must be something to be set. understand that, and as soon as we are done with features will enter documentation phase so more and more docs will come in. Feel free to ask questions until documentation is provided. Kbase and ksession needs to be specified usually when you have more than one base and you want to isolate them but in usual case you have one and the default is just fine. For ksession is slightly different as kmodule.xml allows you to specify some configuration for it, like listeners or work item handlers that might be important to define there too. Please note that human task is not needed to be defined as RuntimeManager configures it by default. marking as modified as there are no planned changes in code. Conclusion: The issue was caused by bad configuration of kmodule.xml and the proper configuration should be explained in documentation to avoid the issue. Simple clear kmodule.xml works fine in BPMS 6.0.0.ER3. |