You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@geode.apache.org by "Darrel Schneider (JIRA)" <ji...@apache.org> on 2019/08/08 17:01:00 UTC
[jira] [Commented] (GEODE-7059) CI Failure:
Tomcat8ClientServerRollingUpgradeTest.canDoARollingUpgradeOfGeodeServersWithSessionModules[170]
[ https://issues.apache.org/jira/browse/GEODE-7059?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16903144#comment-16903144 ]
Darrel Schneider commented on GEODE-7059:
-----------------------------------------
The locator is started like so:
[INFO 23:02:04.643 GMT] (318fd43e301b7936): (1) Executing - start locator --name=loc --classpath=/tmp/geode_container_install6073844666451986856/cargo_containers/Tomcat8AndOldModules/tomcat-8.5.34/apache-tomcat-8.5.34/lib/*:/tmp/geode_container_install6073844666451986856/cargo_containers/Tomcat8AndOldModules/tomcat-8.5.34/apache-tomcat-8.5.34/bin/* --port=25018 --dir=/tmp/junit2980611441746718519/loc --http-service-port=0 --J=-Dgemfire.jmx-manager-port=25019
If we changed this to also do: --J=-Dgemfire.jmx-manager-start=true
then this test would be less flaky because the locator would bind to 25019 sooner (like it does for --port=25018).
> CI Failure: Tomcat8ClientServerRollingUpgradeTest.canDoARollingUpgradeOfGeodeServersWithSessionModules[170]
> -----------------------------------------------------------------------------------------------------------
>
> Key: GEODE-7059
> URL: https://issues.apache.org/jira/browse/GEODE-7059
> Project: Geode
> Issue Type: Bug
> Reporter: Helena Bales
> Priority: Major
>
> Tomcat8ClientServerRollingUpgradeTest failed in CI: https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/UpgradeTestOpenJDK8/builds/954
> Results available here: http://files.apachegeode-ci.info/builds/apache-develop-main/1.11.0-SNAPSHOT.0008/test-results/upgradeTest/1565134781/
> Archive here: http://files.apachegeode-ci.info/builds/apache-develop-main/1.11.0-SNAPSHOT.0008/test-artifacts/1565134781/upgradetestfiles-OpenJDK8-1.11.0-SNAPSHOT.0008.tgz
> The issue appears to be a port conflict, however a connection through GFSH does not seem like it should be triggering JMX startup.
> {noformat}
> Executing db801bc9548a20f6: gfsh -e connect --locator=localhost[25018] -e create region --type=PARTITION_REDUNDANT --name=gemfire_modules_sessions --enable-statistics=true --entry-idle-time-custom-expiry=org.apache.geode.modules.util.SessionCustomExpiry
> [INFO 23:03:02.978 GMT] (db801bc9548a20f6):
> [INFO 23:03:02.978 GMT] (db801bc9548a20f6): (1) Executing - connect --locator=localhost[25018]
> [INFO 23:03:02.979 GMT] (db801bc9548a20f6):
> [INFO 23:03:03.017 GMT] (db801bc9548a20f6): Connecting to Locator at [host=localhost, port=25018] ..
> [ERROR 23:03:05.075 GMT] (db801bc9548a20f6): Exception caused JMX Manager startup to fail because: 'java.rmi.server.ExportException: Port already in use: 25019; nested exception is:
> [ERROR 23:03:05.075 GMT] (db801bc9548a20f6): java.net.BindException: Failed to create server socket on null[25,019]'
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)