× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



David Gibbs wrote:
Oddly though ... I put a sniffer on the system I'm trying to connect to
... and it's not capturing any packets from my java app. If I telnet
into that particular port, from the System i, packets are captured.

So it appears that my java app isn't even sending anything out ... which
is confusing in itself.

Ok, here's something that's odd.

I decided to write a simple test program to see if I could get a java
app to talk SSL by itself (outside of my client code).

The code can be found here: http://code.midrange.com/b671f289b4.html

When I run it as a QPGMR class user, I get the following error:
java -Djava.version=1.4 -classpath bin TestSSL

Consturcting URL

Opening connection

Connecting to URL

javax.net.ssl.SSLException: The certificate container *SYSTEM could
not be accessed.
at java.lang.Throwable.<init>(Throwable.java:195)

at java.lang.Exception.<init>(Exception.java:41)

at java.io.IOException.<init>(IOException.java:40)

at javax.net.ssl.SSLException.<init>(Unknown Source)

at
com.ibm.as400.ibmonly.net.ssl.SSLContextImpl.initialize(SSLContextImpl.java:632)

at
com.ibm.as400.ibmonly.net.ssl.SSLSocketImpl.init(SSLSocketImpl.java:455)


Based on a message in the archives, I tried running the same program as
a QSECOFR class user ... and it hung up on connecting to the URL:

java -Djava.version=1.4 -classpath bin TestSSL

Consturcting URL

Connecting to URL

Opening connection

javax.net.ssl.SSLHandshakeException: No compatible cipher suite
available between SSL end points.
at java.lang.Throwable.<init>(Throwable.java:195)

at java.lang.Exception.<init>(Exception.java:41)

at java.io.IOException.<init>(IOException.java:40)

at javax.net.ssl.SSLHandshakeException.<init>(Unknown Source)

at
com.ibm.as400.ibmonly.net.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:1736)

at com.ibm.net.ssl.www.protocol.https.b.o(Unknown Source)

at com.ibm.net.ssl.www.protocol.https.q.connect(Unknown
Source)
at com.ibm.net.ssl.www.protocol.https.t.connect(Unknown
Source)
at TestSSL.main(TestSSL.java:8)


I guess I'm getting further ... at least I got packets across the wire
this time, but it's still not working correctly.

david



As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.