Bug 852231
Summary: | BRMS AsyncWSHumanTaskHandler port conflicts with JON port configuration | |||
---|---|---|---|---|
Product: | [JBoss] JBoss Enterprise BRMS Platform 5 | Reporter: | Eric D. Schabell <eschabel> | |
Component: | jBPM 5, Tooling (JBDS) | Assignee: | Kris Verlaenen <kverlaen> | |
Status: | VERIFIED --- | QA Contact: | ||
Severity: | medium | Docs Contact: | ||
Priority: | unspecified | |||
Version: | BRMS 5.3.0.GA | CC: | alazarot, kverlaen, ldimaggi | |
Target Milestone: | ER4 | |||
Target Release: | BRMS 5.3.1 GA | |||
Hardware: | Unspecified | |||
OS: | Unspecified | |||
Whiteboard: | ||||
Fixed In Version: | Doc Type: | Bug Fix | ||
Doc Text: |
The AsyncWSHumanTaskHandler handler was configured by default to use port 5446. When JBoss Enterprise BRMS and JBoss Operations Network 3.1 were run on the same machine there was a conflict because JBoss Operations Network also uses port 5446. This has been resolved by changing the default port for the AsyncWSHumanTaskHandler handler to 5153. Both systems can now run on the same machine with no port conflicts.
|
Story Points: | --- | |
Clone Of: | ||||
: | 952626 (view as bug list) | Environment: | ||
Last Closed: | 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: | ||||
Bug Depends On: | ||||
Bug Blocks: | 952626 |
Description
Eric D. Schabell
2012-08-27 23:31:54 UTC
Could we agree on what port we should use then? Kris Setting pm_ack as this issue has been approved by Dev and QE. Also proposing this issue for docs installation guide, in case we do not fix the port conflict but just want to inform customers to configure the port before using. In general port for human task service is already configurable: 1. in jbpm.console.properties (inside business-central.server.war) to configure human task work item handler 2. in web.xml of jbpm-human-task.war for human task server 5446 port was used as by default 5445 (default hornetq port) is already taken by embedded hornetq of EAP5. Shall that be changed on code level or will it be product configuration/documentation? Maciej, I'd recommend we don't just change this for the product, but that we change the default in the community as well. This to avoid issues where people would have problems when trying to connect to the task service in production (for example with the eclipse plugin) or where people would have to always do additional configuration (more complexity) when using the product (as the default is not using the right port). So that would involve changing the port wherever it occurs in the droolsjbpm codebase. Wdyt? Kris, I am fine with that, once we have decided what port number it should be I'll make the changes which including eclipse plugin as well. As a side note, regardless of the port we choose now there is always a risk of port conflict in some environments so the most important is the ability to change it easily which I think we already have So, waiting for port number that should be used. This issue has been marked as requires_doc_text, however, no text has been provided. Please provide the text so it can be added to the release notes document, or set the requires_doc_text flag to '-'. Thanks Lee Seems port 5153 might be a good fit, didn't really find any information about this port commonly being used by other applications. ok, port changed to 5153 for both jbpm code base and eclipse plugin. Change was merged into master and 5.2.x (jbpm), master and 5.3.x (droolsjbpm-tools) This has been resolved a long time ago. Setting VERIFIED. |