I have a working service deployed to weblogic 9.2. We had a server migration, so we moved this application to another server with the same weblogic setup. Now, when I try to access the WSDL, I get 503 Service Unavailable error. It is the same exact application. Any guess as to why this is happening?
503 Service Unavailable error when deploying a working ear file to weblogic server!
application-serverserviceweblogicwsdl
Related Topic
- How-To Configure Weblogic, Agile PLM and an F5 LTM
- Ubuntu – binary executable working in centos but not in ubuntu
- Web service WSDL and discovery is not working correctly
- Standalone WLST for both WebLogic 8.1 and 9.2
- WLS: Oracle data source yields “ORA-01435: user does not exist”
- No admin console, not listening in port when server in STARTING state
- Apache balancing towards Weblogic backends, mod_wl vs mod_proxy_balancer
Best Answer
One thing to definitely check here is that the application's current status is 'Active', not 'Prepared' - I'm likely telling you things you already know, but there's a two-step deployment process in WebLogic Server 9 and beyond, and an application needs to be deployed (targeted to servers and staged by the deployment process) and then activated.
Can you access any other part of the application? What's the web service stack being used? Axis will give you a web application containing test consoles, so it should be possible to access that generated page on the new site to see what kind of response you get.
If none of that behaves, there is a specific debug flag related to HTTP communication which might shed some light - weblogic.servlet.HTTPDebug, which you can enable from inside the Administration Console by going to Servers -> and then clicking the Debug tab.
Let me know if any of that helps.