BUG HTTP monitoring : double service notification

[mdutoo]

When calling once a monitored service (using the Service Scaffolder), we can see in the esperProxy logs that 2 notifications are sent to EasySOA Core Registry, and the same for the total call count displayed in the Registry (except maybe the first time ?).

[mkalam-alami]

This bug has been around for a while indeed. Not sure yet why this happens, since the scaffolder proxy is included in the service scraper ignore list.

[mdutoo]

esperProxy logs :

INFO [RestNotificationRequestImpl] OK: url= http://localhost:8080/nuxeo/site/easysoa/notification/service, body: contentTypeOut=&relatedUsers=&contentTypeIn=&title=services/fibonacci-ws&httpMethod=GET&description=/services/fibonacci-ws&discoveryTypeMonitoring=localhost&parentUrl=http://frascati.elasticbeanstalk.com/services&callcount=1&url=http://frascati.elasticbeanstalk.com/services/fibonacci-ws&fileUrl=null& INFO [RestNotificationRequestImpl] OK: url= http://localhost:8080/nuxeo/site/easysoa/notification/service, body: contentTypeOut=&relatedUsers=&contentTypeIn=&title=services/fibonacci-ws&httpMethod=GET&description=/services/fibonacci-ws&discoveryTypeMonitoring=localhost&parentUrl=http://frascati.elasticbeanstalk.com/services&callcount=1&url=http://frascati.elasticbeanstalk.com/services/fibonacci-ws&fileUrl=null& INFO [RestNotificationRequestImpl] OK: url= http://localhost:8080/nuxeo/site/easysoa/notification/service, body: contentTypeOut=&relatedUsers=&contentTypeIn=&title=services/fibonacci-ws&httpMethod=POST&description=/services/fibonacci-ws&discoveryTypeMonitoring=localhost&parentUrl=http://frascati.elasticbeanstalk.com/services&callcount=1&url=http://frascati.elasticbeanstalk.com/services/fibonacci-ws&fileUrl=http://frascati.elasticbeanstalk.com/services/fibonacci-ws?wsdl& INFO [RestNotificationRequestImpl] OK: url= http://localhost:8080/nuxeo/site/easysoa/notification/service, body: contentTypeOut=&relatedUsers=&contentTypeIn=&title=services/fibonacci-ws&httpMethod=POST&description=/services/fibonacci-ws&discoveryTypeMonitoring=localhost&parentUrl=http://frascati.elasticbeanstalk.com/services&callcount=1&url=http://frascati.elasticbeanstalk.com/services/fibonacci-ws&fileUrl=http://frascati.elasticbeanstalk.com/services/fibonacci-ws?wsdl&

[mdutoo]

My take on it : all GET calls with fileUrl=null are SOAPUI libs within the Service Scaffolder / REST to SOAP proxy that are getting the wsdl of the service about to be called.