Findbugs错误总结

约定不等于承诺〃 2024-02-19 16:49 47阅读 0赞

原文链接:[https://blog.csdn.net/u012483116/article/details/72932214][https_blog.csdn.net_u012483116_article_details_72932214]

**本篇是从别人那找到的，为了让我回头查看findbugs错误怎么解决而保存的![微笑][smile.gif]**

**有很多问题其实挺隐晦的，比如第三条。还有人会使用==来判断常量字符串和String类型是否相等，这个就是基础不牢的缘故了。**

**记得把findbugs尽量清零哦。**

**1. NP\_NULL\_ON\_SOME\_PATH\_EXCEPTION**

**2. NP\_NULL\_ON\_SOME\_PATH**

**3. EC\_UNRELATED\_CLASS\_AND\_INTERFACE**

**4. UG\_SYNC\_SET\_UNSYNC\_GET**

**5. DLS\_DEAD\_LOCAL\_STORE**

**6. RCN\_REDUNDANT\_NULLCHECK\_WOULD\_HAVE\_BEEN\_A\_NPE**

**7. ES\_COMPARING\_STRINGS\_WITH\_EQ**

**8. NP\_NULL\_PARAM\_DEREF**

**9. UWF\_UNWRITTEN\_FIELD**

**10. NP\_TOSTRING\_COULD\_RETURN\_NULL**

**11. MF\_CLASS\_MASKS\_FIELD**

**12. NS\_DANGEROUS\_NON\_SHORT\_CIRCUIT**

**13. HE\_EQUALS\_USE\_HASHCODE**

**14. NP\_EQUALS\_SHOULD\_HANDLE\_NULL\_ARGUMENT**

**15. SE\_BAD\_FIELD**

<table> 
 <tbody> 
 <tr> 
 <td style="vertical-align:top;"> 类型 </td> 
 <td style="vertical-align:top;"> 必改项 </td> 
 </tr> 
 <tr> 
 <td style="vertical-align:top;"> 描述 </td> 
 <td style="vertical-align:top;"> This&nbsp; Serializable class defines a non-primitive instance field which is neither&nbsp; transient, Serializable, or<code>java.lang.Object</code>, and does not appear&nbsp; to implement the<code>Externalizable</code>&nbsp;interface or the<code>readObject()</code>&nbsp;and<code>writeObject()</code>&nbsp;methods.&nbsp; Objects of this class will not be deserialized&nbsp; correctly if a non-Serializable object is stored in this field. &nbsp; 序列化的类定义了一个非原生实例对象，这个对象是不可序列化的或非java对象，而且没有添加transient关键字，没有实现Externalizable接口或没有添加readObject()和writeObject()方法，那么这个类的对象将不能正确的反序列化。 &nbsp; </td> 
 </tr> 
 <tr> 
 <td style="vertical-align:top;"> 案例 </td> 
 <td style="vertical-align:top;"> 示例代码： publicclassMytest&nbsp;implements&nbsp;Serializable { &nbsp;&nbsp;&nbsp;&nbsp;private&nbsp;ThreadmThread; &nbsp;&nbsp;&nbsp;&nbsp;protected&nbsp;FileOutputStreamoutputStream&nbsp;; &nbsp;&nbsp;&nbsp;&nbsp;//这两个变量会提示defines&nbsp; non-transient non-serializable instance field finoutStream &nbsp;&nbsp;&nbsp;&nbsp;private&nbsp;Stringstr; &nbsp;&nbsp;&nbsp;&nbsp;private&nbsp;Stringstr1; &nbsp;&nbsp;&nbsp;&nbsp;privateinti; &nbsp; } &nbsp; </td> 
 </tr> 
 <tr> 
 <td style="vertical-align:top;"> 解决方法 </td> 
 <td style="vertical-align:top;"> 解决方法： 1：给对象加上transient关键字，对该象将不会被序列化保存和恢复。 publicclassMytest&nbsp;implements&nbsp;Serializable{ &nbsp;&nbsp;&nbsp;&nbsp;privatetransient&nbsp;ThreadmThread; &nbsp;&nbsp;&nbsp;&nbsp;protectedtransient&nbsp;FileOutputStreamoutputStream; &nbsp;&nbsp;&nbsp;&nbsp;private&nbsp;Stringstr; private&nbsp;Stringstr1; &nbsp;&nbsp;&nbsp;&nbsp;privateinti; } 2：实现Externalizable接口代替Serializable接口，对序列化过程进行完全自主控制。Externalizable没有默认序列化机制，我们需要在writeExternal()方法中将希望被序列化的对象的信息写入，在readExternal()中将其恢复，并且writeObject()方法与readObject()方法中保存和恢复对象的顺序必须相同。 publicclass&nbsp;Mytestimplements&nbsp;Externalizable{ &nbsp;&nbsp;&nbsp;&nbsp;private&nbsp;ThreadmThread; &nbsp;&nbsp;&nbsp;&nbsp;protected&nbsp;FileOutputStreamfoutputStream; &nbsp;&nbsp;&nbsp;&nbsp;private&nbsp;Stringstr; &nbsp;&nbsp;&nbsp;&nbsp;private&nbsp;Stringstr1; &nbsp;&nbsp;&nbsp;&nbsp;privateinti; &nbsp;&nbsp;&nbsp;&nbsp;@Override &nbsp;&nbsp;&nbsp;&nbsp;publicvoid&nbsp;readExternal(ObjectInput&nbsp; arg0)throws&nbsp;IOException, &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;ClassNotFoundException { &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;str=(String) arg0.readObject(); &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;str1=(String) arg0.readObject(); &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;i= arg0.readInt(); &nbsp;&nbsp;&nbsp;&nbsp;} &nbsp;&nbsp;&nbsp;&nbsp;@Override publicvoid&nbsp; writeExternal(ObjectOutput arg0)throws&nbsp;IOException{ &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;arg0.writeObject(str); &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;arg0.writeObject(str1); &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;arg0.writeInt(i); &nbsp;&nbsp;&nbsp;&nbsp;} } 3：添加writeObject()和readObject()方法替代Externalizable，对序列化过程进行自主控制。注意是“添加”不是“复写”或“实现”，类型必须为private，同样writeObject()方法与readObject()方法中保存和恢复对象的顺序必须相同。 publicclassMytest&nbsp;implements&nbsp;Serializable{ &nbsp;&nbsp;&nbsp;&nbsp;private&nbsp;ThreadmThread; &nbsp;&nbsp;&nbsp;&nbsp;protected&nbsp;FileOutputStreamfoutputStream; &nbsp;&nbsp;&nbsp;&nbsp;private&nbsp;Stringstr; &nbsp;&nbsp;&nbsp;&nbsp;private&nbsp;Stringstr1; &nbsp;&nbsp;&nbsp;&nbsp;privateinti; &nbsp;&nbsp;&nbsp;&nbsp;privatevoid&nbsp; writeObject(ObjectOutputStream outputStream)throws&nbsp;IOException { &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;outputStream.writeObject(str); &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;outputStream.writeObject(str1); &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;outputStream.writeInt(i); &nbsp;&nbsp;&nbsp;&nbsp;}&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;&nbsp;privatevoid&nbsp;readObject(ObjectInputStream&nbsp; inputStream)throws&nbsp;IOException,ClassNotFoundException { &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;str=(String) inputStream.readObject(); &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;str1=(String) inputStream.readObject(); &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;i= inputStream.readInt(); &nbsp;&nbsp;&nbsp;&nbsp;} } </td> 
 </tr> 
 </tbody> 
</table>

**16. NP\_UNWRITTEN\_FIELD**

**17. UWF\_NULL\_FIELD**

**18. IM\_BAD\_CHECK\_FOR\_ODD**

**19. NP\_NULL\_ON\_SOME\_PATH\_MIGHT\_BE\_INFEASIBLE**

**20. RV\_EXCEPTION\_NOT\_THROWN**

**21. DL\_SYNCHRONIZATION\_ON\_BOOLEAN**

**22. ES\_COMPARING\_PARAMETER\_STRING\_WITH\_EQ**

**23. JLM\_JSR166\_UTILCONCURRENT\_MONITORENTER**

**24. DL\_SYNCHRONIZATION\_ON\_SHARED\_CONSTANT**

**25. SP\_SPIN\_ON\_FIELD**

**26. RpC\_REPEATED\_CONDITIONAL\_TEST**

**27. NP\_GUARANTEED\_DEREF**

**28. UR\_UNINIT\_READ**

**29. NP\_NULL\_ON\_SOME\_PATH\_FROM\_RETURN\_VALUE**

**30. IL\_INFINITE\_RECURSIVE\_LOOP**

**31. IA\_AMBIGUOUS\_INVOCATION\_OF\_INHERITED\_OR\_**

**OUTER\_METHOD**

**32. IP\_PARAMETER\_IS\_DEAD\_BUT\_OVERWRITTEN**

**33. FE\_FLOATING\_POINT\_EQUALITY**

**34. NP\_ALWAYS\_NULL**

**35. DLS\_DEAD\_LOCAL\_STORE\_OF\_NULL**

**36. SF\_DEAD\_STORE\_DUE\_TO\_SWITCH\_FALLTHROUGH**

**37. INT\_BAD\_COMPARISON\_WITH\_SIGNED\_BYTE**

**38. NP\_DEREFERENCE\_OF\_READLINE\_VALUE**

**39. SA\_FIELD\_DOUBLE\_ASSIGNMENT**

**40. DMI\_INVOKING\_TOSTRING\_ON\_ARRAY**

**41. EC\_UNRELATED\_TYPES**

**42. BC\_IMPOSSIBLE\_CAST**

**43. ICAST\_INT\_CAST\_TO\_FLOAT\_PASSED\_TO\_ROUND**

**44. RV\_RETURN\_VALUE\_IGNORED**

**45. SF\_SWITCH\_FALLTHROUGH**

**46. DE\_MIGHT\_IGNORE**

**47. VA\_FORMAT\_STRING\_EXTRA\_ARGUMENTS\_PASSED**

<table> 
 <tbody> 
 <tr> 
 <td style="vertical-align:top;"> 类型 </td> 
 <td style="vertical-align:top;"> 比改项 </td> 
 </tr> 
 <tr> 
 <td style="vertical-align:top;"> 描述 </td> 
 <td style="vertical-align:top;"> A&nbsp; format-string method with a variable number of arguments is called, but more&nbsp; arguments are passed than are actually used by the format string. This won't&nbsp; cause a runtime exception, but the code may be silently omitting information&nbsp; that was intended to be included in the formatted string. &nbsp; 使用String的format方法时有非法的参数也经过了格式化操作。 </td> 
 </tr> 
 <tr> 
 <td style="vertical-align:top;"> 案例 </td> 
 <td style="vertical-align:top;"> 这个错误很简单，是使用String.format的时候出了问题，format里面的参数没有被全部用上。 看下面一段代码： &nbsp; public void test(){ &nbsp; &nbsp; &nbsp; String str1 = "123"; &nbsp; &nbsp; &nbsp; String str2 = "456"; &nbsp; &nbsp; &nbsp; String str3 = String.format("{0} {1}" , str1 ,str2); &nbsp; &nbsp; &nbsp; System.out.println(str3); &nbsp; } 输出的结果是：{0}&nbsp; {1} &nbsp;&nbsp; </td> 
 </tr> 
 <tr> 
 <td style="vertical-align:top;"> 解决方法 </td> 
 <td style="vertical-align:top;"> 这个Bug描述就是这种问题，str1和str2根本没有被用上！{0}{1}这种Format格式是.NET上面的用法，java里面应该是%s %s。 这个是一个代码逻辑问题，可能是你写代码时不小心导致的，它在这段代码里不会导致异常，但往往会很可能导致其他地方异常，那时候你可能会<a href="https://www.baidu.com/s?wd=%E7%99%BE%E6%80%9D%E4%B8%8D%E5%BE%97%E5%85%B6%E8%A7%A3&amp;tn=24004469_oem_dg&amp;rsv_dl=gh_pl_sl_csd" rel="nofollow">百思不得其解</a>。 &nbsp; </td> 
 </tr> 
 </tbody> 
</table>

**48. RE\_POSSIBLE\_UNINTENDED\_PATTERN**

**49. SE\_BAD\_FIELD\_INNER\_CLASS**

**50. RV\_01\_TO\_INT**

**51. UW\_UNCOND\_WAIT**

**52. UMAC\_UNCALLABLE\_METHOD\_OF\_ANONYMOUS\_CLASS**

**53. EQ\_SELF\_USE\_OBJECT**

**54. REC\_CATCH\_EXCEPTION**

**55. RU\_INVOKE\_RUN**

**56. NP\_SYNC\_AND\_NULL\_CHECK\_FIELD**

**57. DLS\_DEAD\_STORE\_OF\_CLASS\_LITERAL**

**58. INT\_BAD\_REM\_BY\_1**

**59. DLS\_DEAD\_LOCAL\_STORE\_SHADOWS\_FIELD**

**60. ST\_WRITE\_TO\_STATIC\_FROM\_INSTANCE\_METHOD**

**61. SWL\_SLEEP\_WITH\_LOCK\_HELD**

**62. LI\_LAZY\_INIT\_STATIC**

**63. NM\_SAME\_SIMPLE\_NAME\_AS\_SUPERCLASS**

**64. LI\_LAZY\_INIT\_UPDATE\_STATIC**

**65. GC\_UNRELATED\_TYPES**

<table> 
 <tbody> 
 <tr> 
 <td style="vertical-align:top;"> 类型 </td> 
 <td style="vertical-align:top;"> 选改项 </td> 
 </tr> 
 <tr> 
 <td style="vertical-align:top;"> 描述 </td> 
 <td style="vertical-align:top;"> This call to a generic collection method&nbsp; contains an argument with an incompatible class from that of the collection's&nbsp; parameter (i.e., the type of the argument is neither a supertype nor a&nbsp; subtype of the corresponding generic type argument). Therefore, it is&nbsp; unlikely that the collection contains any objects that are equal to the&nbsp; method argument used here. Most likely, the wrong value is being passed to&nbsp; the method. In general, instances of two unrelated&nbsp; classes are not equal. For example, if the Foo and Bar classes are not&nbsp; related by subtyping, then an instance of Foo should not be equal to an&nbsp; instance of Bar. Among other issues, doing so will likely result in an equals&nbsp; method that is not symmetrical. For example, if you define the Foo class so&nbsp; that a Foo can be equal to a String, your equals method isn't symmetrical&nbsp; since a String can only be equal to a String. In rare cases, people do define&nbsp; nonsymmetrical equals methods and still manage to make their code work.&nbsp; Although none of the APIs document or guarantee it, it is typically the case&nbsp; that if you check if a Collection&lt;String&gt; contains a Foo, the equals&nbsp; method of argument (e.g., the equals method of the Foo class) used to perform&nbsp; the equality checks. &nbsp; &nbsp; </td> 
 </tr> 
 <tr> 
 <td style="vertical-align:top;"> 案例 </td> 
 <td style="vertical-align:top;"> Foo&lt;A, B&gt;&nbsp; foo; &nbsp; foo.remove(a, Collections&lt;B&gt;.emptySet()); //This generated a false&nbsp; positive because it thinks that the second parameter should be of type B, not&nbsp; Set&lt;B&gt; &nbsp;&nbsp; &nbsp; class Foo&lt;X, Y&gt; extends Bar&lt;X, Set&lt;Y&gt;&gt;{ &nbsp; ... &nbsp; } &nbsp;&nbsp; &nbsp; class Bar&lt;T, S&gt; extends ConcurrentHashMap&lt;T, S&gt; { &nbsp; @Override &nbsp; public boolean remove(Object key, Object value) { &nbsp; ... &nbsp; } &nbsp; } </td> 
 </tr> 
 <tr> 
 <td style="vertical-align:top;"> 解决方法 </td> 
 <td style="vertical-align:top;"> &nbsp; &nbsp; </td> 
 </tr> 
 </tbody> 
</table>

**66. SC\_START\_IN\_CTOR**

**67. EQ\_ALWAYS\_FALSE**

<table> 
 <tbody> 
 <tr> 
 <td style="vertical-align:top;"> 类型 </td> 
 <td style="vertical-align:top;"> 选该项 </td> 
 </tr> 
 <tr> 
 <td style="vertical-align:top;"> 描述 </td> 
 <td style="vertical-align:top;"> This class defines an equals method that&nbsp; always returns false. This means that an object is not equal to itself, and&nbsp; it is impossible to create useful Maps or Sets of this class. More&nbsp; fundamentally, it means that equals is not reflexive, one of the requirements&nbsp; of the equals method. The likely intended semantics are object&nbsp; identity: that an object is equal to itself. This is the behavior inherited&nbsp; from class Object. If you need to override an equals inherited from a&nbsp; different superclass, you can use use: public boolean equals(Object o) { return&nbsp; this == o; } &nbsp; 使用equals方法返回值总是false </td> 
 </tr> 
 <tr> 
 <td style="vertical-align:top;"> 案例 </td> 
 <td style="vertical-align:top;"> &nbsp; </td> 
 </tr> 
 <tr> 
 <td style="vertical-align:top;"> 解决方法 </td> 
 <td style="vertical-align:top;"> &nbsp; &nbsp; </td> 
 </tr> 
 </tbody> 
</table>

**68. RC\_REF\_COMPARISON**

**69. IJU\_ASSERT\_METHOD\_INVOKED\_FROM\_RUN\_METHOD**

**70. STCAL\_INVOKE\_ON\_STATIC\_DATE\_FORMAT\_INSTANCE**

**71. STCAL\_STATIC\_SIMPLE\_DATE\_FORMAT\_INSTANCE**

**72. AT\_OPERATION\_SEQUENCE\_ON\_CONCURRENT\_ABSTR**

**ACTION**

**73. BC\_UNCONFIRMED\_CAST**

**74. RV\_ABSOLUTE\_VALUE\_OF\_RANDOM\_INT**

**75. NN\_NAKED\_NOTIFY**

<table> 
 <tbody> 
 <tr> 
 <td style="vertical-align:top;"> 类型 </td> 
 <td style="vertical-align:top;"> 选改项 </td> 
 </tr> 
 <tr> 
 <td style="vertical-align:top;"> 描述 </td> 
 <td style="vertical-align:top;"> A call to notify() or notifyAll() was made&nbsp; without any (apparent) accompanying modification to mutable object&nbsp; state.&nbsp; In general, calling a notify method on a monitor is done because&nbsp; some condition another thread is waiting for has become true.&nbsp; However,&nbsp; for the condition to be meaningful, it must involve a heap object that is&nbsp; visible to both threads. This bug does not necessarily indicate an&nbsp; error, since the change to mutable object state may have taken place in a&nbsp; method which then called the method containing the notification. &nbsp; 赤裸的通知 </td> 
 </tr> 
 <tr> 
 <td style="vertical-align:top;"> 案例 </td> 
 <td style="vertical-align:top;"> protectedvoid&nbsp;notifyExchange(<a href="http://servicemix.apache.org/dist/servicemix-3.2.1/site/parent/core/servicemix-core/xref/org/apache/servicemix/jbi/messaging/MessageExchangeImpl.html" rel="nofollow">MessageExchangeImpl</a>&nbsp;me, Object lock, String from) { <a rel="nofollow"></a>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;if&nbsp;(LOG.isDebugEnabled()) { &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; LOG.debug("Notifying exchange " + me.getExchangeId() +&nbsp; "(" + Integer.toHexString(me.hashCode()) + ") in " +this&nbsp;+ " from "+ from); <a rel="nofollow"></a>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; } <a rel="nofollow"></a>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&amp;nb&nbsp; sp;&nbsp;synchronized&nbsp;(lock) { <a rel="nofollow"></a>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;lock.notify(); <a rel="nofollow"></a>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; } &nbsp;&nbsp;&nbsp;&nbsp; } </td> 
 </tr> 
 <tr> 
 <td style="vertical-align:top;"> 解决方法 </td> 
 <td style="vertical-align:top;"> &nbsp; &nbsp; </td> 
 </tr> 
 </tbody> 
</table>

**76. BC\_IMPOSSIBLE\_INSTANCEOF**

**77. DMI\_RANDOM\_USED\_ONLY\_ONCE**

**78. NP\_GUARANTEED\_DEREF\_ON\_EXCEPTION\_PATH**

<table style="width:615px;"> 
 <tbody> 
 <tr> 
 <td style="vertical-align:top;"> 类型 </td> 
 <td style="vertical-align:top;"> 选改项 </td> 
 </tr> 
 <tr> 
 <td style="vertical-align:top;"> 描述 </td> 
 <td style="vertical-align:top;"> There&nbsp; is a statement or branch on an exception path that if executed guarantees&nbsp; that a value is null at this point, and that value that is guaranteed to be&nbsp; dereferenced (except on forward paths involving runtime exceptions). &nbsp; &nbsp; </td> 
 </tr> 
 <tr> 
 <td style="vertical-align:top;"> 案例 </td> 
 <td style="vertical-align:top;"> &nbsp; </td> 
 </tr> 
 <tr> 
 <td style="vertical-align:top;"> 解决方法 </td> 
 <td style="vertical-align:top;"> &nbsp; &nbsp; </td> 
 </tr> 
 </tbody> 
</table>

**79. WA\_NOT\_IN\_LOOP**

<table> 
 <tbody> 
 <tr> 
 <td style="vertical-align:top;"> 类型 </td> 
 <td style="vertical-align:top;"> 选改项 </td> 
 </tr> 
 <tr> 
 <td style="vertical-align:top;"> 描述 </td> 
 <td style="vertical-align:top;"> This method contains a call to java.lang.Object.wait()&nbsp; which is not in a loop.&nbsp; If the monitor is used for multiple conditions,&nbsp; the condition the caller intended to wait for might not be the one that&nbsp; actually occurred. &nbsp; 这种方法包含调用java.lang.Object.wait（），而这并不是一个循环。如果<a href="https://www.baidu.com/s?wd=%E7%9B%91%E8%A7%86%E5%99%A8&amp;tn=24004469_oem_dg&amp;rsv_dl=gh_pl_sl_csd" rel="nofollow">监视器</a>用于多个条件，打算调用wait()方法的条件可能不是实际发生的。 &nbsp; </td> 
 </tr> 
 <tr> 
 <td style="vertical-align:top;"> 案例 </td> 
 <td style="vertical-align:top;"> protectedvoid&nbsp;waitForExchange(MessageExchangeImpl&nbsp;me, Object&nbsp; lock,long&nbsp;timeout, String from)throws&nbsp;InterruptedException { &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;// If the channel is closed while here, we must abort &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;if&nbsp;(LOG.isDebugEnabled()) { &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;LOG.debug("Waiting for exchange "&nbsp;+ me.getExchangeId() +" ("&nbsp;+&nbsp; Integer.toHexString(me.hashCode()) +") to be answered in " &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;+&nbsp;this&nbsp;+&nbsp;" from "&nbsp;+ from); &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;} &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Thread th = Thread.currentThread(); &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;try&nbsp;{ &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;waiters.put(th,&nbsp; Boolean.TRUE); &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;lock.wait(timeout); &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;}&nbsp;finally&nbsp;{ &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;waiters.remove(th); &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;} &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;if&nbsp;(LOG.isDebugEnabled()) { &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;LOG.debug("Notified: "&nbsp;+ me.getExchangeId() +"("&nbsp;+ Integer.toHexString(me.hashCode()) +") in "&nbsp;+&nbsp;this&nbsp;+" from "&nbsp;+ from); &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;} &nbsp;&nbsp;&nbsp;&nbsp;} </td> 
 </tr> 
 <tr> 
 <td style="vertical-align:top;"> 解决方法 </td> 
 <td style="vertical-align:top;"> &nbsp; &nbsp; </td> 
 </tr> 
 </tbody> 
</table>

**整理的行业规则：**

**80. OBL\_UNSATISFIED\_OBLIGATION**

**81. IC\_SUPERCLASS\_USES\_SUBCLASS\_DURING\_INITIALIZATION**

**82. IMSE\_DONT\_CATCH\_IMSE**

**83. IL\_INFINITE\_LOOP**

**84. NP\_CLOSING\_NULL**

**85. NP\_NONNULL\_PARAM\_VIOLATION**

**86. NP\_NONNULL\_RETURN\_VIOLATION**

**87. NP\_NULL\_PARAM\_DEREF\_ALL\_TARGETS\_DANGEROUS**

**88. NM\_BAD\_EQUAL**

**89. SA\_LOCAL\_SELF\_COMPUTATION**

**90. UR\_UNINIT\_READ\_CALLED\_FROM\_SUPER\_CONSTRUCTOR**

**91. DMI\_INVOKING\_TOSTRING\_ON\_ANONYMOUS\_ARRAY**

**92. UWF\_UNWRITTEN\_FIELD**

**93. DM\_STRING\_VOID\_CTOR**

**94. SBSC\_USE\_STRINGBUFFER\_CONCATENATION**

**95. BC\_BAD\_CAST\_TO\_CONCRETE\_COLLECTION**

**96. DLS\_DEAD\_LOCAL\_STORE**

**97. NS\_NON\_SHORT\_CIRCUIT**

**98. RCN\_REDUNDANT\_NULLCHECK\_OF\_NONNULL\_VALUE**

**99. RI\_REDUNDANT\_INTERFACES**

**100. SA\_LOCAL\_DOUBLE\_ASSIGNMENT**

**101. SA\_LOCAL\_SELF\_ASSIGNMENT**

**102. SF\_SWITCH\_NO\_DEFAULT**

**103. UCF\_USELESS\_CONTROL\_FLOW**

**104. UCF\_USELESS\_CONTROL\_FLOW\_NEXT\_LINE**

**105. NP\_BOOLEAN\_RETURN\_NULL**

**106. SI\_INSTANCE\_BEFORE\_FINALS\_ASSIGNED**

**107. VA\_FORMAT\_STRING\_BAD\_ARGUMENT**

**108. MF\_METHOD\_MASKS\_FIELD**

**109. NP\_ARGUMENT\_MIGHT\_BE\_NULL**

**110. MWN\_MISMATCHED\_NOTIFY**

**111. MWN\_MISMATCHED\_WAIT**

**112. UL\_UNRELEASED\_LOCK**

[https_blog.csdn.net_u012483116_article_details_72932214]: https://blog.csdn.net/u012483116/article/details/72932214
[smile.gif]: https://image.dandelioncloud.cn/pgy_files/images/2024/01/29/2d346a6e1cf84e799107390ddeff2617.png