[
https://issues.apache.org/jira/browse/KARAF-1666?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andreas Pieber resolved KARAF-1666.
-----------------------------------
Resolution: Fixed
Committed r1365047
M assemblies/apache-karaf/src/main/resources/extra/jetty.xml
r1365047 = dc8a3209e32812508b79b6a6da43edd6a12aa8d5 (refs/remotes/origin/trunk)
Committed r1365059
M assemblies/apache-karaf/src/main/resources/extra/jetty.xml
r1365059 = 68c21d99e3431f4be65c5b431a8e5361e517dda3
(refs/remotes/origin/karaf-2.2.x)
Committed r1365060
M assemblies/apache-karaf/src/main/resources/extra/jetty.xml
r1365060 = ad750710e2a306334eb405b946b772464ac806bb
(refs/remotes/origin/karaf-2.3.x)
> Default configuration for jetty.xml could create problems
> ---------------------------------------------------------
>
> Key: KARAF-1666
> URL: https://issues.apache.org/jira/browse/KARAF-1666
> Project: Karaf
> Issue Type: Bug
> Components: karaf-webcontainer
> Affects Versions: 2.2.8, 2.3.0, 3.0.0
> Reporter: Andreas Pieber
> Assignee: Andreas Pieber
> Fix For: 2.2.9, 2.3.0, 3.0.0
>
>
> Today I stumbled over the very "funny" jetty issue [1] at one of our
> customers. While I know that the blocking connector isn't the perfect
> solution I think it's preferable noticing the problem, using the Blocking one
> by default and let the user decide if he wants to take it or not.
--
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