Hi, Andy, The error code went away after I updated Fuseki/TDB to the latest version. Thanks a lot.
Also, merging the local RDF file (containing measurement data) into the remote existing named graph has been successfully completed. Again, thanks for warm help. One last question. Can we 'UNDO' the merging (like roll back) after successfully merged -- if the user wants to try different RDF data? Cheers, Frank ________________________________ From: Andy Seaborne <[email protected]> To: [email protected] Sent: Monday, September 3, 2012 8:14 AM Subject: Re: Merge from Remote named graph and local RDF file On 31/08/12 18:12, Frank Lee wrote: > Thanks a lot, Andy I'll try it shortly. > > This morning, I put new war at my server to deploy. Somehow, saw the > following exceptions when I tried to load one of named graph. > Error code is 500. > > What could be possible root cause then? Thanks,. This is occasional? If so, your running an old version (of Fuseki). Andy > > Cheers, > Frank > > ...... > INFO [33] Query = PREFIX cim: <http://iec.ch/TC57/2010/CIM-schema-cim15#> > PREFIX xsd: <http://www.w3.org/2001/XMLSchema#> PREFIX rdf: > <http://www.w3.org/1999/02/22-rdf-syntax-ns#> SELECT DISTINCT ?id ?name > ?transformer ?windingInfo ?grounded WHERE { { GRAPH > <http://dm360.nexant.com/graphs/HZhang/berkeley/6.0/20120820172059> { > ?id cim:IdentifiedObject.name ?name . ?id rdf:type > cim:DistributionTransformerWinding . ?id > cim:DistributionTransformerWinding.Transformer ?transformer . ?id > cim:DistributionTransformerWinding.WindingInfo ?windingInfo . ?id > cim:DistributionTransformerWinding.grounded ?grounded } } } > WARN [33] RC = 500 : Currently in a transaction > (location:/home/hzhang/tdb/tdb2/) > com.hp.hpl.jena.sparql.JenaTransactionException: Currently in a transaction > (location:/home/hzhang/tdb/tdb2/) > at >com.hp.hpl.jena.tdb.transaction.DatasetGraphTransaction.checkNotActive(DatasetGraphTransaction.java:94) > at >com.hp.hpl.jena.tdb.migrate.DatasetGraphTrackActive.begin(DatasetGraphTrackActive.java:51) > at >org.apache.jena.fuseki.servlets.HttpAction.beginRead(HttpAction.java:87) > at >org.apache.jena.fuseki.servlets.SPARQL_Query.execute(SPARQL_Query.java:228) > at >org.apache.jena.fuseki.servlets.SPARQL_Query.executeWithParameter(SPARQL_Query.java:197) > at >org.apache.jena.fuseki.servlets.SPARQL_Query.perform(SPARQL_Query.java:113) > at >org.apache.jena.fuseki.servlets.SPARQL_ServletBase.doCommon(SPARQL_ServletBase.java:92) > at >org.apache.jena.fuseki.servlets.SPARQL_Query.doGet(SPARQL_Query.java:93) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:707) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:820) > at >org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:547) > at >org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1359) > at >org.eclipse.jetty.servlets.UserAgentFilter.doFilter(UserAgentFilter.java:77) > at >org.eclipse.jetty.servlets.GzipFilter.doFilter(GzipFilter.java:181) > at >org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1330) > at >org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:478) > at >org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:225) > at >org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:941) > at >org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:409) > at >org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:186) > at >org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:875) > at >org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:117) > at >org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:110) > at org.eclipse.jetty.server.Server.handle(Server.java:349) > at >org.eclipse.jetty.server.HttpConnection.handleRequest(HttpConnection.java:441) > at >org.eclipse.jetty.server.HttpConnection$RequestHandler.headerComplete(HttpConnection.java:919) > at org.eclipse.jetty.http.HttpParser.parseNext(HttpParser.java:582) > at >org.eclipse.jetty.http.HttpParser.parseAvailable(HttpParser.java:218) > at >org.eclipse.jetty.server.BlockingHttpConnection.handle(BlockingHttpConnection.java:50) > at >org.eclipse.jetty.server.nio.BlockingChannelConnector$BlockingChannelEndPoint.run(BlockingChannelConnector.java:293) > at >org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:598) > at >org.eclipse.jetty.util.thread.QueuedThreadPool$3.run(QueuedThreadPool.java:533) > at java.lang.Thread.run(Unknown Source) > INFO [33] 500 Currently in a transaction (location:/home/hzhang/tdb/tdb2/) > INFO [32] 200 OK > > > > ++++ > > > > ________________________________ > From: Andy Seaborne <[email protected]> > To: [email protected] > Sent: Friday, August 31, 2012 2:36 AM > Subject: Re: Merge from Remote named graph and local RDF file > > On 30/08/12 19:34, Frank Lee wrote: >> One more question: >> >> What will be the best way to merge tow endpoints, one is the namedGraph at >> remote server and one is the local RDF file. >> For example, the graph does not have status value, but the local rdf file >> has. Thanks. >> >> Cheers, >> Frank. > > Just add the contents of one graph into another > > Remote: > > POST local graph to remote graph > > Local: > > Read remote graph into same model as local graph. > > Take a copy of the target first if you want 3 graphs: 2 originals and > one which is the merge of the two. > > Andy >
