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

Andreas Kuckartz commented on STANBOL-1328:
-------------------------------------------

[~rwesten] Sorry for not making that clear: _those_ errors were indeed the 
result of deliberately created syntactic errors (which I mentioned in my mail). 
The problems this Jira issue is about did _not_ leave such traces in the error 
log. If there are any traces in the error.log they must be _before_ the first 
hit on "Run SPARQL query".

> Running SPARQL query fails / "request body has been consumed by the servlet 
> or a servlet filter"
> ------------------------------------------------------------------------------------------------
>
>                 Key: STANBOL-1328
>                 URL: https://issues.apache.org/jira/browse/STANBOL-1328
>             Project: Stanbol
>          Issue Type: Bug
>    Affects Versions: 1.0.0
>         Environment: java version "1.7.0_55"
> OpenJDK Runtime Environment (IcedTea 2.4.7) (7u55-2.4.7-1)
> OpenJDK 64-Bit Server VM (build 24.51-b03, mixed mode)
>            Reporter: Andreas Kuckartz
>         Attachments: STANBOL-1328.log
>
>
> I am running:
> ```
> java -Xmx1024M -XX:MaxPermSize=400M -Xss512k -jar 
> org.apache.stanbol.launchers.full-1.0.0-SNAPSHOT.jar
> ```
> When I visit http://localhost:8080/sparql/ and click on the button "Run 
> SPARQL query" I see the response "Invalid query."
> At the same time such a warning is logged:
> ```
> Apr 23, 2014 10:19:09 AM org.glassfish.jersey.servlet.WebComponent 
> filterFormParameters
> Warnung: A servlet request to the URI http://localhost:8080/sparql contains 
> form parameters in the request body but the request body has been consumed by 
> the servlet or a servlet filter accessing the request parameters. Only 
> resource methods using @FormParam will work as expected. Resource methods 
> consuming the request body by other means will not work as expected.
> ```



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Reply via email to