2 Replies Latest reply on Jul 3, 2014 9:39 AM by Colin Woodcock

    CDI initialization failure after login on jbpm-console

    klkoster Newbie

      I am hoping someone else has experienced this and has the "magic incantation" resolve it. I have been trying to get the jbpm-console demo up for several days now and have run into the same issue on Mac, Red Hat Linux, and Windows 8. Everything installs and deploys without incident and can bring up the console's login page. However, after I login the initial splash screen comes up and the app never moves on. Just in case it was just an http timeout issue due to long running initialization, I have left it for several hours, come back, refreshed, and still had the same results. I have searched for answers but haven't found the nearest thing I found was a reference to a hard coded timeout within the code (I am hoping this is not the issue). The last thing in the server.log is the completion of a successful deployment of the webapp:

       

      08:14:39,345 INFO  [org.kie.services.remote.jms.RetryTrackerSingleton] (MSC service thread 1-6) JMS message retry limit set to 2

      08:14:39,750 INFO  [solder-servlet] (MSC service thread 1-6) Catch Integration for Servlets enabled

      08:14:40,166 INFO  [org.jboss.errai.bus.server.cluster.noop.NoopClusteringProvider] (MSC service thread 1-6) clustering support not configured.

      08:14:40,178 INFO  [org.jboss.errai.bus.server.service.bootstrap.OrderedBootstrap] (MSC service thread 1-6) starting errai bus ...

      08:14:40,188 INFO  [org.jboss.errai.bus.server.service.bootstrap.DefaultComponents] (MSC service thread 1-6) authentication adapter configured: org.jboss.errai.bus.server.security.auth.JAASAdapter

      08:14:40,272 INFO  [org.jboss.errai.bus.server.service.bootstrap.DefaultComponents] (MSC service thread 1-6) using dispatcher implementation: org.jboss.errai.bus.server.SimpleDispatcher

      08:14:40,288 INFO  [org.jboss.errai.bus.server.service.bootstrap.DefaultComponents] (MSC service thread 1-6) using session provider implementation: org.jboss.errai.bus.server.HttpSessionProvider

      08:14:40,318 INFO  [org.jboss.errai.bus.server.service.bootstrap.LoadExtensions] (MSC service thread 1-6) searching for errai extensions ...

      08:14:40,334 INFO  [org.jboss.errai.bus.server.service.bootstrap.OrderedBootstrap] (MSC service thread 1-6) errai bus started.

      08:14:40,451 INFO  [org.jboss.web] (MSC service thread 1-6) JBAS018210: Registering web context: /jbpm-console

      08:14:40,470 INFO  [org.jboss.as] (MSC service thread 1-7) JBAS015951: Admin console listening on http://127.0.0.1:9990

      08:14:40,476 INFO  [org.jboss.as] (MSC service thread 1-7) JBAS015874: JBoss AS 7.1.1.Final "Brontes" started in 68776ms - Started 675 of 759 services (82 services are passive or on-demand)

      08:14:40,562 INFO  [org.jboss.as.server] (DeploymentScanner-threads - 2) JBAS018559: Deployed "jbpm-console.war"

      08:14:40,567 INFO  [org.jboss.as.server] (DeploymentScanner-threads - 2) JBAS018559: Deployed "dashboard-builder.war"

       

      In the JavaScript log on the browser, there is an error that seems to point to a timeout issue. However, what is causing this timeout is a bit vague. The only thing I can gather is that CDI initialization of the console is taking to long. But if and where this can be configured is a bit of mystery. The JS console shows the following (sorry about the formatting, copying and pasting from Chrome's JS console doesn't work well):

       

       

       

      1. XHR finished loading: POST "http://localhost:8080/jbpm-console/org.kie.workbench.KIEWebapp/out.12760-3003.erraiBus?z=0&clientId=12760-3003&phase=connection&wait=1". 8D4B95D97ABD30060BFFA2EEECE5D794.cache.html:17002

      2014-06-06 08:15:55.926[errai] my queue session id: a42571a5ce6da67a429dfc378ec109e7de94984e16b494b95167de8b7c698e 8D4B95D97ABD30060BFFA2EEECE5D794.cache.html:7788

      2014-06-06 08:15:55.938[errai] transitioning to new handler: SSE[2601] 8D4B95D97ABD30060BFFA2EEECE5D794.cache.html:7788

      2014-06-06 08:15:55.943[errai] transmitting deferred messages now ... 8D4B95D97ABD30060BFFA2EEECE5D794.cache.html:7788

      2014-06-06 08:15:55.991[errai] vote for: org.jboss.errai.bus.client.api.ClientMessageBus 8D4B95D97ABD30060BFFA2EEECE5D794.cache.html:7788

      2014-06-06 08:15:55.993[errai] CDI subsystem syncing with server ... 8D4B95D97ABD30060BFFA2EEECE5D794.cache.html:7788

      2014-06-06 08:15:56.021[errai] requested server to forward CDI events for 32 existing observers 8D4B95D97ABD30060BFFA2EEECE5D794.cache.html:18041

      2014-06-06 08:15:56.025[errai] still waiting for -> [org.jboss.errai.enterprise.client.cdi.api.CDI] 8D4B95D97ABD30060BFFA2EEECE5D794.cache.html:7788

      2014-06-06 08:15:56.025[errai] bus federated and running. 8D4B95D97ABD30060BFFA2EEECE5D794.cache.html:7788

      2014-06-06 08:15:56.097

      1. XHR finished loading: POST "http://localhost:8080/jbpm-console/org.kie.workbench.KIEWebapp/out.12760-3003.erraiBus?z=0&clientId=12760-3003". 8D4B95D97ABD30060BFFA2EEECE5D794.cache.html:17002

      2014-06-06 08:15:56.106

      1. XHR finished loading: POST "http://localhost:8080/jbpm-console/org.kie.workbench.KIEWebapp/out.12760-3003.erraiBus?z=1&clientId=12760-3003". 8D4B95D97ABD30060BFFA2EEECE5D794.cache.html:17002

      2014-06-06 08:15:56.233

      1. XHR finished loading: POST "http://localhost:8080/jbpm-console/org.kie.workbench.KIEWebapp/out.12760-3003.erraiBus?z=1&clientId=12760-3003". 8D4B95D97ABD30060BFFA2EEECE5D794.cache.html:17002

      2014-06-06 08:16:38.329[errai] components failed to initialize 8D4B95D97ABD30060BFFA2EEECE5D794.cache.html:7788

      2014-06-06 08:16:38.329[errai] [failed] -> org.jboss.errai.enterprise.client.cdi.api.CDI 8D4B95D97ABD30060BFFA2EEECE5D794.cache.html:7788

       

       

      Any constructive help would be appreciated.

       

      Thanks,

      Karl

        • 1. Re: CDI initialization failure after login on jbpm-console
          Maciej Swiderski Master

          looks like an errai issue rather than jbpm so I guess cross posting this to errai user forum might bring some answers.

           

          HTH

          • 2. Re: CDI initialization failure after login on jbpm-console
            Colin Woodcock Newbie

            Seeing similar on OSX 10.9.4 with both Safari and Chrome.  Tried against jbpm-6.1.0.CR1 and 6.0.0.Final, that is Errai 2.4.4 and 2.4.1 respectively.

             

            My JS logs...

            [Log] [errai] CDI subsystem syncing with server ... (EF6407B82B421781A12D5D21F87BD730.cache.html, line 7643)

            [Log] [errai] requested server to forward CDI events for 28 existing observers (EF6407B82B421781A12D5D21F87BD730.cache.html, line 17683)

            [Log] [errai]   still waiting for -> [org.jboss.errai.enterprise.client.cdi.api.CDI] (EF6407B82B421781A12D5D21F87BD730.cache.html, line 7643)

            [Log] [errai] bus federated and running. (EF6407B82B421781A12D5D21F87BD730.cache.html, line 7643)

            [Log] [errai] components failed to initialize (EF6407B82B421781A12D5D21F87BD730.cache.html, line 7643)

            [Log] [errai]    [failed] -> org.jboss.errai.enterprise.client.cdi.api.CDI (EF6407B82B421781A12D5D21F87BD730.cache.html, line 7643)

             

            FYI things are fine on Win7+Chrome and Ubuntu 14.04+Firefox.

             

            While I think Maciej is probably right and this is going to be an upstream issue, I suspect they will need help to diagnose it.  Right now there is simply insufficient info.  It might have even been fixed already as they're on 3.x and jbpm is using 2.4.4.

             

            Errai apparently has 4 client-side loggers that apps can configure via a javascript variable.  See Logging - Errai - Project Documentation Editor.


            No idea how this is impl'd in jbpm and it'll be a few weeks before I can pop the hood to take a look myself.  For now I'll just have to ask, does anybody know if there is a way to change the client-side logging level without getting into the code?


            As an aside: if there is not, then I would have thought that would be a very useful enhancement.