Hi
Replace it by this, but substitute ${GLOBUS_LOCATION} with the
value of the environment variable ${GLOBUS_LOCATION}
<?xml version="1.0" encoding="UTF-8"?>
<jndiConfig xmlns="http://wsrf.globus.org/jndi/config";>
<!-- Configuration delta (addition) fpr a Local Resource Manager -->
<!-- Configuration for Managed Job *Factory* Service -->
<service name="ManagedJobFactoryService">
<!-- LRM configuration: Fork -->
<resource
name="ForkResourceConfiguration"
type="org.globus.exec.service.factory.FactoryResourceConfiguration">
<resourceParams>
<parameter>
<name>
factory
</name>
<value>
org.globus.wsrf.jndi.BeanFactory
</value>
</parameter>
<parameter>
<name>
localResourceManagerName
</name>
<value>
Loadleveler
</value>
</parameter>
<!-- Site-specific scratchDir
Default: ${GLOBUS_USER_HOME}/.globus/scratch
<parameter>
<name>
scratchDirectory
</name>
<value>
${GLOBUS_USER_HOME}/.globus/scratch
</value>
</parameter>
-->
<parameter>
<name>
substitutionDefinitionsFile
</name>
<value>
${GLOBUS_LOCATION}/etc/gram-service-Fork/substitution-definition.properties
</value>
</parameter>
<parameter>
<name>
substitutionDefinitionsRefreshPeriod
</name>
<value>
<!-- MINUTES -->
480
</value>
</parameter>
<parameter>
<name>
enableDefaultSoftwareEnvironment
</name>
<value>
false
</value>
</parameter>
</resourceParams>
</resource>
</service>
</jndiConfig>
-Martin
Asish M Madhu wrote:
> Hello Martin,
>
> Please find the content of jndi-config.xml
> ($GLOBUS_LOCATION/etc/gram-service-Loadleveler/jndi-config.xml)
>
>
>
> -------------------------------------------------------------------------------------------------------------
>
> <?xml version="1.0" encoding="UTF-8"?>
> <jndiConfig xmlns="http://wsrf.globus.org/jndi/config";>
>
> <!-- Configuration delta (addition) fpr a Local Resource Manager -->
>
> <!-- Configuration for Managed Job *Factory* Service -->
>
> <service name="ManagedJobFactoryService">
> <!-- LRM configuration: Loadleveler -->
> <resource
> name="LoadlevelerResourceConfiguration"
>
> type="org.globus.exec.service.factory.FactoryResourceConfiguration">
> <resourceParams>
> <parameter>
> <name>
> factory
> </name>
> <value>
> org.globus.wsrf.jndi.BeanFactory
> </value>
> </parameter>
> <parameter>
> <name>
> localResourceManagerName
> </name>
> <value>
> Loadleveler
> </value>
> </parameter>
> <parameter>
> <name>
> scratchDirectory
> </name>
> <value>
> /.globus/scratch
> </value>
> </parameter>
> </resourceParams>
> </resource>
>
> </service>
>
>
> </jndiConfig>
>
> ----------------------------------------------------------------------------------------------------------
>
> Thanking you
>
> Regards
> Asish
>
> On Tue, Aug 25, 2009 at 5:03 PM, Martin Feller <[email protected]> wrote:
>
>> We don't officially support LL, but a group on TeraGrid
>> used LoadLeveler too. I assume it's a problem in
>> $GLOBUS_LOCATION/etc/gram-service-Loadleveler/jndi-config.xml
>> Please send the content of that file.
>>
>> -Martin
>>
>> Asish M Madhu wrote:
>>> Dear All,
>>>
>>> I was trying to integrate GLOBUS 4.0.7 with Loadleveler (version:3) in
>> AIX
>>> 5.2 64 bit machine. I have installed GLOBUS 4.0.7 successfully using 64
>> bit
>>> flavour.
>>>
>>> For integrating with Loadleveler i used the llgrid.tar file from the
>> already
>>> installed Loadleveler. Untared it and run the deploy.sh executable which
>>> will automatically integrate Globus with existing Loadleveler.
>>>
>>> The installation of the integration package didnt throw any error . But
>>> after this integration package is installed I cant start the Globus
>>> Container.
>>>
>>>
>>> I get the below error in the container.log file:
>>>
>>>
>>>
>>> vi $GLOBUS_LOCATION/var/container.log
>>>
>>> *"/usr/local/GARUDA/GLOBUS-4.0.7/var/container.log" 2 lines, 264
>> characters
>>> Failed to start container: Failed to initialize
>> 'ManagedJobFactoryService'
>>> service [Caused by: ; nested exception is:
>>> javax.naming.NamingException: Bean initialization failed [Root
>>> exception is java.lang.RuntimeException: java.lang.NumberFormatException:
>>> null]]*
>>> ~
>>>
>>>
>>> ----------------------------
>>>
>>> What could be the problem? The integration package creates the below file
>> in
>>> Globus path.
>>>
>>> $GLOBUS_LOCATION/lib/perl/Globus/GRAM/JobManager/loadleveler.pm
>>> $GLOBUS_LOCATION/etc/gram-service/globus_gram_fs_map_config.xml
>>> $GLOBUS_LOCATION/etc/gram-service-Loadleveler/jndi-config.xml
>>> $GLOBUS_LOCATION/etc/grid-services/jobmanager-loadleveler
>>> $GLOBUS_LOCATION/etc/globus-loadleveler.conf
>>> $GLOBUS_LOCATION/libexec/globus-scheduler-provider-loadleveler
>>>
>>> But when i remove these files the container starts without any problem.
>> How
>>> can I integrate Globus with Loadleveler ? Kindly help me.
>>> Thanks in advance
>>>
>>> Regards
>>> Asish M Madhu
>>> [email protected]
>>>
>>
>
>
