Hi there,
we are using an outdated Version of Wildfire 3.2.2. But the Version is stable and very useful to support our developer across the world.
Som facts:
-
Wildfire 3.2.2
-
about 200 User
-
Ldap integrated user account
-
several groups organisated
Normally it’s easy to add user to wildfire, just add the user to the AD group.
In the last weeks we regonzie an error.
We add the user to ad group.
the Error log:
2011.10.11 11:28:01 [org.jivesoftware.wildfire.roster.Roster.(Roster.java:162)
] Groups ([DE-Wildfire-Sa, DE-Wildfire-Group-IT-Collaboration]) include non-existent username (testpl)
2011.10.11 12:05:11 [org.jivesoftware.wildfire.roster.Roster.(Roster.java:162)
] Groups ([DE-Wildfire-Ma, DE-Wildfire-Group-IT-Collaboration]) include non-existent username (testpl)
2011.10.11 13:02:42 [org.jivesoftware.wildfire.roster.Roster.(Roster.java:162)
] Groups ([DE-Wildfire-Gr]) include non-existent username (testpl)
2011.10.11 14:20:35 [org.jivesoftware.wildfire.roster.Roster.(Roster.java:162)
] Groups ([DE-Wildfire-Sa, DE-Wildfire-Group-IT-Collaboration]) include non-existent username (testpl)
2011.10.11 14:39:40 [org.jivesoftware.wildfire.roster.Roster.(Roster.java:162)
] Groups ([DE-Wildfire-Sa, DE-Wildfire-Group-IT-Collaboration]) include non-existent username (testpl)
2011.10.11 14:45:47 [org.jivesoftware.wildfire.roster.Roster.(Roster.java:162)
] Groups ([DE-Wildfire-Group-IT-Infrastructure, DE-Wildfire-Group-IT-Collaboration]) include non-existent username (testpl)
the Warning Log
2011.10.11 13:58:59 Could not route packet
2011.10.12 06:15:41 Going to buffer response body of large or unknown size. Using getResponseBodyAsStream instead is recommended. 2011.10.12 06:15:42 Going to buffer response body of large or unknown size. Using getResponseBodyAsStream instead is recommended.The user don’t list in the allocated group.
Thanks for feedback!
henning72