Hi Sagi
Are you able to resolve this issue? I am getting the same error when I try 
to run axis2 client to connect to a service using "https". Below is my 
environment:

client side:
----------------
Java 1.5.0_15-b04
Windows xp 
axis2 1.4.1

server side:
-----------------

Java 1.4.2
axis2 1.3 deployed with my sample service under WAS 6.0 running under 
unix.

When I tried client with axis2 1.3 I am getting totally different errors. 
Please let me know your solution and would like to resolve this problem.

Thanks in advance
Ramesh 



Sagi Mann <[EMAIL PROTECTED]> 
09/25/2008 04:23 AM
Please respond to
[email protected]


To
[email protected]
cc

Subject
Re: SSL: ValidatorException: PKIX path building failed






I have an update:
The sample standalone application only behaves as expected when launched
from outside NetBeans 5.5.1 (using cmdline ANT). I.e. when no truststore 
is
configured, the error occurs, and when it is set, the webservice is 
invoked
correctly. As far as running a servlet client (not standalone), the 
servlet
client behaves as expected when deployed from within/outside NetBeans, and
tested via a browser.

I still don't know why NB has an impact, but I'll investigate this later 
on.

thanks...
--
View this message in context: 
http://www.nabble.com/SSL%3A-ValidatorException%3A-PKIX-path-building-failed-tp19569509p19665120.html

Sent from the Axis - User mailing list archive at Nabble.com.


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]




-----------------------------------------
________________________________________________________
DTCC DISCLAIMER: This email and any files transmitted with it are
confidential and intended solely for the use of the individual or
entity to whom they are addressed. If you have received this email
in error, please notify us immediately and delete the email and any
attachments from your system. The recipient should check this email
and any attachments for the presence of viruses.  The company
accepts no liability for any damage caused by any virus transmitted
by this email.

Reply via email to