• 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
  • Jeanne Boyarsky
  • Ron McLeod
  • Paul Clapham
  • Liutauras Vilda
Sheriffs:
  • paul wheaton
  • Rob Spoor
  • Devaka Cooray
Saloon Keepers:
  • Stephan van Hulst
  • Tim Holloway
  • Carey Brown
  • Frits Walraven
  • Tim Moores
Bartenders:
  • Mikalai Zaikin

Can't access WSDL from Production environment

 
Greenhorn
Posts: 11
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hi All,
I have a webservice which is working fine in test environment, but if I access the same webservice from production environment it is throwing error. I can access the WSDL (production envt) from web browser but not from the client app. Webservice is deployed in Weblogic Application server( in AIX 5.3 box). Please let me know the root cause for this.


Thanks & Regards,
Kishore
 
Bartender
Posts: 1952
7
Eclipse IDE Java
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
If you can access it from a webbrowser I highly doubt the problem is on the production server-side. I guess it could be proxy-related, as web-browsers often have proxy settings set correctly as part of a network policy, and the client app might not use the system proxy settings.
 
Ranch Hand
Posts: 88
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Use a HTTP Monitor (I suggest membrane!) to inspect what's happening. Point both browser and WSclient to the monitor and let it redirect to server. Then you'll see what message, including HTTP headers, each of them is sending and properly compare, and also see response message from each.

A browser should send basic HTTP GET request, os if it's not proxy related it may also be some junk your client is adding and is angering the server.

Personally I think it's some security config in production environment. We use to not worry with security in development env and when deploy in production env we find problems. It's always important to have a test env identical to production env, preferably they being VMs so that you can just clone production env VM to create a test env VM.
 
Mo-om! You're embarassing me! Can you just read a tiny ad like a normal person?
a bit of art, as a gift, the permaculture playing cards
https://gardener-gift.com
reply
    Bookmark Topic Watch Topic
  • New Topic