Bug 1054106 - Intermittent failure of ExternalContextBindingTestCase
Summary: Intermittent failure of ExternalContextBindingTestCase
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: JBoss Enterprise Application Platform 6
Classification: JBoss
Component: Testsuite
Version: 6.2.0
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: DR0
: EAP 6.3.0
Assignee: Jan Martiska
QA Contact: Jan Martiska
URL:
Whiteboard:
Depends On:
Blocks: 1061618 1063823
TreeView+ depends on / blocked
 
Reported: 2014-01-16 09:11 UTC by Jan Martiska
Modified: 2014-08-20 07:21 UTC (History)
3 users (show)

Fixed In Version:
Clone Of:
: 1061618 (view as bug list)
Environment:
Last Closed: 2014-06-28 15:36:59 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 1018834 0 unspecified CLOSED ApacheDS used in the testsuite registers BouncyCastle security provider, but it doesn't unregister it 2021-02-22 00:41:40 UTC
Red Hat Issue Tracker WFLY-2760 0 Minor Resolved Intermittent failure of ExternalContextBindingTestCase 2014-08-20 07:19:22 UTC

Internal Links: 1018834

Description Jan Martiska 2014-01-16 09:11:40 UTC 
The server setup task sometimes fails to start the ApacheDS server instance because for some reason, BouncyCastle security provider doesn't get registered (it is added through a maven dependency rather than added to the JDK). This leads to a "connection refused" error during the test when it is trying to connect to the LDAP instance.

It worked for us if we just programatically forced registration of the BouncyCastleProvider before the initialization of ApacheDS.
Comment 2 Kabir Khan 2014-01-21 17:43:19 UTC 
https://github.com/jbossas/jboss-eap/pull/830
Comment 3 JBoss JIRA Server 2014-01-29 12:18:28 UTC 
Jan Martiska <jmartisk> updated the status of jira WFLY-2760 to Resolved
Comment 5 Pavel Jelinek 2014-02-19 13:09:52 UTC 
The correct PR 852 was merged and this issue didn't happen for EAP 6.3.0 DR0 so far again.
Note You need to log in before you can comment on or make changes to this bug.