| Summary: | SOA-P 5 when started without -c is defined with different config than expected by JON | ||
|---|---|---|---|
| Product: | [JBoss] JBoss Enterprise SOA Platform 5 | Reporter: | Jaroslaw Kijanowski <kijanowski> |
| Component: | JON | Assignee: | Pavel Kralik <pkralik> |
| Status: | CLOSED NEXTRELEASE | QA Contact: | |
| Severity: | high | Docs Contact: | |
| Priority: | high | ||
| Version: | 5.0.0 ER5 | CC: | mvecera |
| Target Milestone: | --- | ||
| Target Release: | 5.1.0.ER1 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| URL: | http://jira.jboss.org/jira/browse/SOA-1692 | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2011-03-02 05:30:42 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: | |
|
Description
Jaroslaw Kijanowski
2009-12-08 20:29:36 UTC
Link: Added: This issue depends JOPR-419 Affects rel notes, since it's not going to be fixed in JON 2.3.1 (04:19:06 PM) ccrouch: jarek: no, its not planned to be fixed (04:20:12 PM) ccrouch: jarek: I've targeted it at 2.4, which is our next major release Affects: Added: [Documentation (Ref Guide, User Guide, etc.), Release Notes] Hey David, can you add this to the release notes? Hello Jaroslaw, Here is the draft text for the Release Notes: https://jira.jboss.org/jira/browse/JOPR-419 When the server is started without the -c configuration switch, the wrong profile is run ("production" instead of "default"). To use the default profile and bind to 127.0.0.1, always use the -c and -b parameters or JON will not recognize the platform. Cheers, David When the server is started without the -c configuration switch then the 'default' config is started. However JON will assume that no '-c' switch means that the 'production' config is up. Similar for the -b switch: no value means 127.0.0.1 but JON will think it's 0.0.0.0 Just to be clear, the second part is fine: "To use the default profile and bind to 127.0.0.1, always use the -c and -b parameters or JON will not recognize the platform." I would just not use the word 'wrong' since we start the 'default' config by default again and this is not a bug ;) Thanks for the quick feedback, Jaroslaw. Here is the second draft: https://jira.jboss.org/jira/browse/JOPR-419 When the server is started without the -c configuration switch, the profile named default is run. This is correct operation. Unfortunately, JON erroneously assumes that the production profile is run instead. JON also mistakenly assumes that the binding address is 0.0.0.0 if this has not been specified. To ensure that JON recognises the default profile and binds to the correct address of 127.0.0.1, always use the -c and -b parameters. By doing so, JON will recognise the platform. Looks good. Just a dot is missing after 'instead': "is run instead JON also mistakenly" Thanks for spotting that. Fixed. :-) Verified release notes. Will close this jira once the corresponding JON issue is fixed. Regression tested with SOA-P 5.1.0.ER1 and JON 2.4.0.GA (PostgreSQL 8.3.8), OpenJDK/SunJDK 1.6. Temporarily reopening to update release note information. Release Notes Docs Status: Added: Documented as Resolved Issue Writer: Added: dlesage Release Notes Text: Added: https://jira.jboss.org/jira/browse/JOPR-419 When the server is started without the -c configuration switch, the profile named default is run. This is correct operation. Unfortunately, JON erroneously assumes that the production profile is run instead. JON also mistakenly assumes that the binding address is 0.0.0.0 if this has not been specified. To ensure that JON recognises the default profile and binds to the correct address of 127.0.0.1, always use the -c and -b parameters. By doing so, JON will recognise the platform. |