Ibm mobilefirst Worklight应用程序：身份验证后对服务器的大量请求

我正在为MY应用程序使用基于Worklight适配器的身份验证。服务器成功响应货物通过身份验证测试后，应用程序开始反复向服务器发送请求

来自服务器的日志显示，该用户在循环中登录和注销

{
    "message": "invoke logout request [project ProjectName]",
    "sourceClass": "com.worklight.integration.js.JavaScriptIntegrationLibraryImplementation",
    "sourceMethodName": "info",
    "level": "INFO",
    "source": "server",
    "threadId": 19,
    "loggerName": "com.worklight.integration.js.JavaScriptIntegrationLibraryImplementation",
    "server": {
      "ip": "--"
    },
    "timestamp": "---"
  }
  {
    "message": "Setting active user [project ProjectName]",
    "sourceClass": "com.worklight.integration.js.JavaScriptIntegrationLibraryImplementation",
    "sourceMethodName": "info",
    "level": "INFO",
    "source": "server",
    "threadId": 19,
    "loggerName": "com.worklight.integration.js.JavaScriptIntegrationLibraryImplementation",
    "server": {
      "ip": "--"
    },
    "timestamp": "---"
  }
  {
    "message": "invoke logout request [project ProjectName]",
    "sourceClass": "com.worklight.integration.js.JavaScriptIntegrationLibraryImplementation",
    "sourceMethodName": "info",
    "level": "INFO",
    "source": "server",
    "threadId": 21,
    "loggerName": "com.worklight.integration.js.JavaScriptIntegrationLibraryImplementation",
    "server": {
      "ip": "--"
    },
    "timestamp": "---"
  }
  {
    "message": "Setting active user [project ProjectName]",
    "sourceClass": "com.worklight.integration.js.JavaScriptIntegrationLibraryImplementation",
    "sourceMethodName": "info",
    "level": "INFO",
    "source": "server",
    "threadId": 21,
    "loggerName": "com.worklight.integration.js.JavaScriptIntegrationLibraryImplementation",
    "server": {
      "ip": "--"
    },
    "timestamp": "---"
  }

源代码的此更改有助于避免此活动。（删除challengeHandler.submitSuccess（）调用）

但通过这种方式，不会调用来自challendeHandler.submitAdapterAuthentication和WL.Client.logout的回调函数

所有活动都显示在日志包中

---

请帮我解决这个问题

在提交用户凭据之前调用Wl.Client.login（“realmname”）对我有帮助

您是否查看过任何现有的身份验证示例，并将其与您的进行了比较？我们需要从您的应用程序中获取更多代码，以查看它发生在哪里。