Uploaded image for project: 'Red Hat Fuse'
  1. Red Hat Fuse
  2. ENTESB-5121

[6.3] Adding quickstart profile to child container takes about ~10 min to provision

    XMLWordPrintable

Details

    • Bug
    • Resolution: Duplicate
    • Major
    • jboss-fuse-6.3
    • jboss-fuse-6.3
    • Fabric8 v1
    • None
    • % %

    Description

      Using these steps:

      fabric:create --profile gateway-http --wait-for-provisioning
container-create-child --profile quickstarts-cxf-rest root test

      takes about 10 minutes to provision the child container (most of the time (around 9 minutes) the container stays in "Analyzing" phase).

      This seems to be related to the problem:

      2016-03-09 11:02:03,809 | INFO  | dProxyServlet #1 | MavenProxyServletSupport         | 184 - io.fabric8.fabric-maven-proxy - 1.2.0.redhat-630026 | Received request for maven artifact : io/fabric8/quickstarts/cxf-rest/1.2.0.redhat-630026/cxf-rest-1.2.0.redhat-630026.jar
2016-03-09 11:07:03,812 | WARN  | qtp297684268-184 | Response                         | 98 - org.eclipse.jetty.util - 9.2.14.v20151106 | Committed before 404 null
2016-03-09 11:07:03,813 | WARN  | qtp297684268-184 | HttpChannel                      | 98 - org.eclipse.jetty.util - 9.2.14.v20151106 | /maven/download/io/fabric8/quickstarts/cxf-rest/1.2.0.redhat-630026/cxf-rest-1.2.0.redhat-630026.jar
java.lang.IllegalStateException: Committed
	at org.eclipse.jetty.server.Response.resetBuffer(Response.java:1243)[95:org.eclipse.jetty.server:9.2.14.v20151106]
	at org.eclipse.jetty.server.Response.sendError(Response.java:567)[95:org.eclipse.jetty.server:9.2.14.v20151106]
	at org.eclipse.jetty.server.Response.sendError(Response.java:544)[95:org.eclipse.jetty.server:9.2.14.v20151106]
	at org.eclipse.jetty.servlet.ServletHandler$Default404Servlet.doGet(ServletHandler.java:1805)[96:org.eclipse.jetty.servlet:9.2.14.v20151106]
	at javax.servlet.http.HttpServlet.service(HttpServlet.java:687)[82:javax.servlet-api:3.1.0]
	at javax.servlet.http.HttpServlet.service(HttpServlet.java:790)[82:javax.servlet-api:3.1.0]
	at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:812)[96:org.eclipse.jetty.servlet:9.2.14.v20151106]
	at org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:587)[96:org.eclipse.jetty.servlet:9.2.14.v20151106]
	at org.ops4j.pax.web.service.jetty.internal.HttpServiceServletHandler.doHandle(HttpServiceServletHandler.java:70)[119:org.ops4j.pax.web.pax-web-jetty:4.2.4]
	at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:143)[95:org.eclipse.jetty.server:9.2.14.v20151106]
	at org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:595)[94:org.eclipse.jetty.security:9.2.14.v20151106]
	at org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:223)[95:org.eclipse.jetty.server:9.2.14.v20151106]
	at org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1127)[95:org.eclipse.jetty.server:9.2.14.v20151106]
	at org.ops4j.pax.web.service.jetty.internal.HttpServiceContext.doHandle(HttpServiceContext.java:271)[119:org.ops4j.pax.web.pax-web-jetty:4.2.4]
	at org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:515)[96:org.eclipse.jetty.servlet:9.2.14.v20151106]
	at org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:185)[95:org.eclipse.jetty.server:9.2.14.v20151106]
	at org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1061)[95:org.eclipse.jetty.server:9.2.14.v20151106]
	at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:141)[95:org.eclipse.jetty.server:9.2.14.v20151106]
	at org.ops4j.pax.web.service.jetty.internal.JettyServerHandlerCollection.handle(JettyServerHandlerCollection.java:99)[119:org.ops4j.pax.web.pax-web-jetty:4.2.4]
	at org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:97)[95:org.eclipse.jetty.server:9.2.14.v20151106]
	at org.eclipse.jetty.server.Server.handleAsync(Server.java:549)[95:org.eclipse.jetty.server:9.2.14.v20151106]
	at org.eclipse.jetty.server.HttpChannel.handle(HttpChannel.java:348)[95:org.eclipse.jetty.server:9.2.14.v20151106]
	at org.eclipse.jetty.server.HttpChannel.run(HttpChannel.java:262)[95:org.eclipse.jetty.server:9.2.14.v20151106]
	at org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:635)[98:org.eclipse.jetty.util:9.2.14.v20151106]
	at org.eclipse.jetty.util.thread.QueuedThreadPool$3.run(QueuedThreadPool.java:555)[98:org.eclipse.jetty.util:9.2.14.v20151106]
	at java.lang.Thread.run(Thread.java:745)[:1.8.0_72-internal]
