Was there nothing useful in the container, then? You can edit
$GLOBUS_LOCATION/container-log4j.properties to enable core debugging.
I suspect the change in question in 4.0.7 may be the use of
signing_policy files in the java code. If you have the CA certificate
as a .0 file in /etc/grid-security/certificates, you can create
a .signing_policy file for it of the form:
access_id_CA X509 '/DN/of/the/CA'
pos_rights globus CA:sign
cond_subjects globus /DN/space/it/signs/for/*'
Also make sure to apply the updates for 4.0.7 from http://www.globus.org/toolkit/advisories.html
.
Charles
On Jul 10, 2008, at 1:19 PM, Jim Basney wrote:
Joel Schneider wrote:
Jim Basney wrote:
An EOFException on the client side indicates to me that the server
aborted the connection, so I suggest trying to enable logging on
the server side to diagnose the problem.
Any suggestions for specific logging configuration changes which
might
shed additional light on the problem?
Sorry, Java WS Core logging configuration is outside my expertise.
Hopefully someone else on the list can suggest.
-Jim
