• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Tim Cooke
  • Liutauras Vilda
  • Jeanne Boyarsky
  • paul wheaton
Sheriffs:
  • Ron McLeod
  • Devaka Cooray
  • Henry Wong
Saloon Keepers:
  • Tim Holloway
  • Stephan van Hulst
  • Carey Brown
  • Tim Moores
  • Mikalai Zaikin
Bartenders:
  • Frits Walraven

Deploying Existing Web App With New JWS

 
Ranch Hand
Posts: 129
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hi all,

I've been banging my head against a brick wall for a few days on this, but I'm sure it must be something trivial. Hopefully someone here will have some advice...

In a nutshell, I'm working on an existing web application, running on Weblogic 8.1, in a clustered environment. I've added a new JWS web service which is largely standalone, but it uses controls from elsewhere in the application.

Locally, on my development box, it works perfectly - I can run it from Weblogic Workshop, and see the handy test form to run the web service, as well as seeing the WSDL by pointing my browser at http://localhost:7001/app/path/Service.jws?WSDL

However, I've now built the EAR for the whole application, and deployed it to our test environment (clustered - a mirror (hopefully!) of the production environment).

When I go to http://test-box:7002/app/path/Service.jws?WSDL I see a nasty-looking error page that looks like:

WebService ERROR

Error:
null

Stack Trace:
null

When I try the same URL without the ?WSDL on the end (so just http://test-box:7002/app/path/Service.jws), I see the nice Weblogic Web Service page, showing that it knows there's something there, but it has no content, just the 'Overview' tab, followed by:

Public Information
about Service.jws Web Service

and that's it - locally I see the same thing, but with options for viewing the WSDL and testing the service.

I'm confident that the URL is correct, because if I put rubbish in, I get a different error message.

Reading around, I've found lots of resources for 'how to deploy a web service to a production environment' for Weblogic 7, but much less for 8.1. I've seen references to jwsCompile, for example, which I think is specific to 7, because I can't find any references to it in the 8.1 docs, but perhaps that's wrong?

I'm pretty sure there's a configuration setting I'm missing, or a step in the deployment, but I'm stuck as to what it is!

Any advice gratefully received.

Edit: I should have mentioned that there are two other JWS's in the same app, both of which have the same symptoms as my new one (they've been there for a while, but are unused).

[ July 31, 2008: Message edited by: Mark Newton ]
[ July 31, 2008: Message edited by: Mark Newton ]
 
Mark Newton
Ranch Hand
Posts: 129
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
I've found the solution to this - just in case it helps anyone else, someone on the BEA forum suggested looking at the frontend settings, and referred to this page in the 9.1 docs:

http://edocs.bea.com/wls/docs92/webserv/setenv.html#wp220521

It turned out to be not quite that, but the 'Cluster Address' wasn't set - setting that to contain a list of the nodes in the cluster and restarting fixed the problem.
 
them good ole boys were drinking whiskey and rye singin' this'll be the day that I die. Drink tiny ad.
Gift giving made easy with the permaculture playing cards
https://coderanch.com/t/777758/Gift-giving-easy-permaculture-playing
reply
    Bookmark Topic Watch Topic
  • New Topic