The above bug happened when using a 3.14.8 client with a 3.14.12 ioc. Using a 3.14.12 client succeeds. So it seems the bug had been fixed. I thought the problem was in the server but it seemed to be a client problem.
The above bug happened when using a 3.14.8 client with a 3.14.12 ioc. Using a 3.14.12 client succeeds. So it seems the bug had been fixed. I thought the problem was in the server but it seemed to be a client problem.