felix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Felix Meschberger (Commented) (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (FELIX-3265) AJAX Error: Request Failed: FULL head
Date Wed, 14 Dec 2011 14:23:30 GMT

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

Felix Meschberger commented on FELIX-3265:
------------------------------------------

This might be a duplicate of FELIX-3162 for which I added new configuration options and actually
already increased the default values to 16KB for the header buffer size.

This has not been released yet, so you might have to try a trunk build.
                
> AJAX Error: Request Failed: FULL head
> -------------------------------------
>
>                 Key: FELIX-3265
>                 URL: https://issues.apache.org/jira/browse/FELIX-3265
>             Project: Felix
>          Issue Type: Bug
>          Components: HTTP Service, Web Console
>    Affects Versions: webconsole-3.1.8, http-2.2.0
>         Environment: Windows Vista x86, Java 6
>            Reporter: Deniz Acay
>              Labels: buffer, felix, jetty
>
> I have been using Web Console for a while to configure my DS components. But recently,
one of my component's metatype.xml file got larger due to increase in configuration options
for the component. Suddenly, now when I try to configure that component, even without changing
a value, I get an AJAX error. Although sometimes there is no message inside the AJAX Error
dialog at all, I frequently get a "Request failed: FULL head" message in the AJAX Error modal
dialog. I have searched around the internet and it looks like the cause of this is about the
size of the Jetty's header buffer (http://jira.codehaus.org/browse/JETTY-336).
> Any fix is appreciated as this prevents me from debugging configuration of my component.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message