Bug 1090554 - [QE] (6.2.x) EJBEndpointAuthenticationTestCase sometimes produces confusing error messages due to reverse order of assert parameters
Summary: [QE] (6.2.x) EJBEndpointAuthenticationTestCase sometimes produces confusing e...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: JBoss Enterprise Application Platform 6
Classification: JBoss
Component: Testsuite
Version: 6.2.1,6.2.2
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: CR1
: EAP 6.2.4
Assignee: Pavel Jelinek
QA Contact: Pavel Jelinek
URL:
Whiteboard:
Depends On: 1090552
Blocks: eap62-cp04-blockers
TreeView+ depends on / blocked
 
Reported: 2014-04-23 15:06 UTC by Pavel Jelinek
Modified: 2016-10-18 10:21 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of: 1090552
Environment:
Last Closed: 2014-08-07 12:12:56 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker JBQA-9708 0 Major Closed EJBEndpointAuthenticationTestCase sometimes produces confusing error messages due to reverse order of assert parameters 2016-10-18 10:21:18 UTC

Description Pavel Jelinek 2014-04-23 15:06:10 UTC 
+++ This bug was initially created as a clone of Bug #1090552 +++

When OracleJDK 1.6 socket closed issue (https://bugzilla.redhat.com/show_bug.cgi?id=908701#c5) happens some EJBEndpointAuthenticationTestCase methods give error messages like
'expected:<[SocketException invoking http://10.16.93.209:8080/jaxws-authentication-ejb3/EJB3AuthService: Socket Clos]ed> but was:<[JBAS014502: Invocation on method: public java.lang.String org.jboss.as.test.integration.ws.authentication.EJBEndpoint.hello(java.lang.String) of bean: EJBEndpoint is not allow]ed>'
see: 
https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/EAP6/view/EAP-6.2.x-CP/view/EAP-6.2.x-CP-jobs/job/eap-62x-patched-as-testsuite-RHEL-matrix-OracleJDK6/43/jdk=java16_default,label_exp=RHEL5%26%26x86_64/testReport/org.jboss.as.test.integration.ws.authentication/EJBEndpointAuthenticationTestCase/accessHelloWithUnauthorizedUser/

The order of expected and actual parameters should be switched.
Comment 2 Pavel Jelinek 2014-05-05 15:01:14 UTC 
Verified for EAP 6.2.3.CP.CR2.
Comment 3 JBoss JIRA Server 2014-05-19 12:54:38 UTC 
Pavel Jelinek <pjelinek> updated the status of jira JBQA-9708 to Resolved
Comment 4 Pavel Jelinek 2014-05-19 12:57:27 UTC 
Unfortunatelly there are yet other methods with reverse order of assert parameters in this testcase.
Comment 6 Pavel Jelinek 2014-06-19 11:07:33 UTC 
Verified for EAP 6.2.4.CP.CR1.
Comment 7 JBoss JIRA Server 2016-10-18 10:21:19 UTC 
Radim Hatlapatka <rhatlapa> updated the status of jira JBQA-9708 to Closed
Note You need to log in before you can comment on or make changes to this bug.