2016-03-09 11:07:03,817 | WARN  | qtp297684268-184 | QueuedThreadPool                 | 98 - org.eclipse.jetty.util - 9.2.14.v20151106 | 
java.lang.IllegalStateException: committed
	at org.eclipse.jetty.server.HttpChannel.sendResponse(HttpChannel.java:772)[95:org.eclipse.jetty.server:9.2.14.v20151106]
	at org.eclipse.jetty.server.HttpChannel.sendResponse(HttpChannel.java:781)[95:org.eclipse.jetty.server:9.2.14.v20151106]
	at org.eclipse.jetty.server.HttpChannel.handleException(HttpChannel.java:473)[95:org.eclipse.jetty.server:9.2.14.v20151106]
	at org.eclipse.jetty.server.HttpConnection$HttpChannelOverHttp.handleException(HttpConnection.java:594)[95:org.eclipse.jetty.server:9.2.14.v20151106]
	at org.eclipse.jetty.server.HttpChannel.handle(HttpChannel.java:399)[95:org.eclipse.jetty.server:9.2.14.v20151106]
	at org.eclipse.jetty.server.HttpChannel.run(HttpChannel.java:262)[95:org.eclipse.jetty.server:9.2.14.v20151106]
	at org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:635)[98:org.eclipse.jetty.util:9.2.14.v20151106]
	at org.eclipse.jetty.util.thread.QueuedThreadPool$3.run(QueuedThreadPool.java:555)[98:org.eclipse.jetty.util:9.2.14.v20151106]
	at java.lang.Thread.run(Thread.java:745)[:1.8.0_72-internal]
2016-03-09 11:07:03,818 | WARN  | qtp297684268-184 | QueuedThreadPool                 | 98 - org.eclipse.jetty.util - 9.2.14.v20151106 | Unexpected thread death: org.eclipse.jetty.util.thread.QueuedThreadPool$3@5e4deab5 in qtp297684268{STARTED,8<=8<=200,i=4,q=0}
2016-03-09 11:07:11,645 | INFO  | dProxyServlet #1 | MavenProxyServletSupport         | 184 - io.fabric8.fabric-maven-proxy - 1.2.0.redhat-630026 | Writing response for file : io/fabric8/quickstarts/cxf-rest/1.2.0.redhat-630026/cxf-rest-1.2.0.redhat-630026.jar
2016-03-09 11:07:11,648 | INFO  | dProxyServlet #1 | MavenProxyServletSupport         | 184 - io.fabric8.fabric-maven-proxy - 1.2.0.redhat-630026 | Writing response for file : io/fabric8/quickstarts/cxf-rest/1.2.0.redhat-630026/cxf-rest-1.2.0.redhat-630026.jar

      The analyzing state ends with this log printed to standard output:

      Exception in thread "Thread-69" Exception in thread "Thread-70" java.lang.IllegalStateException: AsyncContext#dispath s=COMPLETING i=false a=null
	at org.eclipse.jetty.server.HttpChannelState.dispatch(HttpChannelState.java:350)
	at org.eclipse.jetty.server.AsyncContextState.dispatch(AsyncContextState.java:114)
	at io.fabric8.maven.proxy.impl.MavenDownloadProxyServlet$3$1.completed(MavenDownloadProxyServlet.java:205)
	at io.fabric8.maven.proxy.impl.MavenDownloadProxyServlet$3$1.completed(MavenDownloadProxyServlet.java:201)
	at sun.nio.ch.Invoker.invokeUnchecked(Invoker.java:126)
	at sun.nio.ch.SimpleAsynchronousFileChannelImpl$2.run(SimpleAsynchronousFileChannelImpl.java:335)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
	at java.lang.Thread.run(Thread.java:745)
java.lang.IllegalStateException: AsyncContext#dispath s=COMPLETING i=false a=null
	at org.eclipse.jetty.server.HttpChannelState.dispatch(HttpChannelState.java:350)
	at org.eclipse.jetty.server.AsyncContextState.dispatch(AsyncContextState.java:114)
	at io.fabric8.maven.proxy.impl.MavenDownloadProxyServlet$3$1.completed(MavenDownloadProxyServlet.java:205)
	at io.fabric8.maven.proxy.impl.MavenDownloadProxyServlet$3$1.completed(MavenDownloadProxyServlet.java:201)
	at sun.nio.ch.Invoker.invokeUnchecked(Invoker.java:126)
	at sun.nio.ch.SimpleAsynchronousFileChannelImpl$2.run(SimpleAsynchronousFileChannelImpl.java:335)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
	at java.lang.Thread.run(Thread.java:745)

      Then the provisioning successfully continues and the container is provisioned

      Attachments

        Issue Links

          is duplicated by

          Bug - A problem that impairs or prevents the functions of the product. ENTESB-4727 container-create-child experiences long delay if mvn artefacts need to be downloaded from remote repository

          • Critical - To be worked on immediately following BLOCKER issues.
          • Closed

          Bug - A problem that impairs or prevents the functions of the product. ENTESB-4456 Issue with local Maven proxy and provisioning - stuck in Analyzing

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed
          relates to

          Bug - A problem that impairs or prevents the functions of the product. ENTESB-5174 WARN from jetty happens very regular

          • Critical - To be worked on immediately following BLOCKER issues.
          • Closed

          Activity

            People

              ggrzybek Grzegorz Grzybek
              avano@redhat.com Andrej Vano
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: