I am using JNDI to connect to a Sun One Directory Server from
Websphere. It works fine when running Websphere on our developer
(windows-based) workstations but when we put it on the 400 it gets
into an (seemingly) infinite loop. We looked at the network traffic
through a sniffer and it just keeps repeating itself even after an ssl
ALERT (Level: Fatal, Description: Certificate Unkown) pops up.

The message that keeps repeating complains about an incorrect checksum...

We have verified that:
1.) we are using the 1.3 jvm.
2.) the certificate is imported into the cacerts file of said jvm.
3.) both environments (workstation and server) are using the
com.ibm.jsse.IBMJSSEProvider

Can anyone help? 

Here is the beginning of one of the logs which proves a couple of the
assertions that I have made:

WebSphere Platform 5.0 [ND 5.0.2 ptf2M0325.01] [BASE 5.0.2
ptf2M0325.01] [CLIENT 5.0.2 ptf2M0325.01]  running with process name
S02T
Host Operating System is OS/400, version V5R1M0
Java version = 1.3.1, Java Compiler = jitc_de, Java VM name = Classic
VM
was.install.root = /QIBM/ProdData/WebAS5/Base
user.install.root = /QIBM/UserData/WebAS5/Base/default
Java Home = /QIBM/ProdData/Java400/jdk13
ws.ext.dirs = 
/QIBM/ProdData/WebAS5/Base/java/tools:/QIBM/UserData/WebAS5/Base/default/classes:/QIBM/ProdData/WebAS5/Base/classes:/Q
Classpath = 
/QIBM/UserData/WebAS5/Base/default/properties:/QIBM/ProdData/WebAS5/Base/properties:/QIBM/ProdData/WebAS5/Base/lib/boots
Java Library path =
/QSYS.LIB/QEJBAS5.LIB:/QSYS.LIB/QGPL.LIB:/QSYS.LIB/QTEMP.LIB:/QSYS.LIB/WEBTOOLS.LIB:/QSYS.LIB/WSTOOLS.LIB:/QSYS.
Current trace specification = *=all=enabled

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:

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

This mailing list archive is Copyright 1997-2022 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.