Bug 956639
| Summary: | EndpointPublishTestCase testEndpointPublish intermittent failure, EAP 6.1.0 | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | [JBoss] JBoss Enterprise Application Platform 6 | Reporter: | Rostislav Svoboda <rsvoboda> | ||||||
| Component: | Web Services | Assignee: | Jim Ma <ema> | ||||||
| Status: | CLOSED WONTFIX | QA Contact: | |||||||
| Severity: | low | Docs Contact: | |||||||
| Priority: | unspecified | ||||||||
| Version: | 6.1.0 | CC: | ema | ||||||
| Target Milestone: | --- | ||||||||
| Target Release: | --- | ||||||||
| Hardware: | Unspecified | ||||||||
| OS: | Unspecified | ||||||||
| Whiteboard: | |||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||
| Doc Text: | Story Points: | --- | |||||||
| Clone Of: | Environment: | ||||||||
| Last Closed: | 2013-09-20 12:52:37 UTC | 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: |
|
||||||||
|
Description
Rostislav Svoboda
2013-04-25 10:47:56 UTC
From the server log and test log, the most possible cause is the classloader which loads the EndpointRegistryFactory in ServeltHelper is not the classloader in EndpointRegistryDeploymentAspect. I don't think this classloader(the jbossws.common mdoule's module classloader) can be changed by module reload or module/module classloader is gc-ed. But I am not sure if this is some strange ibm jdk's jdk behaviour. I think we can add some log to look at the classloader name to make it clear. Created attachment 741061 [details]
jbossws-common patch jar
Created attachment 741067 [details]
jbossws-cxf-server patch jar
Hi Rostislav , Can you please patched these two jars to EAP6.1 and get this test run again ? Let's see if this is cause of the classloader change. Thanks ! Cloning my jobs, will be using 4.1.3.snapshot + patches from BZ 956639 Issue not replicated yet, running again. We didn't hit this issue again for several months. Closing. |