wojciech.kapcia@tigase.net opened 5 years ago
|
|
@bmalkow after second look (especially at the removed part) it seems that the packet was not processed by |
|
@andrzej.wojcik given that similar issue was reported by client I took a look and it seems (judging by the presence of I think, that we should
At any rate - currently the Warning can be ignored it seems. Comments? |
|
@andrzej.wojcik can you take a look at my previous comment as this issue started to happen more and more recently. |
|
OK, let's start with the fact that this is a message sent from MAM archive (MAM component) to the client upon clients request. Those messages should not be stored in MAM nor in offline storage. Why message had no XMLNS? I have no idea, the code properly stamps MAM messages in the Why there is no I suppose that MAM messages sent to not connected resources (bounced with |
|
@andrzej.wojcik Well, not exactly. There are a lot of warnings about
What's seems to be a pattern here is that majority (all?) of them relates to mobile devices (judging by the resource name: Id' say Xabber, Monal and even Siskin). I think that my previous suggestion: "change I checked one of the packets processing (message) and it seems that the issue is caused by
As I said - in this case we should handle MAM case and don't generate further messages/error. Here is non-message example:
|
|
I agree that we may be able to fix that by improving a check in |
|
About MAM and mobile clients, those issues appear as mobile clients are disappearing during synchronization of messages and MAM component already sent those messages to the clients so we need to process them if there is no client (and drop them). |
|
About change in |
|
As fixing I checked other places and it seems this shouldn't generate more warnings in this context (warnings for those errors were very inadequate). |
|
It looks like this change caused some tests (JUnit) to fail. See TC errors. |
|
There was a problem with test - |
|
The problem still exists in a way, but only for
|
|
Complete log entry:
|
Type |
Bug
|
Priority |
Normal
|
Assignee | |
Version |
tigase-server-8.2.0
|
Spent time |
16h 35m
|
-
Customers/Verizon#183 You are not authorized to access this issue
From monitor: