Xfire Nested exception is org.codehaus.xfire.fault.XFireFault:Couldn ' t send message.

Org.codehaus.xfire.XFireRuntimeException:Could not invoke service. Nested exception is org.codehaus.xfire.fault.XFireFault:Couldn ' t send message.
ORG.CODEHAUS.XFIRE.FAULT.XFIREFAULT:COULDN ' t send message.
At Org.codehaus.xfire.fault.XFireFault.createFault (xfirefault.java:89)
At Org.codehaus.xfire.handler.OutMessageSender.invoke (outmessagesender.java:30)

At Org.codehaus.xfire.handler.HandlerPipeline.invoke (handlerpipeline.java:131)

When using Xfire to make the WebService interface, use HTTP://LOCALHOST:8080/WEBSERVICE/SERVICES/DEMO?WSDL to access the

However, the interface server is not connected during the call.

This link is not accessible after using IP access discovery.

Workaround:

1. Use the cmd command netstat-n to view the Tomcat address bindings, found to be bound to:: 1, IPv6.

2. Configure Tomcat Server.xml, change the connector configuration, the port does not change, plus address= "0.0.0.0" to bind to IPv4, as follows (for reference to the solution) <1> use cmd command netstat-n, View Tomcat address bindings, found to be bound to:: 1, IPV6; <2> Configure Tomcat Server.xml, change Connector configuration, port does not need to change, plus address= "0.0.0.0" to bind it to IPv4 <connector port= "8080" Maxhttpheadersize= "8192" address= "0.0.0.0" maxthreads= "," minsparethreads= "maxsparethreads=" "75"
Enablelookups= "false" redirectport= "8443" acceptcount= "connectiontimeout=" 20000 "true"/ > <3> restart Tomcat, use Netstat-n again to view Tomcat address bindings, changed to IPV4.
This problem can be solved. (This problem seems to exist TOMCAT5.5)