axis-java-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Christian Gosch" <christian.go...@inovex.de>
Subject SOAP/ssl: Axis2 1.4.1 (client to remote) vs. IBM WebSphere 6.0.2 AdminClient (to local)
Date Thu, 03 Dec 2009 13:56:12 GMT
Hi,

in a J2EE web application running on IBM WebSphere 6.0.2 we use Axis2 
1.4.1 as WS client to execute SOAP calls to a remote host via SSL *and* 
the IBM WebSphere AdminClient (from inside the app) to execute tasks on 
the local host.

When AdminClient is used first *before* first use of Axis2 client (ssl), 
everything is fine and both clients work also on subsequent operations.

BUT: When Axis2 client (ssl) is used first *before* first use of 
AdminClient, then AdminClient fails to connect permanently, but Axis2 
runs fine.

Has anybody experienced similar things?

This may include using CXF or other WS client libraries *for ssl 
connections* together with IBM WebSphere AdminClient.


Thanks for any help on this topic. (Yes, there is another instance of 
this topic, but this one is shorter :-)

Regards,
-- 
Dipl.-Inform. Christian Gosch, PMI PMP
Systems Architecture, Project Management

inovex GmbH
Büro Pforzheim
Karlsruher Strasse 71
D-75179 Pforzheim
Tel: +49 (0)7231 3191-85
Fax: +49 (0)7231 3191-91
c.gosch@inovex.de
www.inovex.de

Sitz der Gesellschaft: Pforzheim
AG Mannheim, HRB 502126
Geschäftsführer: Stephan Müller 




Mime
View raw message