You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@geode.apache.org by "Jens Deppe (JIRA)" <ji...@apache.org> on 2016/01/07 18:48:40 UTC

[jira] [Commented] (GEODE-740) JMX ClientIds returns info for killed client (which should not be included in the list of ClientIds)

    [ https://issues.apache.org/jira/browse/GEODE-740?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15087752#comment-15087752 ] 

Jens Deppe commented on GEODE-740:
----------------------------------

The initial Trac bug report for this issue:
----
{noformat}
Host name: w1-gst-dev33
OS name: Windows 7
Architecture: amd64
OS version: 6.1
Java version: 1.7.0_79
Java vm name: Java HotSpot(TM) 64-Bit Server VM
Java vendor: Oracle Corporation
Java home: J:\where\jdk\1.7.0_79\x86_64.Windows_NT\jre

  #####################################################

  GemFire Version 8.2.0
  Source Date: Wed, 12 Aug 2015 15:03:17 -0700
  Source Revision: 18d88257d3133474a75c1362a4933b5163134318
  Source Repository: gemfire82_dev

  Build Id: build 081215
  Build Date: 08/12/2015 15:45:01 PDT
  Build Version: 8.2.0 build 081215 08/12/2015 15:45:01 PDT javac 1.7.0_79
  Build JDK: Java 1.7.0_79
  Build Platform: Linux 2.6.32-220.23.1.el6.x86_64 i386

  #####################################################


Test was run from T:\gfe\82\Windows_NT\snapshots.081215\gf82devsancout\tests\classes\management/test/jmx.bt

Test:
management/test/jmx/cacheServerClientHA.conf
   duration=600
   edge_Hosts=5
   edge_ThreadsPerVM=2
   edge_VMsPerHost=1
   jmxIterations=10
   locator_managing_Hosts=2
   locator_managing_ThreadsPerVM=3
   locator_managing_VMsPerHost=1
   managed_1_Hosts=2
   managed_1_ThreadsPerVM=2
   managed_1_VMsPerHost=1
   managed_2_Hosts=2
   managed_2_ThreadsPerVM=2
   managed_2_VMsPerHost=1
   managing_1_Hosts=2
   managing_1_ThreadsPerVM=2
   managing_1_VMsPerHost=1

No local.conf for this run

//randomSeed extracted from test:
hydra.Prms-randomSeed=1439482110886;

*** Test failed with this error:
CLIENT vm_21_thr_31_managed_12_w1-gst-dev33_63008
TASK[0] management.test.jmx.JMXTest.HydraTask_jmxOperations
ERROR util.TestException: Error running test doClientHA

util.TestException: Error running test doClientHA
        at management.util.HydraUtil.logErrorAndRaiseException(HydraUtil.java:83)
        at management.operations.ops.jmx.AbstractTestMBean.runMethod(AbstractTestMBean.java:276)
        at management.operations.ops.jmx.AbstractTestMBean.executeTest(AbstractTestMBean.java:290)
        at management.operations.ops.JMXOperations.doJMXTest(JMXOperations.java:105)
        at management.test.jmx.JMXTest.doJMXOps(JMXTest.java:818)
        at management.test.jmx.JMXTest.HydraTask_jmxOperations(JMXTest.java:206)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
        at java.lang.reflect.Method.invoke(Method.java:606)
        at hydra.MethExecutor.execute(MethExecutor.java:189)
        at hydra.MethExecutor.execute(MethExecutor.java:153)
        at hydra.TestTask.execute(TestTask.java:194)
        at hydra.RemoteTestModule$1.run(RemoteTestModule.java:217)
Caused by: java.lang.reflect.InvocationTargetException
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
        at java.lang.reflect.Method.invoke(Method.java:606)
        at management.operations.ops.jmx.AbstractTestMBean.runMethod(AbstractTestMBean.java:270)
        ... 12 more
Caused by: util.TestException: Client list shows 5 clients expected 4 diff : [w1-gst-dev33(edge_gemfire3_w1-gst-dev33_32604:32604:loner):5691:70a3d427:edge_gemfire3_w1-gst-dev33_32604]
        at management.operations.ops.jmx.CacheServerTestMBean.doClientHA(CacheServerTestMBean.java:363)
        ... 17 more

*** Failed thread logs ***
[info 2015/08/13 09:11:41.025 PDT <vm_21_thr_31_managed_12_w1-gst-dev33_63008> tid=0xd1] CliendIds not expected after shutdown :  List [
[info 2015/08/13 09:11:41.040 PDT <vm_21_thr_31_managed_12_w1-gst-dev33_63008> tid=0xd1] Added CacheServer JMX listener for GemFire:service=CacheServer,port=22759,type=Member,member=managed_1_gemfire2_w1-gst-dev33_63008 on server service:jmx:rmi:///jndi/rmi://w1-gst-dev33.gemstone.com:21737/jmxrmi
[info 2015/08/13 09:11:41.040 PDT <vm_21_thr_31_managed_12_w1-gst-dev33_63008> tid=0xd1] client w1-gst-dev33(edge_gemfire3_w1-gst-dev33_32604:32604:loner):5691:70a3d427:edge_gemfire3_w1-gst-dev33_32604 is going down with mode MEAN_KILL
[info 2015/08/13 09:11:41.040 PDT <vm_21_thr_31_managed_12_w1-gst-dev33_63008> tid=0xd1] Adding expectation for Notif Type gemfire.distributedsystem.cacheserver.client.crashed with message Client crashed with Id w1-gst-dev33(edge_gemfire3_w1-gst-dev33_32604:32604:loner):5691:70a3d427:edge_gemfire3_w1-gst-dev33_32604 on mbean GemFire:service=CacheServer,port=22759,type=Member,member=managed_1_gemfire2_w1-gst-dev33_63008
[info 2015/08/13 09:11:41.040 PDT <vm_21_thr_31_managed_12_w1-gst-dev33_63008> tid=0xd1] In stopStartVMs, vms to stop: [vm_15_edge3_*], corresponding stop modes: [MEAN_KILL]
[info 2015/08/13 09:11:41.040 PDT <vm_21_thr_31_managed_12_w1-gst-dev33_63008 Subthread> tid=0xd9] Started <StopStartVMs-thread to stop vm_15_edge3_* with mean_kill>
[info 2015/08/13 09:11:41.040 PDT <vm_21_thr_31_managed_12_w1-gst-dev33_63008 Subthread> tid=0xd9] Reserving vm_15_edge3_* for dynamic stop
[info 2015/08/13 09:11:41.040 PDT <vm_21_thr_31_managed_12_w1-gst-dev33_63008 Subthread> tid=0xd9] Reserved vm_15_edge3_edge_host3 for dynamic stop (synchronous:mean_kill:on_demand) vm_15_edge3_edge_host3 because Test is synchronously stopping vm_15_edge3_* with mean_kill
[info 2015/08/13 09:11:41.056 PDT <vm_21_thr_31_managed_12_w1-gst-dev33_63008 Subthread> tid=0xd9] Issuing dynamic stop (synchronous:mean_kill:on_demand) vm_15_edge3_edge_host3 because Test is synchronously stopping vm_15_edge3_* with mean_kill
[info 2015/08/13 09:11:41.072 PDT <vm_21_thr_31_managed_12_w1-gst-dev33_63008 Subthread> tid=0xd9] Waiting for completion of dynamic stop (synchronous:mean_kill:on_demand) vm_15_edge3_edge_host3 because Test is synchronously stopping vm_15_edge3_* with mean_kill
[info 2015/08/13 09:11:41.072 PDT <vm_21_thr_31_managed_12_w1-gst-dev33_63008 Subthread> tid=0xd9] Completed dynamic stop (synchronous:mean_kill:on_demand) vm_15_edge3_edge_host3 because Test is synchronously stopping vm_15_edge3_* with mean_kill
[info 2015/08/13 09:11:41.087 PDT <vm_21_thr_31_managed_12_w1-gst-dev33_63008 Subthread> tid=0xd9] <StopStartVMs-thread to stop vm_15_edge3_* with mean_kill> terminating
[info 2015/08/13 09:11:41.087 PDT <vm_21_thr_31_managed_12_w1-gst-dev33_63008> tid=0xd1] In stopStartVMs, done with stop: [vm_15_edge3_*]
[info 2015/08/13 09:11:41.087 PDT <vm_21_thr_31_managed_12_w1-gst-dev33_63008> tid=0xd1] 1 clients were Shutdown
[info 2015/08/13 09:11:51.103 PDT <vm_21_thr_31_managed_12_w1-gst-dev33_63008> tid=0xd1] Accessing attribute ClientIds on GemFire:service=CacheServer,port=22759,type=Member,member=managed_1_gemfire2_w1-gst-dev33_63008 hosted in manging node service:jmx:rmi:///jndi/rmi://w1-gst-dev33.gemstone.com:21737/jmxrmi
[info 2015/08/13 09:11:51.103 PDT <vm_21_thr_31_managed_12_w1-gst-dev33_63008> tid=0xd1] Successfully accessed attribute ClientIds on GemFire:service=CacheServer,port=22759,type=Member,member=managed_1_gemfire2_w1-gst-dev33_63008 hosted in manging node service:jmx:rmi:///jndi/rmi://w1-gst-dev33.gemstone.com:21737/jmxrmi result of type : class [Ljava.lang.String;
[info 2015/08/13 09:11:51.103 PDT <vm_21_thr_31_managed_12_w1-gst-dev33_63008> tid=0xd1] CliendIds after shutdown : Array [w1-gst-dev33(edge_gemfire3_w1-gst-dev33_32604:32604:loner):5691:70a3d427:edge_gemfire3_w1-gst-dev33_32604, w1-gst-dev33(edge_gemfire4_w1-gst-dev33_71416:71416:loner):5666:eaa1d427:edge_gemfire4_w1-gst-dev33_71416, w1-gst-dev33(edge_gemfire5_w1-gst-dev33_66620:66620:loner):5693:8fa3d427:edge_gemfire5_w1-gst-dev33_66620, w1-gst-dev33(edge_gemfire2_w1-gst-dev33_43740:43740:loner):5503:8ab7d327:edge_gemfire2_w1-gst-dev33_43740, w1-gst-dev33(edge_gemfire1_w1-gst-dev33_73636:73636:loner):5582:c72ad427:edge_gemfire1_w1-gst-dev33_73636, ]
[error 2015/08/13 09:11:51.103 PDT <vm_21_thr_31_managed_12_w1-gst-dev33_63008> tid=0xd1] Error running test doClientHA
[severe 2015/08/13 09:11:51.118 PDT <vm_21_thr_31_managed_12_w1-gst-dev33_63008> tid=0xd1] Task result: TASK[0] management.test.jmx.JMXTest.HydraTask_jmxOperations: ERROR util.TestException: Error running test doClientHA
{noformat}

> JMX ClientIds returns info for killed client (which should not be included in the list of ClientIds)
> ----------------------------------------------------------------------------------------------------
>
>                 Key: GEODE-740
>                 URL: https://issues.apache.org/jira/browse/GEODE-740
>             Project: Geode
>          Issue Type: Bug
>          Components: management
>            Reporter: Jens Deppe
>
> I think this bug is initially about ensuring that we have a test which checks that the clientIDs reported by the management framework is accurate when clients are killed.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)