-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Dan,
On 1/29/16 3:55 PM, Hrivnak, Dan wrote:
> In case anyone was following this or seeing similar issues, I was
> able to track it down. When debugging into the Axis library code
> itself I was able to see one more frame of the stack trace
> (java
In case anyone was following this or seeing similar issues, I was able to track
it down. When debugging into the Axis library code itself I was able to see one
more frame of the stack trace
(java.security.InvalidAlgorithmParameterException: parameter object not a
ECParameterSpec) before it got
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Dan,
On 1/25/16 9:28 AM, Hrivnak, Dan wrote:
> Thank you Chris! I’m glad to hear that Tomcat should have nothing
> to do with this as that helps narrow down what I should look at.
> The unit test (really an integration test) spins up an app server
> u
Thank you Chris! I’m glad to hear that Tomcat should have nothing to do with
this as that helps narrow down what I should look at. The unit test (really an
integration test) spins up an app server using Guice and makes a call to the
same remote service (verified same URL, certificate chains, etc
Dan,
On 1/21/16 2:57 PM, Hrivnak, Dan wrote:
> Environments:
> * Mac OS X 10.10.5; Tomcat 7.0.67, 8.0.30; Java 1.8.0_60
> * RHEL 6 (Kernel 2.6.32); Tomcat 7.0.67; Java 1.8.0_60
>
> Problem:
> Making an outgoing HTTPS connection from Axis2 client code living inside the
> war, I get a failure duri
