It's not the port... the .NET stub works on 443.. but I tried anyway and as expected, no joy.
Also, HttpsURLConnection.setRequestProperty(String key, String value) sets HTTP headers as per the J2SE Javadoc: http://java.sun.com/j2se/1.4.2/docs/api/java/net/URLConnection.html#setRequestProperty%28java.lang.String,%20java.lang.String%29
I'm using the same code for AXL and AXL Serviceability and they do work (for AXL it's the CUCM

B ver=6.0 string, for Serviceability it's http://schemas.cisco.com/ast/soap/action/#RisPort#SelectCmDevice string) . I recall having the 500 error on serviceability before putting the proper SOAPAction header.
Now.. I installed fiddler (there's really no place in CCM to catch this? Seems like a very important debugging feature is missing) and managed to trace it down.. now that I see the response as well (I must be calling the wrong method.. the server actually tells what's wrong with the request) I managed to fix things.
Bottom line.. if I use the .net notation in java, it fails (something about the mustsupport being MS specific and requiring another element in the soapenv header). If I use my original copy&paste from the documentation, it works. But.. I must add a SOAPAction HTTP header. It does not seem to matter what I put in there though.. I managed to call getProfileSoap with urn:isClusterSoap, as well as with an empty SOAPHeader - that seems kinda weird.
Anyway.. I just wished that WSDLs would be tested against at least one framework for the major languages. I also work with other PBXes that offer Webservices.. and you can be sure that if you import their WSDL into either .NET or Java (they test against Axis and I believe their end uses Axis as well), it always works out of the box.
And might I suggest tha the SOAPAction thing be added to future documentation.. it's there for AXL & Servieability.. but anybody trying on their own (whether it is that their chosen toolkit doesn't import the WSDL or cannot deal with all the responses (e.g. .NET cannot handle the getProfileSoap response deserialization) will run into this trap.