Yeah fixed this problem it was due to the LdapCodecServiceFactory not properly initializing.
On Thu, Feb 24, 2011 at 4:07 PM, Emmanuel Lecharny <elecha...@gmail.com> wrote: > On 2/24/11 3:24 AM, Alex Karasulu wrote: >> >> Here's more data that might shed light. Starting to maybe see what's >> going on now: >> >> org.apache.mina.filter.codec.ProtocolDecoderException: >> java.lang.NullPointerException (Hexdump: 30 81 89 02 01 02 68 67 04 1E >> 6F 75 3D 53 74 6F 72 65 64 20 50 72 6F 63 65 64 75 72 65 73 2C 6F 75 >> 3D 73 79 73 74 65 6D 30 45 30 19 04 02 6F 75 31 13 04 11 53 74 6F 72 >> 65 64 20 50 72 6F 63 65 64 75 72 65 73 30 28 04 0B 6F 62 6A 65 63 74 >> 43 6C 61 73 73 31 19 04 03 74 6F 70 04 12 6F 72 67 61 6E 69 7A 61 74 >> 69 6F 6E 61 6C 55 6E 69 74 A0 1B 30 19 04 17 32 2E 31 36 2E 38 34 30 >> 2E 31 2E 31 31 33 37 33 30 2E 33 2E 34 2E 32) > > This is a perfectly correct message : > 30 81 89 > 02 01 02 > 68 67 Add request > 04 1E > ou=Stored Procedures,ou=system > 30 45 > 30 19 > 04 02 > ou > 31 13 > 04 11 > Stored Procedures > 30 28 > 04 0B > objectClass > 31 19 > 04 03 > top > 04 12 > organizationalUnit > A0 1B > 30 19 > 04 17 > 32 2E 31 36 2E 38 34 30 2.16.840.1.113730.3.4.2 > 2E 31 2E 31 31 33 37 33 ManageDSAIt > 30 2E 33 2E 34 2E 32 > > >> Caused by: java.lang.NullPointerException >> at >> org.apache.directory.shared.ldap.codec.actions.controls.AddControl.action(AddControl.java:97) > > Message message = container.getMessage(); > > Control control = container.getLdapCodecService().newControl( > oidValue ); > > message.addControl( control ); <--- That means the message is null, > so the container does not hold any message. This is weird, this might be > because the NoD has requested the container to be cleared up. > > To be investigated... May be adding some logs in the > LdapMessageContainer.clear() method could help... > > > -- > Regards, > Cordialement, > Emmanuel Lécharny > www.iktek.com > >
