First message published to a topic after ADM/AEM startup does not get decoded/encoded

[usdot-jpo-ode]

First message published to a topic after ADM/AEM startup does not get decoded/encoded

[jmcarter9t]

Are you able to attached the message that was sent to cause this error? I know it is something other than the message, but just wanted to make sure I can replicate with the message.

[mvs5465]

So it happens with all messages and types, but this is a sample distress message (TIM) log file that goes to the decoder:
dnMsg_1506986050_2001_3A470_3A41af_3A1_3A226_3Aadff_3Afe05_3A13f1.csv.txt

And here is the XML of a TIM that gets sent to the encoder:

<OdeAsn1Data><metadata><payloadType>us.dot.its.jpo.ode.model.OdeTimPayload</payloadType><serialId><streamId>38be72fb-5eb2-4f72-b227-b4085bd4a2ec</streamId><bundleSize>1</bundleSize><bundleId>0</bundleId><recordId>0</recordId><serialNumber>0</serialNumber></serialId><odeReceivedAt>2018-02-09T18:10:13.751Z[UTC]</odeReceivedAt><schemaVersion>4</schemaVersion><sanitized>false</sanitized><request><ode><version>2</version><index>54</index><verb>0</verb></ode><rsus><rsuTarget>127.0.0.1</rsuTarget><rsuUsername>v3user</rsuUsername><rsuPassword>fakePassword</rsuPassword><rsuRetries>2</rsuRetries><rsuTimeout>5000</rsuTimeout></rsus><snmp><rsuid>00000083</rsuid><msgid>31</msgid><mode>1</mode><channel>178</channel><interval>2</interval><deliverystart>2017-06-01T17:47:11-05:00</deliverystart><deliverystop>2018-02-02T17:47:11-05:15</deliverystop><enable>1</enable><status>4</status></snmp></request><encodings><encodings><elementName>MessageFrame</elementName><elementType>MessageFrame</elementType><encodingRule>UPER</encodingRule></encodings></encodings></metadata><payload><dataType>MessageFrame</dataType><data><MessageFrame><messageId>31</messageId><value><TravelerInformation><msgCnt>2</msgCnt><timeStamp>309505</timeStamp><packetID>EC9C236B0000000000</packetID><urlB>null</urlB><dataFrames><TravelerDataFrame><sspTimRights>0</sspTimRights><frameType><advisory></advisory></frameType><msgId><roadSignID><position><lat>416784730</lat><long>-1087827750</long><elevation>9171</elevation></position><viewAngle>1010101010101010</viewAngle><mutcdCode><warning></warning></mutcdCode><crc>0000</crc></roadSignID></msgId><startYear>2017</startYear><startTime>308065</startTime><duratonTime>1</duratonTime><priority>0</priority><sspLocationRights>3</sspLocationRights><regions><GeographicalPath><name>Testing TIM</name><id><region>0</region><id>33</id></id><anchor><lat>412500807</lat><long>-1110093847</long><elevation>20206</elevation></anchor><laneWidth>700</laneWidth><directionality><both></both></directionality><closedPath><false /></closedPath><direction>0000000000001010</direction><description><path><scale>0</scale><offset><ll><nodes><NodeLL><delta><node-LL3><lon>31024</lon><lat>14506</lat></node-LL3></delta></NodeLL><NodeLL><delta><node-LL3><lon>30974</lon><lat>14568</lat></node-LL3></delta></NodeLL><NodeLL><delta><node-LL3><lon>30983</lon><lat>14559</lat></node-LL3></delta></NodeLL><NodeLL><delta><node-LL3><lon>30980</lon><lat>14563</lat></node-LL3></delta></NodeLL><NodeLL><delta><node-LL3><lon>30982</lon><lat>14562</lat></node-LL3></delta></NodeLL></nodes></ll></offset></path></description></GeographicalPath></regions><sspMsgRights1>2</sspMsgRights1><sspMsgRights2>3</sspMsgRights2><content><advisory><SEQUENCE><item><itis>513</itis></item></SEQUENCE></advisory></content><url>null</url></TravelerDataFrame></dataFrames></TravelerInformation></value></MessageFrame></data></payload></OdeAsn1Data>

[aferber]

@mvs5465 I tested the latest build (and latest dependencies) but could not reproduce this using my kafka-docker setup. I don't having a working ODE build at the moment; do you think that would help with reproducibility?

[mvs5465]

A solution has been found and merged in PR #13.