Red Hat Bugzilla – Bug 847070
HornetQ human task service communication does not work due to "IllegalStateException: unread block data" on EAP 6.0
Last modified: 2015-06-01 21:34:58 EDT
Created attachment 603276 [details]
HornetQ human task service communication does not work in BRMS 5.3.0 GA deployed on EAP 6.0. A test client is not able to connect to the human task service. The task service server throws the following exception (the whole stack trace is attached in server log):
Caused by: java.lang.IllegalStateException: unread block data
My test client fails on a timeout (20 seconds) and a message "unable to retrieve results".
I have deployed brms 5.3.0.GA deployable on EAP 6.0 using the steps described in this document:
My human task server uses the default port 5446.
I'll be working on a reproducer.
I have run the same test from our test suite also on BRMS 5.3.0 GA with patch 01 (our test version corresponds with patch 01) and the result is that the two sides - client and server do not communicate and fail with the same messages. There is only one difference - the exception "java.lang.IllegalStateException: unread block data" is not thrown.
DId you manage to get a reproducer test on this one?
So I can take a look and see what is wrong?
Created attachment 605923 [details]
Simple human task test to reproduce
I have managed to create an isolated reproducer. It's just a simple test which registers human task handler and connects to the human task service.
To make everything clear - this issue happens only with BRMS 5.3.0 GA deployed on EAP 6.0. I have tested this with BRMS 5.3.0 GA patch 01 on EAP 6.0 and HornetQ connection works fine. I have used Hibernate 3.
I expect that the fixes from patch01 will be included in BRMS 5.3.1, so this bug is no longer relevant.
Unexpectedly fixed in a patch release, closing.