Problems creating repo with latest version

247 views
Skip to first unread message

Pat McBennett

unread,
Oct 27, 2016, 9:09:50 AM10/27/16
to rdf4j...@googlegroups.com
Hi,

I'm a very seasoned (and happy!) Sesame user, but today I decided to upgrade to the latest and greatest RDF4J release.

Unfortunately I haven't gotten very far though, as just creating a basic new repository isn't working for me.

I'm working with Windows 10, and Tomcat 8.0.27. I removed the old 'openrdf' WARs from my 'webapps' directory, and dropped in the two new RDF4J ones (i.e. rdf4j-server.war and rdf4j-workbench.war). I connect to the workbench as normal, and create a new repository (just an 'In Memory Store'). I don't get any errors on screen, but none of the options to work with the new repository are enabled - see the attached screenshot, which also shows the Tomcat output and the browser console.

I can't get beyond this point as none of the options are enabled (also pointed out in the attached screenshot), although the repo I just created does appear in the dropdown list box of repos when I try to delete it, but deleting and re-creating just repeats the behaviour above.

Any help in getting started would be greatly appreciated!

Cheers,

Pat.

RDJ4JError.png

Jeen Broekstra

unread,
Oct 27, 2016, 9:17:22 PM10/27/16
to rdf4j...@googlegroups.com
Very odd, I don’t think I’ve seen that before. 

Can you have a look in the RDF4J Server log to see if there’s any warning or error that sheds more light on the issue? You can find this in %APPDATA\RDF4J\Server\logs\main.log . If you’re unsure about the exact location, go to http://localhost:8090/rdf4j-server/home/overview.view in your browser and click on ’System’ in the menu - you’ll see system configuration settings, including the data directory used by RDF4J Server (which also contains the log). 

Cheers,

Jeen

Pat McBennett

unread,
Oct 28, 2016, 5:11:20 AM10/28/16
to rdf4j...@googlegroups.com
Hi Jeen,

So I've enabled DEBUG logging and attached the log output from RDF4J. Literally all I did was start Tomcat, go to the workbench, and create a new repository called 'Test DD' with the default values for all options (but then, as per the screenshot in my original mail, I can't click on any of the controls to add data to the repo 'cause it seems it was never actually created in the first place!).

I've also attached the Tomcat output logs. The 'catalina.2016-10-28.log' shows nothing much, and although the 'localhost.2016-10-28.log' shows the 'No such repository' exception it doesn't give any indication of why. For completeness I've included 'localhost_access_log.2016-10-28.txt'.

