Details
Bug
Resolved
Major
Activity
- All
- Comments
- Work Log
- History
- Activity
- Subversion Commits
| Field | Original Value | New Value |
|---|---|---|
| Assignee | Default Project Leader [ mmbaseleader ] | Michiel Meeuwissen [ mihxil ] |
| Status | Open [ 1 ] | In Progress [ 3 ] |
| Fix Version/s | 1.8.3 [ 10118 ] | |
| Fix Version/s | 1.9.0 [ 10119 ] |
| Status | In Progress [ 3 ] | Resolved [ 5 ] |
| Resolution | Fixed [ 1 ] |
| Comment | [ ie, the ${HOST} setting I only did in HEAD. ] |
| Description |
You can not specify 'machinename' in mmbaseroot.xml, it then defaults to java.net.InetAddress.getLocalHost().getHostName() + the context. You can however have several servers on the same machine, and even on the same context (using a different mmbaseroot.host), then, there don't arise different MMServer entries. This can be fixed by either considering also the 'host' entry in mmserver, or by having a differnte defualt machinename based on the host-setting. (this is possble already, using ${HOST} but then it does not any more contain the context. So, we could also fix that last thing. |
You can not specify 'machinename' in mmbaseroot.xml, it then defaults to java.net.InetAddress.getLocalHost().getHostName() + the context. You can however have several servers on the same machine, and even on the same context (using a different mmbaseroot.host), then, there don't arise different MMServer entries. This can be fixed by either considering also the 'host' entry in mmserver, or by having a different default machinename based on the host-setting. (this is possble already, using ${HOST} but then it does not any more contain the context. So, we could also fix that last thing (recognition of ${CONTEXT} in the machinename setting) |