Data upload to Business Services Console fails intermittently

Products

• VMware Usage Meter

Issue/Introduction

• Usage Meter fails intermittently with notification and upload errors.
  
  
• A connection test from VCF Usage Meter to Business Services Connsole works fine.
  
  
• The /var/log/vmware-um-platform/dss_main.log file reports failure to upload files:
  
  ERROR --- [TaskScheduler-10] c.v.um.dss.uploader.UploaderService : Upload failure for UM_Collection stream. Authentication flow returned an error
ERROR --- [TaskScheduler-10] c.v.um.dss.uploader.UploaderService : Upload failure for Collection stream. Authentication flow returned an error.
ERROR --- [TaskScheduler-10] c.v.um.dss.uploader.UploaderService : Upload failure for Notification stream. Authentication flow returned an error.
  
  

• In the /var/log/vmware-um-platform/dss_error.log file on the Usage Meter appliance, an intermittent connection error through the proxy was observed.

  INFO --- [TaskScheduler-6] c.v.u.d.u.ConnectivityTesterService : Using configured proxy for communication between the appliance and the VCF Business Service console: type: http, host: ###.###.###.###, port: ####, user: null, pass: <PASSED>
  INFO --- [TaskScheduler-6] c.v.u.d.h.CloudAuthenticatorService : VCF access token expire, requesting new.
  WARN --- [TaskScheduler-6] c.v.um.common.http.LoggingInterceptor : POST /vcf/generateToken failed with Unexpected response code for CONNECT: 500
  java.io.IOException: Unexpected response code for CONNECT: 500

Environment

• VCF Usage meter 9.x
  
  
• Usage Meter connects Internet through a proxy server.

Cause

The error code may vary depending on the environment. In this example, CONNECT:500 indicates that the client sent an HTTP CONNECT request to the proxy server, and the proxy returned a 500 Internal Server Error. This occurs when the proxy server encounters an unexpected condition that prevents it from establishing the requested tunnel to the destination server.

Resolution

Verify the proxy server connection status and review the proxy server logs for related error entries.