I don't want to confuse things, as my problem seems very straightforward and very easy to reproduce on my laptop, but for the record the only other time I've noticed Sesame behave like this (i.e. where I create a repository in the workbench, but then can't actually click on any of the controls to 'Explore' or 'Modify' that repository) was when I was connecting to a remote Sesame instance via HTTP, and when I switched instead to using HTTPS it all worked normally (but that scenario was via lots of complex internal infrastructure with routers, proxypass and firewalls).

From the browser console I can see the response of the failed HTTP request (status 500) to get the 'info' of the newly created repository, and it clearly seems to think the repo doesn't exist:

    1. Request URL:
    2. Request Method:
      GET
    3. Status Code:
      500 Internal Server Error (from disk cache)
  1. Response Headers
    1. Cache-Control:
      max-age=600, public
    2. Content-Language:
      en
    3. Content-Length:
      2017
    4. Content-Type:
      text/html;charset=utf-8
    5. Date:
      Fri, 28 Oct 2016 08:38:16 GMT
    6. Server:
      Apache-Coyote/1.1
    7. Vary:
      Cookie, Cookie, Cookie
  2. Request Headers
    1. Provisional headers are shown
    2. Referer:
    3. User-Agent:
      Mozilla/5.0 (Windows NT 10.0; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/54.0.2840.71 Safari/537.36

RESPONSE:

<!DOCTYPE html><html><head><title>Apache Tomcat/8.0.27 - Error report</title><style type="text/css">H1 {font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;font-size:22px;} H2 {font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;font-size:16px;} H3 {font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;font-size:14px;} BODY {font-family:Tahoma,Arial,sans-serif;color:black;background-color:white;} B {font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;} P {font-family:Tahoma,Arial,sans-serif;background:white;color:black;font-size:12px;}A {color : black;}A.name {color : black;}.line {height: 1px; background-color: #525D76; border: none;}</style> </head><body><h1>HTTP Status 500 - No such repository: TestDD</h1><div class="line"></div><p><b>type</b> Exception report</p><p><b>message</b> <u>No such repository: TestDD</u></p><p><b>description</b> <u>The server encountered an internal error that prevented it from fulfilling this request.</u></p><p><b>exception</b></p><pre>org.eclipse.rdf4j.workbench.exceptions.BadRequestException: No such repository: TestDD
org.eclipse.rdf4j.workbench.proxy.WorkbenchServlet.service(WorkbenchServlet.java:220)
org.eclipse.rdf4j.workbench.proxy.WorkbenchServlet.handleRequest(WorkbenchServlet.java:141)
org.eclipse.rdf4j.workbench.proxy.WorkbenchServlet.service(WorkbenchServlet.java:109)
org.eclipse.rdf4j.workbench.proxy.WorkbenchGateway.service(WorkbenchGateway.java:120)
org.eclipse.rdf4j.workbench.base.AbstractServlet.service(AbstractServlet.java:125)
org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:52)
org.eclipse.rdf4j.workbench.proxy.CacheFilter.doFilter(CacheFilter.java:62)
org.eclipse.rdf4j.workbench.proxy.CookieCacheControlFilter.doFilter(CookieCacheControlFilter.java:53)
</pre><p><b>note</b> <u>The full stack trace of the root cause is available in the Apache Tomcat/8.0.27 logs.</u></p><hr class="line"><h3>Apache Tomcat/8.0.27</h3></body></html>

Curioser and curioser...

Thanks,

Pat.


--
You received this message because you are subscribed to the Google Groups "RDF4J Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to rdf4j-users+unsubscribe@googlegroups.com.
To post to this group, send email to rdf4j...@googlegroups.com.
Visit this group at https://groups.google.com/group/rdf4j-users.
To view this discussion on the web visit https://groups.google.com/d/msgid/rdf4j-users/F1C24289-C3A0-40AD-AFA6-452EB49D3447%40gmail.com.
For more options, visit https://groups.google.com/d/optout.

localhost_access_log.2016-10-28.txt
CreateRepositoryFail-main.log
localhost.2016-10-28.log
catalina.2016-10-28.log

Pat McBennett

unread,
Oct 28, 2016, 7:00:32 AM10/28/16
to rdf4j...@googlegroups.com
And by the way... isn't it a bug that the RDF4J workbench UI isn't displaying anything on-screen about the fact that the HTTP request it just sent to the server for '/info' on the repository it thinks it just created (i.e. the GET on http://localhost:8090/rdf4j-workbench/repositories/TestDD/info) returned a status 500 error with information saying 'No such repository: TestDD' ?

Although this wouldn't help me in my current situation ('cos I had to delve into the console output to already find this out), but for others encountering repository-creation-problems, at least they'd know there was an error. At the moment, no error appears on the screen, but the links to add data etc. are all disabled, which is pretty confusing and frustrating!

Cheers,

Pat.

Pat McBennett

unread,
Nov 1, 2016, 10:39:25 AM11/1/16
to rdf4j...@googlegroups.com
Hi Jeen,

Would you have any further ideas to investigate the problems I'm seeing?

Cheers,

Pat.

Jeen Broekstra

unread,
Nov 2, 2016, 1:21:04 AM11/2/16
to rdf4j...@googlegroups.com
On 2 Nov. 2016, at 01:39, Pat McBennett <pat.mc...@gmail.com> wrote:

Hi Jeen,

Would you have any further ideas to investigate the problems I'm seeing?

Not immediately, I’m afraid. I could ask you to clear your browser cache and restart Tomcat, but I assume that you’ve already done both those things and in any case I’m not quite sure why that would fix anything (but it can’t hurt ;)).

I’ll investigate further and if possible try to reproduce. Just to be clear: this problem occurs for you in a clean new installation of RDF4J Server + Workbench release 2.1, on Tomcat 8, using Windows 10, correct? And you are running a Java 8 Runtime Environment?


Jeen

To unsubscribe from this group and stop receiving emails from it, send an email to rdf4j-users...@googlegroups.com.

To post to this group, send email to rdf4j...@googlegroups.com.
Visit this group at https://groups.google.com/group/rdf4j-users.

Pat McBennett

unread,
Nov 2, 2016, 8:54:56 AM11/2/16
to rdf4j...@googlegroups.com
Hi Jeen,

Yep, that's exactly my environment, and yes, I am using Java 8 (latest version 1.8.0_60).

I managed to work-around the problem by as you say, restarting Tomcat completely. When I did that the repo I created previously was available, and when selected all the links on the left-hand side of the workbench were enabled as expected. So it seems the repo was created the first time around after all!

So the only real issue is why are newly created repos 'apparently' failing (even though they do seem to be created on the filesystem)? I still see that behaviour consistently every time I create a brand new repo (i.e. all the controls on the left-hand-side are disabled, but restarting Tomcat and selecting that repo again re-enables all the controls as expected).

And secondly, the UI code doesn't seem to gracefully handle the status 500 error when the browser tries to get '/info' for a newly created repo (i.e. it doesn't notify the user that there was a problem, thereby leaving the user confused as to why the controls are all disabled).

