[ 
https://issues.apache.org/jira/browse/JENA-1480?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16360249#comment-16360249
 ] 

David Cook commented on JENA-1480:
----------------------------------

Interesting. I can reproduce it with this WAR: 
[https://repository.apache.org/content/repositories/snapshots/org/apache/jena/jena-fuseki-war/3.7.0-SNAPSHOT/jena-fuseki-war-3.7.0-20180207.100806-20.war.]

Yeah, digging through the git history, I noticed that you switched from 
something like 2.7.0 to 3.4.0 back in July 2017? I was referring to 2.6.0, 
because that's the version that I have currently running on an existing system.

The browser isn't showing me much of the response. 

However, looking in the console log again, I see this:

query?query=select%20(count(*)%20as%20?count)%20\{?s%20?p%20?o}

I'm guessing that those unescaped question marks might be causing a problem?

> Bad Request 400 returned when clicking "count triples in all graphs" in 
> Fuseki info
> -----------------------------------------------------------------------------------
>
>                 Key: JENA-1480
>                 URL: https://issues.apache.org/jira/browse/JENA-1480
>             Project: Apache Jena
>          Issue Type: Bug
>          Components: Fuseki
>    Affects Versions: Jena 3.7.0
>            Reporter: David Cook
>            Priority: Minor
>
> When I click "count triples in all graphs", the UI doesn't change and I see 
> the following in the Chrome console:
> {noformat}
> GET 
> <FUSEKI_URL>/query?query=select%20(count(*)%20as%20?count)%20\{?s%20?p%20?o}
> 400 (Bad Request)
> jquery-1.10.2.min.js:6
> {noformat}
> I've experienced this in Fuseki 2.6.0 when using the WAR too. I'm also using 
> the "tdb:unionDefaultGraph true" configuration setting.
> I've used someone else's install of Fuseki 2.5.0 and it works for them. I 
> don't think they're using "tdb:unionDefaultGraph true", and I'm not sure if 
> they're using the WAR or a standalone. Since there is no Server: 
> Apache-Coyote response header, I'm guessing they're using the standalone. I 
> don't know if that would make a difference. 
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to