Forum Discussion
Aug 30, 2007
Another reason for an exception, as you pointed out, very well could be corrupted client data. I've heard of issues when ASP apps are using keep-alive connections (re-using HTTP connections). If you are using the iControl assembly, that reuses proxy class instances, this could be your problem. A quick and easy way to enable iControl logging on the BIG-IP might be your best bet in diagnosing this. Here's the steps
1. Edit your /etc/syslog-ng/syslog-ng.conf file on your BIG-IP and make sure that the local4 settings are as follows:
local4.* /var/log/ltm
filter f_local4 {
facility(local4) and level(debug..emerg);
};
2. Set the database key for iControl tracing
$ b db iControl.LogLevel trace
3. Restart the httpd server
$ bigstart restart httpd
Now you'll be getting a bunch of data in the /var/log/ltm file including the first 2k of the XML payload along with the data after the server side has extracted it.
***Make sure you turn off the tracing when you are finished with your testing as it will dump a lot of data to the log file.
$ b db iControl.LogLevel none
$ bigstart restart httpd
Hope this helps and let me know what you find out...
-Joe