apache-karaf + http feature spins
---------------------------------
Key: KARAF-996
URL: https://issues.apache.org/jira/browse/KARAF-996
Project: Karaf
Issue Type: Bug
Components: karaf-features
Affects Versions: 2.2.4, 2.2.3, 2.2.2
Environment: windows, linux jvm 1.6
Reporter: Dan Tran
Priority: Critical
When use karaf + http feature as a file download server, karaf can easily spin
and an CPU can go higher than 100+ depending number of CPU you have.
Similar issue as been posted at at service mix forum (
http://fusesource.com/forums/message.jspa?messageID=10574 )
For my case, I am using karaf + http feature just to server as a static maven
repository, here are the stop to produce
1. Install apache-karaf-2.2+
2. User karaf shell to install http feature
3. Configure karaf web via etc/org.ops4j.pax.web.cfg
##########################################
# Configuration file for HTTP access.
##########################################
##########################################
# Basic HTTP access
##########################################
org.osgi.service.http.enabled=true
org.osgi.service.http.port=8181
#########################################
# Set the location where the repository is located.
#########################################
org.ops4j.pax.web.config.file=etc/jetty.xml
5. Configure etc/jetty.xml
<?xml version="1.0"?>
<!DOCTYPE Configure PUBLIC "-//Mort Bay Consulting//
DTD Configure//EN" "http://jetty.mortbay.org/configure.dtd";>
<Configure id="FileServer" class="org.eclipse.jetty.server.Server">
<Set name="handler">
<New class="org.eclipse.jetty.server.handler.HandlerList">
<Set name="handlers">
<Array type="org.eclipse.jetty.server.Handler">
<Item>
<New class="org.eclipse.jetty.server.handler.ResourceHandler">
<Set name="directoriesListed">true</Set>
<Set name="resourceBase"><Property name="jetty.home" default="."
/>/repo</Set>
</New>
</Item>
<Item>
<New class="org.eclipse.jetty.server.handler.DefaultHandler">
</New>
</Item>
</Array>
</Set>
</New>
</Set>
</Configure>
the spike can occur any time even at idle. More likely to happen when using is
as a maven repository ( wget a big file can also trigger it )
--
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
