Bug 1247931
Summary: | Qpid-jms amqp 1.0 client fails in many TCK JMS 1.1 tests | ||||||||
---|---|---|---|---|---|---|---|---|---|
Product: | Red Hat Enterprise MRG | Reporter: | Michal Toth <mtoth> | ||||||
Component: | qpid-java | Assignee: | messaging-bugs <messaging-bugs> | ||||||
Status: | NEW --- | QA Contact: | Messaging QE <messaging-qe-bugs> | ||||||
Severity: | high | Docs Contact: | |||||||
Priority: | medium | ||||||||
Version: | 3.2 | CC: | gsim, jross, rgemmell | ||||||
Target Milestone: | 3.2 | ||||||||
Target Release: | --- | ||||||||
Hardware: | Unspecified | ||||||||
OS: | Unspecified | ||||||||
Whiteboard: | |||||||||
Fixed In Version: | Doc Type: | Bug Fix | |||||||
Doc Text: | Story Points: | --- | |||||||
Clone Of: | Environment: | ||||||||
Last Closed: | Type: | Bug | |||||||
Regression: | --- | Mount Type: | --- | ||||||
Documentation: | --- | CRM: | |||||||
Verified Versions: | Category: | --- | |||||||
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||
Cloudforms Team: | --- | Target Upstream Version: | |||||||
Embargoed: | |||||||||
Attachments: |
|
Created attachment 1057256 [details]
Filtered test failures of TCK run with comments
Forgot to mention broker version (MRG M 3.2) qpid-cpp-server-0.34-1.el6.i686 |
Created attachment 1057255 [details] TCK test log output Description of problem: Qpid-jms-client amqp 1.0 fails in 54 test cases of TCK test suite. There are 13 general issues (first ones listed in "failures log" file) and around ~40 selector issues. Version-Release number of selected component (if applicable): qpid-jms-client 0.3.0 (same with 0.2.0) How reproducible: Always Steps to Reproduce: 1. Set up TCK 1.1 tests with amqp 1.0 qpid-jms client 2. Start MRG 3.2 and create manually needed queues (found in [1]) 3. Run TCK JMS 1.1 tests Actual results: 54 test failures (see attached test log) Expected results: Amqp 1.0 jms client passes TCK JMS 1.1 test suite. Additional info: See the provided log files for more information. I think some of the failures might be caused by inability of client to create destinations on mrg broker. (Invalid destinations) [1] - $TCK_HOME/jmstck/bin/xml/impl/ri/jndi.properties (lists queue/topic destinations, but are they all, which TCK uses?)