
- Post History
- Subscribe to RSS Feed
- Mark as New
- Mark as Read
- Bookmark
- Subscribe
- Printer Friendly Page
- Report Inappropriate Content
on 09-01-2015 05:51 AM
Our system logs were being overrun with SOAP call related records. Here is an example below:
<?xml version="1.0" encoding="UTF-8"?><SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"><SOAP-ENV:Body><insert xmlns="http://www.service-now.com"><name>glide.ldap.listener-5f627dab6fac0a00ddd82fa0be3ee4f1</name><type>info</type><value>Listening for changes...</value></insert></SOAP-ENV:Body></SOAP-ENV:Envelope>
After setting the property glide.processor.debug.SOAPProcessor with a value of false. See SOAP Web Service - ServiceNow Wiki for more details related to this property.
Thanks to Akash Mehta for the insight.
Mike Cole
ServiceNow Specialist
Smart Solutions