-
Type:
Bug
-
Status: Resolved
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: 2.0.7
-
Fix Version/s: 2.0.8
-
Component/s: None
-
Labels:None
First, flush method initializes WriteFuture with a null reference.
The object can be constructed later, if buffers queue isn't empty, but otherwise remains untouched.
If it still holds a null reference, the DefaultWriteRequest constructor call always fails, as it doesn't accept null as a message param.
Excerpt from the stack trace:
Caused by: java.lang.IllegalArgumentException: message at org.apache.mina.core.write.DefaultWriteRequest.<init>(DefaultWriteRequest.java:133) at org.apache.mina.filter.codec.ProtocolCodecFilter$ProtocolEncoderOutputImpl.flush(ProtocolCodecFilter.java:448) at com.ugcs.messaging.mina.MinaEncoder.encode(MinaEncoder.java:27) at org.apache.mina.filter.codec.ProtocolCodecFilter.filterWrite(ProtocolCodecFilter.java:308) ... 33 more
- is duplicated by
-
DIRMINA-970 ProtocolEncoderOutputImpl.flush() occur a IllegalArgumentException
-
- Resolved
-
-
DIRMINA-973 IllegalArgumentException thrown on ProtocolCodecFilter.flush
-
- Resolved
-