1 2 Previous Next 24 Replies Latest reply on Oct 2, 2006 10:08 AM by Kabir Khan

    What's the status of HEAD?

    Bill Burke Master

      I've been gone for a week and trying to catch up on things. My EJB3 team tells me that HEAD is f'd up and stop/destroy is not being called on managed EJB3 components. Has the switch to the new MC been done? Can somebody post a status message or point me to a forum post? I'm unable to find one ATM that explains what is the current state of HEAD.

      Thanks

        • 2. Re: What's the status of HEAD?
          Scott Stark Master

          I was out last week as well and as far as I know the trunk has not been converted over to use the mc based SARDeployer and jmx integration. I'm checking out the trunk to see what its state is.

          All the VDF/MC work that I have been doing is ocurring on https://svn.jboss.org/repos/jbossas/branches/MC_VDF_WORK/

          • 3. Re: What's the status of HEAD?
            Scott Stark Master

            The ServiceController in trunk was updated to use the jmx/mc integration code on the 16th, so that is the underlying change. I'm looking into the behavior of the testcase Anil mentioned.

            • 4. Re: What's the status of HEAD?
              Scott Stark Master

              So what are the ejb3 uses that are failing? I need pointers to specific uses so I can get corresponding unit tests into the JMX/MC codebase.

              • 5. Re: What's the status of HEAD?
                Adrian Brock Master

                I think Bill is referring to this?
                "
                Author: wolfc
                Date: 2006-08-16 12:04:56 -0400 (Wed, 16 Aug 2006)
                New Revision: 55992

                Modified:
                trunk/ejb3/src/main/org/jboss/ejb3/JmxKernelAbstraction.java
                Log:
                uninstallation in the correct order

                Modified: trunk/ejb3/src/main/org/jboss/ejb3/JmxKernelAbstraction.java
                ===================================================================
                --- trunk/ejb3/src/main/org/jboss/ejb3/JmxKernelAbstraction.java 2006-08-16 15:38:48 UTC (rev 55991)
                +++ trunk/ejb3/src/main/org/jboss/ejb3/JmxKernelAbstraction.java 2006-08-16 16:04:56 UTC (rev 55992)
                @@ -145,11 +145,11 @@
                {
                try
                {
                - server.unregisterMBean(on);
                - removeParentDependency(on);
                serviceController.stop(on);
                serviceController.destroy(on);
                serviceController.remove(on);
                + removeParentDependency(on);
                + server.unregisterMBean(on);
                }
                catch (Exception e)
                {
                "

                If there isn't a clear bug report/test, not an "IT IS BROKEN"
                then the problem doesn't exist AFAIC. :-)

                • 6. Re: What's the status of HEAD?
                  Bill Burke Master

                  I just wanted to know if the kernel changes went in because my guys were having problems...

                  • 7. Re: What's the status of HEAD?
                    Vicky Kak Master

                    I am not able to run the testsuite , the build fails with the error as
                    **********************************
                    compile-annotated-classes-50:
                    [javac] Compiling 3 source files to C:\svn\trunk\testsuite\output\classes

                    BUILD FAILED
                    C:\svn\trunk\testsuite\build.xml:382: Reference sun.opends.classpath not found.
                    **********************************

                    Regards
                    Vicky

                    • 8. Re: What's the status of HEAD?
                      Scott Stark Master

                      Your thirdparty contents are not up to date then. Remove it and do a clean build as sun.opends.classpath exists in my build.

                      [starksm@succubus testsuite]$ grep -C3 sun.opends.classpath ../thirdparty/libraries.ent
                      <property name="sun.opends.root" value="${project.thirdparty}/sun-opends"/>
                      <property name="sun.opends.lib" value="${sun.opends.root}/lib/"/>
                      <property name="sun.opends.resources" value="${sun.opends.root}/resources/"/>
                      <path id="sun.opends.classpath">
                       <pathelement path="${sun.opends.lib}/OpenDS.jar"/>
                      </path>
                      



                      • 9. Re: What's the status of HEAD?
                        Vicky Kak Master

                        Yes this was because of the thirdparty not being updated, build works fine now.
                        But I am getting the booting issues, I cant see the jmx-console coming up after the booting is over.
                        Additional the testsuite build fails.
                        Here is the booting error pasted ,

                        ***********************************************************
                        jar:file:/C:/svn/trunk/build/output/jboss-5.0.0.Beta/server/default/deploy/jboss
                        ws.sar/jbossws-context.war!/

                        *** CONTEXTS MISSING DEPENDENCIES: Name -> Dependency{Required State:Actual Stat
                        e}

                        jboss.ejb3:service=EJB3Deployer
                        -> jboss.ejb:service=EJBDeployer{Create:** NOT FOUND **}
                        -> jboss.ejb:service=EJBDeployer{Start:** NOT FOUND **}

                        jboss.ws:service=DeployerInterceptorEJB21
                        -> jboss.ejb:service=EJBDeployer{Start:** NOT FOUND **}
                        -> jboss.ejb:service=EJBDeployer{Create:** NOT FOUND **}

                        jboss.ws:service=DeployerInterceptorEJB3
                        -> jboss.ejb3:service=EJB3Deployer{Start:Configured}
                        -> jboss.ejb3:service=EJB3Deployer{Create:Configured}


                        *** CONTEXTS IN ERROR: Name -> Error

                        jboss.ejb:service=EJBDeployer -> ** NOT FOUND **


                        16:01:19,203 INFO [Http11Protocol] Starting Coyote HTTP/1.1 on http-0.0.0.0-8080
                        ***********************************************************

                        • 10. Re: What's the status of HEAD?
                          Scott Stark Master

                          That is the current state. Until the deployers get ported over not all content is deploying.

                          • 11. Re: What's the status of HEAD?
                            Vicky Kak Master

                            ok :(
                            Actually I was trying to run the MainWithSimpleHotDeployTestCase , this was earlier in the head . It seems this has been moved to the MC_VDF_WORK which also does not appear to be working as of now .
                            Is there any other branch where I can run this.

                            • 12. Re: What's the status of HEAD?
                              Scott Stark Master

                              I guess that was not merged to trunk when the MC_VDF_WORK branch was merged. It was broken anyway with the recent changes. I now have the MainWithSimpleHotDeployTestCase running for me within eclipse on trunk:

                              19:42:35,015 INFO [ServerImpl] Starting JBoss (Microcontainer)...
                              19:42:35,015 INFO [ServerImpl] Release ID: null null
                              19:42:35,015 INFO [ServerImpl] Home Dir: C:\svn\JBossHead\jboss-head\system
                              19:42:35,015 INFO [ServerImpl] Home URL: file:/C:/svn/JBossHead/jboss-head/system/
                              19:42:35,015 INFO [ServerImpl] Library URL: file:/C:/svn/JBossHead/jboss-head/system/lib/
                              19:42:35,015 INFO [ServerImpl] Patch URL: null
                              19:42:35,015 INFO [ServerImpl] Server Name: defaulthotdeploy
                              19:42:35,015 INFO [ServerImpl] Server Home Dir: C:\svn\JBossHead\jboss-head\system\server\defaulthotdeploy
                              19:42:35,015 INFO [ServerImpl] Server Home URL: file:/C:/svn/JBossHead/jboss-head/system/server/defaulthotdeploy/
                              19:42:35,031 INFO [ServerImpl] Server Data Dir: C:\svn\JBossHead\jboss-head\system\server\defaulthotdeploy\data
                              19:42:35,031 INFO [ServerImpl] Server Temp Dir: C:\svn\JBossHead\jboss-head\system\server\defaulthotdeploy\tmp
                              19:42:35,031 INFO [ServerImpl] Server Config URL: file:/C:/svn/JBossHead/jboss-head/system/server/defaulthotdeploy/conf/
                              19:42:35,031 INFO [ServerImpl] Server Library URL: file:/C:/svn/JBossHead/jboss-head/system/server/defaulthotdeploy/lib/
                              19:42:35,031 INFO [ServerImpl] Root Deployment Filename: jboss-service.xml
                              19:42:35,109 INFO [ServerImpl] Starting Microcontainer, deployerBeansPrefix=tests/bootstrap/defaulthotdeploy/
                              19:42:36,140 INFO [ProfileImpl] Using profile root:C:\svn\JBossHead\jboss-head\system\file:\C:\svn\JBossHead\jboss-head\system\output\eclipse-resources
                              19:42:36,453 INFO [ServerImpl] JBoss (Microcontainer) [null] Started in 1s:422ms
                              19:42:36,453 INFO [MainWithSimpleHotDeployTestCase] TestBean.CS: (file:/C:/svn/JBossHead/jboss-head/system/output/eclipse-test-classes/ <no signer certificates>)
                              19:42:36,453 INFO [MainWithSimpleHotDeployTestCase] TestBean.ClassLoader: sun.misc.Launcher$AppClassLoader@133056f
                              19:42:36,468 INFO [ServerImpl] LifeThread.run exits!
                              19:42:36,468 INFO [ServerImpl] Shutting down the JVM now!
                              19:42:36,468 INFO [ServerImpl] JBoss SHUTDOWN
                              19:42:36,468 INFO [ServerImpl] Undeploying all packages
                              Shutting down Microcontainer
                              19:42:36,515 INFO [ServerImpl] Shutdown complete
                              Shutdown complete
                              Halting VM
                              



                              • 13. Re: What's the status of HEAD?
                                Vicky Kak Master

                                Na I am not yet able to get it .....
                                Here is the error

                                Testsuite: org.jboss.test.server.profileservice.MainWithSimpleHotDeployTestCase
                                Tests run: 1, Failures: 0, Errors: 1, Time elapsed: 0.641 sec
                                ------------- Standard Output ---------------
                                0 [main] DEBUG org.jboss.test.server.profileservice.MainWithSimpleHotDeployTestCase - ==== Starting testDefaultStartup ====
                                32 [main] INFO org.jboss.system.server.profileservice.ServerImpl - Starting JBoss (Microcontainer)...
                                32 [main] INFO org.jboss.system.server.profileservice.ServerImpl - Release ID: null null
                                32 [main] DEBUG org.jboss.system.server.profileservice.ServerImpl - Using config: org.jboss.system.server.BaseServerConfig@5d173
                                32 [main] DEBUG org.jboss.system.server.profileservice.ServerImpl - Server type: class org.jboss.system.server.profileservice.ServerImpl
                                32 [main] INFO org.jboss.system.server.profileservice.ServerImpl - Home Dir: C:\svn\trunk\system
                                32 [main] INFO org.jboss.system.server.profileservice.ServerImpl - Home URL: file:/C:/svn/trunk/system/
                                47 [main] INFO org.jboss.system.server.profileservice.ServerImpl - Library URL: file:/C:/svn/trunk/system/lib/
                                47 [main] INFO org.jboss.system.server.profileservice.ServerImpl - Patch URL: null
                                47 [main] INFO org.jboss.system.server.profileservice.ServerImpl - Server Name: defaulthotdeploy
                                47 [main] INFO org.jboss.system.server.profileservice.ServerImpl - Server Home Dir: C:\svn\trunk\system\server\defaulthotdeploy
                                47 [main] INFO org.jboss.system.server.profileservice.ServerImpl - Server Home URL: file:/C:/svn/trunk/system/server/defaulthotdeploy/
                                47 [main] INFO org.jboss.system.server.profileservice.ServerImpl - Server Data Dir: C:\svn\trunk\system\server\defaulthotdeploy\data
                                47 [main] INFO org.jboss.system.server.profileservice.ServerImpl - Server Temp Dir: C:\svn\trunk\system\server\defaulthotdeploy\tmp
                                47 [main] INFO org.jboss.system.server.profileservice.ServerImpl - Server Config URL: file:/C:/svn/trunk/system/server/defaulthotdeploy/conf/
                                47 [main] INFO org.jboss.system.server.profileservice.ServerImpl - Server Library URL: file:/C:/svn/trunk/system/server/defaulthotdeploy/lib/
                                47 [main] INFO org.jboss.system.server.profileservice.ServerImpl - Root Deployment Filename: jboss-service.xml
                                63 [main] INFO org.jboss.system.server.profileservice.ServerImpl - Starting Microcontainer, deployerBeansPrefix=
                                78 [main] DEBUG org.jboss.system.server.profileservice.ServerImpl - Shutdown hook added
                                78 [main] DEBUG org.jboss.kernel.KernelFactory - Starting JBoss Kernel construction...
                                141 [main] DEBUG org.jboss.system.server.profileservice.ServerImpl - Failed to start
                                java.lang.RuntimeException: Unable to create a KernelInitializer based on the specified KernelConfig
                                 at org.jboss.kernel.KernelFactory.createKernelInitializer(KernelFactory.java:156)
                                 at org.jboss.kernel.KernelFactory.assembleNewKernel(KernelFactory.java:99)
                                 at org.jboss.kernel.KernelFactory.newInstance(KernelFactory.java:67)
                                 at org.jboss.kernel.plugins.bootstrap.AbstractBootstrap.bootstrap(AbstractBootstrap.java:120)
                                 at org.jboss.system.server.profileservice.ProfileServiceBootstrap.bootstrap(ProfileServiceBootstrap.java:186)
                                 at org.jboss.kernel.plugins.bootstrap.AbstractBootstrap.run(AbstractBootstrap.java:89)
                                 at org.jboss.system.server.profileservice.ServerImpl.doStart(ServerImpl.java:401)
                                 at org.jboss.system.server.profileservice.ServerImpl.start(ServerImpl.java:340)
                                 at org.jboss.Main.boot(Main.java:210)
                                 at org.jboss.test.server.profileservice.MainWithSimpleHotDeployTestCase.testDefaultStartup(MainWithSimpleHotDeployTestCase.java:105)
                                 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
                                 at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
                                 at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
                                 at java.lang.reflect.Method.invoke(Method.java:585)
                                 at junit.framework.TestCase.runTest(TestCase.java:154)
                                 at junit.framework.TestCase.runBare(TestCase.java:127)
                                 at junit.framework.TestResult$1.protect(TestResult.java:106)
                                 at junit.framework.TestResult.runProtected(TestResult.java:124)
                                 at junit.framework.TestResult.run(TestResult.java:109)
                                 at junit.framework.TestCase.run(TestCase.java:118)
                                 at junit.framework.TestSuite.runTest(TestSuite.java:208)
                                 at junit.framework.TestSuite.run(TestSuite.java:203)
                                 at org.apache.tools.ant.taskdefs.optional.junit.JUnitTestRunner.run(JUnitTestRunner.java:297)
                                 at org.apache.tools.ant.taskdefs.optional.junit.JUnitTestRunner.launch(JUnitTestRunner.java:672)
                                 at org.apache.tools.ant.taskdefs.optional.junit.JUnitTestRunner.main(JUnitTestRunner.java:567)
                                Caused by: java.lang.NoClassDefFoundError: org/jboss/aop/proxy/container/AOPProxyFactory
                                 at org.jboss.aop.microcontainer.integration.AOPJoinpointFactory.getConstructorJoinpoint(AOPJoinpointFactory.java:45)
                                 at org.jboss.kernel.plugins.config.Configurator.findConstructor(Configurator.java:211)
                                 at org.jboss.kernel.plugins.config.Configurator.getConstructorJoinPoint(Configurator.java:194)
                                 at org.jboss.kernel.plugins.config.Configurator.instantiate(Configurator.java:92)
                                 at org.jboss.kernel.plugins.config.Configurator.instantiateAndConfigure(Configurator.java:68)
                                 at org.jboss.kernel.plugins.config.property.PropertyKernelConfig.getImplementation(PropertyKernelConfig.java:159)
                                 at org.jboss.kernel.plugins.config.property.PropertyKernelConfig.createKernelInitializer(PropertyKernelConfig.java:118)
                                 at org.jboss.kernel.KernelFactory.createKernelInitializer(KernelFactory.java:150)
                                 ... 24 more
                                141 [main] DEBUG org.jboss.test.server.profileservice.MainWithSimpleHotDeployTestCase - testDefaultStartup took 141ms
                                141 [main] DEBUG org.jboss.test.server.profileservice.MainWithSimpleHotDeployTestCase - ==== Stopping testDefaultStartup ====
                                ------------- ---------------- ---------------
                                
                                Testcase: testDefaultStartup took 0.297 sec
                                 Caused an ERROR
                                Unable to create a KernelInitializer based on the specified KernelConfig
                                java.lang.RuntimeException: Unable to create a KernelInitializer based on the specified KernelConfig
                                 at org.jboss.kernel.KernelFactory.createKernelInitializer(KernelFactory.java:156)
                                 at org.jboss.kernel.KernelFactory.assembleNewKernel(KernelFactory.java:99)
                                 at org.jboss.kernel.KernelFactory.newInstance(KernelFactory.java:67)
                                 at org.jboss.kernel.plugins.bootstrap.AbstractBootstrap.bootstrap(AbstractBootstrap.java:120)
                                 at org.jboss.system.server.profileservice.ProfileServiceBootstrap.bootstrap(ProfileServiceBootstrap.java:186)
                                 at org.jboss.kernel.plugins.bootstrap.AbstractBootstrap.run(AbstractBootstrap.java:89)
                                 at org.jboss.system.server.profileservice.ServerImpl.doStart(ServerImpl.java:401)
                                 at org.jboss.system.server.profileservice.ServerImpl.start(ServerImpl.java:340)
                                 at org.jboss.Main.boot(Main.java:210)
                                 at org.jboss.test.server.profileservice.MainWithSimpleHotDeployTestCase.testDefaultStartup(MainWithSimpleHotDeployTestCase.java:105)
                                Caused by: java.lang.NoClassDefFoundError: org/jboss/aop/proxy/container/AOPProxyFactory
                                 at org.jboss.aop.microcontainer.integration.AOPJoinpointFactory.getConstructorJoinpoint(AOPJoinpointFactory.java:45)
                                 at org.jboss.kernel.plugins.config.Configurator.findConstructor(Configurator.java:211)
                                 at org.jboss.kernel.plugins.config.Configurator.getConstructorJoinPoint(Configurator.java:194)
                                 at org.jboss.kernel.plugins.config.Configurator.instantiate(Configurator.java:92)
                                 at org.jboss.kernel.plugins.config.Configurator.instantiateAndConfigure(Configurator.java:68)
                                 at org.jboss.kernel.plugins.config.property.PropertyKernelConfig.getImplementation(PropertyKernelConfig.java:159)
                                 at org.jboss.kernel.plugins.config.property.PropertyKernelConfig.createKernelInitializer(PropertyKernelConfig.java:118)
                                 at org.jboss.kernel.KernelFactory.createKernelInitializer(KernelFactory.java:150)
                                 ... 24 more
                                
                                


                                I tried to make the changes in the system\build-test.xml by modifying the classpath to contain the org/jboss/aop/proxy/container/AOPProxyFactory , but then it gave me the method not found error . Looks some changes in the AOPProxyFactory is not updated in the trunk .


                                • 14. Re: What's the status of HEAD?
                                  Vicky Kak Master

                                   

                                  63 [main] INFO org.jboss.system.server.profileservice.ServerImpl - Starting Microcontainer, deploye
                                  rBeansPrefix=
                                  

                                  This looks the cause , it is not set .....

                                  1 2 Previous Next