Hi Michael,

Thanks for the response. I do have FILEMGR_HOME set in my environment, but this 
problem only happens when I am running my system without the resource manager 
and batch_stub.  When I run my system with just filemgr and workflow manager, I 
do not get this problem, i.e. the pge_metadata file is written out just fine. I 
do export my FILEMGR_HOME variable though and I start the resource manager and 
batch_stub from the same script that FILEMGR_HOME is exported from. But I'm 
wondering if either of them are not seeing it for some reason. I will do some 
investigating in that area.

Thanks,
Val
 


Valerie A. Mallder
New Horizons Deputy Mission System Engineer
Johns Hopkins University/Applied Physics Laboratory


> -----Original Message-----
> From: [email protected] [mailto:[email protected]] On Behalf Of Michael
> Starch
> Sent: Monday, August 31, 2015 5:47 PM
> To: [email protected]
> Subject: RE: (to Michael Starch) Problems Using Serializable Metadata after
> Loading Validation Layer
> 
> Valerie,
> 
> My issue was actually using "System.setProperties(Properties properties)"
> in my code as this clobbers all existing system properties in your current 
> JVM.
> The solution was to set each specific property I needed using "System.
> setPropertie(String name, String value)" as this doesn't clobber other values.
> 
> If you are not calling these things programmaticly, the it is a different 
> issue. I will
> happily look at any errors If you supply them but a quick
> note: FILEMGR_HOME may not be set is this environment variable defined in
> your?
> 
> Michael
> On Sep 1, 2015 4:23 AM, "Mallder, Valerie" <[email protected]>
> wrote:
> 
> > Hi Michael,
> >
> > Could you explain your fix to this issue with more detail?  I am
> > having the same problem. The default filemgr.properties file sets
> > these two values to directories that do not exist (so I have to set them to
> 'something'
> > valid). Here are the default settings:
> >
> > # XML repository manager configuration
> > org.apache.oodt.cas.filemgr.repositorymgr.dirs=file:///dir1,file:///di
> > r2
> >
> > # XML validation layer configuration
> > org.apache.oodt.cas.filemgr.validation.dirs=file:///dir1,file:///dir2
> >
> >
> > And this is what I set them to:
> >
> > # XML repository manager configuration
> >
> > org.apache.oodt.cas.filemgr.repositorymgr.dirs=file://[FILEMGR_HOME]/p
> > olicy/core
> >
> > # XML validation layer configuration
> >
> > org.apache.oodt.cas.filemgr.validation.dirs=file://[FILEMGR_HOME]/poli
> > cy/core
> >
> > And I still get the error.  Could you explain more about how I can
> > work around this issue?
> >
> > Thanks,
> > Valerie
> >
> >
> > > -----Original Message-----
> > > From: [email protected] [mailto:[email protected]] On Behalf Of
> > Michael
> > > Starch
> > > Sent: Friday, July 31, 2015 12:20 PM
> > > To: [email protected]
> > > Subject: Re: Problems Using Serializable Metadata after Loading
> > Validation Layer
> > >
> > > All,
> > >
> > > I found the issue.
> > >
> > > Using "System.setProperties()" and filling it from properties read
> > > from filemanager.properties clears out other properties setup by the
> > > system
> > which was
> > > needed in the XML calls for SerializableMetadata. I did the above
> > > call
> > to setup
> > > properties needed by the XMLValidationLayer
> > >
> > > To fix set only the properties you need individually.  This adds to
> > > the
> > System
> > > properties, not erasing them.
> > >
> > > System.setProperty("org.apache.oodt.cas.filemgr.repositorymgr.dirs",
> > ...);
> > >
> > > System.setProperty("org.apache.oodt.cas.filemgr.validation.dirs",
> > > ...);
> > >
> > > -Michael
> > >
> > >
> > > On Thu, Jul 30, 2015 at 4:20 PM, Michael Starch <[email protected]>
> > wrote:
> > >
> > > > Here is the stack trace, but this only happens after a completely
> > > > unrelated peice of the process load the XML Validation Layer.
> > > >
> > > > -Michael
> > > >
> > > > java.lang.NullPointerException
> > > >     at
> > > >
> > com.sun.org.apache.xml.internal.serializer.ToStream.<init>(ToStream.ja
> > va:143)
> > > >     at
> > > >
> > >
> >
> com.sun.org.apache.xml.internal.serializer.ToXMLStream.<init>(ToXMLStream.java:
> > > 67)
> > > >     at
> > > >
> > >
> > com.sun.org.apache.xml.internal.serializer.ToUnknownStream.<init>(ToUn
> > knownStr
> > > eam.java:143)
> > > >     at
> > > >
> > >
> > com.sun.org.apache.xalan.internal.xsltc.runtime.output.TransletOutputH
> > andlerFacto
> > > ry.getSerializationHandler(TransletOutputHandlerFactory.java:160)
> > > >     at
> > > >
> > >
> > com.sun.org.apache.xalan.internal.xsltc.trax.TransformerImpl.getOutput
> > Handler(Tra
> > > nsformerImpl.java:461)
> > > >     at
> > > >
> > >
> > com.sun.org.apache.xalan.internal.xsltc.trax.TransformerImpl.transform
> > (Transforme
> > > rImpl.java:344)
> > > >     at
> > > > org.apache.oodt.cas.metadata.SerializableMetadata.writeMetadataToX
> > > > mlSt
> > > > ream(SerializableMetadata.java:157)
> > > >
> > > >
> > > > On Thu, Jul 30, 2015 at 4:16 PM, Chris Mattmann
> > > > <[email protected]>
> > > > wrote:
> > > >
> > > >> Mike can you give some specific line numbers? I can help look
> > > >>
> > > >> —
> > > >> Chris Mattmann
> > > >> [email protected]
> > > >>
> > > >>
> > > >>
> > > >>
> > > >>
> > > >>
> > > >> -----Original Message-----
> > > >> From: <[email protected]> on behalf of Michael Starch <
> > > >> [email protected]>
> > > >> Reply-To: <[email protected]>
> > > >> Date: Thursday, July 30, 2015 at 4:03 PM
> > > >> To: <[email protected]>
> > > >> Subject: Problems Using Serializable Metadata after Loading
> > > >> Validation Layer
> > > >>
> > > >> >All,
> > > >> >
> > > >> >I am getting a NullPointerException deep in the XML library if I
> > > >> >try to use the SerializableMetadata's write to xml function
> > > >> >after I load in the XML Validation Layer from the filemanager.
> > > >> >However, if I remove the call to load in the XML Validation
> > > >> >Layer, everything works fine.  Any ideas as to what might cause this
> issue?
> > > >> >
> > > >> >Thanks,
> > > >> >
> > > >> >Michael
> > > >>
> > > >>
> > > >>
> > > >
> >

Reply via email to