SharedShell and NTLM support
Sunday Dec 16, 2007
One of the customers I have done a lot of performance analysis work with this year are keen to use SharedShell. I am also very keen for them to use SharedShell as it saves me a 7 hour drive or train trip for what can often be 30 minutes work to root cause a performance issue. However, it appears that they use NTLM(not something I have come across before) with do not play nice together. The error message looks like this
09:17:15.638 [10] WARNING
com.sun.srs.tunneling.client.util.Connection.doHttpsProxy()
PROXY_ERROR:407 Proxy Authentication Required ( The ISA Server
requires authorization to fulfill the request. Access to the Web Proxy
filter is denied. )
There is a work around. So if you want to use SharedShell, you have to use NTLM, but can't use the work around, drop me a mail or add a comment to the page on SharedShell as support for the case for this to get addressed.
On a related SharedShell subject, Matthew Cheek of the University of Pittsburgh Medical Center found my posting on /proc scalability and dropped me a mail asking if I could use SharedShell to look at a scalability problem on a T2000 which fitted the pattern described in the blog. The 1st order root actually cause turned out to be 2 disk LUN's being saturated. The analysis included a 45 minute DTrace demo on a real problem to a cube full of people (I am told) from 3,000 odd miles, so took a bit longer than it usually does to find 2 disk which are 100% busy. Matthew has asked for some more local help from our P.S. organization in the US to do a wider sweep of a in-house application and getting it to run well on T2000, but it does show the combined power of Google, blogs, SharedShell and having an hour spare in the evening to set things off in the right direction.
|
|
|
|
