[ptp-dev] SAXParseException with PE JAXB resource manager

[Dave Wootton <dwootton@xxxxxxxxxx>]

I modified my PE JAXB resource manager
to specify 

        <monitor-data
schedulerType="PE">
         
      <driver>
         
              <name></name>
         
      </driver>
        </monitor-data>

When I start the resource manager and
when I run my test program I get the following exception

org.xml.sax.SAXParseException:
cvc-complex-type.2.4.b: The content of element 'scheme' is not complete.
One of '{el1}' is expected.
     
  at org.apache.xerces.util.ErrorHandlerWrapper.createSAXParseException(Unknown
Source)
     
  at org.apache.xerces.util.ErrorHandlerWrapper.error(Unknown
Source)
     
  at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown
Source)
     
  at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown
Source)
     
  at org.apache.xerces.impl.xs.XMLSchemaValidator$XSIErrorReporter.reportError(Unknown
Source)
     
  at org.apache.xerces.impl.xs.XMLSchemaValidator.reportSchemaError(Unknown
Source)
     
  at org.apache.xerces.impl.xs.XMLSchemaValidator.elementLocallyValidComplexType(Unknown
Source)
     
  at org.apache.xerces.impl.xs.XMLSchemaValidator.elementLocallyValidType(Unknown
Source)
     
  at org.apache.xerces.impl.xs.XMLSchemaValidator.processElementContent(Unknown
Source)
     
  at org.apache.xerces.impl.xs.XMLSchemaValidator.handleEndElement(Unknown
Source)
     
  at org.apache.xerces.impl.xs.XMLSchemaValidator.endElement(Unknown
Source)
     
  at org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanEndElement(Unknown
Source)
     
  at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown
Source)
     
  at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown
Source)
     
  at org.apache.xerces.parsers.XML11Configuration.parse(Unknown
Source)
     
  at org.apache.xerces.parsers.XML11Configuration.parse(Unknown
Source)
     
  at org.apache.xerces.jaxp.validation.StreamValidatorHelper.validate(Unknown
Source)
     
  at org.apache.xerces.jaxp.validation.ValidatorImpl.validate(Unknown
Source)
     
  at javax.xml.validation.Validator.validate(Unknown Source)
     
  at org.eclipse.ptp.rm.lml.core.util.JAXBUtil.validate(JAXBUtil.java:245)
     
  at org.eclipse.ptp.rm.lml.core.util.JAXBUtil.unmarshal(JAXBUtil.java:530)
     
  at org.eclipse.ptp.rm.lml.internal.core.model.LguiItem.update(LguiItem.java:475)
     
  at org.eclipse.ptp.rm.lml.core.LMLManager.update(LMLManager.java:261)
     
  at org.eclipse.ptp.rm.lml.monitor.core.LMLResourceManagerMonitor$MonitorJob.run(LMLResourceManagerMonitor.java:92)
     
  at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)

The active Jobs view and the Inactive
Jobs views have column headings step, owner, queue, wall, queuedata, dispatch
date, totalcores and status. The active jobs view updates to show an entry
for my application very briefly, 1 second or less, when the application
terminates, then the inactive jobs view is updated with the job info. Stdout
output seems to be held until the application terminates then is displayed
in the console window.

If I specify the schedulerType as OPENMPI,
then I don't get the exception, the job appears in the Active Jobs view
and moves to the Inactive Jobs view, but there is only a single column
displaying the job id in both views.

I also have a stdout-parser defined


         
              <stdout-parser
delim="\n">
         
               
      <target
ref="@jobId">
         
               
              <match>
         
               
               
      <_expression_>::::PoePid=([0-9]+)::::</_expression_>
         
               
               
      <set
field="name">
         
               
               
              <entry
valueGroup="1"/>
         
               
               
      </set>
         
               
               
      <set
field="value">
         
               
               
              <entry
value="RUNNING"/>
         
               
               
      </set>
         
               
              </match>
         
               
      </target>
         
              </stdout-parser>

Could that have anything to do
with the stdout output apparently being buffered?


Dave