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

On Windows offline patching causes "javax.management.InstanceAlreadyExistsException: org.fusesource.insight:type=Log Query"

    XMLWordPrintable

    Details

    • Sprint:
      6.3 Sprint 1 (4-Jan->29-Jan)
    • Steps to Reproduce:
      Hide

      1) Copy patch.bat from JBossFuseInstallation/bin/patch.bat into the A-MQInstallation/bin
      2) Edit the script to correctly point to patch-client.jar so changing:

      CLASSPATH=%KARAF_HOME%\lib\bin\patch-client.jar
      

      to

      CLASSPATH=%KARAF_HOME%\lib\patch-client.jar
      

      3) >jboss-a-mq-6.1.0.redhat-379\bin>patch.bat D:\jboss-fuse-6.1.0.
      redhat-379-r2-611423.zip
      4) >jboss-a-mq-6.1.0.redhat-379\bin>patch.bat D:\jboss-fuse-6.1.1.
      redhat-442-r2p6.zip
      5) >amq.bat

      Show
      1) Copy patch.bat from JBossFuseInstallation/bin/patch.bat into the A-MQInstallation/bin 2) Edit the script to correctly point to patch-client.jar so changing: CLASSPATH=%KARAF_HOME%\lib\bin\patch-client.jar to CLASSPATH=%KARAF_HOME%\lib\patch-client.jar 3) >jboss-a-mq-6.1.0.redhat-379\bin>patch.bat D:\jboss-fuse-6.1.0. redhat-379-r2-611423.zip 4) >jboss-a-mq-6.1.0.redhat-379\bin>patch.bat D:\jboss-fuse-6.1.1. redhat-442-r2p6.zip 5) >amq.bat

      Description

      JBoss A-MQ distribution seems to have missed the patch script that we have added to allow patching containers in offline mode, as a result a ENTMQ-1152 is created to track this. However there seems to be a workaround where this script can be copied from JBossFuseInstallation/bin/patch into the A-MQInstallation/bin. This however needs a manual modification to adjust the classpath in the script and point it to the location of patch-client.jar.
      so changing:

      CLASSPATH=%KARAF_HOME%\lib\bin\patch-client.jar
      
      CLASSPATH=%KARAF_HOME%\lib\patch-client.jar
      

      with this patch can be applied successfully. However in Windows it looks like after starting A-MQ container the following WARN can be seen in the logs:

      2015-10-07 11:45:08,468 | WARN  | FelixStartLevel  | LogQuerySupport
            | ight.log.support.LogQuerySupport  168 | 59 - org.fusesource.insight.insi
      ght-log - 1.0.0.redhat-423 | An error occured during mbean server registration:
      javax.management.InstanceAlreadyExistsException: org.fusesource.insight:type=Log
      Query
      javax.management.InstanceAlreadyExistsException: org.fusesource.insight:type=Log
      Query
              at com.sun.jmx.mbeanserver.Repository.addMBean(Repository.java:437)[:1.7
      .0_79]
              at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerWithRep
      ository(DefaultMBeanServerInterceptor.java:1898)[:1.7.0_79]
              at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerDynamic
      MBean(DefaultMBeanServerInterceptor.java:966)[:1.7.0_79]
              at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerObject(
      DefaultMBeanServerInterceptor.java:900)[:1.7.0_79]
              at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerMBean(D
      efaultMBeanServerInterceptor.java:324)[:1.7.0_79]
              at com.sun.jmx.mbeanserver.JmxMBeanServer.registerMBean(JmxMBeanServer.j
      ava:522)[:1.7.0_79]
              at org.fusesource.insight.log.support.LogQuerySupport.registerMBeanServe
      r(LogQuerySupport.java:166)[59:org.fusesource.insight.insight-log:1.0.0.redhat-4
      23]
              at org.fusesource.insight.log.service.LogQueryActivator.start(LogQueryAc
      tivator.java:44)[59:org.fusesource.insight.insight-log:1.0.0.redhat-423]
              at org.apache.felix.framework.util.SecureAction.startActivator(SecureAct
      ion.java:645)[org.apache.felix.framework-4.0.3.redhat-610379.jar:]
              at org.apache.felix.framework.Felix.doActivateBundle(Felix.java:2387)[or
      g.apache.felix.framework-4.0.3.redhat-610379.jar:]
              at org.apache.felix.framework.Felix$7.call(Felix.java:2325)[org.apache.f
      elix.framework-4.0.3.redhat-610379.jar:]
              at org.apache.felix.framework.Felix.runInContext(Felix.java:2188)[org.ap
      ache.felix.framework-4.0.3.redhat-610379.jar:]
              at org.apache.felix.framework.Felix.activateBundle(Felix.java:2323)[org.
      apache.felix.framework-4.0.3.redhat-610379.jar:]
              at org.apache.felix.framework.Felix.startBundle(Felix.java:2090)[org.apa
      che.felix.framework-4.0.3.redhat-610379.jar:]
              at org.apache.felix.framework.Felix.setActiveStartLevel(Felix.java:1317)
      [org.apache.felix.framework-4.0.3.redhat-610379.jar:]
              at org.apache.felix.framework.FrameworkStartLevelImpl.run(FrameworkStart
      LevelImpl.java:304)[org.apache.felix.framework-4.0.3.redhat-610379.jar:]
              at java.lang.Thread.run(Thread.java:745)[:1.7.0_79]
      

      This might be harmless however it raises the concern among customers.

        Gliffy Diagrams

          Attachments

            Issue Links

              Activity

                People

                • Assignee:
                  grgrzybek Grzegorz Grzybek
                  Reporter:
                  hooman_b2455 Hooman Broujerdi
                  Tester:
                  Tomas Plevko
                • Votes:
                  0 Vote for this issue
                  Watchers:
                  5 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved: