Unfortunately, I haven't seen this in the past and haven't used the Cleo integration software.
Just from a troubleshooting perspective, though, I'd recommend testing using some simple scripts and determining whether the transmission number is returned and whether the integration is posted to the tables you mentioned in OTM. Here's some posted earlier to the forums:
http://www.otmfaq.com/forums/f24/scr...ervlet-pl-213/ ([SCRIPT] Testing Integration - mw-OtmPostWMServlet.pl)
Assuming they work, I'd believe the issue is either within the Cleo software, or an incompatibility between the two. The latter would be odd, however, as it's simply an HTTP post with an ack -- not much can go wrong there.
Now, playing devil's advocate and looking at this from the OTM side, the OTM web server is going to accept the integration, do some initial verification (just XML syntax), then pass it back to the OTM app server. The app server immediately persists it to the DB and then (when a thread is available) reads it back and processes it. If the web and app servers were out-of-sync, this may cause an issue similar to what you described. Have you restarted OTM since beginning testing? Just for normal sanity testing - are the OTM web and app tiers on the same platform and JDK? Are they also at the same patch level? I'm sure these last questions are all okay, but I have to ask anyways.
--Chris
Linear Mode
