Hide Forgot
Description of problem: Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
fixed to ensure that once manager is closed it can be re-registered on jbpm-executor end droolsjbpm-knowledge master: https://github.com/droolsjbpm/droolsjbpm-knowledge/commit/931581c840dd2618d05c722ebabce9b0d89a449e 6.0.x https://github.com/droolsjbpm/droolsjbpm-knowledge/commit/996209428305109ae49c29b2991a221896d8e61f jbpm master: https://github.com/droolsjbpm/jbpm/commit/c4b36c4605417a1732bfb2531e2985a9eb4ac5c8 6.0.x: https://github.com/droolsjbpm/jbpm/commit/ec500e7aada5f495b81e160f5e75ed416bd2f339
Maciej Swiderski <swiderski.maciej> updated the status of jira JBPM-4168 to Resolved
Verified in BPMS 6 ER7 (6.0.1-redhat-2).