Client is using Orbiter 2.0 (so far only the server is being upgraded).
Same client software in all cases.
Two servers, A) has Union 2.0 and B) has Union 2.1.1
On both A & B, union.xml says:
<rule>
<action>MODIFY_CLIENT_ATTRIBUTE</action>
<roles></roles>
</rule>
With server A, there are no error messages.
With server B, I see this in the log:
- Code: Select all
2014-12-02 20:31:21,862 INFO - Client [2] attempted restricted action [MODIFY_CLIENT_ATTRIBUTE].
2014-12-02 20:31:36,863 INFO - Client [2] attempted restricted action [MODIFY_CLIENT_ATTRIBUTE].
2014-12-02 20:31:51,861 INFO - Client [2] attempted restricted action [MODIFY_CLIENT_ATTRIBUTE].
2014-12-02 20:32:06,862 INFO - Client [2] attempted restricted action [MODIFY_CLIENT_ATTRIBUTE].
2014-12-02 20:32:22,709 INFO - Client [2] attempted restricted action [MODIFY_CLIENT_ATTRIBUTE].
There is no information in the server log as to details such as which attribute.
Since I do not have any client.setAttribute calls anywhere in my client code, and the ones on the
server side appear to be working fine, and these are occurring at regular 15-second intervals,
which is what I have my heartbeat interval set to,
... I assume the cause lies there -
and it is probably the _PING attribute
(which UnionAdmin 2.0 displays [as empty now] and UnionAdmin 2.1 does not display at all).
Never seeing those on Union 2.0, I guess 2.1 is being more strict about something ... or maybe
that attribute is no longer there?
(Switching to Orbiter 2.1 did not change anything - the errors still occur.
If I modify union.xml to allow ALL for MODIFY_CLIENT_ATTRIBUTE, which I'd rather not do,
the errors go away, but I do not see any messages relating to some attribute changing, either.)