Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I'm evaluating the use of Riftsaw and have been following the Getting Started guide:

I've installed JBossAS 6, JBoss ESB 4.10 and Riftsaw 2.3.0 on my server (let's call it server1, with IP a FQDN of and can access the admin console fine from both server1 and my development PC. I have deployed the "Hello World" quickstart example and I can view the WSDL from both computers in a web browser from server1:8080/Quickstart_hello_worldWS?wsdl. On server1, I can also use localhost:8080/Quickstart_hello_worldWS?wsdl (please assume URLs have http:// prefix – as a new user I'm restricted to 2 hyperlinks).

I am trying to use soapUI to test invocation of the service. I create a new sopaUI project, enter server1:8080/Quickstart_hello_worldWS?wsdl for "Initial WSDL/WADL" and I receive an "Unexpected element: CDATA" error. Looking at the http log, soapUI receives HTML with the following data:

404 Not Found

No context found for request

This happens on both my development PC and server1 itself.

If I create a soapUI project on server1 using localhost:8080/Quickstart_hello_worldWS?wsdl, it successfully processes the WSDL and creates a sample request. However, the endpoint for this request (in the WSDL) is SERVER1:8080/Quickstart_hello_worldWS and if I try and submit it, the "404" data is returned. Using soapUI, I manually edited the endpoint to be localhost:8080/Quickstart_hello_worldWS and it works, returning the expected response.

I have also received the "404" page when doing the following:

  • Opening from my dev PC in a web browser
  • Opening from my dev PC or from server1 in a web browser

So my question is, why is soapUI only able to read the WSDL and send a request using "localhost" and how can I do that using the servers DNS name?

share|improve this question

I inspected the HTTP GET requests sent by IE, Firefox and soapUI and found that soapUI was sending the request to the IPv4 address of server1, whereas IE and Firefox were sending it to the IPv6 address. I set the "network.dns.disableIPv6" to TRUE in Firefox's "about:config" and Firefox then received the same 404 error as soapUI.

Up until now, I had run JBoss bound to all network interfaces:

.\run.bat -b

I managed to work around this problem by binding JBoss to the IPv4 address of server1:

.\run.bat -b
share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.