[jira] [Updated] (GEODE-5816) ClusterStartupRule fails to launch JMX manager (port already in use)

2019-04-12 Thread Shelley Lynn Hughes-Godfrey (JIRA)


 [ 
https://issues.apache.org/jira/browse/GEODE-5816?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Shelley Lynn Hughes-Godfrey updated GEODE-5816:
---
Labels: CI swat  (was: swat)

> ClusterStartupRule fails to launch JMX manager (port already in use)
> 
>
> Key: GEODE-5816
> URL: https://issues.apache.org/jira/browse/GEODE-5816
> Project: Geode
>  Issue Type: Bug
>  Components: tests
>Reporter: Bill Burcham
>Assignee: Dan Smith
>Priority: Major
>  Labels: CI, swat
>
> We see these related failures on a couple tests in 
> RegionMembershipMBeanOverHttpDUnitTest from our recent mass-test-run.
> From looking at the stack traces though, we surmise that the problem occurs 
> in the ClusterStartupRule _before_ the actual tests run. Since it occurs 
> before the tests run, we think the problem lies outside the 
> RegionMembershipMBeanOverHttpDUnitTest class.
> {noformat}
>   4 failures (99.600% success 
> rate)org.apache.geode.management.internal.cli.commands.RegionMembershipMBeanOverHttpDUnitTest
>  |  .testAddRmNewMemberWithReplicatedRegionsAndSubregions:  1 failures 
> (99.900% success rate)
>  |   |  Failed build 24   at 
> https://concourse.apachegeode-ci.info/teams/main/pipelines/mass-test-run/jobs/DistributedTest/builds/24
>  |  .testMultiplePartitionedRegions:  3 failures (99.700% success rate)
>  |   |  Failed build 982  at 
> https://concourse.apachegeode-ci.info/teams/main/pipelines/mass-test-run/jobs/DistributedTest/builds/982
>  |   |  Failed build 256  at 
> https://concourse.apachegeode-ci.info/teams/main/pipelines/mass-test-run/jobs/DistributedTest/builds/256
> {noformat}
> Here's a stack trace:
> {noformat}
> java.lang.AssertionError: Suspicious strings were written to the log during 
> this run.
> Fix the strings or use IgnoredException.addIgnoredException to ignore.
> ---
> Found suspect string in log4j at line 358
> [error 2018/10/01 06:28:30.869 UTC  
> tid=0x20] Jmx manager could not be started because 
> java.rmi.server.ExportException: Port already in use: 25305; nested exception 
> is: 
>   java.net.BindException: Failed to create server socket on  
> ffd50f3577c5/172.17.0.20[25305]
> org.apache.geode.management.ManagementException: 
> java.rmi.server.ExportException: Port already in use: 25305; nested exception 
> is: 
>   java.net.BindException: Failed to create server socket on  
> ffd50f3577c5/172.17.0.20[25305]
>   at 
> org.apache.geode.management.internal.ManagementAgent.startAgent(ManagementAgent.java:162)
>   at 
> org.apache.geode.management.internal.SystemManagementService.startManager(SystemManagementService.java:435)
>   at 
> org.apache.geode.management.internal.beans.ManagementAdapter.handleCacheCreation(ManagementAdapter.java:173)
>   at 
> org.apache.geode.management.internal.beans.ManagementListener.handleEvent(ManagementListener.java:118)
>   at 
> org.apache.geode.distributed.internal.InternalDistributedSystem.notifyResourceEventListeners(InternalDistributedSystem.java:2201)
>   at 
> org.apache.geode.distributed.internal.InternalDistributedSystem.handleResourceEvent(InternalDistributedSystem.java:591)
>   at 
> org.apache.geode.internal.cache.GemFireCacheImpl.initialize(GemFireCacheImpl.java:1218)
>   at 
> org.apache.geode.internal.cache.GemFireCacheImpl.basicCreate(GemFireCacheImpl.java:793)
>   at 
> org.apache.geode.internal.cache.GemFireCacheImpl.create(GemFireCacheImpl.java:779)
>   at org.apache.geode.cache.CacheFactory.create(CacheFactory.java:177)
>   at org.apache.geode.cache.CacheFactory.create(CacheFactory.java:224)
>   at 
> org.apache.geode.distributed.internal.InternalLocator.startCache(InternalLocator.java:662)
>   at 
> org.apache.geode.distributed.internal.InternalLocator.startDistributedSystem(InternalLocator.java:649)
>   at 
> org.apache.geode.distributed.internal.InternalLocator.startLocator(InternalLocator.java:311)
>   at org.apache.geode.distributed.Locator.startLocator(Locator.java:253)
>   at 
> org.apache.geode.distributed.Locator.startLocatorAndDS(Locator.java:140)
>   at 
> org.apache.geode.test.junit.rules.LocatorStarterRule.startLocator(LocatorStarterRule.java:87)
>   at 
> org.apache.geode.test.junit.rules.LocatorStarterRule.before(LocatorStarterRule.java:68)
>   at 
> org.apache.geode.test.dunit.rules.ClusterStartupRule.lambda$startLocatorVM$22d9b8a8$1(ClusterStartupRule.java:206)
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>   at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>   at 
> 

[jira] [Updated] (GEODE-5816) ClusterStartupRule fails to launch JMX manager (port already in use)

2019-02-27 Thread Dan Smith (JIRA)


 [ 
https://issues.apache.org/jira/browse/GEODE-5816?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Dan Smith updated GEODE-5816:
-
Fix Version/s: (was: 1.9.0)

> ClusterStartupRule fails to launch JMX manager (port already in use)
> 
>
> Key: GEODE-5816
> URL: https://issues.apache.org/jira/browse/GEODE-5816
> Project: Geode
>  Issue Type: Bug
>  Components: tests
>Reporter: Bill Burcham
>Assignee: Dan Smith
>Priority: Major
>  Labels: swat
>
> We see these related failures on a couple tests in 
> RegionMembershipMBeanOverHttpDUnitTest from our recent mass-test-run.
> From looking at the stack traces though, we surmise that the problem occurs 
> in the ClusterStartupRule _before_ the actual tests run. Since it occurs 
> before the tests run, we think the problem lies outside the 
> RegionMembershipMBeanOverHttpDUnitTest class.
> {noformat}
>   4 failures (99.600% success 
> rate)org.apache.geode.management.internal.cli.commands.RegionMembershipMBeanOverHttpDUnitTest
>  |  .testAddRmNewMemberWithReplicatedRegionsAndSubregions:  1 failures 
> (99.900% success rate)
>  |   |  Failed build 24   at 
> https://concourse.apachegeode-ci.info/teams/main/pipelines/mass-test-run/jobs/DistributedTest/builds/24
>  |  .testMultiplePartitionedRegions:  3 failures (99.700% success rate)
>  |   |  Failed build 982  at 
> https://concourse.apachegeode-ci.info/teams/main/pipelines/mass-test-run/jobs/DistributedTest/builds/982
>  |   |  Failed build 256  at 
> https://concourse.apachegeode-ci.info/teams/main/pipelines/mass-test-run/jobs/DistributedTest/builds/256
> {noformat}
> Here's a stack trace:
> {noformat}
> java.lang.AssertionError: Suspicious strings were written to the log during 
> this run.
> Fix the strings or use IgnoredException.addIgnoredException to ignore.
> ---
> Found suspect string in log4j at line 358
> [error 2018/10/01 06:28:30.869 UTC  
> tid=0x20] Jmx manager could not be started because 
> java.rmi.server.ExportException: Port already in use: 25305; nested exception 
> is: 
>   java.net.BindException: Failed to create server socket on  
> ffd50f3577c5/172.17.0.20[25305]
> org.apache.geode.management.ManagementException: 
> java.rmi.server.ExportException: Port already in use: 25305; nested exception 
> is: 
>   java.net.BindException: Failed to create server socket on  
> ffd50f3577c5/172.17.0.20[25305]
>   at 
> org.apache.geode.management.internal.ManagementAgent.startAgent(ManagementAgent.java:162)
>   at 
> org.apache.geode.management.internal.SystemManagementService.startManager(SystemManagementService.java:435)
>   at 
> org.apache.geode.management.internal.beans.ManagementAdapter.handleCacheCreation(ManagementAdapter.java:173)
>   at 
> org.apache.geode.management.internal.beans.ManagementListener.handleEvent(ManagementListener.java:118)
>   at 
> org.apache.geode.distributed.internal.InternalDistributedSystem.notifyResourceEventListeners(InternalDistributedSystem.java:2201)
>   at 
> org.apache.geode.distributed.internal.InternalDistributedSystem.handleResourceEvent(InternalDistributedSystem.java:591)
>   at 
> org.apache.geode.internal.cache.GemFireCacheImpl.initialize(GemFireCacheImpl.java:1218)
>   at 
> org.apache.geode.internal.cache.GemFireCacheImpl.basicCreate(GemFireCacheImpl.java:793)
>   at 
> org.apache.geode.internal.cache.GemFireCacheImpl.create(GemFireCacheImpl.java:779)
>   at org.apache.geode.cache.CacheFactory.create(CacheFactory.java:177)
>   at org.apache.geode.cache.CacheFactory.create(CacheFactory.java:224)
>   at 
> org.apache.geode.distributed.internal.InternalLocator.startCache(InternalLocator.java:662)
>   at 
> org.apache.geode.distributed.internal.InternalLocator.startDistributedSystem(InternalLocator.java:649)
>   at 
> org.apache.geode.distributed.internal.InternalLocator.startLocator(InternalLocator.java:311)
>   at org.apache.geode.distributed.Locator.startLocator(Locator.java:253)
>   at 
> org.apache.geode.distributed.Locator.startLocatorAndDS(Locator.java:140)
>   at 
> org.apache.geode.test.junit.rules.LocatorStarterRule.startLocator(LocatorStarterRule.java:87)
>   at 
> org.apache.geode.test.junit.rules.LocatorStarterRule.before(LocatorStarterRule.java:68)
>   at 
> org.apache.geode.test.dunit.rules.ClusterStartupRule.lambda$startLocatorVM$22d9b8a8$1(ClusterStartupRule.java:206)
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>   at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>   at 

[jira] [Updated] (GEODE-5816) ClusterStartupRule fails to launch JMX manager (port already in use)

2018-10-03 Thread Bill (JIRA)


 [ 
https://issues.apache.org/jira/browse/GEODE-5816?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Bill updated GEODE-5816:

Labels: swat  (was: )

> ClusterStartupRule fails to launch JMX manager (port already in use)
> 
>
> Key: GEODE-5816
> URL: https://issues.apache.org/jira/browse/GEODE-5816
> Project: Geode
>  Issue Type: Bug
>  Components: tests
>Reporter: Bill
>Priority: Major
>  Labels: swat
>
> We see these related failures on a couple tests in 
> RegionMembershipMBeanOverHttpDUnitTest from our recent mass-test-run.
> From looking at the stack traces though, we surmise that the problem occurs 
> in the ClusterStartupRule _before_ the actual tests run. Since it occurs 
> before the tests run, we think the problem lies outside the 
> RegionMembershipMBeanOverHttpDUnitTest class.
> {noformat}
>   4 failures (99.600% success 
> rate)org.apache.geode.management.internal.cli.commands.RegionMembershipMBeanOverHttpDUnitTest
>  |  .testAddRmNewMemberWithReplicatedRegionsAndSubregions:  1 failures 
> (99.900% success rate)
>  |   |  Failed build 24   at 
> https://concourse.apachegeode-ci.info/teams/main/pipelines/mass-test-run/jobs/DistributedTest/builds/24
>  |  .testMultiplePartitionedRegions:  3 failures (99.700% success rate)
>  |   |  Failed build 982  at 
> https://concourse.apachegeode-ci.info/teams/main/pipelines/mass-test-run/jobs/DistributedTest/builds/982
>  |   |  Failed build 256  at 
> https://concourse.apachegeode-ci.info/teams/main/pipelines/mass-test-run/jobs/DistributedTest/builds/256
> {noformat}
> Here's a stack trace:
> {noformat}
> java.lang.AssertionError: Suspicious strings were written to the log during 
> this run.
> Fix the strings or use IgnoredException.addIgnoredException to ignore.
> ---
> Found suspect string in log4j at line 358
> [error 2018/10/01 06:28:30.869 UTC  
> tid=0x20] Jmx manager could not be started because 
> java.rmi.server.ExportException: Port already in use: 25305; nested exception 
> is: 
>   java.net.BindException: Failed to create server socket on  
> ffd50f3577c5/172.17.0.20[25305]
> org.apache.geode.management.ManagementException: 
> java.rmi.server.ExportException: Port already in use: 25305; nested exception 
> is: 
>   java.net.BindException: Failed to create server socket on  
> ffd50f3577c5/172.17.0.20[25305]
>   at 
> org.apache.geode.management.internal.ManagementAgent.startAgent(ManagementAgent.java:162)
>   at 
> org.apache.geode.management.internal.SystemManagementService.startManager(SystemManagementService.java:435)
>   at 
> org.apache.geode.management.internal.beans.ManagementAdapter.handleCacheCreation(ManagementAdapter.java:173)
>   at 
> org.apache.geode.management.internal.beans.ManagementListener.handleEvent(ManagementListener.java:118)
>   at 
> org.apache.geode.distributed.internal.InternalDistributedSystem.notifyResourceEventListeners(InternalDistributedSystem.java:2201)
>   at 
> org.apache.geode.distributed.internal.InternalDistributedSystem.handleResourceEvent(InternalDistributedSystem.java:591)
>   at 
> org.apache.geode.internal.cache.GemFireCacheImpl.initialize(GemFireCacheImpl.java:1218)
>   at 
> org.apache.geode.internal.cache.GemFireCacheImpl.basicCreate(GemFireCacheImpl.java:793)
>   at 
> org.apache.geode.internal.cache.GemFireCacheImpl.create(GemFireCacheImpl.java:779)
>   at org.apache.geode.cache.CacheFactory.create(CacheFactory.java:177)
>   at org.apache.geode.cache.CacheFactory.create(CacheFactory.java:224)
>   at 
> org.apache.geode.distributed.internal.InternalLocator.startCache(InternalLocator.java:662)
>   at 
> org.apache.geode.distributed.internal.InternalLocator.startDistributedSystem(InternalLocator.java:649)
>   at 
> org.apache.geode.distributed.internal.InternalLocator.startLocator(InternalLocator.java:311)
>   at org.apache.geode.distributed.Locator.startLocator(Locator.java:253)
>   at 
> org.apache.geode.distributed.Locator.startLocatorAndDS(Locator.java:140)
>   at 
> org.apache.geode.test.junit.rules.LocatorStarterRule.startLocator(LocatorStarterRule.java:87)
>   at 
> org.apache.geode.test.junit.rules.LocatorStarterRule.before(LocatorStarterRule.java:68)
>   at 
> org.apache.geode.test.dunit.rules.ClusterStartupRule.lambda$startLocatorVM$22d9b8a8$1(ClusterStartupRule.java:206)
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>   at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>   at java.lang.reflect.Method.invoke(Method.java:498)
>   at