[Mulgara-dev] dateTime information being corrupted

[Paul Gearon]

The memory-mapping problem... that's where the Java libs are throwing the
error, rather than us, right?  Which system does that happen to you on?
Windows?  (I think you've already answered me here, but I could do with the
refresh).

Did you ever get to try it on another OS?

(BTW, I've done the updates to make Mulgara compile on Java 1.6, but not it
won't compile on Java 1.5!  I'll drop back to using reflection to fix this.
Hopefully you can trial Java 1.6 by the weekend).

Paul

On 11/2/06, David Moll <DMoll at viewpointusa.com> wrote:
>
>  Unfortunately the problem appears to be completely random.  But it is
> happening with more frequency.
>
> I'm trying to get to the point where we can mirror our production system
> with Mulgara replacing TKS.  I believe that we're almost there, with just a
> few last details that need to be worked out.  I went through all of the old
> issues in Kowari on Sourceforge and I didn't see anything related to this,
> but it could be caused by something that doesn't mention dateTime at all,
> naturally.
>
> Or, it could have been fixed in MGR-2!
>
> The only thing that has me hesitant to set up Mulgara on a production
> mirror right now is the memory mapping problem, but I don't think that it is
> a real issue for us on production.
>
> ~Dave
>
>  ------------------------------
> *From:* gearon at gmail.com [mailto:gearon at gmail.com] *On Behalf Of *Paul
> Gearon
> *Sent:* Thursday, November 02, 2006 1:03 PM
> *To:* David Moll
> *Cc:* mulgara-dev at mulgara.org
> *Subject:* Re: [Mulgara-dev] dateTime information being corrupted
>
> Ah, OK.
>
>
> On 11/2/06, David Moll <DMoll at viewpointusa.com> wrote:
> >
> >  Actually we're just doing an insertion of raw triples.  The insert
> > query looks like:
> >
>  <snip/>
>
> >  This is also the query that we run to correct the incorrect dateTime
> > elements, and checking the triples immediately after they are inserted shows
> > the correct information.  So we are reasonably certain the the problem is
> > not in the initial insert query that puts the triples into the data store,
> > but is occurring at some later point.
> >
>
> Doesn't sound like an easy one to track down.
>
> Do you have any way to reproduce this?  I suppose it is completely random?
>
>  Logging is not currently running on our production system.  I have not
> > looked at the log4j-conf.xml file much as of yet.  Our production system
> > is running TKS, so while I can't look at any of that code, I can investigate
> > the logging options that should be turned on the next time we restart the
> > system.
> >
>
> TKS?!?  Erk.  I never knew when TKS releases were built, so I don't know
> which will be your corresponding Kowari.  You may well be looking at a bug
> that was since fixed, but I don't know how to find out.
>
> I'm not about to suggest that you change your production system, but is it
> possible to duplicate it using Mulgara (or a recent Kowari) instead of TKS?
> If this is still a problem then we will need to get to it quickly.  I have a
> feeling that it may be resolved though...
>
> Paul
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mulgara.org/pipermail/mulgara-dev/attachments/20061102/890101af/attachment.html