[
https://issues.jboss.org/browse/WFLY-9900?page=com.atlassian.jira.plugin....
]
Radoslav Husar commented on WFLY-9900:
--------------------------------------
Ok, no problem. I have raised the priority to bring attention to a possible blocker
problem here (since this might easily fall through the cracks). Though, I agree with
David, there is little we can do now without at least the thread dump (but ideally a local
and non-SmartFrog reproducer). [~rjanik] I would recommend to always obtain thread dumps
before killing a stuck test job.
EJB client rarely hangs
-----------------------
Key: WFLY-9900
URL:
https://issues.jboss.org/browse/WFLY-9900
Project: WildFly
Issue Type: Bug
Components: Clustering, EJB
Affects Versions: 12.0.0.Beta1
Reporter: Richard JanÃk
Assignee: David Lloyd
Seen in our clustering tests where remote EJB clients invoke beans on 4 servers in
cluster, while each of those is being killed and restarted. This is done in sequence and
there's plenty of time in between the kill/start/kill-another (1 minute).
In two ouf our tests, we saw a small number of clients hang and resist termination at the
end. The scenarios are:
[
jvmkill-dist-sync|https://jenkins.hosts.mwqe.eng.bos.redhat.com/hudson/jo...]
(36 clients)
[
shutdown-dist-sync|https://jenkins.hosts.mwqe.eng.bos.redhat.com/hudson/j...]
(1 client)
The hangs are not related to any error or warning message on the server-side. There are
ClosedChannelExceptions on the client side, but these seem to be unrelated as the numbers
of clients reporting the exceptions are not the same (lower) as the numbers of hanging
clients.
No thread dump as I didn't manage to reproduce yet.
Might be related to JBEAP-12074 or JBEAP-13169.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)