Chris Jackson wrote: > This doesn't work for me. When I use svccfg -s setenv CATALINA_OPTS "Xms256m > -Xmx256m" the properties as displayed via svccfg's listprop are so: > > [b]method_context framework > method_context/environment astring "CATALINA_OPTS=\"-Xms256m -Xmx256m\""[/b] > > This is ignored when svcadm restarts the tomcat process. I've gone in via > editprop and removed the backslashes and extra quotes so it looks like this: > > [b]method_context framework > method_context/environment astring "CATALINA_OPTS=-Xms256m -Xmx256m"[/b] > > but that parameter seems to be ignored during startup and restart. >
No follow-up to this? I'm still befuddled by the requirements when you fill out method_context/[stuff]. My next suggestion is instead of using svccfg against the repository, modify the manifest and put in the method_context stuff and re-import. This is the *only* time I recommend this, because the existence of method_context/[stuff] in a manifest causes SMF to auto-fill-in-the-blank for you for some other method_context properties. When you use svccfg, SMF doesn't tell you that you need some other method_context/[stuff] to be filled out with the "default" value, it just silently fails. I've found this out playing with setting privileges. If that still doesn't work, I would setenv in the method. However, this goes against the principle of not having to modify any file when you want to change service properties. Let us know how this works out. CT
