[
https://issues.apache.org/jira/browse/DIRSERVER-942?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12521723
]
Emmanuel Lecharny commented on DIRSERVER-942:
---------------------------------------------
There is an interesting thread stack :
"main" prio=10 tid=0x0805c400 nid=0x42b9 in Object.wait()
[0xb7df3000..0xb7df4208]
java.lang.Thread.State: TIMED_WAITING (on object monitor)
at java.lang.Object.wait(Native Method)
- waiting on <0x8c16c478> (a com.sun.jndi.ldap.LdapRequest)
at com.sun.jndi.ldap.Connection.readReply(Connection.java:431)
- locked <0x8c16c478> (a com.sun.jndi.ldap.LdapRequest)
at com.sun.jndi.ldap.LdapClient.getSearchReply(LdapClient.java:611)
at com.sun.jndi.ldap.LdapClient.search(LdapClient.java:534)
at com.sun.jndi.ldap.LdapCtx.doSearch(LdapCtx.java:1948)
at com.sun.jndi.ldap.LdapCtx.searchAux(LdapCtx.java:1810)
at com.sun.jndi.ldap.LdapCtx.c_search(LdapCtx.java:1735)
at
com.sun.jndi.toolkit.ctx.ComponentDirContext.p_search(ComponentDirContext.java:368)
at
com.sun.jndi.toolkit.ctx.PartialCompositeDirContext.search(PartialCompositeDirContext.java:338)
at
com.sun.jndi.toolkit.ctx.PartialCompositeDirContext.search(PartialCompositeDirContext.java:321)
at
javax.naming.directory.InitialDirContext.search(InitialDirContext.java:248)
at
org.apache.directory.server.DeleteIllegalDNITest.testSearch(DeleteIllegalDNITest.java:64)
We can see that the client is waiting forever for a reply. But while using
wireshark, here is the data which are being sent back to the client for the
last search :
30 5c 02 01 02 65 57 0a 01 22 04 00 ..P.0\..
.eW.."..
0050 04 50 49 6e 76 61 6c 69 64 20 72 6f 6f 74 20 44 .PInvali d root D
0060 4e 20 67 69 76 65 6e 20 3a 20 6d 79 42 61 64 44 N given : myBadD
0070 4e 20 28 30 78 36 44 20 30 78 37 39 20 30 78 34 N (0x6D 0x79 0x4
0080 32 20 30 78 36 31 20 30 78 36 34 20 30 78 34 34 2 0x61 0 x64 0x44
0090 20 30 78 34 45 20 29 20 69 73 20 69 6e 76 61 6c 0x4E ) is inval
00a0 69 64
id
cryptic, eh ? :) This is just a SearchResultDone message ( the response from
the previous request ). Why do we get it now is what we should understand... It
seems that some state is not correctly handled if we have an error in the
decoded PDU.
> Server Feezes When Doing https://issues.apache.org/jira/browse/DIRSERVER-935
> ----------------------------------------------------------------------------
>
> Key: DIRSERVER-942
> URL: https://issues.apache.org/jira/browse/DIRSERVER-942
> Project: Directory ApacheDS
> Issue Type: Bug
> Components: ldap
> Affects Versions: 1.5.0
> Reporter: Ole Ersoy
> Priority: Blocker
> Fix For: 1.5.1
>
> Attachments: CreateSyntaxEntrySelfContainedTest.java,
> IllegalDNITest.java, thread-dump.txt
>
>
> This is related to https://issues.apache.org/jira/browse/DIRSERVER-935
> By accident I tried running some code that deletes (935 looks up)
> entries that are not present.
> The server froze and I could not connect with LS
> anymore.
> First I assumed it crashed, so I tried doing
> ./apacheds start
> But I still could not connect
> so I tried doing
> ./apacheds stop
> ./aapcheds start
> and back to normal.
> I need to code a self contained test for this.
> Cheers,
> - Ole
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
