Home/ Questions/Q 788201
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-14T21:19:28+00:00

I have a simple web service sitting on our internal network. I used SOAPUI

  • 0

I have a simple web service sitting on our internal network. I used SOAPUI to do a bit of testing, generated the service classes from the WSDL , and wrote some java code to access the service. All went as expected as I was able to create the service proxy classes and make calls. Pretty simple stuff. The only speed bump was getting java to trust the certificate from the machine providing the web service. That was not a technical problem, but rather my lack of experience with SSL based web services.
Now onto my problem. I coded up a simple EJB service and deployed it into JBoss Application Server 4.3 and now get the following error in the code that previously worked.

12:21:50,235 WARN  [ServiceDelegateImpl] Cannot access wsdlURL: https://WS-Test/TestService/v2/TestService?wsdl

I can access the wsdl file from a web browser running on the same machine as the application server using the URL in the error message. I can also run the code that access the webservice outside of the application server on the same machine as the application server ( just not from within ). I am at a loss as to where to go from here. I turned on the debug logs in JBOSS and got nothing more than what I showed above. I have done some searching on the net and found the same error in some questions, but those questions had no answers. The web services classes where generated with JAX-WS 2.2 using the wsimport ant task and placed in a jar that is included in the ejb package. JBoss is deployed in RHEL 5.4. I posted this on the JBOSS community forum but have had no responses as of this writing.

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    Having a look at ServiceDelegateImpl it tries to do:

    InputStream is = wsdlURL.openStream();

    where wsdlURL is a non-null URL. That means the trouble lies in the openStream(). I expect the problem to be with the https root certificate; I can imagine that JBoss has it’s own store of acceptable root certificates somewhere, and that your root is not in there.

    What I would do to test this is to deploy the service on a HTTP server, and make the wsdlURL a http URL. If that works, it’s the SSL layer.

    If it is the SSL layer, try to manually add a keyStore, by defining it on the command line, like in the answer to this SO question.

    • 0