13 Replies Latest reply on May 13, 2009 9:38 AM by jaikiran pai

    EJBTHREE-1800

    Søren Hilmer Newbie

      Hi

      We are currently switching from WebLogic to JBoss AS.

      The (re)deploy time of our ear is somewhat annoying, a faktor 2-3 slower than on weblogic (we have ~200 EJB's). We are currently running on JBoss AS 5.1.0CR1.
      I can see that the above mentioned JIRA issue, is dedicated to look into this.

      Any chance this will be fixed before GA?

      Best regards
      Soren

        • 1. Re: EJBTHREE-1800
          jaikiran pai Master

          Yes, that issue is dedicated to look into deployment performance issues with EJB3 deployments. As you can see there, it depends on various other non-EJB3 components of the AS to be fixed. Some of the fixes that were needed in EJB3 have been done. We will continue to work on that and are targeting it to be done for 5.1.0 GA

          • 2. Re: EJBTHREE-1800
            jaikiran pai Master

            If you have anything specific related to deployment performance, that's not covered there, feel free to post the details here.

            • 3. Re: EJBTHREE-1800
              Søren Hilmer Newbie

              Thank you for the update. Looking forward to 5.1.0 GA :-)

              • 4. Re: EJBTHREE-1800
                Søren Hilmer Newbie

                Hi Jaikiran

                A little more info. This is our startup log on 5.1.0 CR1. If it can help you.
                If there is anything else I can provide you with of information, please ask.

                --Soren

                =========================================================================

                JBoss Bootstrap Environment

                JBOSS_HOME: /opt/jboss-5.1.0.CR1

                JAVA: java

                JAVA_OPTS: -Dprogram.name=run.sh -server -Xms128m -Xmx512m -XX:MaxPermSize=256m -Dorg.jboss.resolver.warning=true -Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000 -Djava.net.preferIPv4Stack=true -Dxb.builder.useUnorderedSequence=true

                CLASSPATH: /opt/jboss-5.1.0.CR1/bin/run.jar

                =========================================================================

                09:21:00,832 INFO [ServerImpl] Starting JBoss (Microcontainer)...
                09:21:00,832 INFO [ServerImpl] Release ID: JBoss [The Oracle] 5.1.0.CR1 (build: SVNTag=JBoss_5_1_0_CR1 date=200904290912)
                09:21:00,833 INFO [ServerImpl] Bootstrap URL: null
                09:21:00,833 INFO [ServerImpl] Home Dir: /opt/jboss-5.1.0.CR1
                09:21:00,833 INFO [ServerImpl] Home URL: file:/opt/jboss-5.1.0.CR1/
                09:21:00,833 INFO [ServerImpl] Library URL: file:/opt/jboss-5.1.0.CR1/lib/
                09:21:00,833 INFO [ServerImpl] Patch URL: null
                09:21:00,833 INFO [ServerImpl] Common Base URL: file:/opt/jboss-5.1.0.CR1/common/
                09:21:00,833 INFO [ServerImpl] Common Library URL: file:/opt/jboss-5.1.0.CR1/common/lib/
                09:21:00,834 INFO [ServerImpl] Server Name: ampep
                09:21:00,834 INFO [ServerImpl] Server Base Dir: /opt/jboss-5.1.0.CR1/server
                09:21:00,834 INFO [ServerImpl] Server Base URL: file:/opt/jboss-5.1.0.CR1/server/
                09:21:00,834 INFO [ServerImpl] Server Config URL: file:/opt/jboss-5.1.0.CR1/server/ampep/conf/
                09:21:00,834 INFO [ServerImpl] Server Home Dir: /opt/jboss-5.1.0.CR1/server/ampep
                09:21:00,834 INFO [ServerImpl] Server Home URL: file:/opt/jboss-5.1.0.CR1/server/ampep/
                09:21:00,834 INFO [ServerImpl] Server Data Dir: /opt/jboss-5.1.0.CR1/server/ampep/data
                09:21:00,834 INFO [ServerImpl] Server Library URL: file:/opt/jboss-5.1.0.CR1/server/ampep/lib/
                09:21:00,834 INFO [ServerImpl] Server Log Dir: /opt/jboss-5.1.0.CR1/server/ampep/log
                09:21:00,834 INFO [ServerImpl] Server Native Dir: /opt/jboss-5.1.0.CR1/server/ampep/tmp/native
                09:21:00,834 INFO [ServerImpl] Server Temp Dir: /opt/jboss-5.1.0.CR1/server/ampep/tmp
                09:21:00,834 INFO [ServerImpl] Server Temp Deploy Dir: /opt/jboss-5.1.0.CR1/server/ampep/tmp/deploy
                09:21:01,256 INFO [ServerImpl] Starting Microcontainer, bootstrapURL=file:/opt/jboss-5.1.0.CR1/server/ampep/conf/bootstrap.xml
                09:21:01,637 INFO [VFSCacheFactory] Initializing VFSCache [org.jboss.virtual.plugins.cache.CombinedVFSCache]
                09:21:01,639 INFO [VFSCacheFactory] Using VFSCache [CombinedVFSCache[real-cache: null]]
                09:21:01,848 INFO [CopyMechanism] VFS temp dir: /opt/jboss-5.1.0.CR1/server/ampep/tmp
                09:21:01,848 INFO [ZipEntryContext] VFS force nested jars copy-mode is enabled.
                09:21:02,824 INFO [ServerInfo] Java version: 1.6.0_07,Sun Microsystems Inc.
                09:21:02,824 INFO [ServerInfo] Java Runtime: Java(TM) SE Runtime Environment (build 1.6.0_07-b06)
                09:21:02,824 INFO [ServerInfo] Java VM: Java HotSpot(TM) Server VM 10.0-b23,Sun Microsystems Inc.
                09:21:02,824 INFO [ServerInfo] OS-System: Linux 2.6.24-23-generic,i386
                09:21:02,824 INFO [ServerInfo] VM arguments: -Dprogram.name=run.sh -Xms128m -Xmx512m -XX:MaxPermSize=256m -Dorg.jboss.resolver.warning=true -Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000 -Djava.net.preferIPv4Stack=true -Dxb.builder.useUnorderedSequence=true -Djava.endorsed.dirs=/opt/jboss-5.1.0.CR1/lib/endorsed
                09:21:02,901 INFO [JMXKernel] Legacy JMX core initialized
                09:21:05,235 INFO [ProfileServiceBootstrap] Loading profile: ProfileKey@1747e0f[domain=default, server=default, name=ampep]
                09:21:26,054 WARN [JBossASSecurityMetadataStore] WARNING! POTENTIAL SECURITY RISK. It has been detected that the MessageSucker component which sucks messages from one node to another has not had its password changed from the installation default. Please see the JBoss Messaging user guide for instructions on how to do this.
                09:21:26,068 WARN [AnnotationCreator] No ClassLoader provided, using TCCL: org.jboss.managed.api.annotation.ManagementComponent
                09:21:26,147 WARN [AnnotationCreator] No ClassLoader provided, using TCCL: org.jboss.managed.api.annotation.ManagementComponent
                09:21:28,768 WARN [TransactionManagerService] XAExceptionFormatters are not supported by the JBossTS Transaction Service - this warning can safely be ignored
                09:21:34,501 WARN [InjectInterceptorsFactory] WEIRDNESS IN AOP: advisor org.jboss.ejb3.aop.ExtendedManagedObjectAdvisor@1a28371
                09:21:34,515 WARN [InjectInterceptorsFactory] WEIRDNESS IN AOP: advisor org.jboss.ejb3.aop.ExtendedManagedObjectAdvisor@1a28371
                09:21:35,310 WARN [InjectInterceptorsFactory] WEIRDNESS IN AOP: advisor org.jboss.ejb3.aop.ExtendedManagedObjectAdvisor@801b34
                09:21:35,311 WARN [InjectInterceptorsFactory] WEIRDNESS IN AOP: advisor org.jboss.ejb3.aop.ExtendedManagedObjectAdvisor@801b34
                09:21:35,315 WARN [InjectInterceptorsFactory] WEIRDNESS IN AOP: advisor org.jboss.ejb3.aop.ExtendedManagedObjectAdvisor@801b34
                09:21:35,316 WARN [InjectInterceptorsFactory] WEIRDNESS IN AOP: advisor org.jboss.ejb3.aop.ExtendedManagedObjectAdvisor@801b34
                09:21:35,470 WARN [InjectInterceptorsFactory] WEIRDNESS IN AOP: advisor org.jboss.ejb3.aop.ExtendedManagedObjectAdvisor@5a99f7
                09:21:35,471 WARN [InjectInterceptorsFactory] WEIRDNESS IN AOP: advisor org.jboss.ejb3.aop.ExtendedManagedObjectAdvisor@5a99f7
                09:21:35,472 WARN [InjectInterceptorsFactory] WEIRDNESS IN AOP: advisor org.jboss.ejb3.aop.ExtendedManagedObjectAdvisor@5a99f7
                09:21:35,473 WARN [InjectInterceptorsFactory] WEIRDNESS IN AOP: advisor org.jboss.ejb3.aop.ExtendedManagedObjectAdvisor@5a99f7
                09:21:35,474 WARN [InjectInterceptorsFactory] WEIRDNESS IN AOP: advisor org.jboss.ejb3.aop.ExtendedManagedObjectAdvisor@5a99f7
                09:21:35,475 WARN [InjectInterceptorsFactory] WEIRDNESS IN AOP: advisor org.jboss.ejb3.aop.ExtendedManagedObjectAdvisor@5a99f7
                09:21:35,476 WARN [InjectInterceptorsFactory] WEIRDNESS IN AOP: advisor org.jboss.ejb3.aop.ExtendedManagedObjectAdvisor@5a99f7
                09:21:35,487 WARN [InjectInterceptorsFactory] WEIRDNESS IN AOP: advisor org.jboss.ejb3.aop.ExtendedManagedObjectAdvisor@5a99f7
                09:21:35,488 WARN [InjectInterceptorsFactory] WEIRDNESS IN AOP: advisor org.jboss.ejb3.aop.ExtendedManagedObjectAdvisor@5a99f7
                09:21:35,490 WARN [InjectInterceptorsFactory] WEIRDNESS IN AOP: advisor org.jboss.ejb3.aop.ExtendedManagedObjectAdvisor@5a99f7
                09:21:35,491 WARN [InjectInterceptorsFactory] WEIRDNESS IN AOP: advisor org.jboss.ejb3.aop.ExtendedManagedObjectAdvisor@5a99f7
                09:21:35,491 WARN [InjectInterceptorsFactory] WEIRDNESS IN AOP: advisor org.jboss.ejb3.aop.ExtendedManagedObjectAdvisor@5a99f7
                09:21:35,493 WARN [InjectInterceptorsFactory] WEIRDNESS IN AOP: advisor org.jboss.ejb3.aop.ExtendedManagedObjectAdvisor@5a99f7
                09:21:35,493 WARN [InjectInterceptorsFactory] WEIRDNESS IN AOP: advisor org.jboss.ejb3.aop.ExtendedManagedObjectAdvisor@5a99f7
                09:21:35,601 WARN [InjectInterceptorsFactory] WEIRDNESS IN AOP: advisor org.jboss.ejb3.aop.ExtendedManagedObjectAdvisor@1d551eb
                09:21:35,602 WARN [InjectInterceptorsFactory] WEIRDNESS IN AOP: advisor org.jboss.ejb3.aop.ExtendedManagedObjectAdvisor@1d551eb
                09:21:35,602 WARN [InjectInterceptorsFactory] WEIRDNESS IN AOP: advisor org.jboss.ejb3.aop.ExtendedManagedObjectAdvisor@1d551eb
                09:21:35,602 WARN [InjectInterceptorsFactory] WEIRDNESS IN AOP: advisor org.jboss.ejb3.aop.ExtendedManagedObjectAdvisor@1d551eb
                09:21:35,603 WARN [InjectInterceptorsFactory] WEIRDNESS IN AOP: advisor org.jboss.ejb3.aop.ExtendedManagedObjectAdvisor@1d551eb
                09:21:35,608 WARN [InjectInterceptorsFactory] WEIRDNESS IN AOP: advisor org.jboss.ejb3.aop.ExtendedManagedObjectAdvisor@1d551eb
                09:21:35,609 WARN [InjectInterceptorsFactory] WEIRDNESS IN AOP: advisor org.jboss.ejb3.aop.ExtendedManagedObjectAdvisor@1d551eb
                09:21:35,609 WARN [InjectInterceptorsFactory] WEIRDNESS IN AOP: advisor org.jboss.ejb3.aop.ExtendedManagedObjectAdvisor@1d551eb
                09:21:35,609 WARN [InjectInterceptorsFactory] WEIRDNESS IN AOP: advisor org.jboss.ejb3.aop.ExtendedManagedObjectAdvisor@1d551eb
                09:21:35,610 WARN [InjectInterceptorsFactory] WEIRDNESS IN AOP: advisor org.jboss.ejb3.aop.ExtendedManagedObjectAdvisor@1d551eb
                09:21:35,712 WARN [InjectInterceptorsFactory] WEIRDNESS IN AOP: advisor org.jboss.ejb3.aop.ExtendedManagedObjectAdvisor@1632afe
                09:21:35,742 WARN [InjectInterceptorsFactory] WEIRDNESS IN AOP: advisor org.jboss.ejb3.aop.ExtendedManagedObjectAdvisor@1632afe
                09:21:35,743 WARN [InjectInterceptorsFactory] WEIRDNESS IN AOP: advisor org.jboss.ejb3.aop.ExtendedManagedObjectAdvisor@1632afe
                09:21:35,743 WARN [InjectInterceptorsFactory] WEIRDNESS IN AOP: advisor org.jboss.ejb3.aop.ExtendedManagedObjectAdvisor@1632afe
                09:21:35,749 WARN [InjectInterceptorsFactory] WEIRDNESS IN AOP: advisor org.jboss.ejb3.aop.ExtendedManagedObjectAdvisor@1632afe
                09:21:35,750 WARN [InjectInterceptorsFactory] WEIRDNESS IN AOP: advisor org.jboss.ejb3.aop.ExtendedManagedObjectAdvisor@1632afe
                09:21:35,750 WARN [InjectInterceptorsFactory] WEIRDNESS IN AOP: advisor org.jboss.ejb3.aop.ExtendedManagedObjectAdvisor@1632afe
                09:21:35,751 WARN [InjectInterceptorsFactory] WEIRDNESS IN AOP: advisor org.jboss.ejb3.aop.ExtendedManagedObjectAdvisor@1632afe
                09:21:35,768 WARN [InjectInterceptorsFactory] WEIRDNESS IN AOP: advisor org.jboss.ejb3.aop.ExtendedManagedObjectAdvisor@1535917
                09:21:35,769 WARN [InjectInterceptorsFactory] WEIRDNESS IN AOP: advisor org.jboss.ejb3.aop.ExtendedManagedObjectAdvisor@1535917
                09:21:35,773 WARN [InjectInterceptorsFactory] WEIRDNESS IN AOP: advisor org.jboss.ejb3.aop.ExtendedManagedObjectAdvisor@1535917
                09:21:35,774 WARN [InjectInterceptorsFactory] WEIRDNESS IN AOP: advisor org.jboss.ejb3.aop.ExtendedManagedObjectAdvisor@1535917
                09:21:35,915 WARN [InjectInterceptorsFactory] WEIRDNESS IN AOP: advisor org.jboss.ejb3.aop.ExtendedManagedObjectAdvisor@1d2cd78
                09:21:35,915 WARN [InjectInterceptorsFactory] WEIRDNESS IN AOP: advisor org.jboss.ejb3.aop.ExtendedManagedObjectAdvisor@1d2cd78
                09:21:35,921 WARN [InjectInterceptorsFactory] WEIRDNESS IN AOP: advisor org.jboss.ejb3.aop.ExtendedManagedObjectAdvisor@1d2cd78
                09:21:35,921 WARN [InjectInterceptorsFactory] WEIRDNESS IN AOP: advisor org.jboss.ejb3.aop.ExtendedManagedObjectAdvisor@1d2cd78
                09:21:35,945 WARN [InjectInterceptorsFactory] WEIRDNESS IN AOP: advisor org.jboss.ejb3.aop.ExtendedManagedObjectAdvisor@b24245
                09:21:35,948 WARN [InjectInterceptorsFactory] WEIRDNESS IN AOP: advisor org.jboss.ejb3.aop.ExtendedManagedObjectAdvisor@b24245
                09:21:36,065 WARN [InjectInterceptorsFactory] WEIRDNESS IN AOP: advisor org.jboss.ejb3.aop.ExtendedManagedObjectAdvisor@1ee970
                09:21:36,071 WARN [InjectInterceptorsFactory] WEIRDNESS IN AOP: advisor org.jboss.ejb3.aop.ExtendedManagedObjectAdvisor@1ee970
                09:21:36,192 WARN [InjectInterceptorsFactory] WEIRDNESS IN AOP: advisor org.jboss.ejb3.aop.ExtendedManagedObjectAdvisor@1e67792
                09:21:36,194 WARN [InjectInterceptorsFactory] WEIRDNESS IN AOP: advisor org.jboss.ejb3.aop.ExtendedManagedObjectAdvisor@1e67792
                09:21:36,194 WARN [InjectInterceptorsFactory] WEIRDNESS IN AOP: advisor org.jboss.ejb3.aop.ExtendedManagedObjectAdvisor@1e67792
                09:21:36,199 WARN [InjectInterceptorsFactory] WEIRDNESS IN AOP: advisor org.jboss.ejb3.aop.ExtendedManagedObjectAdvisor@1e67792
                09:21:36,200 WARN [InjectInterceptorsFactory] WEIRDNESS IN AOP: advisor org.jboss.ejb3.aop.ExtendedManagedObjectAdvisor@1e67792
                09:21:36,200 WARN [InjectInterceptorsFactory] WEIRDNESS IN AOP: advisor org.jboss.ejb3.aop.ExtendedManagedObjectAdvisor@1e67792
                09:21:36,466 WARN [InjectInterceptorsFactory] WEIRDNESS IN AOP: advisor org.jboss.ejb3.aop.ExtendedManagedObjectAdvisor@7db532
                09:21:36,470 WARN [InjectInterceptorsFactory] WEIRDNESS IN AOP: advisor org.jboss.ejb3.aop.ExtendedManagedObjectAdvisor@7db532
                09:21:36,694 WARN [InjectInterceptorsFactory] WEIRDNESS IN AOP: advisor org.jboss.ejb3.aop.ExtendedManagedObjectAdvisor@1f613c
                09:21:36,698 WARN [InjectInterceptorsFactory] WEIRDNESS IN AOP: advisor org.jboss.ejb3.aop.ExtendedManagedObjectAdvisor@1f613c
                09:21:36,901 WARN [InjectInterceptorsFactory] WEIRDNESS IN AOP: advisor org.jboss.ejb3.aop.ExtendedManagedObjectAdvisor@f55979
                09:21:36,902 WARN [InjectInterceptorsFactory] WEIRDNESS IN AOP: advisor org.jboss.ejb3.aop.ExtendedManagedObjectAdvisor@f55979
                09:21:36,902 WARN [InjectInterceptorsFactory] WEIRDNESS IN AOP: advisor org.jboss.ejb3.aop.ExtendedManagedObjectAdvisor@f55979
                09:21:36,903 WARN [InjectInterceptorsFactory] WEIRDNESS IN AOP: advisor org.jboss.ejb3.aop.ExtendedManagedObjectAdvisor@f55979
                09:21:36,903 WARN [InjectInterceptorsFactory] WEIRDNESS IN AOP: advisor org.jboss.ejb3.aop.ExtendedManagedObjectAdvisor@f55979
                09:21:36,908 WARN [InjectInterceptorsFactory] WEIRDNESS IN AOP: advisor org.jboss.ejb3.aop.ExtendedManagedObjectAdvisor@f55979
                09:21:36,908 WARN [InjectInterceptorsFactory] WEIRDNESS IN AOP: advisor org.jboss.ejb3.aop.ExtendedManagedObjectAdvisor@f55979
                09:21:36,909 WARN [InjectInterceptorsFactory] WEIRDNESS IN AOP: advisor org.jboss.ejb3.aop.ExtendedManagedObjectAdvisor@f55979
                09:21:36,909 WARN [InjectInterceptorsFactory] WEIRDNESS IN AOP: advisor org.jboss.ejb3.aop.ExtendedManagedObjectAdvisor@f55979
                09:21:36,909 WARN [InjectInterceptorsFactory] WEIRDNESS IN AOP: advisor org.jboss.ejb3.aop.ExtendedManagedObjectAdvisor@f55979
                09:21:39,515 WARN [InjectInterceptorsFactory] WEIRDNESS IN AOP: advisor org.jboss.ejb3.aop.ExtendedManagedObjectAdvisor@12030cd
                09:21:39,518 WARN [InjectInterceptorsFactory] WEIRDNESS IN AOP: advisor org.jboss.ejb3.aop.ExtendedManagedObjectAdvisor@12030cd
                09:21:39,678 WARN [InjectInterceptorsFactory] WEIRDNESS IN AOP: advisor org.jboss.ejb3.aop.ExtendedManagedObjectAdvisor@9533f5
                09:21:39,685 WARN [InjectInterceptorsFactory] WEIRDNESS IN AOP: advisor org.jboss.ejb3.aop.ExtendedManagedObjectAdvisor@9533f5
                09:21:41,249 WARN [InjectInterceptorsFactory] WEIRDNESS IN AOP: advisor org.jboss.ejb3.aop.ExtendedManagedObjectAdvisor@db3d3e
                09:21:41,250 WARN [InjectInterceptorsFactory] WEIRDNESS IN AOP: advisor org.jboss.ejb3.aop.ExtendedManagedObjectAdvisor@db3d3e
                09:21:41,252 WARN [InjectInterceptorsFactory] WEIRDNESS IN AOP: advisor org.jboss.ejb3.aop.ExtendedManagedObjectAdvisor@db3d3e
                09:21:41,252 WARN [InjectInterceptorsFactory] WEIRDNESS IN AOP: advisor org.jboss.ejb3.aop.ExtendedManagedObjectAdvisor@db3d3e
                09:21:41,425 WARN [InjectInterceptorsFactory] WEIRDNESS IN AOP: advisor org.jboss.ejb3.aop.ExtendedManagedObjectAdvisor@326c52
                09:21:41,427 WARN [InjectInterceptorsFactory] WEIRDNESS IN AOP: advisor org.jboss.ejb3.aop.ExtendedManagedObjectAdvisor@326c52
                09:21:41,705 WARN [InjectInterceptorsFactory] WEIRDNESS IN AOP: advisor org.jboss.ejb3.aop.ExtendedManagedObjectAdvisor@18a6420
                09:21:41,707 WARN [InjectInterceptorsFactory] WEIRDNESS IN AOP: advisor org.jboss.ejb3.aop.ExtendedManagedObjectAdvisor@18a6420
                09:21:47,947 WARN [Ejb3Configuration] Persistence provider caller does not implement the EJB3 spec correctly. PersistenceUnitInfo.getNewTempClassLoader() is null.
                09:21:49,266 WARN [SessionFactoryObjectFactory] InitialContext did not implement EventContext
                09:21:58,377 WARN [InterceptorsFactory] EJBTHREE-1246: Do not use InterceptorsFactory with a ManagedObjectAdvisor, InterceptorRegistry should be used via the bean container
                09:21:58,378 WARN [InterceptorsFactory] EJBTHREE-1246: Do not use InterceptorsFactory with a ManagedObjectAdvisor, InterceptorRegistry should be used via the bean container
                09:21:58,564 WARN [InterceptorsFactory] EJBTHREE-1246: Do not use InterceptorsFactory with a ManagedObjectAdvisor, InterceptorRegistry should be used via the bean container
                09:21:58,564 WARN [InterceptorsFactory] EJBTHREE-1246: Do not use InterceptorsFactory with a ManagedObjectAdvisor, InterceptorRegistry should be used via the bean container
                09:21:58,631 WARN [InterceptorsFactory] EJBTHREE-1246: Do not use InterceptorsFactory with a ManagedObjectAdvisor, InterceptorRegistry should be used via the bean container
                09:21:58,631 WARN [InterceptorsFactory] EJBTHREE-1246: Do not use InterceptorsFactory with a ManagedObjectAdvisor, InterceptorRegistry should be used via the bean container
                09:21:58,671 WARN [InterceptorsFactory] EJBTHREE-1246: Do not use InterceptorsFactory with a ManagedObjectAdvisor, InterceptorRegistry should be used via the bean container
                09:21:58,671 WARN [InterceptorsFactory] EJBTHREE-1246: Do not use InterceptorsFactory with a ManagedObjectAdvisor, InterceptorRegistry should be used via the bean container
                09:21:58,799 WARN [InterceptorsFactory] EJBTHREE-1246: Do not use InterceptorsFactory with a ManagedObjectAdvisor, InterceptorRegistry should be used via the bean container
                09:21:58,799 WARN [InterceptorsFactory] EJBTHREE-1246: Do not use InterceptorsFactory with a ManagedObjectAdvisor, InterceptorRegistry should be used via the bean container
                09:21:58,857 WARN [InterceptorsFactory] EJBTHREE-1246: Do not use InterceptorsFactory with a ManagedObjectAdvisor, InterceptorRegistry should be used via the bean container
                09:21:58,858 WARN [InterceptorsFactory] EJBTHREE-1246: Do not use InterceptorsFactory with a ManagedObjectAdvisor, InterceptorRegistry should be used via the bean container
                09:21:58,895 WARN [InterceptorsFactory] EJBTHREE-1246: Do not use InterceptorsFactory with a ManagedObjectAdvisor, InterceptorRegistry should be used via the bean container
                09:21:58,895 WARN [InterceptorsFactory] EJBTHREE-1246: Do not use InterceptorsFactory with a ManagedObjectAdvisor, InterceptorRegistry should be used via the bean container
                09:21:58,932 WARN [InterceptorsFactory] EJBTHREE-1246: Do not use InterceptorsFactory with a ManagedObjectAdvisor, InterceptorRegistry should be used via the bean container
                09:21:58,932 WARN [InterceptorsFactory] EJBTHREE-1246: Do not use InterceptorsFactory with a ManagedObjectAdvisor, InterceptorRegistry should be used via the bean container
                09:21:58,971 WARN [InterceptorsFactory] EJBTHREE-1246: Do not use InterceptorsFactory with a ManagedObjectAdvisor, InterceptorRegistry should be used via the bean container
                09:21:58,972 WARN [InterceptorsFactory] EJBTHREE-1246: Do not use InterceptorsFactory with a ManagedObjectAdvisor, InterceptorRegistry should be used via the bean container
                09:21:59,008 WARN [InterceptorsFactory] EJBTHREE-1246: Do not use InterceptorsFactory with a ManagedObjectAdvisor, InterceptorRegistry should be used via the bean container
                09:21:59,008 WARN [InterceptorsFactory] EJBTHREE-1246: Do not use InterceptorsFactory with a ManagedObjectAdvisor, InterceptorRegistry should be used via the bean container
                09:22:09,149 ERROR [SmsManager] No scan dir was found. Stopping reader

                • 5. Re: EJBTHREE-1800
                  jaikiran pai Master

                   

                  "hilmer" wrote:

                  If there is anything else I can provide you with of information, please ask.

                  --Soren


                  If possible, can you attach this app to EJBTHREE-1800?

                  • 6. Re: EJBTHREE-1800
                    Søren Hilmer Newbie

                    Sorry, I am no allowed to do that.
                    I can provide some statistics if that is in your interest (methods pr. bean, exact number of beans, ...)

                    --Soren

                    • 7. Re: EJBTHREE-1800
                      jaikiran pai Master

                       

                      "hilmer" wrote:
                      Sorry, I am no allowed to do that.


                      Fair enough :)

                      "hilmer" wrote:

                      I can provide some statistics if that is in your interest (methods pr. bean, exact number of beans, ...)

                      --Soren


                      These might help:

                      1) Start a clean "default" server configuration of JBossAS-5.1.0.CR1
                      2) Once the server completely starts, place your application in the deploy folder
                      3) Note the time, on the server console, when the first log message appears when your applications gets picked up by the hot deployer.
                      4) Wait for the application to be completely deployed and note the time.
                      5) Post the time details here and attach the server.log and the console log to EJBTHREE-1800

                      Also let us know, how many beans you have. What kind of beans are they? Stateless, Stateful or a mix of both? How heavily are objects injected in these beans? Any @EJB or @Resource injections? And approximately how many methods per bean?


                      • 8. Re: EJBTHREE-1800
                        jaikiran pai Master

                        One of the fixes to the deployment timing was done as part of https://jira.jboss.org/jira/browse/EJBTHREE-1808

                        This fix is a one xml file change. So if you want to test it out then here's what you could do:

                        1) Get this fix from the EJB3 trunk SVN http://anonsvn.jboss.org/repos/jbossas/projects/ejb3/trunk/core/src/main/resources/ejb3-interceptors-aop.xml
                        2) Backup the existing ejb3-interceptors-aop.xml from server/< serverName>/deploy folder of JBossAS
                        3) Replace the existing file with this new fixed copy.

                        Then follow the steps that i mentioned in my previous post (let the server start first, before deploying your application - to give us some accurate timings).

                        Locally, on my sample applications, this fix has shown around 30% improvement in deployment timings. Let us know if that fix shows any improvements for you :)

                        • 9. Re: EJBTHREE-1800
                          Henrik Thuesen Newbie

                          I am working on the same project as hilmer, and I would like to answer the above questions:

                          We currently have about 290 stateless session beans and no other kind of beans. Most of them have references via @EJB to 1-4 other beans. We have about 5 servlets and some special beans, which have more @EJB annotations in the order of 10-20.

                          We use both @Resource and @PersistenceContext; @Resource not so often, but we do have quite a few DAOs with references to EntityManagers.

                          The number of methods per bean varies a lot, but it certainly fit into the range 2-20, where 20 is very rare. Typically in the order of 9 methods.

                          • 10. Re: EJBTHREE-1800
                            jaikiran pai Master

                            Thanks for this information, henrikthuesen.

                            How much time does this application take to deploy on JBossAS-5.1.0 CR1?

                            • 11. Re: EJBTHREE-1800
                              Søren Hilmer Newbie

                              Hi

                              The time on my machine using the CR1 version of ejb3-interceptors-aop.xml is 37sec
                              With the trunk version of ejb3-interceptors-aop.xml the time is 33sec, so it is a 10% speedup.

                              --Soren

                              • 12. Re: EJBTHREE-1800
                                jaikiran pai Master

                                Thanks for the info. Not much improvement with this single change. We are currently working on various issues related to EJBTHREE-1800. Will keep that JIRA updated.