[ https://issues.jboss.org/browse/TEIIDDES-2129?page=com.atlassian.jira.plu... ] Brian Stansberry commented on TEIIDDES-2129: -------------------------------------------- This is a custom admin client, not the WildFly CLI, right? The designer thread dump indicates that. Typically a thread dump like that on the client side is paired with a stuck thread on the server side, where a thread executing the management operation is blocking. But all looks well in your server side thread dump. This leads toward looking at 1) the client itself -- since its custom -- although it may very well be a standard custom client from ModelControllerClient.Factory; I'd have to look at the code. 2) The possibility of some message exchange between client and server getting lost. There appeared to be something like that going on in WFLY-1536, but in that case a more complex protocol between hosts in a managed domain was involved. Different from this client to server call, but there are enough similarities. The WFLY-1536 issue doesn't happen any more. I didn't see it on EAP 6.1; it started appearing during WildFly 8 development. Does this happen as part of some management write operation? If so, is the change reflected in the server? Knowing that would help narrow it down to something related to getting the response back to the client or handling it there. -- This message was sent by Atlassian JIRA (v6.2.3#6260)