[MAGNOLIA-454] Let administrator set author port for activation. Created: 15/Jun/05 Updated: 14/Oct/05 Resolved: 14/Oct/05 |
|
| Status: | Closed |
| Project: | Magnolia |
| Component/s: | core |
| Affects Version/s: | 2.0 Final |
| Fix Version/s: | 2.0 Final |
| Type: | Improvement | Priority: | Minor |
| Reporter: | Geli Crick | Assignee: | Boris Kraft |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Tomcat as shipped with Magnolia 2.0, author and public instances running separately on ports 8081 and 8082, behind Apache HTTP Server 2.0.54 (with mod_jk) on port 80. |
||
| Attachments: |
|
| Template: |
|
| Acceptance criteria: |
Empty
|
| Task DoD: |
[ ]*
Doc/release notes changes? Comment present?
[ ]*
Downstream builds green?
[ ]*
Solution information and context easily available?
[ ]*
Tests
[ ]*
FixVersion filled and not yet released
[ ] 
Architecture Decision Record (ADR)
|
| Date of First Response: |
| Description |
|
With this set up: author on Tomcat localhost:8081 there is a problem with activation. The public instance is unable to connect back to the author instance in order to retrieve the activated content (it tries to use port 80 when it should be using 8081). |
| Comments |
| Comment by Geli Crick [ 15/Jun/05 ] |
|
I was able to fix this problem by changing Syndicator.java and Subscribe.java so that the administrator may set the port on which the author is listening. I am attatching a patch made from http://svn.magnolia.info/svn/magnolia/tags/magnolia2.0-041110. In the author instance, set the node of Config > subscribers > SubscriberConfig > 0001 > authorPort to the local port on which the author instance is running. |
| Comment by Philipp Bracher [ 15/Jun/05 ] |
|
in current trunk one is able to define the url including the port in the config: /subscribers/SubscriberConfig/0001/senderURL I don't now if this was not possible in 2.0 |
| Comment by Geli Crick [ 16/Jun/05 ] |
|
Yes, it is fixed in the current trunk of the latest version. I think this only affects Magnolia 2.0. |