java.lang.RuntimeException

No named subject in statement patterns

Samebug tips0

There are no available Samebug tips for this exception. If you know how to solve this issue, help other users by writing a short tip.

Don't give up yet. Paste your full stack trace to get a solution.

Solutions on the web10911

  • via Sakai JIRA by Tim Worrall, 1 year ago
    No named subject in statement patterns
  • via Sakai JIRA by Tim Worrall, 1 year ago
    No named subject in statement patterns
  • via Oracle Community by 729043, 11 months ago
    No subject specified in request.
  • Stack trace

    • java.lang.RuntimeException: No named subject in statement patterns at edu.cornell.mannlib.vitro.webapp.rdfservice.impl.jena.RDFServiceJena.sort(RDFServiceJena.java:229) at edu.cornell.mannlib.vitro.webapp.rdfservice.impl.jena.RDFServiceJena.removeUsingSparqlUpdate(RDFServiceJena.java:178) at edu.cornell.mannlib.vitro.webapp.rdfservice.impl.jena.RDFServiceJena.removeBlankNodesWithSparqlUpdate(RDFServiceJena.java:122) at edu.cornell.mannlib.vitro.webapp.rdfservice.impl.jena.RDFServiceJena.operateOnModel(RDFServiceJena.java:64) at edu.cornell.mannlib.vitro.webapp.rdfservice.impl.jena.sdb.RDFServiceSDB.changeSetUpdate(RDFServiceSDB.java:119) at edu.cornell.mannlib.vitro.webapp.dao.jena.RDFServiceGraphBulkUpdater.removeAll(RDFServiceGraphBulkUpdater.java:210) at edu.cornell.mannlib.vitro.webapp.dao.jena.RDFServiceGraphBulkUpdater.removeAll(RDFServiceGraphBulkUpdater.java:148) at com.hp.hpl.jena.rdf.model.impl.ModelCom.removeAll(ModelCom.java:315) at edu.cornell.mannlib.vitro.webapp.servlet.setup.FileGraphSetup.updateGraphInDB(FileGraphSetup.java:227) at edu.cornell.mannlib.vitro.webapp.servlet.setup.FileGraphSetup.readGraphs(FileGraphSetup.java:180) at edu.cornell.mannlib.vitro.webapp.servlet.setup.FileGraphSetup.contextInitialized(FileGraphSetup.java:90) at edu.cornell.mannlib.vitro.webapp.startup.StartupManager.initialize(StartupManager.java:176) at edu.cornell.mannlib.vitro.webapp.startup.StartupManager.contextInitialized(StartupManager.java:65) at org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:4135) at org.apache.catalina.core.StandardContext.start(StandardContext.java:4630) at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:791) at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:771) at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:546) at org.apache.catalina.startup.HostConfig.deployDescriptor(HostConfig.java:637) at org.apache.catalina.startup.HostConfig.deployDescriptors(HostConfig.java:563) at org.apache.catalina.startup.HostConfig.deployApps(HostConfig.java:498) at org.apache.catalina.startup.HostConfig.start(HostConfig.java:1277) at org.apache.catalina.startup.HostConfig.lifecycleEvent(HostConfig.java:321) at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:119) at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1053) at org.apache.catalina.core.StandardHost.start(StandardHost.java:785) at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1045) at org.apache.catalina.core.StandardEngine.start(StandardEngine.java:445) at org.apache.catalina.core.StandardService.start(StandardService.java:519) at org.apache.catalina.core.StandardServer.start(StandardServer.java:710) at org.apache.catalina.startup.Catalina.start(Catalina.java:581) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:601) at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:289) at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:414)

    Write tip

    You have a different solution? A short tip here would help you and many other users who saw this issue last week.

    Users with the same issue

    You’re the first here who have seen this exception.