Bug 782774

Summary: TCK: Some of the tests hang during TCK execution
Product: Red Hat Enterprise MRG Reporter: Jiri Pechanec <jpechane>
Component: qpid-javaAssignee: Jiri Pechanec <jpechane>
Status: CLOSED CURRENTRELEASE QA Contact: MRG Quality Engineering <mrgqe-bugs>
Severity: urgent Docs Contact:
Priority: urgent    
Version: DevelopmentCC: iboverma, jross
Target Milestone: 2.1.2   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: qpid-jca-0.14-5 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
Log files none

Description Jiri Pechanec 2012-01-18 12:22:07 UTC 
There is a subset of tests that ends with error during TCK execution
com/sun/ts/tests/jms/ee/ejb/sessiontests
com/sun/ts/tests/jms/ee/all/queuetests/QueueTests.java#emptyMsgsQueueTest

The symptoms are always the same - a call to session.receive(timeout) does not end after the timeout and the test is abruptly terminated after 5 mins.

Moroever EAP server then cannot be shut down gracefully.

I tried to execute sessiontests locally and take thread dumps to saee what is going on
threaddump1.txt - during the first test execution
threaddump2.txt - second time during the first test
threaddump3.txt - during the second test execution
threaddump4.txt - after second test timeout
threaddump5.txt - after unsuccessful EAP shutdown

test.log - Log of TCK execution
server.log - EAP log with org.qpid on TRACE level
fulltck.log - A log from full TCK execution - shows com/sun/ts/tests/jms/ee/all/queuetests/QueueTests.java#emptyMsgsQueueTest
Comment 1 Jiri Pechanec 2012-01-18 13:09:54 UTC 
Created attachment 556025 [details]
Log files
Comment 2 Justin Ross 2012-01-24 18:25:31 UTC 
QPID-3715, revision 1228583
Comment 3 Rajith Attapattu 2012-01-24 22:15:48 UTC 
I've run the TCK on my local copy and have verified the above test passes in the standalone version