This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 95057 - Execution of application failed with an exception.
Summary: Execution of application failed with an exception.
Status: CLOSED WONTFIX
Alias: None
Product: soa
Classification: Unclassified
Component: Composite Application (show other bugs)
Version: 5.x
Hardware: All All
: P1 blocker (vote)
Assignee: Alexander Fung
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-02-09 11:09 UTC by pcmreddy
Modified: 2007-04-09 10:29 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description pcmreddy 2007-02-09 11:09:58 UTC 
Used "netbeans-ent_pack-5_5_1-gavotte-070208_28-windows.exe" with JDK 1.5.0_10
on XP.

Test Case : 
http://blogs.sun.com/pcmreddy/resource/StockQuoteCA_files/StockQuoteCA2.html

After completing BPEL editing 
Run BPEL JUnit test case.
Change the value in input file as "SUNW"  This is the stock quote we are
requesting here.

Observe test case execution failed with the following error.

PWC3982: Cannot register MBean for the Protocol
grizzlyHttpProtocol.selectorRegisterProtocol
WEB0712: Starting Sun-Java-System/Application-Server HTTP/1.1 on 18181
Exception in processing reply. 
javax.xml.ws.soap.SOAPFaultException: Server did not recognize the value of HTTP
Header SOAPAction: .
        at
com.sun.xml.ws.fault.SOAP11Fault.getProtocolException(SOAP11Fault.java:163)
        at
com.sun.xml.ws.fault.SOAPFaultBuilder.createException(SOAPFaultBuilder.java:94)
        at
com.sun.xml.ws.client.dispatch.DispatchImpl.doInvoke(DispatchImpl.java:174)
        at com.sun.xml.ws.client.dispatch.DispatchImpl.invoke(DispatchImpl.java:193)
        at
com.sun.jbi.httpsoapbc.OutboundMessageProcessor.outboundCall(OutboundMessageProcessor.java:585)
        at
com.sun.jbi.httpsoapbc.OutboundMessageProcessor.processRequestReplyOutbound(OutboundMessageProcessor.java:272)
        at
com.sun.jbi.httpsoapbc.OutboundMessageProcessor.processMessage(OutboundMessageProcessor.java:157)
        at com.sun.jbi.httpsoapbc.OutboundAction.run(OutboundAction.java:57)
        at
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650)
        at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675)
        at java.lang.Thread.run(Thread.java:595)
Comment 1 pcmreddy 2007-02-09 21:29:30 UTC 
This is reproducible in Build : netbeans-ent_pack-5_5_1-gavotte-070209-windows.exe
Comment 2 Sergey Lunegov 2007-02-10 12:55:06 UTC 
Venkat, please assign somebody to to this issue
Comment 3 Jun Qian 2007-02-13 03:10:32 UTC 
Alex, could you please take a look at this issue?
Comment 4 Alexander Fung 2007-02-13 21:47:06 UTC 
This is a runtime issue.  I've filed a separate bug, 6524674, to address this 
issue.  It appears that with the move to JAX-WS, we need to specify the SOAP 
Action URI in a different manner than before.  I've fixed the issue, but it 
will likely not make it to beta.  Please track this issue from now on in 
Bugster with the aforementioned bug number.
Comment 5 srinivaschintalapati 2007-04-09 10:29:23 UTC 
Verified 6524674 in bugster and closed.