Bug 826990
Summary: | NoClassDefFoundError when calling a webservice using Wise SOAPClient(JDK7) | ||||||
---|---|---|---|---|---|---|---|
Product: | [JBoss] JBoss Enterprise SOA Platform 5 | Reporter: | Filip Elias <felias> | ||||
Component: | JBossESB | Assignee: | Kevin Conner <kevin.conner> | ||||
Status: | VERIFIED --- | QA Contact: | |||||
Severity: | urgent | Docs Contact: | |||||
Priority: | unspecified | ||||||
Version: | 5.3.0 GA | CC: | jcoleman, mvecera, ncross, soa-p-jira | ||||
Target Milestone: | ER4 | ||||||
Target Release: | 5.3.0 GA | ||||||
Hardware: | Unspecified | ||||||
OS: | Unspecified | ||||||
Whiteboard: | |||||||
Fixed In Version: | Doc Type: | Bug Fix | |||||
Doc Text: |
When attempting to invoke a webservice with the Wise SOAPClient it will throw an exception. This is caused by a class error in JDK 7. A logmanager patch has been added to address this. As a result, users will no longer encounter this exception when invoking webservices via Wise.
|
Story Points: | --- | ||||
Clone Of: | Environment: |
SOA-P 5.3
java version "1.7.0_04"
|
|||||
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: | |||||||
Bug Depends On: | 820498 | ||||||
Bug Blocks: | |||||||
Attachments: |
|
Logmanager patched in https://bugzilla.redhat.com/show_bug.cgi?id=820498 Technical note added. If any revisions are required, please edit the "Technical Notes" field accordingly. All revisions will be proofread by the Engineering Content Services team. New Contents: When attempting to invoke a webservice with the Wise SOAPClient it will throw the exception. This is caused by a class error in JDK 7. Technical note updated. If any revisions are required, please edit the "Technical Notes" field accordingly. All revisions will be proofread by the Engineering Content Services team. Diffed Contents: @@ -1 +1 @@ -When attempting to invoke a webservice with the Wise SOAPClient it will throw the exception. This is caused by a class error in JDK 7.+When attempting to invoke a webservice with the Wise SOAPClient it will throw an exception. This is caused by a class error in JDK 7. A logmanager patch has been added to address this. As a result, users will no longer encounter this exception when invoking webservices via Wise. Verified in SOA-P 5.3 ER4 |
Created attachment 588051 [details] ESB service with soapclient and webservice Description of problem: When you try to call a webservice using Wise SOAPClient it will throw "java.lang.NoClassDefFoundError: Could not initialize class sun.net.www.protocol.http.HttpURLConnection". This problem occurs in JDK 7. Version-Release number of selected component (if applicable): SOA-P 5.3 ER3 Steps to Reproduce: 1.Deploy archive from the attachment(it contains also webservice) 2.Call service (Category:"MyServiceCategory" Name:"Webserviceconsumer_wise2") Exception: java.lang.NoClassDefFoundError: Could not initialize class sun.net.www.protocol.http.HttpURLConnection at sun.net.www.protocol.http.Handler.openConnection(Handler.java:62) at sun.net.www.protocol.http.Handler.openConnection(Handler.java:57) at java.net.URL.openConnection(URL.java:969) at org.jboss.soa.esb.actions.soap.wise.WSDynamicClientFactory.transferWSDL(WSDynamicClientFactory.java:126) at org.jboss.soa.esb.actions.soap.wise.WSDynamicClientFactory.downloadWsdl(WSDynamicClientFactory.java:111) at org.jboss.soa.esb.actions.soap.wise.WSDynamicClientFactory.create(WSDynamicClientFactory.java:71) at org.jboss.soa.esb.actions.soap.wise.SOAPClient.createClient(SOAPClient.java:330) at org.jboss.soa.esb.actions.soap.wise.SOAPClient.process(SOAPClient.java:263) at org.jboss.soa.esb.listeners.message.ActionProcessingPipeline.processPipeline(ActionProcessingPipeline.java:657) at org.jboss.soa.esb.listeners.message.ActionProcessingPipeline.processPipeline(ActionProcessingPipeline.java:611) at org.jboss.soa.esb.listeners.message.ActionProcessingPipeline.process(ActionProcessingPipeline.java:441) at org.jboss.soa.esb.listeners.message.MessageAwareListener$TransactionalRunner.run(MessageAwareListener.java:587) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) at java.lang.Thread.run(Thread.java:722)