• 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

Calling Axis2 WebService deployed on JBoss5

 
Greenhorn
Posts: 8
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hi.

I have an Axis2-1.4 web service deployed on JBoss 5.0. When I call the service from a client I get the following exception: java.net.ConnectException
Connection refused: connect

I can navigate to the WSDL, and if I call the server from the browser with GET it works, but I cannot call it from a client. When I deploy it on Tomcat it works fine.

Can anyone help?

Thanks,

Amir
 
Ranch Hand
Posts: 100
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
this might help:
Deploying Axis on JBOSS

Unless you have already resolved the issue, if so care to post what was the problem and how was it solved? We might learn something new, who knows...

Trilochan.

Addendum: Are you using "https" as opposed to "http", if so can you try without s and see if it makes a difference?
 
Amir Kost
Greenhorn
Posts: 8
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
I solved the problem. The problem was that the generated client used my computer's IP address, and JBoss was configured to run on localhost. There are 2 ways to solve this:

1. The better solution is to make JBoss run on the IP address and not on localhost. This is done by using the parameter -b when running JBoss. For example : run.bat -b 192.168.33.33

2. For the lazy people among us, if you are using Eclipse's Web Services Explorer you can add an endpoint using localhost instead of the IP address.
 
Those who dance are thought mad by those who hear not the music. This tiny ad plays the bagpipes:
a bit of art, as a gift, that will fit in a stocking
https://gardener-gift.com
reply
    Bookmark Topic Watch Topic
  • New Topic