FUSE ESB
  1. FUSE ESB
  2. ESB-1628

ServiceMix hangs when installing a more complex feature.

        Details

        • Type: Bug Bug
        • Status: Open
        • Priority: Major Major
        • Resolution: Unresolved
        • Affects Version/s: 4.4.1-fuse-01-20
        • Fix Version/s: 4.5.0.fuse-7-xxx
        • Component/s: Core
        • Labels:
          None
        • Similar Issues:
          Show 7 results 

          Description

          When installing the attached feature, the ServiceMix console will hang and not return. In addition the CPU going spinning.
          To reproduce:

          The console will log this error:

          karaf@root> features:install hangsup-smx-all-features
          		 
          Refreshing bundles org.springframework.aop (79), org.springframework.context (75), org.apache.activemq.activemq-pool (53), org.springframework.transaction (92), org.apache.activemq.activemq-spring (86)
          		 
          ERROR: Bundle org.springframework.osgi.extender [84] Error stopping bundle. (java.lang.NoClassDefFoundError: org/osgi/framework/ServiceRegistration)
          		 
          java.lang.NoClassDefFoundError: org/osgi/framework/ServiceRegistration
          		 
          	at org.springframework.osgi.util.OsgiServiceUtils.unregisterService(OsgiServiceUtils.java:41)
          		 
          	at org.springframework.osgi.extender.internal.support.NamespaceManager.unregisterResolverService(NamespaceManager.java:195)
          		 
          	at org.springframework.osgi.extender.internal.support.NamespaceManager.destroy(NamespaceManager.java:223)
          		 
          	at org.springframework.osgi.extender.internal.activator.ContextLoaderListener.shutdown(ContextLoaderListener.java:547)
          		 
          	at org.springframework.osgi.extender.internal.activator.ContextLoaderListener.stop(ContextLoaderListener.java:431)
          		 
          	at org.apache.felix.framework.util.SecureAction.stopActivator(SecureAction.java:651)
          		 
          	at org.apache.felix.framework.Felix.stopBundle(Felix.java:2225)
          		 
          	at org.apache.felix.framework.Felix$RefreshHelper.stop(Felix.java:4573)
          		 
          	at org.apache.felix.framework.Felix.refreshPackages(Felix.java:3590)
          		 
          	at org.apache.felix.framework.PackageAdminImpl.run(PackageAdminImpl.java:365)
          		 
          	at java.lang.Thread.run(Thread.java:680)
          		 
          Caused by: java.lang.ClassNotFoundException: org.osgi.framework.ServiceRegistration not found by org.springframework.osgi.core [81]
          		 
          	at org.apache.felix.framework.ModuleImpl.findClassOrResourceByDelegation(ModuleImpl.java:812)
          		 
          	at org.apache.felix.framework.ModuleImpl.access$400(ModuleImpl.java:72)
          		 
          	at org.apache.felix.framework.ModuleImpl$ModuleClassLoader.loadClass(ModuleImpl.java:1806)
          		 
          	at java.lang.ClassLoader.loadClass(ClassLoader.java:247)
          		 
          	... 11 more

          Interestingly, if all of the bundles of this feature are installed manually via the console, then there is no problem.

            Gliffy Diagrams

            1. XML File
              features-4.4.1-fuse-01-20.xml
              4 kB
              Torsten Mielke
            2. Text File
              StackTraces.txt
              8 kB
              Torsten Mielke

              Activity

              Hide
              Permalink
              Torsten Mielke added a comment - - edited

              Found the following threads showing up in a funny stated when attaching jvisualvm to the hung SMX instance (see attached file StackTraces.txt).

              Thread Blueprint-Extender-2 seems to be cycling from active to blocking but does never finish its call to NamespaceHandlerRegistryImpl.getNamespaceHandlers().
              The threads Blueprint-Extender-1 and -3 are blocked all the time waiting on the lock that Blueprint-Extender-2 owns.

              Show
              Torsten Mielke added a comment - - edited Found the following threads showing up in a funny stated when attaching jvisualvm to the hung SMX instance (see attached file StackTraces.txt). Thread Blueprint-Extender-2 seems to be cycling from active to blocking but does never finish its call to NamespaceHandlerRegistryImpl.getNamespaceHandlers(). The threads Blueprint-Extender-1 and -3 are blocked all the time waiting on the lock that Blueprint-Extender-2 owns.

                People

                • Assignee:
                  Unassigned
                  Reporter:
                  Torsten Mielke
                • Votes:
                  1 Vote for this issue
                  Watchers:
                  1 Start watching this issue

                  Dates

                  • Created:
                    Updated: