jabber_register.xml reuses old user IDs and causes 409 errors (user conflict)

[acoccimiglio]

I believe the id="new" attribute in the <jabber> tag is supposed to guarantee a new user id instead of reusing a disconnected one. However, this is not documented anywhere, and does not appear to do anything. The example register load test results in many 409 errors (user conflict) because users will attempt to re-register upon disconnecting.

[thinkingshu]

I believe the id="new" attribute in the <jabber> tag is supposed to guarantee a new user id instead of reusing a disconnected one. However, this is not documented anywhere, and does not appear to do anything. The example register load test results in many 409 errors (user conflict) because users will attempt to re-register upon disconnecting.

I have the same problem when register load test.

[thinkingshu]

I believe the id="new" attribute in the <jabber> tag is supposed to guarantee a new user id instead of reusing a disconnected one. However, this is not documented anywhere, and does not appear to do anything. The example register load test results in many 409 errors (user conflict) because users will attempt to re-register upon disconnecting.

I have the same problem when register load test.
Setting the ack="global" attribute in the tag can solve the problem.