Skip to main content

Wrong context-root

Please note these forums are being decommissioned and use the new and improved forums at
No replies
Joined: 2009-08-13


I've deployed a SOAP application as a WAR in Glassfish V3.0 final. The context root of the application is set on the sun-web.xml as:

<sun-web-app error-url="">

In my log, however, I see this:

 [#|2011-03-23T18:52:02.048+0545|INFO|glassfish3.1||_ThreadID=2567;_ThreadName=Thread-2;|WS00019: EJB Endpoint deployed  project-1.0_debug  listening at address at http://server-928:9080/configurationService/configuration|#]
[#|2011-03-23T18:52:02.138+0545|INFO|glassfish3.1||_ThreadID=2567;_ThreadName=Thread-2;|WEB0671: Loading application [project-1.0_debug] at [/blablasoap]|#

As you can see, the address my application is listening at doesn't contain the context root, but Glassfish tells me that it's being deployed in that path.

If I do a wget to that address, I get a:

--2011-03-23 18:59:41--  http://localhost:9080/blablasoap
localhost... ::1,
Connecting to localhost|::1|:9080... connected.
HTTP request sent, awaiting response... 301 Moved Permanently
Location: http://localhost:9080/blablasoap/ [following]
--2011-03-23 18:59:41--  http://localhost:9080/blablasoap/
to localhost|::1|:9080... connected.
HTTP request sent, awaiting response... 404 Not Found
2011-03-23 18:59:41 ERROR 404: Not Found.

...and getting the wsdl works when trying to get http://localhost:9080/configurationService/configuration?wsdl, but not http://localhost:9080/blablasoap/configurationService/configuration?wsdl

I'm (almost) sure that isn't code related, as this exact WAR was working a few months ago in another server, but we've updated our servers, and now Glassfish is acting this way in two different servers (one with custom config, another with default config).

I know that maybe I'm not saying a lot, but any thoughts? If you need any more info, just ask.

Thanks a lot in advance!!