Bug 826990 - NoClassDefFoundError when calling a webservice using Wise SOAPClient(JDK7)
Summary: NoClassDefFoundError when calling a webservice using Wise SOAPClient(JDK7)
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: JBoss Enterprise SOA Platform 5
Classification: JBoss
Component: JBossESB
Version: 5.3.0 GA
Hardware: Unspecified
OS: Unspecified
unspecified
urgent
Target Milestone: ER4
: 5.3.0 GA
Assignee: Kevin Conner
QA Contact:
URL:
Whiteboard:
Depends On: 820498
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-05-31 11:30 UTC by Filip Elias
Modified: 2025-02-10 03:20 UTC (History)
4 users (show)

Fixed In Version:
Clone Of:
Environment:
SOA-P 5.3 java version "1.7.0_04"
Last Closed: 2025-02-10 03:20:01 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
ESB service with soapclient and webservice (12.40 KB, application/octet-stream)
2012-05-31 11:30 UTC, Filip Elias
no flags Details

Description Filip Elias 2012-05-31 11:30:31 UTC
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)

Comment 4 Nick Cross 2012-06-06 09:57:52 UTC
Logmanager patched in https://bugzilla.redhat.com/show_bug.cgi?id=820498

Comment 5 Suz 2012-06-13 05:48:23 UTC
    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.

Comment 6 David Le Sage 2012-06-14 03:58:59 UTC
    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.

Comment 7 Filip Elias 2012-06-28 10:26:37 UTC
Verified in SOA-P 5.3 ER4

Comment 8 Red Hat Bugzilla 2025-02-10 03:20:01 UTC
This product has been discontinued or is no longer tracked in Red Hat Bugzilla.


Note You need to log in before you can comment on or make changes to this bug.