Solved

Axis/JWSDP1.4 interoperability (using HTTP Proxy)

Posted on 2004-09-01
5
271 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
5 Comments
 
LVL 23

Expert Comment

by:rama_krishna580
ID: 12119884
0
 

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

Microsoft Certification Exam 74-409

Veeam® is happy to provide the Microsoft community with a study guide prepared by MVP and MCT, Orin Thomas. This guide will take you through each of the exam objectives, helping you to prepare for and pass the examination.

Question has a verified solution.

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

Verbose logging is used to diagnose garbage collector problems. By default, -verbose:gc output is written to either native_stderr.log or native_stdout.log.   It is also possible to redirect the logs to a user-specified file. This article will de…
There are numerous questions about how to setup an IBM HTTP Server to be administered from WebSphere Application Server administrative console. I do hope this article will wrap things up and become a reference for this task. You need three things…
Along with being a a promotional video for my three-day Annielytics Dashboard Seminor, this Micro Tutorial is an intro to Google Analytics API data.
This video shows how to quickly and easily add an email signature for all users on Exchange 2016. The resulting signature is applied on a server level by Exchange Online. The email signature template has been downloaded from: www.mail-signatures…

803 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