This week's book giveaway is in the OO, Patterns, UML and Refactoring forum. We're giving away four copies of Refactoring for Software Design Smells: Managing Technical Debt and have Girish Suryanarayana, Ganesh Samarthyam & Tushar Sharma on-line! See this thread for details.
Are you behind any firewalls, which should not really matter as usually port 8080 and GET operation are allowed? but just curious.
Joined: Dec 14, 2004
I dont get any error except for a linkage error when i boot up the JBOSS server
java.lang.LinkageError: loader constraint violation: when resolving method "javax.xml.parsers.DocumentBuilder.setErrorHandler(Lorg/xml/sax/ErrorHandler;)V" the class loader (instance of org/jboss/classloader/spi/base/BaseClassLoader) of the current class, org/apache/log4j/xml/DOMConfigurator, and the class loader (instance of <bootloader>) for resolved class, javax/xml/parsers/DocumentBuilder, have different Class objects for the type org/xml/sax/ErrorHandler used in the signature
apart from that the application works fine and there are no issues as such. When i try to hit the WSDL i see no traces on the console or the server
When I looked into the description of HTTP 503, it says
The server is currently unable to handle the request due to a temporary overloading or maintenance of the server. The implication is that this is a temporary condition which will be alleviated after some delay. If known, the length of the delay MAY be indicated in a Retry-After header. If no Retry-After is given, the client SHOULD handle the response as it would for a 500 response.
Note: The existence of the 503 status code does not imply that a
server must use it when becoming overloaded. Some servers may wish
to simply refuse the connection.
I'm not really sure about the Linkage error, but I feel that there might be some kind of conflict while loading the classes in JBoss, given that you see some issues in booting. Have you tried deploying your app in another container or Have you tried deploying another service in the same JBoss instance and see how it is responding.
My feeling is, it may not be an issue with your service, but may be with your JBoss instance or they way it is installed or configured....