Problem connecting to a Sesame 2 remote repository

[PaulZH]

Having successfully Sesame 2.2.4 running on localhost.
Created a repository, loaded some triples which I can see and query in
the Sesame Workbench.

Connecting now from TBC-ME 3.1.1 using the wizard.
Using Sesame's service URL I'm able to fetch the list of repositories,
so I think the connection works.
Choosing a repository then opens TBC, but no custom triples to be seen
or found.

A similar issue was reported by James A Miller end of May, but I was
not able to find more info.

>I am able to successfully connect to the Sesame 2 remote repository, but
>I don't see triples. I don't get any error messages. I was able
>to Fetch Repositories successfully--my store was in the list.

>I ran a SELECT * WHERE {?a ?b ?c} query, and I get results--but only the
>standard OWL, RDF, XSD triples: none of my 'custom' triples that I see
>in the Sesame workbench.

Paul

[PaulZH]

Did find error message.

Error
Mon Oct 05 11:44:09 CEST 2009
Could not connect to Sesame repository
org.openrdf.repository.http.HTTPRepository@1af1ad8

org.openrdf.repository.RepositoryException: java.net.ConnectException:
Connection refused
at org.openrdf.repository.http.HTTPRepositoryConnection.getNamespaces
(HTTPRepositoryConnection.java:304)
at org.topbraid.sesame2.graph.RepositoryGraph.initNamespaces(Unknown
Source)
at org.topbraid.sesame2.graph.RepositoryGraph.<init>(Unknown Source)
at
org.topbraid.sesame2.module.importSesameRemoteRepository.ImportSesameRemoteRepositoryModule.getRDFOutput
(Unknown Source)
at org.topbraid.sparqlmotion.engine.impl.ExecutionEngine.executeModule
(Unknown Source)
at org.topbraid.sparqlmotion.engine.impl.ExecutionEngine.execute
(Unknown Source)
at org.topbraid.sparqlmotion.util.AbstractSMGraphStore.getGraph
(Unknown Source)
at org.topbraid.sparqlmotion.util.AbstractSMGraphStore.getBaseURI
(Unknown Source)

Paul

[James A Miller]

I had moved on to other issues.  I just tried this again (with BigOWLIM), and I still see only the "base" triples, not any of mine.  (They do appear in the Sesame Workbench).

Jim

From:	PaulZH <pa...@proxml.be>
To:	TopBraid Composer Users <topbraid-co...@googlegroups.com>
Date:	10/05/2009 06:16 AM
Subject:	[tbc-users] Problem connecting to a Sesame 2 remote repository
Sent by:	topbraid-co...@googlegroups.com

---

The following line is added for your protection and will be used for analysis if this message is reported as spam: (Raytheon Analysis: IP=209.85.221.140; e-from=grbounce--O7MwAUAAADwl_G2BQLyHjkrnqoVTNO4=james_a_miller=raythe...@googlegroups.com; from=pa...@proxml.be; date=Oct 5, 2009 9:31:40 AM; subject=[tbc-users] Problem connecting to a Sesame 2 remote repository)

[Scott Henninger]

Paul; I have been doing some experiments and have not been able to
reproduce this problem. However, the core issue could be that
Composer ships with Sesame 2.1.2.

I am able to export a model to a Sesame 2.2.4 server (localhost). I
can can then perform a New... for a new connection to that
repository. All of the triples are found OK.

Your log does indicate that thee may be a connection problem. Perhaps
looking at the Tomcat (I'm assuming that is your servlet container)
logs for Sesame will provide some more information?

-- Scott

[PaulZH]

Scott,

Thanks for looking into this.

My workflow is as follows.

With the Sesame workbench (= outside TBC) I create a repository and
then I add an RDF data file to it.
Having done so I can ask for the used namespaces, types and any query
I want.
Results as expected.

Now moving to TBC
Making a new RDF/OWL remote Sesame 2 Connection with params
a filename
a base uri
a service url being http://localhost:8080/openrdf-sesame/

then fetching the repositories, which I do get.
Choosing one, TBC is opening but then no custom triples to be found.

I looked into the Sesame logging, but haven't found anything relevant
yet.
I'll keep searching.

Paul

[Scott Henninger]

Paul; By "custom triples" do you mean triples other than those
contained in the imported rdf, rdfs, owl, and xsd files? If so, then
if may mean that only the imports are being passed by Sesame. What
kind of Sesame repository are you creating - in memory, Java, remote
RDF store?

Do keep in mind that the key difference may be that Composer is using
the 2.1.2 API and you are using Sesame 2.2.4. There may be some
differences here that are causing the problem. We are upgrading to
the Sesame 2.2.4 for the next release of Composer.

-- Scott

On Oct 7, 10:33 am, PaulZH <p...@proxml.be> wrote:
> Scott,
>
> Thanks for looking into this.
>
> My workflow is as follows.
>
> With the Sesame workbench (= outside TBC) I create a repository and
> then I add an RDF data file to it.
> Having done so I can ask for the used namespaces, types and any query
> I want.
> Results as expected.
>
> Now moving to TBC
> Making a new RDF/OWL remote Sesame 2 Connection with params
> a filename
> a base uri

> a service url beinghttp://localhost:8080/openrdf-sesame/

[PaulZH]

Scott,

Indeed triples other than those from rdf, rdfs, owl, xsd.

The type of repository is a native Java store.

Is the next release to be expected soon, then I'll wait.

Paul

[PaulZH]

Scott,

I discovered that this error message is not relevant for the issue.

Paul

[Scott Henninger]

...and I see that my post is also not relevant as you state you are
using TBC-ME localhost (hence no Live/Tomcat).

There are currently some issues with opening Sesame repositories that
are not created by Composer. We are investigating this. In the
meantime, a possible work-around is to read the repository into
Composer (TDB can be used if the repository is too large for memory),
then use export to write to Sesame. Composer will be able to open the
resulting repository and you will see the triples is stores.

-- Scott

[PaulZH]

Indeed, this procedure works.

Paul

On Oct 12, 3:54 pm, Scott Henninger <shennin...@topquadrant.com>
wrote:

[Holger Knublauch]

Paul,

I have had a chance to try out Sesame using the workbench and I notice
that if you upload a file to a repository, then the workbench will
automatically fill in a value for the Context field. I guess this acts
as a named graph on the Sesame side, and you would need to mirror the
same set up in your TBC connection. The easiest is to ensure that the
context field is empty before you add data to Sesame.

I did fix a small bug in the Sesame 2 connection wizard today, but
overall I think the current implementation is correct.

Regards,
Holger

[PaulZH]

Indeed Holger and many thanks for coming back to this,

It has to do with the automatically filled in value of the context
field in the Sesame workbench.
Or leaving it out in the Sesame workbench (e.g. supplying no context),
or filling in the context value in the graph name (optional) field of
the TBC wizard solves the issue.

I expected however leaving the graph name empty in TBC = having chosen
the default graph, including all statements, disregarding any context
information they have .


Paul