powered by Jive Software

Message received by a client only after sending a second dummy message

Hi,

We are using OpenFire 3.6.3 server and we have used Smack API 3.1 to develop the client.

Once client application sends the following message (570 bytes):

PZFp8ChRWw7X0elmcOd5AozlWtdiounU9mOzc/9R+0GIsSTzRF4vwObrIreeh1AeZeIKKZ1tvGoM
MMGG7TFX/7sVbqZrAwSlxP0spsJTUhrnzysGJ598akrQJ4tPHN5wqomb2Kz+eIK13fdDfKEatHFG
xZmjfqCobhwd8HVsRqr4iW6uwKC3vXK1hN2rBSMYqaKOak5O3nEVnNW8JWKoPS62wc04gD0u3Qdf
R6AvCjqPjcqrEpJjn8GmIfqgX+wwfQ/J2RD3nqhyNIy89WkV849+n+5tHAwp6SW/KGpJ4Ga4x4Kd
jXtmKZdTggMyB6i83RQjOn+zYVpb4f++41JAApZotigArDvha4Lzb7M6QfNWo+5Glzc7AuRSITye
+NcAKsAs2MtJsk/Fjf26rQF97ZNEtcS1v38bf3u9nMAb9pFaqFYLInnOxmeINoORpk/3VqFgWvXI
jvsvawbIAqWSJ/g6CuXgo264xGhnpDXu9WPNWR1/N7P0+QqtlnG3uS4azSqcnWnShA+dKpQWhr0s
14qIbUugPC1d1AlikptbACw=

But it never reaches the other client. Other messages which are 812 and 484 bytes long respectively (created just by changing a few parts in the original message) reach the other client successfully:

PZFp8ChRWw7X0elmcOd5AozlWtdiounU9mOzc/9R+0GIsSTzRF4vwObrIreeh1AeZeIKKZ1tvGoM
MMGG7TFX/7sVbqZrAwSlxP0spsJTUhrnzysGJ598akrQJ4tPHN5wqomb2Kz+eIK13fdDfKEatHFG
xZmjfqCobhwd8HVsRqr4iW6uwKC3vXK1hN2rBSMYqaKOak5O3nEVnNW8JWKoPS62wc04gD0u3Qdf
R6AvCjqPjcqrEpJjn8GmIfqgX+wwfQ/J2RD3nqhyNIy89WkV849+n+5tHAwp6SW/KGpJ4Ga4x4Kd
jXtmKZdTggMyB6i83RQjOn+zYVpb4f++41JAApZotigArDvha4Lzb7M6QfNWo+5Glzc7AuRSITye
+NcALp4Y9kO4jfA3RdSG7ZHQCj7XkwhZNdJXSyTGQP3HqBxzb7Z43Rcb//FTYJfJZorJY3Ow0Wpz
2Mwu1L0aIZREzMNtJW9v40+6qpqUL6JAvBipSZ+acvusaHHQxyW7J8EvtLyZCuHGCU/LfiAKdUtl
6tmQhMcWHVj4pjs0di6T3bwAelh6KZ3hzUsqb/ZDN3oMi3pEZwPuCHQWjC5szn5EnyEWcDnGw8z+
Xwsv4dxpstHOdzavK2H4xUleZ1LynVt7bP0LE/NRSpVsn0j9H+4dFBkAr4jHA5HqcvTQ6NOuniit
qIs0jJRzgUR682KOfGpB45lX9f578oD6nCjV2IdTzm7J3LeGuBo3ROWbWljbNW9gIr3hmnXriBQf
Wm2QKPcLv5/DqQkDQJf4O0ePgZ3ZKA==

And…

PZFp8ChRWw7X0elmcOd5AozlWtdiounU9mOzc/9R+0GIsSTzRF4vwObrIreeh1AeZeIKKZ1tvGoM
MMGG7TFX/7sVbqZrAwSlxP0spsJTUhrnzysGJ598akrQJ4tPHN5wqomb2Kz+eIK13fdDfKEatHFG
xZmjfqCobhwd8HVsRqr4iW6uwKC3vXK1hN2rBSMYqaKOak5O3nEVnNW8JWKoPS62wc04gD0u3Qdf
R6AvCjqPjcqrEpJjn8GmIfqgX+wwfQ/J2RD3nqhyNIy89WkV849+n+5tHAwp6SW/KGpJ4Ga4x4Kd
jXtmKZdTggMyB6i83RQjOn+zYVpb4f++41JAApZotigArDvha4Lzb7M6QfNWo+5Glzc7AuRSITye
+NcAYCK94Zp164gUH1ptkCj3C0CFQ4fIVELSU4sZ0xmqHhj0sOQWmMUuW7ktKulMKxFz90EJyLRw
wNQURze3dbUFsQ==

If in the original message, we just change a small thing by which the size of the message does not change and remains the same (570 bytes), it again gets delivered to the other client successfully. Following message despite having the same length gets delivered:

PZFp8ChRWw7X0elmcOd5AozlWtdiounU9mOzc/9R+0GIsSTzRF4vwObrIreeh1AeZeIKKZ1tvGoM
MMGG7TFX/7sVbqZrAwSlxP0spsJTUhrnzysGJ598akrQJ4tPHN5wqomb2Kz+eIK13fdDfKEatHFG
xZmjfqCobhwd8HVsRqr4iW6uwKC3vXK1hN2rBSMYqaKOak5O3nEVnNW8JWKoPS62wc04gD0u3Qdf
R6AvCjqPjcqrEpJjn8GmIfqgX+wwfQ/J2RD3nqhyNIy89WkV849+n+5tHAwp6SW/KGpJ4Ga4x4Kd
jXtmKZdTggMyB6i83RQjOn+zYVpb4f++41JAApZotigArDvha4Lzb7M6QfNWo+5Glzc7AuRSITye
+NcAKsAs2MtJsk/Fjf26rQF97ZNEtcS1v38bf3u9nMAb9pFaqFYLInnOxmeINoORpk/3VqFgWvXI
jvsvawbIAqWSJ/g6CuXgo264xGhnpDXu9WPNWR1/N7P0+QqtlnG3uS4af6gni//UUmrICzelSzcc
/10hNUus94XlG3j4ibEAPaU=

Another strange thing is, if just a small second message is sent (e.g. “Hi”) from the first client to the second client after sending the first message, then both the messages are received by the second client immediately after this small ‘Hi’ message.

Has any one faced such a problem? Is there any way out of this?

Our application does not seem to have any problem. We just created a small application that just connects to the OpenFire server using Smack API and sends this message without our application’s business logic and it still works the same way as our application. Could there by any configuration issue in OpenFire server? OR problem with Smack API?

Thanks in advance.

Regards,
Ishan.