2 Replies Latest reply on Mar 10, 2008 10:34 PM by Denis Forveille

    Urgent: seam 1.2.1. is there a limit in the number of components?

    Denis Forveille Novice

      This sounds very strange but it seems that there is a limit in the number of declared components seam 1.2.1 can handle.


      Until yesterday, our seam 1.2.1 application was working well, but today we added some new components and our application doesnt even want to start.


      After some testing, it seems that adding just ONE component make the application fail to start (whatever the scope and where this component is defined)


      It seems that we have 128 components declared (1 is the hibernate session, the others are declared with annotations). This counting does not count the components created by the application itself (eg outjected components, DataModels, factories etc...).


      The symptoms? when we add that extra components, we have jndi lookup exceptions on the hibernate session factory which is not present in the jndi space. when we remove ONE of the seam components, the application works ...strange


      I know this sounds silly but we are blocked as we can not add any new component..


      Our env:



      • seam v1.2.1 with plain POJOs

      • WebSphere v6.1.0.13

      • JSF 1.2_07

      • facelets v1.1.14

      • rich faces v3.1.14

        • 1. Re: Urgent: seam 1.2.1. is there a limit in the number of components?
          Nicklas Karlsson Master

          Can you do something like (on a clean app)


          
          for (int i = 0; i < 130; i++) {
          
            Contexts.getSessionContext.set(i + "", new String(i + ""));
          
          }
          
          



          (OK, OK, ugly conversion forcing and unnecessary lookup but it's a test)

          • 2. Re: Urgent: seam 1.2.1. is there a limit in the number of components?
            Denis Forveille Novice

            Nicklas,
            I put the code you post in our application at various places and it works without any problem.
            Seam produces the following traces: Is this normal to trace related to org.jboss.seam.core.interpolator present only on the last variable ?



            DEBUG [web.WebApptil ] - Before Loop============
            DEBUG [seam.Component] - instantiating Seam component: org.jboss.seam.core.events
            DEBUG [seam.Component] - initializing new instance of: org.jboss.seam.core.events
            DEBUG [seam.Component] - done initializing: org.jboss.seam.core.events
            DEBUG [seam.Component] - instantiating Seam component: org.jboss.seam.core.events
            DEBUG [seam.Component] - initializing new instance of: org.jboss.seam.core.events
            DEBUG [seam.Component] - done initializing: org.jboss.seam.core.events
            DEBUG [core.Events   ] - Processing event:org.jboss.seam.preSetVariable.0
            DEBUG [seam.Component] - instantiating Seam component: org.jboss.seam.core.events
            DEBUG [seam.Component] - initializing new instance of: org.jboss.seam.core.events
            DEBUG [seam.Component] - done initializing: org.jboss.seam.core.events
            DEBUG [seam.Component] - instantiating Seam component: org.jboss.seam.core.events
            DEBUG [seam.Component] - initializing new instance of: org.jboss.seam.core.events
            DEBUG [seam.Component] - done initializing: org.jboss.seam.core.events
            DEBUG [core.Events   ] - Processing event:org.jboss.seam.postSetVariable.0
            ...
            DEBUG [seam.Component] - instantiating Seam component: org.jboss.seam.core.events
            DEBUG [seam.Component] - initializing new instance of: org.jboss.seam.core.events
            DEBUG [seam.Component] - done initializing: org.jboss.seam.core.events
            DEBUG [seam.Component] - instantiating Seam component: org.jboss.seam.core.events
            DEBUG [seam.Component] - initializing new instance of: org.jboss.seam.core.events
            DEBUG [seam.Component] - done initializing: org.jboss.seam.core.events
            DEBUG [core.Events   ] - Processing event:org.jboss.seam.preSetVariable.129
            DEBUG [seam.Component] - instantiating Seam component: org.jboss.seam.core.events
            DEBUG [seam.Component] - initializing new instance of: org.jboss.seam.core.events
            DEBUG [seam.Component] - done initializing: org.jboss.seam.core.events
            DEBUG [seam.Component] - instantiating Seam component: org.jboss.seam.core.events
            DEBUG [seam.Component] - initializing new instance of: org.jboss.seam.core.events
            DEBUG [seam.Component] - done initializing: org.jboss.seam.core.events
            DEBUG [core.Events   ] - Processing event:org.jboss.seam.postSetVariable.129
            DEBUG [seam.Component] - instantiating Seam component: org.jboss.seam.core.interpolator
            DEBUG [seam.Component] - initializing new instance of: org.jboss.seam.core.interpolator
            DEBUG [seam.Component] - done initializing: org.jboss.seam.core.interpolator
            DEBUG [web.WebApptil ] - After Loop============