Uploaded image for project: 'Red Hat Fuse'
  1. Red Hat Fuse
  2. ENTESB-3997

admin:create && admin:start doesn't work after 6.2 P2 patch

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Blocker
    • jboss-fuse-6.2.1
    • jboss-fuse-6.2
    • Karaf
    • None
    • % %

    Description

      Can't create and start child containers with admin:create and admin:start commands.
      It worked on 6.2 GA, but it's broken after applying P2 patch.

      Steps to reproduce

      1. start fuse 6.2
      2. create child container with admin:create

      JBossFuse:karaf@root> features:install admin

JBossFuse:karaf@root> admin:create child1
Creating new instance on SSH port 8102 and RMI ports 1100/44445 at: /home/jludvice/apps/fuse/6.2/jboss-fuse-6.2.0.redhat-133/instances/child1

JBossFuse:karaf@root> admin:start child1 

JBossFuse:karaf@root> admin:list
  SSH Port   RMI Ports         State       Pid  Name
[    8101] [1099/44444     ] [Started ] [11709] root
[    8102] [1100/44445     ] [Starting] [12011] child1

JBossFuse:karaf@root> admin:list
  SSH Port   RMI Ports         State       Pid  Name
[    8101] [1099/44444     ] [Started ] [11709] root
[    8102] [1100/44445     ] [Started ] [12011] child1

      3. add and install patch P2

      JBossFuse:karaf@root> patch:add file:///home/jludvice/apps/fuse/6.2/rc4/jboss-fuse-6.2.0.redhat-153-p2.zip
[name]                                   [installed] [description]
jboss-fuse-6.2.0.redhat-153-p2           false      JBoss Fuse 6.2 P2

JBossFuse:karaf@root> patch:install jboss-fuse-6.2.0.redhat-153-p2 
Skipping bundle mvn:org.apache.aries.blueprint/org.apache.aries.blueprint.core.compatibility/1.0.0 - unable to process bundle without a version range configuration
DEBUG: Applying patch: jboss-fuse-6.2.0.redhat-153-p2 / JBoss Fuse 6.2 P2
...

      4. create another child container with patched fuse and start it

      JBossFuse:karaf@root> patch:list
[name]                                   [installed] [description]
jboss-fuse-6.2.0.redhat-153-p2           true       JBoss Fuse 6.2 P2

JBossFuse:karaf@root> admin:create child_patched
Creating new instance on SSH port 8103 and RMI ports 1101/44446 at: /home/jludvice/apps/fuse/6.2/jboss-fuse-6.2.0.redhat-133/instances/child_patched

JBossFuse:karaf@root> admin:start child_patched 

JBossFuse:karaf@root> admin:list
  SSH Port   RMI Ports         State       Pid  Name
[    8101] [1099/44444     ] [Started ] [11709] root
[    8102] [1100/44445     ] [Started ] [12011] child1
[    8103] [1101/44446     ] [Starting] [12403] child_patched

      5. container, created from patched root doesn't start due to missing features.xml for karaf assemblies spring

      2015-09-14 13:11:12,413 | WARN  | FelixStartLevel  | AetherBasedResolver              | 4 - org.ops4j.pax.logging.pax-logging-api - 1.8.2 | Error resolving artifactorg.apache.karaf.assemblies.features:spring:xml:features:2.4.0.redhat-620153:Could not find artifact org.apache.karaf.assemblies.features:spring:xml:features:2.4.0.redhat-620153 in central (http://repo1.maven.org/maven2/)
shaded.org.eclipse.aether.resolution.ArtifactResolutionException: Could not find artifact org.apache.karaf.assemblies.features:spring:xml:features:2.4.0.redhat-620153 in central (http://repo1.maven.org/maven2/)
	at shaded.org.eclipse.aether.internal.impl.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:444)[1:org.ops4j.pax.url.mvn:2.4.0]
...

      Workaround

      For some reason, creating child container works from already existing child.

      JBossFuse:karaf@root> admin:connect -u karaf  child1
Connecting to host localhost on port 8102
Connected
Password:  *****
      _ ____                  ______
     | |  _ \                |  ____|             
     | | |_) | ___  ___ ___  | |__ _   _ ___  ___
 _   | |  _ < / _ \/ __/ __| |  __| | | / __|/ _ \
| |__| | |_) | (_) \__ \__ \ | |  | |_| \__ \  __/
 \____/|____/ \___/|___/___/ |_|   \__,_|___/\___|

  JBoss Fuse (6.2.0.redhat-133)
  http://www.redhat.com/products/jbossenterprisemiddleware/fuse/

Hit '<tab>' for a list of available commands
and '[cmd] --help' for help on a specific command.

Open a browser to http://localhost:8181 to access the management console

Create a new Fabric via 'fabric:create'
or join an existing Fabric via 'fabric:join [someUrls]'

Hit '<ctrl-d>' or 'osgi:shutdown' to shutdown JBoss Fuse.

JBossFuse:karaf@child1> admin:create child_patched_2
Creating new instance on SSH port 8104 and RMI ports 1102/44447 at: /home/jludvice/apps/fuse/6.2/jboss-fuse-6.2.0.redhat-133/instances/child_patched_2

JBossFuse:karaf@child1> admin:start child_patched_2 
JBossFuse:karaf@child1> admin:list
  SSH Port   RMI Ports         State       Pid  Name
[    8101] [1099/44444     ] [Started ] [11709] root
[    8102] [1100/44445     ] [Started ] [12011] child1
[    8103] [1101/44446     ] [Starting] [12403] child_patched
[    8104] [1102/44447     ] [Started ] [13272] child_patched_2
JBossFuse:karaf@child1> ^D # disconect child1, go back to root container

JBossFuse:karaf@root> admin:list
  SSH Port   RMI Ports         State       Pid  Name
[    8101] [1099/44444     ] [Started ] [11709] root
[    8102] [1100/44445     ] [Started ] [12011] child1
[    8103] [1101/44446     ] [Starting] [12403] child_patched
[    8104] [1102/44447     ] [Started ] [13272] child_patched_2
JBossFuse:karaf@root>

      Attachments

        Issue Links

          is related to

          Bug - A problem that impairs or prevents the functions of the product. ENTESB-4886 6.2.1 Patching mechanism should support applying rollup patch to non-fabric child containers

          • Critical - To be worked on immediately following BLOCKER issues.
          • Closed
          relates to

          Bug - A problem that impairs or prevents the functions of the product. ENTESB-3756 Remote child container fails to start if remote root is created at a patched version

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed
          is caused by

          KARAF-3754 Loading...

          Activity

            People

              ggrzybek Grzegorz Grzybek
              jludvice Josef Ludvicek (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: