简体   繁体   English

Opendaylight:其余的每次调用一次,重发401错误

[英]Opendaylight : One of the rest calls out of many returing 401 error everytime

I am making rest calls to opendaylight. 我正在打电话给opendaylight。 Suppose i make 15 calls simultaneously using a for loop(each call is handeled by a seperate thread), then one or two of them always result in 401 status code. 假设我使用for循环同时进行15个调用(每个调用由一个单独的线程处理),那么其中一个或两个总是导致401状态代码。

I dont want that to happen. 我不希望那样发生。 Please help me on this. 请帮我。

This sounds like a bug. 这听起来像个错误。 ODL is an opensource project with an active community and you will get a better response there than on stackoverflow. ODL是一个拥有活跃社区的开源项目,与堆栈溢出相比,您会得到更好的响应。

I suggest that you retry using the helium release http://www.opendaylight.org/software and report it on https://bugs.opendaylight.org/ in the controller project. 我建议您重试使用氦气版本http://www.opendaylight.org/software,并在控制器项目中的https://bugs.opendaylight.org/上进行报告。 You will need to register. 您将需要注册。

There is not enough information here to investigate so when you write the bug report please provide: 这里没有足够的信息来调查,因此在编写错误报告时,请提供:

  • Software build used: Needed for quick turn-around of 'probably fixed' issues 使用的软件版本:快速解决“可能已解决”的问题
  • Environment used: To diagnose potential environment problems: 使用的环境:诊断潜在的环境问题:
  • Any customization outside of project-wide baseline To understand deviations, helps prioritizing 'currently unsupported' issues 超出项目范围基准的任何自定义项要了解偏差,有助于确定“当前不受支持”的问题的优先级
  • Description of steps taken: Needed for reproduction, helps finding 'you are doing it wrong' issues, here you need to describe the API call used 步骤描述:需要复制,有助于发现“您做错了”问题,在这里您需要描述所使用的API调用
  • Description of expected result: Eg what the reporter thinks should happen, helps finding 'not-a-bug' and architecture/design issues 预期结果的描述:例如,记者认为应该发生的事情,有助于发现“非错误”和架构/设计问题
  • Description of actual result: Eg what actually happened 实际结果描述:例如实际发生了什么
  • Reasonable amount of logs 合理数量的日志

声明:本站的技术帖子网页,遵循CC BY-SA 4.0协议,如果您需要转载,请注明本站网址或者原文地址。任何问题请咨询:yoyou2525@163.com.

 
粤ICP备18138465号  © 2020-2024 STACKOOM.COM