A strange problem arises when the WebService is recently written with. NET invoke Java: The WebService service is deployed on this machine, and the Web reference for the outside machine can be added correctly, but when debugging runs, the target machine actively rejects (target machine Actively refused) "wrong!" said the Stranger.
A strange problem arises when the WebService is recently written with. NET invoke Java: The WebService service is deployed on this machine, and the Web reference for the outside machine can be added correctly, but when debugging runs, the target machine actively rejects (target machine Actively refused) "wrong!" said the Stranger. And in this machine can be normal operation. Check the Internet, most of them are said to be a firewall or port problems, but the firewall is not open, the port is open, how can still appear access denied error?
Study for a long time, finally found the problem is: the original in the generated WSDL file address is localhost, so that the external machine to resolve, the natural will be from the localhost to find, but the service deployed in my place, they can find from the local? ? Of course it can't be accessed. I'm running locally and I'm sure I can access it. OK, the localhost to the local intranet or extranet IP, try again, success!
The answer to the online search question is not necessarily the answer to your question, including this article, perhaps just kind, maybe just a similar situation, but also need the user to detect.