Hello Rachana,
On Fri, 2010-04-09 at 10:58 -0500, Rachana Ananthakrishnan wrote:
> Can you try to run,
$GLOBUS_LOCATION/bin/globus-validate-descriptors,
> and if it reports any errors on your descriptor?
Ok, seems there is an error in jndi-config.xml.
Here is the result of globus-validate-descriptors:
Validating...
Validating jndi-config.xml files...
Validating /usr/local/globus-4.2.1.1/etc/service_core/jndi-config.xml...
Validating /usr/local/globus-4.2.1.1/etc/globus_cas_service/jndi-config.xml...
Validating /usr/local/globus-4.2.1.1/etc/globus_cas_unit_test/jndi-config.xml...
Validating
/usr/local/globus-4.2.1.1/etc/globus_delegation_service/jndi-config.xml...
Validating
/usr/local/globus-4.2.1.1/etc/globus_delegation_test/jndi-config.xml...
Validating
/usr/local/globus-4.2.1.1/etc/globus_java_authz_base_test/jndi-config.xml...
Validating
/usr/local/globus-4.2.1.1/etc/globus_java_saml_authzService/jndi-config.xml...
Validating
/usr/local/globus-4.2.1.1/etc/globus_saml_authz_test/jndi-config.xml...
Validating
/usr/local/globus-4.2.1.1/etc/globus_wsrf_core/client-jndi-config.xml...
Validating /usr/local/globus-4.2.1.1/etc/globus_wsrf_core/jndi-config.xml...
schema_reference.4: Failed to read schema document
'resource.xsd', because 1) could not find the document; 2) the
document could not be read; 3) the root element of the document
is not <xsd:schema>.
cvc-complex-type.2.4.c: The matching wildcard is strict, but no
declaration can be found for element 'wsrf:resourceStore'.
schema_reference.4: Failed to read schema document
'resource.xsd', because 1) could not find the document; 2) the
document could not be read; 3) the root element of the document
is not <xsd:schema>.
schema_reference.4: Failed to read schema document
'resource.xsd', because 1) could not find the document; 2) the
document could not be read; 3) the root element of the document
is not <xsd:schema>.
schema_reference.4: Failed to read schema document
'resource.xsd', because 1) could not find the document; 2) the
document could not be read; 3) the root element of the document
is not <xsd:schema>.
schema_reference.4: Failed to read schema document
'resource.xsd', because 1) could not find the document; 2) the
document could not be read; 3) the root element of the document
is not <xsd:schema>.
cvc-complex-type.2.4.c: The matching wildcard is strict, but no
declaration can be found for element 'wsrf:resourceStore'.
schema_reference.4: Failed to read schema document
'resource.xsd', because 1) could not find the document; 2) the
document could not be read; 3) the root element of the document
is not <xsd:schema>.
schema_reference.4: Failed to read schema document
'resource.xsd', because 1) could not find the document; 2) the
document could not be read; 3) the root element of the document
is not <xsd:schema>.
schema_reference.4: Failed to read schema document
'resource.xsd', because 1) could not find the document; 2) the
document could not be read; 3) the root element of the document
is not <xsd:schema>.
schema_reference.4: Failed to read schema document
'commonj.xsd', because 1) could not find the document; 2) the
document could not be read; 3) the root element of the document
is not <xsd:schema>.
cvc-complex-type.2.4.c: The matching wildcard is strict, but no
declaration can be found for element 'commonj:workmanager'.
schema_reference.4: Failed to read schema document
'commonj.xsd', because 1) could not find the document; 2) the
document could not be read; 3) the root element of the document
is not <xsd:schema>.
cvc-complex-type.2.4.c: The matching wildcard is strict, but no
declaration can be found for element 'commonj:timermanager'.
schema_reference.4: Failed to read schema document
'resource.xsd', because 1) could not find the document; 2) the
document could not be read; 3) the root element of the document
is not <xsd:schema>.
cvc-complex-type.2.4.c: The matching wildcard is strict, but no
declaration can be found for element 'wsrf:resourceStore'.
schema_reference.4: Failed to read schema document
'resource.xsd', because 1) could not find the document; 2) the
document could not be read; 3) the root element of the document
is not <xsd:schema>.
schema_reference.4: Failed to read schema document
'resource.xsd', because 1) could not find the document; 2) the
document could not be read; 3) the root element of the document
is not <xsd:schema>.
schema_reference.4: Failed to read schema document
'resource.xsd', because 1) could not find the document; 2) the
document could not be read; 3) the root element of the document
is not <xsd:schema>.
schema_reference.4: Failed to read schema document
'resource.xsd', because 1) could not find the document; 2) the
document could not be read; 3) the root element of the document
is not <xsd:schema>.
cvc-complex-type.2.4.c: The matching wildcard is strict, but no
declaration can be found for element 'wsrf:cache'.
schema_reference.4: Failed to read schema document
'resource.xsd', because 1) could not find the document; 2) the
document could not be read; 3) the root element of the document
is not <xsd:schema>.
cvc-complex-type.2.4.c: The matching wildcard is strict, but no
declaration can be found for element 'wsrf:resourceStore'.
schema_reference.4: Failed to read schema document
'resource.xsd', because 1) could not find the document; 2) the
document could not be read; 3) the root element of the document
is not <xsd:schema>.
schema_reference.4: Failed to read schema document
'resource.xsd', because 1) could not find the document; 2) the
document could not be read; 3) the root element of the document
is not <xsd:schema>.
schema_reference.4: Failed to read schema document
'resource.xsd', because 1) could not find the document; 2) the
document could not be read; 3) the root element of the document
is not <xsd:schema>.
Validateion
failed.: /usr/local/globus-4.2.1.1/etc/globus_wsrf_core/jndi-config.xml
is not a valid XML document.
>
> Was there more stack trace you can send ?
You can find the complete trace here: http://pastebin.com/Vn4KRt6t
But it is possible at all to use a separate grid map for a service?
Greetings,
Johannes
> Rachana
> On Apr 9, 2010, at 8:38 AM, Johannes Duschl wrote:
>
> > Hello,
> >
> > I'm running gt-4.2.1.1 on Debian Lenny and want to use a separate
> > gridmap-file for a service. The security descriptor looks like this:
> >
> > <serviceSecurityConfig
> > xmlns="http://www.globus.org/security/descriptor/service";
> > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
> > xsi:schemaLocation="http://www.globus.org/security/descriptor
> > name_value_type.xsd"
> > xmlns:param="http://www.globus.org/security/descriptor";>
> >
> > <auth-method>
> > <GSISecureConversation/>
> > </auth-method>
> >
> > <authzChain>
> > <pdps>
> > <interceptor name="gridmap">
> > <parameter>
> > <param:nameValueParam>
> > <param:parameter
> > name="gridmap-file"
> >
> > value="/home/globus/grid-mapfile"/>
> > </param:nameValueParam>
> > </parameter>
> > </interceptor>
> > </pdps>
> > </authzChain>
> >
> > </serviceSecurityConfig>
> >
> > However, when I connect to the service I get the following error:
> >
> > org.globus.wsrf.ResourceContextException: ; nested exception
> > is:
> > javax.naming.NamingException: [JWSCORE-203] Bean
security
> > initialization failed [Root exception is
> > org.globus.wsrf.config.ConfigException: [JWSSEC-245] Error
> > parsing file:
> > "etc/at_jku_tk_service_core/service-instance-
> > security.xml" [Caused by: cvc-complex-type.2.4.c: The matching
> > wildcard is strict, but no declaration can be found for element
> > 'param:nameValueParam'.]]
> > Exception in thread "main" java.lang.NullPointerException
> >
> > I assume there is something wrong with this schema
> >
> > xsi:schemaLocation="http://www.globus.org/security/descriptor
> > name_value_type.xsd
> >
> > but I have no idea what's causing the error. Anybody got a clue?
> >
> > Greetings,
> > Johannes
> >
>
