I'm receiving StringIndexOutOfBoundsException when I do msg.encodeInit, I can debug/see the code because UPA API is obfuscated.
// init message int ret = msg.encodeInit(encodeIter, 0);
java.lang.StringIndexOutOfBoundsException: String index out of range: 4 at java.lang.StringLatin1.charAt(StringLatin1.java:44) ~[?:?] at java.lang.String.charAt(String.java:704) ~[?:?] at com.thomsonreuters.upa.codec.R.A(Unknown Source) ~[upa-7.4.0.jar:upaj7.4.F9] at com.thomsonreuters.upa.codec.K.B(Unknown Source) ~[upa-7.4.0.jar:upaj7.4.F9] at com.thomsonreuters.upa.codec.K.A(Unknown Source) ~[upa-7.4.0.jar:upaj7.4.F9] at com.thomsonreuters.upa.codec.K.A(Unknown Source) ~[upa-7.4.0.jar:upaj7.4.F9] at com.thomsonreuters.upa.codec.K.A(Unknown Source) ~[upa-7.4.0.jar:upaj7.4.F9] at com.thomsonreuters.upa.codec.K.B(Unknown Source) ~[upa-7.4.0.jar:upaj7.4.F9] at com.thomsonreuters.upa.codec.K.A(Unknown Source) ~[upa-7.4.0.jar:upaj7.4.F9] at com.thomsonreuters.upa.codec.u.encodeInit(Unknown Source) ~[upa-7.4.0.jar:upaj7.4.F9]
Does channel.getBuffer(size, packedBuffer, error) returns a new instance of TransportBuffer or if it recycles an existing instance?
if it recycles, - and we have the exception above in msg.encodeInit, where the TransportBuffer has been assigned to the EncodeIterator >> is the TransportBuffer impacted? Should we "clean" it?