On Wed, Mar 10, 2010 at 10:11 AM, Scott Lawrence <[email protected]> wrote:
> On Wed, 2010-03-10 at 09:57 -0500, Robert Joly wrote:
>>
>> > I suggest that you take the safe route and just disable the
>> > Attach API.
>>
>> I agree with this suggestion.  I could modify the startup script for
>> each java process to add a -Dcom.ibm.tools.attach.enable=no argument
>> but
>> this would not be optimal as new java processes that get introduce
>> later
>> may forget to do this.
>>
>> Instead, I was toying with the idea of modifying the 'sipx-config'
>> script that is used to generate the string to use to launch
>> 'java' (i.e.
>> /usr/bin/java).  Every startup script for java processes invoke it and
>> it appears to me that it would be a good central place to put my
>> -Dcom.ibm.tools.attach.enable=no argument so that it gets applied to
>> all
>> present and future java processes.
>
> Seems like a good idea.
>
> If there's anything you can do (like put those properties in a file?) to
> shorten the command lines for java, it would make many process
> monitoring tools easier to use.
>
> There was some discussion of this with respect to the use of classpath
> arguments vs CLASSPATH environment variable some time ago, in which Woof
> asserted that there used to be a difference that favored the arguments,
> but that now using CLASSPATH works just as well, so if we could (now or
> later) get rid of all those arguments it would be very nice.


You cannot get rid of --claspath .

CLASSPATH is an environment variable that has special meaning to java
and it is equivalent to -classpath (argument). We do not rely on that
environment variable.

It is fine as is.

Ranga


>
> _______________________________________________
> sipx-dev mailing list [email protected]
> List Archive: http://list.sipfoundry.org/archive/sipx-dev
> Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev
> sipXecs IP PBX -- http://www.sipfoundry.org/
>



-- 
M. Ranganathan
_______________________________________________
sipx-dev mailing list [email protected]
List Archive: http://list.sipfoundry.org/archive/sipx-dev
Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev
sipXecs IP PBX -- http://www.sipfoundry.org/

Reply via email to