Go Premium for a chance to win a PS4. Enter to Win

x
?
Solved

Axis/JWSDP1.4 interoperability (using HTTP Proxy)

Posted on 2004-09-01
5
Medium Priority
?
287 Views
Last Modified: 2013-12-10
We are currently working on a Web Services client program which sits within WebSphere as a number of EJB's and makes WebService calls to the outside world.

In order to create and make the WebService call we are trying to use a combination of JWSDP 1.4 and Axis 1.2.  The reason for this is that we need some of the more advanced facilities of both of the solutions.  So basically we use JWSDP 1.4 for everything, except for the Web Service transport itself, which we use Axis for.

The solution works perfectly well under normal circumstances, however if we configure an http proxy (using the JVM params http.proxyHost and proxyPort) the whole thing starts failing.  The reason for this seems to be that Axis is making an invalid request to the HTTP Proxy, as it returns "Invalid Http Header".

I've tried various different HTTP proxies so I'm pretty sure that they aren't at fault.  I think the problem is that Axis is omitting part of the URL when it makes the Web Service request.  If I use Axis's TCP Monitor as my proxy, the invalid call looks something like:

POST /axis/Blah.jsp

Where as a normal request just using URL Connection looks like:

GET http://mymachine/axis/Blah.jsp

My guess is that the omitting the machine section of the URL for some reason, but why I don't know!  I've looked through the Log4j output that Axis throws out, and all looks well until the actual call is made - I can see further up the log that it has identified the machine correctly, so at some point it did know!

My question is, has anyone else encountered this problem.  Alternatively, has anyone tried to mix JWSDP 1.4 and Axis - if so what combination of libraries did you use, as that seems to be the key to the problem.

Thanks in advance for any help
0
Comment
Question by:krytenxpert
  • 2
4 Comments
 

Author Comment

by:krytenxpert
ID: 12241059
Still no idea on this - we've not managed to get any further, so I guess just close the question.
0
 

Author Comment

by:krytenxpert
ID: 12380939
We've now upgraded to Axis 1.2RC1 and the proxy has now started working - just in case anyone else comes across this in the future.
0
 

Accepted Solution

by:
modulo earned 0 total points
ID: 12624079
PAQed with points refunded (500)

modulo
Community Support Moderator
0

Featured Post

Free Tool: SSL Checker

Scans your site and returns information about your SSL implementation and certificate. Helpful for debugging and validating your SSL configuration.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Configure Web Service (server application) I. Configure security for Web Services methods First, we need to protect Session bean which implements the service: 1. Open EJB deployment descriptor (ejb-jar.xml) in the EJB project that contains you…
Upgrading Tomcat – There are a couple of methods to upgrade Tomcat is to use The Apache Installer is to download and unzip and run the services.bat remove|install Tomcat6 Because of the App that we are working with, we can only use Tomcat 6.…
Is your data getting by on basic protection measures? In today’s climate of debilitating malware and ransomware—like WannaCry—that may not be enough. You need to establish more than basics, like a recovery plan that protects both data and endpoints.…
Whether it be Exchange Server Crash Issues, Dirty Shutdown Errors or Failed to mount error, Stellar Phoenix Mailbox Exchange Recovery has always got your back. With the help of its easy to understand user interface and 3 simple steps recovery proced…

876 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question