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 52685 - Exception when invoking Test Operation on WS
Summary: Exception when invoking Test Operation on WS
Status: CLOSED DUPLICATE of bug 57542
Alias: None
Product: webservices
Classification: Unclassified
Component: Code (show other bugs)
Version: 4.x
Hardware: PC Windows XP
: P2 blocker (vote)
Assignee: _ pcw
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-12-20 16:39 UTC by L Martinek
Modified: 2006-03-24 12:59 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments
Stack trace (BTW: CR-LF is missing so it would be hard to read) (5.23 KB, text/plain)
2004-12-20 16:41 UTC, L Martinek
Details

Note You need to log in before you can comment on or make changes to this bug.
Description L Martinek 2004-12-20 16:39:51 UTC
[Build 200412191900, AppServer 8.1 b41]

I followed document "Developing J2EE Applications
in NetBeans IDE" on netbeans.org. In part
"Creating a Web Service" at
http://www.netbeans.org/kb/articles/quickstart-j2ee-41.html#web_service
I registered the web service successfuly. When I
right-clicked on the getYen method node and chose
Test Operation I got error: 
HTTP transport error:
com.sun.xml.messaging.saaj.SOAPExceptionImpl:
Unable to internalize message
Comment 1 L Martinek 2004-12-20 16:41:29 UTC
Created attachment 19367 [details]
Stack trace (BTW: CR-LF is missing so it would be hard to read)
Comment 2 _ pcw 2004-12-22 22:46:18 UTC
According to this message:
http://swforum.sun.com/jive/thread.jspa?threadID=49576&tstart=45 this
error will be thrown if the service is not running.

Was the service running when you attempted to test it?  (I agree that
the registry should see if it can be smarter about this sort of thing,
but that is a different issue.)
Comment 3 L Martinek 2004-12-23 11:36:48 UTC
How can I easily find out whether service is running? When I ran WS
client it worked properly. 
Comment 4 _ pcw 2004-12-23 19:14:59 UTC
Well, in this case, the service should be running if the appserver is
running and the service was deployed successfully.  One way to confirm
this is to use a browser to view the WSDL file as retrieved from the
service.  For example, the url to use for the service in the
quickstart guide is http://localhost:8080/ConverterWS/ConverterWS?wsdl
(adjust to your machine for port and host name of course.)  If the
service is deployed and running, this will return the text of the WSDL
file.
Comment 5 L Martinek 2005-01-13 17:59:07 UTC
I no longer saw this bug, so you may mark it as fixed.
Comment 6 L Martinek 2005-02-08 12:09:37 UTC
probably fixed
Comment 7 L Martinek 2005-02-08 12:10:21 UTC
verified
Comment 8 L Martinek 2005-02-25 16:44:50 UTC
Now I find reproducible testcase. I can reproduce it on my WinXP, but
not on Linux.

1. Create new web application.
2. Add web service to web application.
3. Deploy web application.
4. Register web service.
5. Invoke Test Operation on ws in Runtime. Now it works.
6. Restart IDE.
7. Start AppServer.
8. Invoke Test Operation on ws. Now it doesn't work and it throws
exception.
9. Register web service again. Now Test Operation works.
Comment 9 _ pcw 2005-03-21 05:26:25 UTC
I cannot reproduce this (Windows 2000) given the steps shown above.

asadmin version --verbose returns: Sun Java System Application Server Platform
Edition 8.1 (build b41-fcs)

Can you verify that the test machine that reliably reproduces this problem has
the FCS build of the application server installed on it?  I discovered a while
ago that even slightly earlier builds of the appserver had an older version of
JWSDP integrated into them and some bugs had been fixed that were integrated
into the build that is part of the appserver FCS build.

Honestly, I don't see any hard evidence there is a bug here.  But there are some
extra investigative steps I can suggest:  When the system is working, download
the WSDL to a browser (using service to do this, e.g.
http://localhost:8080/WebApp52685/NewWebService?WSDL).  Then try doing this same
step again in the circumstance where it is not working and see if there are any
differences.

Lastly, in the steps above, I presume an operation was added to the webservice.
 Can this be any operation, or is there one in particular you are using?  This
problem could be related to that.  The operation I used was prototyped "String
greet(String name)", though orginally, I used the ConverterWS instructions and
those worked fine as well.
Comment 10 Petr Jiricka 2005-03-21 15:46:05 UTC
Lukas Jungmann will look at this - thanks.
Comment 11 Lukas Jungmann 2005-03-23 11:07:31 UTC
I can reproduce this only if websvc or appsrv is not running, so I'm marking
this invalid.

using: jdk5.0_02-b09, SJSAS 8.1_01-b04, nb 200503221900


Comment 12 L Martinek 2005-04-01 11:38:35 UTC
I am not able to reproduce it now.
Comment 13 _ pcw 2005-04-13 23:53:59 UTC
Reopen because I'm going to close it as a dup of 57542
Comment 14 _ pcw 2005-04-13 23:54:49 UTC
I'm reclosing this issue as a duplicate of 57542 for better bug tracking.

*** This issue has been marked as a duplicate of 57542 ***
Comment 15 Lukas Jungmann 2005-11-24 12:12:24 UTC
v.