Title:
Bug 72001:(Watson Migration Closure)When creating new instances within the CFAdmin Instance Manager, we should have the ability to specify an instance specific jvm
| View in TrackerStatus/Resolution/Reason: Closed/Won't Fix/LowImpact
Reporter/Name(from Bugbase): ANDY ALLAN / Andy Allan (ANDY ALLAN)
Created: 06/17/2008
Components: Installation/Config, Config
Versions: 9.0
Failure Type: Unspecified
Found In Build/Fixed In Build: 0000 /
Priority/Frequency: Normal / Unknown
Locale/System: English / Platforms All
Vote Count: 1
Problem:
When creating new instances within the CFAdmin Instance Manager, we should have the ability to specify an instance specific jvm.config file.
I believe this was something that was on the cards for JRun4.5 before it was thrown in the bin.
This could work in a number of ways:
1. Each instance specific jvm.config file could be created from a master template and therefore created automatically.
2. The user may have to manually specify an existing jvm.config file.
To be fair, this will probably only affect a small group of folks, as most of us will just do the extra configuration manually.
Method:
Result:
----------------------------- Additional Watson Details -----------------------------
Watson Bug ID: 3035234
External Customer Info:
External Company:
External Customer Name: Andy Allan
External Customer Email: 44FB6280464CC51B992015C3
External Test Config: 06/17/2008Attachments:
Comments: