Hmmm ... FusekiConfig.readConfigurationDirectory is broken. It doesn't even use the java7 Paths API so I'm not sure how it got into the state it's in.

It's finding files but failing to add the directory name before opening them.

Recorded as JENA-915.

        Andy

On 16/04/15 10:23, Bart van Leeuwen wrote:
+1 for a explanation on this one !

Mark D Wood <[email protected]> wrote on 15-04-2015 23:37:01:

Sorry for the (very) tardy response.  I get the same exception
either way, pasted below.

However, I am confused by Trevor's suggestion.  I thought the idea
was that one could have multiple config files in the configuration
directory, each corresponding to a separate dataset, and the system
automatically processed all of them?

Thanks,
-Mark



[2015-04-15 17:31:43] Server     INFO  Fuseki 2.0.0
2015-03-08T09:49:20+0000
[2015-04-15 17:31:43] Config     INFO  FUSEKI_HOME=D:\SrvApps
\apache-jena-fuseki
-2.0.0\.
[2015-04-15 17:31:43] Config     INFO  FUSEKI_BASE=D:\SrvApps
\apache-jena-fuseki
-2.0.0\run
[2015-04-15 17:31:44] Servlet    INFO  Initializing Shiro environment
[2015-04-15 17:31:44] Config     INFO  Shiro file: file://D:\SrvApps
\apache-jena
-fuseki-2.0.0\run\shiro.ini
[2015-04-15 17:31:44] Server     ERROR Exception in initialization:
Not found: S
OACuration.ttl
[2015-04-15 17:31:44] WebAppContext WARN  Failed startup of context
o.e.j.w.WebA
ppContext@514e8e8a{/,file:/D:/SrvApps/apache-jena-fuseki-2.0.0/
webapp/,STARTING}

org.apache.jena.riot.RiotNotFoundException: Not found: SOACuration.ttl
         at org.apache.jena.riot.RDFDataMgr.open(RDFDataMgr.java:870)
         at org.apache.jena.riot.RDFDataMgr.open(RDFDataMgr.java:852)
         at org.apache.jena.riot.RDFDataMgr.parse(RDFDataMgr.java:684)
         at org.apache.jena.riot.RDFDataMgr.read(RDFDataMgr.java:210)
         at org.apache.jena.riot.RDFDataMgr.read(RDFDataMgr.java:103)
         at org.apache.jena.riot.RDFDataMgr.read(RDFDataMgr.java:94)
         at
org.apache.jena.riot.RDFDataMgr.loadModel(RDFDataMgr.java:328)
         at
org.apache.jena.fuseki.build.FusekiConfig.readConfigurationDirectory(
FusekiConfig.java:197)
         at
org.apache.jena.fuseki.server.FusekiServer.initializeDataAccessPoints
(FusekiServer.java:217)
         at org.apache.jena.fuseki.server.FusekiServerListener.init
(FusekiServerL
istener.java:70)
         at
org.apache.jena.fuseki.server.FusekiServerListener.contextInitialized
(FusekiServerListener.java:45)
         at
org.eclipse.jetty.server.handler.ContextHandler.callContextInitialize
d(ContextHandler.java:799)
         at
org.eclipse.jetty.servlet.ServletContextHandler.callContextInitialize
d(ServletContextHandler.java:446)
         at
org.eclipse.jetty.server.handler.ContextHandler.startContext(ContextH
andler.java:791)
         at
org.eclipse.jetty.servlet.ServletContextHandler.startContext(ServletC
ontextHandler.java:296)
         at org.eclipse.jetty.webapp.WebAppContext.startContext
(WebAppContext.jav
a:1347)
         at org.eclipse.jetty.server.handler.ContextHandler.doStart
(ContextHandle
r.java:743)
         at org.eclipse.jetty.webapp.WebAppContext.doStart
(WebAppContext.java:492
)
         at org.eclipse.jetty.util.component.AbstractLifeCycle.start
(AbstractLife
Cycle.java:69)
         at org.eclipse.jetty.util.component.ContainerLifeCycle.start
(ContainerLi
feCycle.java:117)
         at org.eclipse.jetty.server.Server.start(Server.java:355)
         at
org.eclipse.jetty.util.component.ContainerLifeCycle.doStart(Container
LifeCycle.java:99)
         at org.eclipse.jetty.server.handler.AbstractHandler.doStart
(AbstractHand
ler.java:60)
         at org.eclipse.jetty.server.Server.doStart(Server.java:324)
         at org.eclipse.jetty.util.component.AbstractLifeCycle.start
(AbstractLife
Cycle.java:69)
         at org.apache.jena.fuseki.jetty.JettyFuseki.start
(JettyFuseki.java:121)
         at org.apache.jena.fuseki.cmd.FusekiCmd$FusekiCmdInner.exec
(FusekiCmd.ja
va:331)
         at arq.cmdline.CmdMain.mainMethod(CmdMain.java:102)
         at arq.cmdline.CmdMain.mainRun(CmdMain.java:63)
         at arq.cmdline.CmdMain.mainRun(CmdMain.java:50)
         at org.apache.jena.fuseki.cmd.FusekiCmd
$FusekiCmdInner.innerMain(FusekiC
md.java:97)
         at org.apache.jena.fuseki.cmd.FusekiCmd.main(FusekiCmd.java:60)
[2015-04-15 17:31:44] Server     INFO  Started 2015/04/15 17:31:44
EDT on port 3
040

-----Original Message-----
From: Andy Seaborne [mailto:[email protected]]
Sent: Saturday, April 04, 2015 1:56 PM
To: [email protected]
Subject: Re: migrating configuration to Fuseki 2 style

Hi Mark,

Does the server work with Trevor's suggestion?

Either way, could you provide the full stacktrace please?

    Andy


On 03/04/15 19:10, Trevor Donaldson wrote:
I think you want fuseki - server -port 3040
-config=run/confuguration/name.ttl
On Apr 3, 2015 2:06 PM, "Mark D Wood" <[email protected]>
wrote:

Undoubtedly operator error, but I'm trying to migrate my Fuseki 1
style config file into the run/configuration files recommended for
Fuseki 2, and I'm getting an error.

I have a file of the form

run\configuration\NAME.ttl  (this is Windows)

and when I start up Fuseki by typing

fuseki-server -port 3040

in the root directory, I get the exception

[2015-04-03 14:01:04] Server     ERROR Exception in initialization:
Not
found: NAME.ttl
[2015-04-03 14:01:04] WebAppContext WARN  Failed startup of context
o.e.j.w.WebAppContext@11e2a4dd
{/,file:/D:/SrvApps/apache-jena-fuseki-2.0.0/webapp/,STARTING}

org.apache.jena.riot.RiotNotFoundException: Not found: NAME.ttl
          at org.apache.jena.riot.RDFDataMgr.open(RDFDataMgr.java:870)
          at org.apache.jena.riot.RDFDataMgr.open(RDFDataMgr.java:852)
          at
org.apache.jena.riot.RDFDataMgr.parse(RDFDataMgr.java:684)

It clearly found the file since it reports it by name, but something
obviously is not right.

Thanks,
-Mark






Reply via email to