[OPENDJ-3853] "Directory is already processing..." message while running OULU enc test suite Created: 10/Mar/17  Updated: 08/Nov/19  Resolved: 15/Mar/17

Status: Done
Project: OpenDJ
Component/s: core server
Affects Version/s: 4.0.0
Fix Version/s: 4.0.0

Type: Bug Priority: Major
Reporter: Christophe Sovant Assignee: Christophe Sovant
Resolution: Cannot Reproduce Votes: 0
Labels: None

Dev Assignee: Christophe Sovant

 Description   

Found using OpenDJ 4.0.0 rev ff9ce14b894.

Running the OULU enc test suite a lot of test case received the following message from the server:

Writing test case #0, 39 bytes, localhost port 1389
Wrote, waiting 1000 ms for reply
133 bytes received
00000000  30 81 82 02 01 01 65 7d 0a 01 02 04 00 04 76 54  0.....e}......vT
00000016  68 65 20 44 69 72 65 63 74 6f 72 79 20 53 65 72  he Directory Ser
00000032  76 65 72 20 69 73 20 61 6c 72 65 61 64 79 20 70  ver is already p
00000048  72 6f 63 65 73 73 69 6e 67 20 61 6e 6f 74 68 65  rocessing anothe
00000064  72 20 72 65 71 75 65 73 74 20 6f 6e 20 74 68 65  r request on the
00000080  20 73 61 6d 65 20 63 6c 69 65 6e 74 20 63 6f 6e   same client con
00000096  6e 65 63 74 69 6f 6e 20 77 69 74 68 20 74 68 65  nection with the
00000112  20 73 61 6d 65 20 6d 65 73 73 61 67 65 20 49 44   same message ID
00000128  20 6f 66 20 31                                    of 1

Same test case using OpenDJ 3.5.0:

Writing test case #0, 39 bytes, to comte.internal.forgerock.com port 1389
Wrote, waiting 1000 ms for reply
74 bytes received
00000000  30 3a 02 01 01 64 35 04 06 64 63 3d 63 6f 6d 30  0:...d5..dc=com0
00000016  2b 30 1c 04 0b 6f 62 6a 65 63 74 43 6c 61 73 73  +0...objectClass
00000032  31 0d 04 06 64 6f 6d 61 69 6e 04 03 74 6f 70 30  1...domain..top0
00000048  0b 04 02 64 63 31 05 04 03 63 6f 6d 30 0c 02 01  ...dc1...com0...
00000064  01 65 07 0a 01 00 04 00 04 00                    .e........


 Comments   
Comment by Matthew Swift [ 15/Mar/17 ]

Any update?

Comment by Christophe Sovant [ 15/Mar/17 ]

I tried using 4.0.0 rev 97b73b33b7d and I don't have this issue anymore.

Comment by Matthew Swift [ 07/Nov/19 ]

Moved to closed state because the fixVersion has already been released.

Generated at Mon Nov 23 16:43:18 UTC 2020 using Jira 7.13.12#713012-sha1:6e07c38070d5191bbf7353952ed38f111754533a.