Anyway, I seem to have gotten around my repo-creation problem for the moment (i.e. reboot Tomcat!), so I'm good to go again now...

Cheers,

Pat




Cheers,

Pat.


To post to this group, send email to rdf4j-users@googlegroups.com.

-- 
You received this message because you are subscribed to the Google Groups "RDF4J Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to rdf4j-users+unsubscribe@googlegroups.com.
To post to this group, send email to rdf4j-users@googlegroups.com.

--
You received this message because you are subscribed to the Google Groups "RDF4J Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to rdf4j-users+unsubscribe@googlegroups.com.
To post to this group, send email to rdf4j...@googlegroups.com.
Visit this group at https://groups.google.com/group/rdf4j-users.

Jeen Broekstra

unread,
Nov 2, 2016, 6:04:26 PM11/2/16
to rdf4j...@googlegroups.com
I have just managed to recreate the issue. It appears to be browser-specific. Firefox and Safari open the newly create store without trouble, but my Google Chrome (on my Mac) shows the exact same problem you reported. Can I assume that you are using Google Chrome? 

I’ll investigate a bit further and log an issue. Thanks again for the report Pat!

Cheers,

Jeen


To unsubscribe from this group and stop receiving emails from it, send an email to rdf4j-users...@googlegroups.com.

To post to this group, send email to rdf4j...@googlegroups.com.
Visit this group at https://groups.google.com/group/rdf4j-users.

Pat McBennett

unread,
Nov 2, 2016, 6:22:42 PM11/2/16
to rdf4j...@googlegroups.com
Hiya Jeen,

That's great news that you can reproduce this behaviour (since it's always a great relief to get past the 'it works on my machine' problem!).

So, yes absolutely, I almost exclusively work with Chrome as my browser, mainly because it's officially supported where I work and it's so much more performant than the 'other' supported browser, which of course is IE (my team does a lot of visualization work with D3).

I'm more than happy to help out if I can to help you verify any fixes or changes, as I work on Windows. My collegue works on a Mac though (using Chrome too), so we can help with any verification there too if you need it - just let me know.

Cheers, and good luck tracking down the culprit :) !

Pat.




Cheers,

Pat.


To post to this group, send email to rdf4j...@googlegroups.com.

-- 
You received this message because you are subscribed to the Google Groups "RDF4J Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to rdf4j-users+unsubscribe@googlegroups.com.
To post to this group, send email to rdf4j...@googlegroups.com.

--
You received this message because you are subscribed to the Google Groups "RDF4J Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to rdf4j-users+unsubscribe@googlegroups.com.
To post to this group, send email to rdf4j...@googlegroups.com.
Visit this group at https://groups.google.com/group/rdf4j-users.
To view this discussion on the web visit https://groups.google.com/d/msgid/rdf4j-users/0DD08343-D599-4AD2-B275-A4C98F9563DA%40gmail.com.

For more options, visit https://groups.google.com/d/optout.

--
You received this message because you are subscribed to the Google Groups "RDF4J Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to rdf4j-users+unsubscribe@googlegroups.com.
To post to this group, send email to rdf4j...@googlegroups.com.
Visit this group at https://groups.google.com/group/rdf4j-users.

--
You received this message because you are subscribed to the Google Groups "RDF4J Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to rdf4j-users+unsubscribe@googlegroups.com.
To post to this group, send email to rdf4j...@googlegroups.com.
Visit this group at https://groups.google.com/group/rdf4j-users.
Reply all
Reply to author
Forward
0 new messages