Having to migrate to Vista, I took this opportunity to upgrade my Websphere Integration Developer to the latest and greatest WID 6.1.2 just released by IBM. And the first immediate problem I’ve encoutered – it just would not startup! Every try to start WID gets the error with printout of all the startup parameters:
JVM termintaed. Exit code =1
I have scanned all the newsgroups – apparently this problem existed before this release in other IBM and Eclipse based products. IBM support site suggests it may be due to the java cache and -Xshareclasses flag:
And numerous newsgroups publishing workarounds:
The solution for the new WID 6.1.2 was to clear out eclipse.ini from all the arguments leaving only 2 lines specifying the jdk to call:
And Wow – it’s starting up.
I have played with all the parameters by adding/removing them from eclipse.ini and the offending one was – Xmx1024m, specifying the maximum java heap. (decreasing it to 512m – helped in my case) Looks like launcher tries to start up few java processes and exhausted the RAM available on the laptop.
Anyways just clear out eclipse.ini and leave 2 line – it will work with defaults.
Here is common problem with faults modeled using WSCF (WebServiceContractFirst) tool – while trying to generate C# Proxy for a webservice WSDL, I have kept getting the following error:
Error: Unable to cast object of type ‘System.Xml.XmlElement’ to type ‘System.Web
After a careful investigation of WSDL on W3C, I have discovered that the the bogus definition ( that wsdl.exe can’t understand) was in fault section of the binding:
<binding name=”SOAServices“ type=”tns:SOAServicesInterface“>
<soap:operation soapAction=”soa:validateUserIn“ style=”document“/>
Replacing the definition to include soap:fault instead of soap:body resolves the problem.
<wsdl:fault name=” ValidateUserFault “>
<soap:fault name=” ValidateUserFault “ use=”literal“/>
It would have been nice if wsdl.exe will generate more information for the errors, but ….
Free SOAP tesing resources
My favourite Web Service testing tools – collection of links:
|SOAPUI||java based desktop application for inspecting, invoking and functional and load testing of webservices over HTTP/HTTPS|
|Microsoft WFetch||Lightweight utility tool that helps to send any HTTP/HTTPS traffic including SOAP.It allows for very granular testing down to the authentication, authorization, custom headers, and much more. Especially useful for for SSL/certificate issues debugging|
|STORM||.NET desktop application used to dynamically invoke web services.|
|Web Service Studio Express||.NET based desktop application for invoking and testing of webservices over HTTP|
|WSDL Validator||Online WSDL validator|
|SOAP Sonar Personal||Powerful Web Services Functional Testing and Performance Loading for Developer and QA personnel developing applications based on WSDL and SOAP|
Websphere Application Server has a nice utility to check Fixpacks and iFixes installed in the system
- <WAS_ROOT>/bin/versionInfo.bat -maintenancePackages
It will print all the version details and information on Fixpacks.
More on versionInfo options: