[jira] [Commented] (GEODE-7649) upgrade tests fail when v1.11 is added to geode-old-versions
[
https://issues.apache.org/jira/browse/GEODE-7649?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17009278#comment-17009278
]
ASF subversion and git services commented on GEODE-7649:
Commit 0b232758ed708b90e4ccc787d438676e5ac7f58c in geode's branch
refs/heads/develop from Bruce Schuchardt
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=0b23275 ]
GEODE-7649 upgrade tests fail when v1.11 is added to geode-old-versions (#4564)
* GEODE-7649 upgrade tests fail when v1.11 is added to geode-old-versions
Geode v1.11 inadvertently changed the form of its saved membership view
by using a FileOutputStream to write it to disk instead of using
an ObjectOutputStream. The latter writes additional information during
serialization.
Note: there is already a test for this change that will start running
when v1.12 is created and v1.11 is added as a geode-old-version in
settings.gradle.
* corrected serialization in integration test
* flipping equals() check to avoid possible NPE
> upgrade tests fail when v1.11 is added to geode-old-versions
>
>
> Key: GEODE-7649
> URL: https://issues.apache.org/jira/browse/GEODE-7649
> Project: Geode
> Issue Type: Bug
> Components: membership
>Reporter: Bruce J Schuchardt
>Priority: Major
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> With v1.11 being released we are adding it as an old-version for upgrade
> tests. This is failing when a locator is rolled from v1.11 to develop
> (v1.12).
> {noformat}
> org.apache.geode.cache.wan.WANRollingUpgradeCreateGatewaySenderMixedSiteOneCurrentSiteTwo
> > CreateGatewaySenderMixedSiteOneCurrentSiteTwo[from_v1.11.0] FAILED
> org.apache.geode.test.dunit.RMIException: While invoking
> org.apache.geode.cache.wan.WANRollingUpgradeCreateGatewaySenderMixedSiteOneCurrentSiteTwo$$Lambda$200/0x000840855440.call
> in VM 0 running on Host 7ab3b8a613a7 with 7 VMs
> at org.apache.geode.test.dunit.VM.executeMethodOnObject(VM.java:610)
> at org.apache.geode.test.dunit.VM.invoke(VM.java:462)
> at
> org.apache.geode.cache.wan.WANRollingUpgradeCreateGatewaySenderMixedSiteOneCurrentSiteTwo.CreateGatewaySenderMixedSiteOneCurrentSiteTwo(WANRollingUpgradeCreateGatewaySenderMixedSiteOneCurrentSiteTwo.java:92)
> Caused by:
> java.lang.IllegalStateException: Unable to recover previous
> membership view from
> /home/geode/geode/geode-wan/build/upgradeTest38/dunit/vm0/locator28263view.dat
> at
> org.apache.geode.distributed.internal.membership.gms.locator.GMSLocator.recoverFromFile(GMSLocator.java:482)
> at
> org.apache.geode.distributed.internal.membership.gms.locator.GMSLocator.recover(GMSLocator.java:397)
> at
> org.apache.geode.distributed.internal.membership.gms.locator.GMSLocator.init(GMSLocator.java:181)
> at
> org.apache.geode.distributed.internal.membership.adapter.GMSLocatorAdapter.init(GMSLocatorAdapter.java:108)
> at
> org.apache.geode.distributed.internal.PrimaryHandler.init(PrimaryHandler.java:61)
> at
> org.apache.geode.distributed.internal.tcpserver.TcpServer.start(TcpServer.java:172)
> at
> org.apache.geode.distributed.internal.InternalLocator.startTcpServer(InternalLocator.java:563)
> at
> org.apache.geode.distributed.internal.InternalLocator.startPeerLocation(InternalLocator.java:620)
> at
> org.apache.geode.distributed.internal.InternalLocator.startLocator(InternalLocator.java:375)
> at
> org.apache.geode.distributed.internal.InternalLocator.startLocator(InternalLocator.java:330)
> at
> org.apache.geode.distributed.Locator.startLocator(Locator.java:253)
> at
> org.apache.geode.distributed.Locator.startLocatorAndDS(Locator.java:140)
> at
> org.apache.geode.cache.wan.WANRollingUpgradeDUnitTest.startLocatorWithJmxManager(WANRollingUpgradeDUnitTest.java:115)
> at
> org.apache.geode.cache.wan.WANRollingUpgradeCreateGatewaySenderMixedSiteOneCurrentSiteTwo.lambda$CreateGatewaySenderMixedSiteOneCurrentSiteTwo$e0147a59$1(WANRollingUpgradeCreateGatewaySenderMixedSiteOneCurrentSiteTwo.java:92)
> Caused by:
> java.io.StreamCorruptedException: invalid type code: 02
> at
> java.io.ObjectInputStream$BlockDataInputStream.readBlockHeader(ObjectInputStream.java:2973)
> at
> java.io.ObjectInputStream$BlockDataInputStream.refill(ObjectInputStream.java:3007)
> at
> java.io.ObjectInputStream$BlockDataInputStream.read(ObjectInputStream.java:3079)
> at java.io.ObjectInputStream.read(ObjectInputStream.java:913)
> at java.io.DataInputStream.readByte(DataInputStream.java:270)
>
[jira] [Commented] (GEODE-7649) upgrade tests fail when v1.11 is added to geode-old-versions
[
https://issues.apache.org/jira/browse/GEODE-7649?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17009277#comment-17009277
]
ASF subversion and git services commented on GEODE-7649:
Commit 0b232758ed708b90e4ccc787d438676e5ac7f58c in geode's branch
refs/heads/develop from Bruce Schuchardt
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=0b23275 ]
GEODE-7649 upgrade tests fail when v1.11 is added to geode-old-versions (#4564)
* GEODE-7649 upgrade tests fail when v1.11 is added to geode-old-versions
Geode v1.11 inadvertently changed the form of its saved membership view
by using a FileOutputStream to write it to disk instead of using
an ObjectOutputStream. The latter writes additional information during
serialization.
Note: there is already a test for this change that will start running
when v1.12 is created and v1.11 is added as a geode-old-version in
settings.gradle.
* corrected serialization in integration test
* flipping equals() check to avoid possible NPE
> upgrade tests fail when v1.11 is added to geode-old-versions
>
>
> Key: GEODE-7649
> URL: https://issues.apache.org/jira/browse/GEODE-7649
> Project: Geode
> Issue Type: Bug
> Components: membership
>Reporter: Bruce J Schuchardt
>Priority: Major
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> With v1.11 being released we are adding it as an old-version for upgrade
> tests. This is failing when a locator is rolled from v1.11 to develop
> (v1.12).
> {noformat}
> org.apache.geode.cache.wan.WANRollingUpgradeCreateGatewaySenderMixedSiteOneCurrentSiteTwo
> > CreateGatewaySenderMixedSiteOneCurrentSiteTwo[from_v1.11.0] FAILED
> org.apache.geode.test.dunit.RMIException: While invoking
> org.apache.geode.cache.wan.WANRollingUpgradeCreateGatewaySenderMixedSiteOneCurrentSiteTwo$$Lambda$200/0x000840855440.call
> in VM 0 running on Host 7ab3b8a613a7 with 7 VMs
> at org.apache.geode.test.dunit.VM.executeMethodOnObject(VM.java:610)
> at org.apache.geode.test.dunit.VM.invoke(VM.java:462)
> at
> org.apache.geode.cache.wan.WANRollingUpgradeCreateGatewaySenderMixedSiteOneCurrentSiteTwo.CreateGatewaySenderMixedSiteOneCurrentSiteTwo(WANRollingUpgradeCreateGatewaySenderMixedSiteOneCurrentSiteTwo.java:92)
> Caused by:
> java.lang.IllegalStateException: Unable to recover previous
> membership view from
> /home/geode/geode/geode-wan/build/upgradeTest38/dunit/vm0/locator28263view.dat
> at
> org.apache.geode.distributed.internal.membership.gms.locator.GMSLocator.recoverFromFile(GMSLocator.java:482)
> at
> org.apache.geode.distributed.internal.membership.gms.locator.GMSLocator.recover(GMSLocator.java:397)
> at
> org.apache.geode.distributed.internal.membership.gms.locator.GMSLocator.init(GMSLocator.java:181)
> at
> org.apache.geode.distributed.internal.membership.adapter.GMSLocatorAdapter.init(GMSLocatorAdapter.java:108)
> at
> org.apache.geode.distributed.internal.PrimaryHandler.init(PrimaryHandler.java:61)
> at
> org.apache.geode.distributed.internal.tcpserver.TcpServer.start(TcpServer.java:172)
> at
> org.apache.geode.distributed.internal.InternalLocator.startTcpServer(InternalLocator.java:563)
> at
> org.apache.geode.distributed.internal.InternalLocator.startPeerLocation(InternalLocator.java:620)
> at
> org.apache.geode.distributed.internal.InternalLocator.startLocator(InternalLocator.java:375)
> at
> org.apache.geode.distributed.internal.InternalLocator.startLocator(InternalLocator.java:330)
> at
> org.apache.geode.distributed.Locator.startLocator(Locator.java:253)
> at
> org.apache.geode.distributed.Locator.startLocatorAndDS(Locator.java:140)
> at
> org.apache.geode.cache.wan.WANRollingUpgradeDUnitTest.startLocatorWithJmxManager(WANRollingUpgradeDUnitTest.java:115)
> at
> org.apache.geode.cache.wan.WANRollingUpgradeCreateGatewaySenderMixedSiteOneCurrentSiteTwo.lambda$CreateGatewaySenderMixedSiteOneCurrentSiteTwo$e0147a59$1(WANRollingUpgradeCreateGatewaySenderMixedSiteOneCurrentSiteTwo.java:92)
> Caused by:
> java.io.StreamCorruptedException: invalid type code: 02
> at
> java.io.ObjectInputStream$BlockDataInputStream.readBlockHeader(ObjectInputStream.java:2973)
> at
> java.io.ObjectInputStream$BlockDataInputStream.refill(ObjectInputStream.java:3007)
> at
> java.io.ObjectInputStream$BlockDataInputStream.read(ObjectInputStream.java:3079)
> at java.io.ObjectInputStream.read(ObjectInputStream.java:913)
> at java.io.DataInputStream.readByte(DataInputStream.java:270)
>
[jira] [Resolved] (GEODE-7649) upgrade tests fail when v1.11 is added to geode-old-versions
[
https://issues.apache.org/jira/browse/GEODE-7649?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bruce J Schuchardt resolved GEODE-7649.
---
Resolution: Fixed
> upgrade tests fail when v1.11 is added to geode-old-versions
>
>
> Key: GEODE-7649
> URL: https://issues.apache.org/jira/browse/GEODE-7649
> Project: Geode
> Issue Type: Bug
> Components: membership
>Reporter: Bruce J Schuchardt
>Priority: Major
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> With v1.11 being released we are adding it as an old-version for upgrade
> tests. This is failing when a locator is rolled from v1.11 to develop
> (v1.12).
> {noformat}
> org.apache.geode.cache.wan.WANRollingUpgradeCreateGatewaySenderMixedSiteOneCurrentSiteTwo
> > CreateGatewaySenderMixedSiteOneCurrentSiteTwo[from_v1.11.0] FAILED
> org.apache.geode.test.dunit.RMIException: While invoking
> org.apache.geode.cache.wan.WANRollingUpgradeCreateGatewaySenderMixedSiteOneCurrentSiteTwo$$Lambda$200/0x000840855440.call
> in VM 0 running on Host 7ab3b8a613a7 with 7 VMs
> at org.apache.geode.test.dunit.VM.executeMethodOnObject(VM.java:610)
> at org.apache.geode.test.dunit.VM.invoke(VM.java:462)
> at
> org.apache.geode.cache.wan.WANRollingUpgradeCreateGatewaySenderMixedSiteOneCurrentSiteTwo.CreateGatewaySenderMixedSiteOneCurrentSiteTwo(WANRollingUpgradeCreateGatewaySenderMixedSiteOneCurrentSiteTwo.java:92)
> Caused by:
> java.lang.IllegalStateException: Unable to recover previous
> membership view from
> /home/geode/geode/geode-wan/build/upgradeTest38/dunit/vm0/locator28263view.dat
> at
> org.apache.geode.distributed.internal.membership.gms.locator.GMSLocator.recoverFromFile(GMSLocator.java:482)
> at
> org.apache.geode.distributed.internal.membership.gms.locator.GMSLocator.recover(GMSLocator.java:397)
> at
> org.apache.geode.distributed.internal.membership.gms.locator.GMSLocator.init(GMSLocator.java:181)
> at
> org.apache.geode.distributed.internal.membership.adapter.GMSLocatorAdapter.init(GMSLocatorAdapter.java:108)
> at
> org.apache.geode.distributed.internal.PrimaryHandler.init(PrimaryHandler.java:61)
> at
> org.apache.geode.distributed.internal.tcpserver.TcpServer.start(TcpServer.java:172)
> at
> org.apache.geode.distributed.internal.InternalLocator.startTcpServer(InternalLocator.java:563)
> at
> org.apache.geode.distributed.internal.InternalLocator.startPeerLocation(InternalLocator.java:620)
> at
> org.apache.geode.distributed.internal.InternalLocator.startLocator(InternalLocator.java:375)
> at
> org.apache.geode.distributed.internal.InternalLocator.startLocator(InternalLocator.java:330)
> at
> org.apache.geode.distributed.Locator.startLocator(Locator.java:253)
> at
> org.apache.geode.distributed.Locator.startLocatorAndDS(Locator.java:140)
> at
> org.apache.geode.cache.wan.WANRollingUpgradeDUnitTest.startLocatorWithJmxManager(WANRollingUpgradeDUnitTest.java:115)
> at
> org.apache.geode.cache.wan.WANRollingUpgradeCreateGatewaySenderMixedSiteOneCurrentSiteTwo.lambda$CreateGatewaySenderMixedSiteOneCurrentSiteTwo$e0147a59$1(WANRollingUpgradeCreateGatewaySenderMixedSiteOneCurrentSiteTwo.java:92)
> Caused by:
> java.io.StreamCorruptedException: invalid type code: 02
> at
> java.io.ObjectInputStream$BlockDataInputStream.readBlockHeader(ObjectInputStream.java:2973)
> at
> java.io.ObjectInputStream$BlockDataInputStream.refill(ObjectInputStream.java:3007)
> at
> java.io.ObjectInputStream$BlockDataInputStream.read(ObjectInputStream.java:3079)
> at java.io.ObjectInputStream.read(ObjectInputStream.java:913)
> at java.io.DataInputStream.readByte(DataInputStream.java:270)
> at
> org.apache.geode.internal.InternalDataSerializer.basicReadObject(InternalDataSerializer.java:2556)
> at
> org.apache.geode.DataSerializer.readObject(DataSerializer.java:2864)
> at
> org.apache.geode.internal.InternalDataSerializer$1.readObject(InternalDataSerializer.java:304)
> at
> org.apache.geode.distributed.internal.membership.gms.locator.GMSLocator.recoverFromFile(GMSLocator.java:458)
> ... 13 more
> {noformat}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (GEODE-7653) Enforce required attributes of MembershipBuilder and MembershipLocatorBuilder
Dan Smith created GEODE-7653: Summary: Enforce required attributes of MembershipBuilder and MembershipLocatorBuilder Key: GEODE-7653 URL: https://issues.apache.org/jira/browse/GEODE-7653 Project: Geode Issue Type: Improvement Components: membership Reporter: Dan Smith Right now it is not clear from the API which attributes of MembershipBuilder and MembershipLocatorBuilder are required vs. which ones are optional. Ideally, it should be enforced at compile time that all required fields are specified, maybe by passing all required fields to the contructor -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GEODE-7651) Provide docker target for geode-assembly
[
https://issues.apache.org/jira/browse/GEODE-7651?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17009236#comment-17009236
]
Anthony Baker commented on GEODE-7651:
--
Note that publishing of pre-release binary artifacts (such as snapshot images)
are a point of ASF policy contention. We should double-check with ASF Legal to
ensure that we're doing the right thing *before* publishing images.
> Provide docker target for geode-assembly
>
>
> Key: GEODE-7651
> URL: https://issues.apache.org/jira/browse/GEODE-7651
> Project: Geode
> Issue Type: Improvement
> Components: build
>Reporter: Michael Oleske
>Assignee: Michael Oleske
>Priority: Major
>
> It would be nice to provide a gradle target to build a docker image using the
> output of a {{./gradlew build}}. This would allow people who consume the
> Geode docker image to be able to use snapshots. And maybe a future story can
> be about hosting those snapshots on Geode's Google Cloud Repository
> Given {{./gradlew build}} has run successfully
> When I run {{./gradlew geode-assembly:docker}}
> Then I see {{geode:develop}} listed as an image in the command {{docker
> images}}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (GEODE-7652) Improve API for creating a MembershipLocator
Dan Smith created GEODE-7652: Summary: Improve API for creating a MembershipLocator Key: GEODE-7652 URL: https://issues.apache.org/jira/browse/GEODE-7652 Project: Geode Issue Type: Improvement Components: membership Reporter: Dan Smith The relationship between MembershipLocator and Membership is still a little strange - you must call MembershipLocator.setMembership at a specific point during the Membership startup sequence. Instead, we should pass the MembershipLocator into the MembershipBuilder and remove the MembershipLocator.setMembership method. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GEODE-7585) Add API to Membership to start a locator
[ https://issues.apache.org/jira/browse/GEODE-7585?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17009233#comment-17009233 ] ASF subversion and git services commented on GEODE-7585: Commit 65260ef6cec059f6da5b1877941e4a86bf8c0179 in geode's branch refs/heads/develop from Dan Smith [ https://gitbox.apache.org/repos/asf?p=geode.git;h=65260ef ] GEODE-7585: Create API for starting a locator in the membership package Creating a new MembershipLocator and MembershipLocatorBuilder that are used to create the membership locator. These classes encapsulate the TcpServer, PrimaryHandler, and GMSLocator that were previously held by InternalLocator. Getting rid of some intermdiate classes that wrapped the GMSLocator - NetLocator and GMSLocatorAdapter. Refactoring the restart logic out of PrimaryHandler. There is now a separate RestartHandler, and a separate collection that tracks RestartHandlers. Removing RestartableTcpHandler. Removing TcpServerFactory. > Add API to Membership to start a locator > > > Key: GEODE-7585 > URL: https://issues.apache.org/jira/browse/GEODE-7585 > Project: Geode > Issue Type: Improvement > Components: membership >Reporter: Bill Burcham >Assignee: Bill Burcham >Priority: Major > Time Spent: 1h 40m > Remaining Estimate: 0h > > After we have decoupled the tcpserver package from the rest of core, we would > like to have a way to inject a TCPServer configuration into membership. > Right now the core is directly creating and calling GMSLocator from > GMSLocatorAdapter. GMSLocatorAdapter is not going through the membership API, > it's interacting with a GMSLocator component that was created before > Membership was started. GMSLocator is not part of the membership API. > Instead, we would like core to only use the membership API, so we should have > a better way to inject the TCPServer into membership. We want to have all of > the membership code encapsulated behind the the classes in gms.api package > (Membership, MembershipBuilder). We also want all of the components of > membership to be instantiated when we call MembershipBuilder.create. > For production, we would have an implementation that would include any > core-specific behaviors. For isolated testing of the membership component, we > would have an implementation that would include just what is required for > membership, which is essentially the ability to register a handler for > PeerLocationRequests. The InternalLocator will pass along its additional > handlers (and whatever else it needs) to membership. > For the interface, we might just add another setter to our builder like this: > MembershipBuilder > .setTcpServerConfiguration(TcpServerConfiguration) > .. > Acceptance Criteria: > geode-core code will only interface with the classes in the gms.api > package. It will not directly use GMSLocator. > We have an API to start the locator part of membership within the > membership module. > We have a test that starts a locator and connects two members to it, > using only the membership module (through it's public API). This should be an > integration test (no dunit). Perhaps MembershipJUnitTest could be used. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GEODE-7646) Simplify SSL Examples by Eliminating Need for LD_LIBRARY_PATH on Linux
[ https://issues.apache.org/jira/browse/GEODE-7646?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17009231#comment-17009231 ] ASF subversion and git services commented on GEODE-7646: Commit d188839d43f469c7da37b6dd3c296230705373d2 in geode-native's branch refs/heads/develop from Michael Martell [ https://gitbox.apache.org/repos/asf?p=geode-native.git;h=d188839 ] GEODE-7646: Parameterize GeodeNative::crypto to use PRODUCT_NAME (#569) > Simplify SSL Examples by Eliminating Need for LD_LIBRARY_PATH on Linux > -- > > Key: GEODE-7646 > URL: https://issues.apache.org/jira/browse/GEODE-7646 > Project: Geode > Issue Type: Improvement > Components: native client >Reporter: Michael Martell >Priority: Major > Time Spent: 1h 20m > Remaining Estimate: 0h > > The new SSL examples for the native client currently require the > LD_LIBRARY_PATH environment variable to include the path to our crypto > library (libcryptoImpl.so) on Linux. This ticket is to eliminate the need for > this environment variable and make Linux and OSX be consistent. > The driving force to fix this was the recent switch to using RPATH to bake in > the path to our crypto library into the executable. On newer versions of OSX, > System Integrity Protection (SIP) ignores LD_LIBRARY_PATH. Using RPATH was > the solution for this. However, until this fix the RPATH solution doesn't > work on Linux. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (GEODE-7651) Provide docker target for geode-assembly
[
https://issues.apache.org/jira/browse/GEODE-7651?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Oleske reassigned GEODE-7651:
-
Assignee: Michael Oleske
> Provide docker target for geode-assembly
>
>
> Key: GEODE-7651
> URL: https://issues.apache.org/jira/browse/GEODE-7651
> Project: Geode
> Issue Type: Improvement
> Components: build
>Reporter: Michael Oleske
>Assignee: Michael Oleske
>Priority: Major
>
> It would be nice to provide a gradle target to build a docker image using the
> output of a {{./gradlew build}}. This would allow people who consume the
> Geode docker image to be able to use snapshots. And maybe a future story can
> be about hosting those snapshots on Geode's Google Cloud Repository
> Given {{./gradlew build}} has run successfully
> When I run {{./gradlew geode-assembly:docker}}
> Then I see {{geode:develop}} listed as an image in the command {{docker
> images}}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (GEODE-7651) Provide docker target for geode-assembly
Michael Oleske created GEODE-7651:
-
Summary: Provide docker target for geode-assembly
Key: GEODE-7651
URL: https://issues.apache.org/jira/browse/GEODE-7651
Project: Geode
Issue Type: Improvement
Components: build
Reporter: Michael Oleske
It would be nice to provide a gradle target to build a docker image using the
output of a {{./gradlew build}}. This would allow people who consume the Geode
docker image to be able to use snapshots. And maybe a future story can be
about hosting those snapshots on Geode's Google Cloud Repository
Given {{./gradlew build}} has run successfully
When I run {{./gradlew geode-assembly:docker}}
Then I see {{geode:develop}} listed as an image in the command {{docker images}}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Resolved] (GEODE-7647) Remove unused code from GMSJoinLeave.findCoordinator
[ https://issues.apache.org/jira/browse/GEODE-7647?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Smith resolved GEODE-7647. -- Fix Version/s: 1.12.0 Resolution: Fixed > Remove unused code from GMSJoinLeave.findCoordinator > > > Key: GEODE-7647 > URL: https://issues.apache.org/jira/browse/GEODE-7647 > Project: Geode > Issue Type: Improvement > Components: membership >Reporter: Dan Smith >Assignee: Dan Smith >Priority: Major > Fix For: 1.12.0 > > Time Spent: 20m > Remaining Estimate: 0h > > There is some dead code in this method that computes a couple of local > variables that are never used - coord and coordIsNoob > https://github.com/apache/geode/blob/2178ba8fefcda23d4b2d3b6ecc68b58dd8839f7f/geode-core/src/main/java/org/apache/geode/distributed/internal/membership/gms/membership/GMSJoinLeave.java#L1223 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GEODE-7647) Remove unused code from GMSJoinLeave.findCoordinator
[ https://issues.apache.org/jira/browse/GEODE-7647?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17009171#comment-17009171 ] ASF subversion and git services commented on GEODE-7647: Commit 13362a00bfb2718777d5238109c971e4db561be8 in geode's branch refs/heads/develop from Dan Smith [ https://gitbox.apache.org/repos/asf?p=geode.git;h=13362a0 ] GEODE-7647: Removing unused code from GMSJoinLeave Removing some code which set the coord and coordIsNoob local variables but never used them. > Remove unused code from GMSJoinLeave.findCoordinator > > > Key: GEODE-7647 > URL: https://issues.apache.org/jira/browse/GEODE-7647 > Project: Geode > Issue Type: Improvement > Components: membership >Reporter: Dan Smith >Assignee: Dan Smith >Priority: Major > Time Spent: 20m > Remaining Estimate: 0h > > There is some dead code in this method that computes a couple of local > variables that are never used - coord and coordIsNoob > https://github.com/apache/geode/blob/2178ba8fefcda23d4b2d3b6ecc68b58dd8839f7f/geode-core/src/main/java/org/apache/geode/distributed/internal/membership/gms/membership/GMSJoinLeave.java#L1223 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (GEODE-7542) Break dependency on JavaWorkArounds
[ https://issues.apache.org/jira/browse/GEODE-7542?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17009160#comment-17009160 ] ASF subversion and git services commented on GEODE-7542: Commit b32ff42ff987c213d8f73c02912d093a1c76f41f in geode's branch refs/heads/develop from Ernie Burghardt [ https://gitbox.apache.org/repos/asf?p=geode.git;h=b32ff42 ] GEODE-7542: Remove dependency upon JavaWorkarounds. (#4556) * Moved JavaWorkarounds to a new package in geode-common module * Cleaned up ArchUnit exceptions to be package based, when possible. > Break dependency on JavaWorkArounds > --- > > Key: GEODE-7542 > URL: https://issues.apache.org/jira/browse/GEODE-7542 > Project: Geode > Issue Type: Improvement > Components: membership >Reporter: Ernest Burghardt >Priority: Major > Fix For: 1.12.0 > > Time Spent: 1h > Remaining Estimate: 0h > > this work around exists only for pre-Java9 JDKs, fwiw... -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (GEODE-7542) Break dependency on JavaWorkArounds
[ https://issues.apache.org/jira/browse/GEODE-7542?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ernest Burghardt resolved GEODE-7542. - Fix Version/s: 1.12.0 Resolution: Fixed > Break dependency on JavaWorkArounds > --- > > Key: GEODE-7542 > URL: https://issues.apache.org/jira/browse/GEODE-7542 > Project: Geode > Issue Type: Improvement > Components: membership >Reporter: Ernest Burghardt >Priority: Major > Fix For: 1.12.0 > > Time Spent: 1h > Remaining Estimate: 0h > > this work around exists only for pre-Java9 JDKs, fwiw... -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (GEODE-632) SUPERFLAKY: DistributedRegionFunctionExecutionDUnitTest.testDistributedRegionFunctionExecutionOnDataPolicyEmpty_ClientServer_NoLastResult
[
https://issues.apache.org/jira/browse/GEODE-632?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kirk Lund resolved GEODE-632.
-
Fix Version/s: 1.12.0
Resolution: Fixed
> SUPERFLAKY:
> DistributedRegionFunctionExecutionDUnitTest.testDistributedRegionFunctionExecutionOnDataPolicyEmpty_ClientServer_NoLastResult
> -
>
> Key: GEODE-632
> URL: https://issues.apache.org/jira/browse/GEODE-632
> Project: Geode
> Issue Type: Bug
> Components: functions
>Reporter: Darrel Schneider
>Assignee: Kirk Lund
>Priority: Major
> Labels: CI, Flaky, swat
> Fix For: 1.12.0
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> git rev 9283282c64076c5f8e599f3d47895f3c48e205e8 build #813
> java.lang.AssertionError: Suspicious strings were written to the log during
> this run.
> Fix the strings or use DistributedTestCase.addExpectedException to ignore.
> ---
> Found suspect string in log4j at line 4649
> {noformat}
> [fatal 2015/12/06 15:02:06.760 PST
> tid=0x233b] Uncaught exception processing
> com.gemstone.gemfire.internal.cache.FunctionStreamingReplyMessage(processorId=10999
> from cc4-rh6(25294):1027;msgNum 0;lastMsg=false)
> com.gemstone.gemfire.cache.execute.FunctionException: IOException while
> sending the result chunk to client
> at
> com.gemstone.gemfire.internal.cache.execute.ServerToClientFunctionResultSender65.sendResult(ServerToClientFunctionResultSender65.java:247)
> at
> com.gemstone.gemfire.internal.cache.execute.DistributedRegionFunctionResultSender.sendResult(DistributedRegionFunctionResultSender.java:204)
> at
> com.gemstone.gemfire.internal.cache.execute.StreamingFunctionOperation.processData(StreamingFunctionOperation.java:93)
> at
> com.gemstone.gemfire.internal.cache.execute.FunctionStreamingResultCollector.process(FunctionStreamingResultCollector.java:541)
> at
> com.gemstone.gemfire.distributed.internal.ReplyMessage.process(ReplyMessage.java:231)
> at
> com.gemstone.gemfire.distributed.internal.ReplyMessage.dmProcess(ReplyMessage.java:212)
> at
> com.gemstone.gemfire.distributed.internal.ReplyMessage.process(ReplyMessage.java:201)
> at
> com.gemstone.gemfire.distributed.internal.DistributionMessage.scheduleAction(DistributionMessage.java:380)
> at
> com.gemstone.gemfire.distributed.internal.DistributionMessage$1.run(DistributionMessage.java:451)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at
> com.gemstone.gemfire.distributed.internal.DistributionManager.runUntilShutdown(DistributionManager.java:658)
> at
> com.gemstone.gemfire.distributed.internal.DistributionManager$5$1.run(DistributionManager.java:969)
> at java.lang.Thread.run(Thread.java:745)
> Caused by: java.net.SocketException: Socket closed
> at java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:116)
> at java.net.SocketOutputStream.write(SocketOutputStream.java:153)
> at
> com.gemstone.gemfire.internal.cache.tier.sockets.Message.flushBuffer(Message.java:668)
> at
> com.gemstone.gemfire.internal.cache.tier.sockets.ChunkedMessage.sendHeader(ChunkedMessage.java:295)
> at
> com.gemstone.gemfire.internal.cache.execute.ServerToClientFunctionResultSender.sendHeader(ServerToClientFunctionResultSender.java:271)
> at
> com.gemstone.gemfire.internal.cache.execute.ServerToClientFunctionResultSender65.sendResult(ServerToClientFunctionResultSender65.java:228)
> {noformat}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (GEODE-7649) upgrade tests fail when v1.11 is added to geode-old-versions
[
https://issues.apache.org/jira/browse/GEODE-7649?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17009134#comment-17009134
]
ASF subversion and git services commented on GEODE-7649:
Commit c11c856e0b12a409cd48e9f7fab26583e2b189af in geode's branch
refs/heads/feature/GEODE-7649 from Bruce Schuchardt
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=c11c856 ]
GEODE-7649 upgrade tests fail when v1.11 is added to geode-old-versions
Geode v1.11 inadvertently changed the form of its saved membership view
by using a FileOutputStream to write it to disk instead of using
an ObjectOutputStream. The latter writes additional information during
serialization.
Note: there is already a test for this change that will start running
when v1.12 is created and v1.11 is added as a geode-old-version in
settings.gradle.
> upgrade tests fail when v1.11 is added to geode-old-versions
>
>
> Key: GEODE-7649
> URL: https://issues.apache.org/jira/browse/GEODE-7649
> Project: Geode
> Issue Type: Bug
> Components: membership
>Reporter: Bruce J Schuchardt
>Priority: Major
>
> With v1.11 being released we are adding it as an old-version for upgrade
> tests. This is failing when a locator is rolled from v1.11 to develop
> (v1.12).
> {noformat}
> org.apache.geode.cache.wan.WANRollingUpgradeCreateGatewaySenderMixedSiteOneCurrentSiteTwo
> > CreateGatewaySenderMixedSiteOneCurrentSiteTwo[from_v1.11.0] FAILED
> org.apache.geode.test.dunit.RMIException: While invoking
> org.apache.geode.cache.wan.WANRollingUpgradeCreateGatewaySenderMixedSiteOneCurrentSiteTwo$$Lambda$200/0x000840855440.call
> in VM 0 running on Host 7ab3b8a613a7 with 7 VMs
> at org.apache.geode.test.dunit.VM.executeMethodOnObject(VM.java:610)
> at org.apache.geode.test.dunit.VM.invoke(VM.java:462)
> at
> org.apache.geode.cache.wan.WANRollingUpgradeCreateGatewaySenderMixedSiteOneCurrentSiteTwo.CreateGatewaySenderMixedSiteOneCurrentSiteTwo(WANRollingUpgradeCreateGatewaySenderMixedSiteOneCurrentSiteTwo.java:92)
> Caused by:
> java.lang.IllegalStateException: Unable to recover previous
> membership view from
> /home/geode/geode/geode-wan/build/upgradeTest38/dunit/vm0/locator28263view.dat
> at
> org.apache.geode.distributed.internal.membership.gms.locator.GMSLocator.recoverFromFile(GMSLocator.java:482)
> at
> org.apache.geode.distributed.internal.membership.gms.locator.GMSLocator.recover(GMSLocator.java:397)
> at
> org.apache.geode.distributed.internal.membership.gms.locator.GMSLocator.init(GMSLocator.java:181)
> at
> org.apache.geode.distributed.internal.membership.adapter.GMSLocatorAdapter.init(GMSLocatorAdapter.java:108)
> at
> org.apache.geode.distributed.internal.PrimaryHandler.init(PrimaryHandler.java:61)
> at
> org.apache.geode.distributed.internal.tcpserver.TcpServer.start(TcpServer.java:172)
> at
> org.apache.geode.distributed.internal.InternalLocator.startTcpServer(InternalLocator.java:563)
> at
> org.apache.geode.distributed.internal.InternalLocator.startPeerLocation(InternalLocator.java:620)
> at
> org.apache.geode.distributed.internal.InternalLocator.startLocator(InternalLocator.java:375)
> at
> org.apache.geode.distributed.internal.InternalLocator.startLocator(InternalLocator.java:330)
> at
> org.apache.geode.distributed.Locator.startLocator(Locator.java:253)
> at
> org.apache.geode.distributed.Locator.startLocatorAndDS(Locator.java:140)
> at
> org.apache.geode.cache.wan.WANRollingUpgradeDUnitTest.startLocatorWithJmxManager(WANRollingUpgradeDUnitTest.java:115)
> at
> org.apache.geode.cache.wan.WANRollingUpgradeCreateGatewaySenderMixedSiteOneCurrentSiteTwo.lambda$CreateGatewaySenderMixedSiteOneCurrentSiteTwo$e0147a59$1(WANRollingUpgradeCreateGatewaySenderMixedSiteOneCurrentSiteTwo.java:92)
> Caused by:
> java.io.StreamCorruptedException: invalid type code: 02
> at
> java.io.ObjectInputStream$BlockDataInputStream.readBlockHeader(ObjectInputStream.java:2973)
> at
> java.io.ObjectInputStream$BlockDataInputStream.refill(ObjectInputStream.java:3007)
> at
> java.io.ObjectInputStream$BlockDataInputStream.read(ObjectInputStream.java:3079)
> at java.io.ObjectInputStream.read(ObjectInputStream.java:913)
> at java.io.DataInputStream.readByte(DataInputStream.java:270)
> at
> org.apache.geode.internal.InternalDataSerializer.basicReadObject(InternalDataSerializer.java:2556)
> at
> org.apache.geode.DataSerializer.readObject(DataSerializer.java:2864)
> at
[jira] [Commented] (GEODE-7650) CI Failure: PutAllClientServerDistributedTest > testHADRFailOver FAILED
[ https://issues.apache.org/jira/browse/GEODE-7650?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17009114#comment-17009114 ] Steve Sienkowski commented on GEODE-7650: - Note from Bill on commit 3476e83de0c9fe56acd4fc770f33926e204950f2: DistributedTestOpenJDK8 does not run as part of the PR pipeline. apparently only DistributedTestOpenJDK11 does. And here is the (green) run of that test that ran before I merged that PR:[https://concourse.apachegeode-ci.info/builds/124022|https://slack-redir.net/link?url=https%3A%2F%2Fconcourse.apachegeode-ci.info%2Fbuilds%2F124022] > CI Failure: PutAllClientServerDistributedTest > testHADRFailOver FAILED > --- > > Key: GEODE-7650 > URL: https://issues.apache.org/jira/browse/GEODE-7650 > Project: Geode > Issue Type: Bug >Reporter: Steve Sienkowski >Priority: Major > > This might be test flakiness. The following build #1454 passed with the same > commit as this > #[1453|[https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/DistributedTestOpenJDK8/builds/1453]]. > > === > org.apache.geode.internal.cache.PutAllClientServerDistributedTest > > testHADRFailOver FAILED > 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 2540 > [error 2020/01/04 02:39:33.282 GMT > tid=32] org.apache.geode.distributed.DistributedSystemDisconnectedException: > This connection to a distributed system has been disconnected. > 679 tests completed, 1 failed, 39 skipped > =-=-=-=-=-=-=-=-=-=-=-=-=-=-= Test Results URI > =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= > [*http://files.apachegeode-ci.info/builds/apache-develop-main/1.12.0-SNAPSHOT.0168/test-results/distributedTest/1578111422/*] > =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= > Test report artifacts from this job are available at: > [*http://files.apachegeode-ci.info/builds/apache-develop-main/1.12.0-SNAPSHOT.0168/test-artifacts/1578111422/distributedtestfiles-OpenJDK8-1.12.0-SNAPSHOT.0168.tgz*] -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (GEODE-7650) CI Failure: PutAllClientServerDistributedTest > testHADRFailOver FAILED
Steve Sienkowski created GEODE-7650: --- Summary: CI Failure: PutAllClientServerDistributedTest > testHADRFailOver FAILED Key: GEODE-7650 URL: https://issues.apache.org/jira/browse/GEODE-7650 Project: Geode Issue Type: Bug Reporter: Steve Sienkowski This might be test flakiness. The following build #1454 passed with the same commit as this #[1453|[https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/DistributedTestOpenJDK8/builds/1453]]. === org.apache.geode.internal.cache.PutAllClientServerDistributedTest > testHADRFailOver FAILED 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 2540 [error 2020/01/04 02:39:33.282 GMT tid=32] org.apache.geode.distributed.DistributedSystemDisconnectedException: This connection to a distributed system has been disconnected. 679 tests completed, 1 failed, 39 skipped =-=-=-=-=-=-=-=-=-=-=-=-=-=-= Test Results URI =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= [*http://files.apachegeode-ci.info/builds/apache-develop-main/1.12.0-SNAPSHOT.0168/test-results/distributedTest/1578111422/*] =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Test report artifacts from this job are available at: [*http://files.apachegeode-ci.info/builds/apache-develop-main/1.12.0-SNAPSHOT.0168/test-artifacts/1578111422/distributedtestfiles-OpenJDK8-1.12.0-SNAPSHOT.0168.tgz*] -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (GEODE-7649) upgrade tests fail when v1.11 is added to geode-old-versions
Bruce J Schuchardt created GEODE-7649:
-
Summary: upgrade tests fail when v1.11 is added to
geode-old-versions
Key: GEODE-7649
URL: https://issues.apache.org/jira/browse/GEODE-7649
Project: Geode
Issue Type: Bug
Components: membership
Reporter: Bruce J Schuchardt
With v1.11 being released we are adding it as an old-version for upgrade tests.
This is failing when a locator is rolled from v1.11 to develop (v1.12).
{noformat}
org.apache.geode.cache.wan.WANRollingUpgradeCreateGatewaySenderMixedSiteOneCurrentSiteTwo
> CreateGatewaySenderMixedSiteOneCurrentSiteTwo[from_v1.11.0] FAILED
org.apache.geode.test.dunit.RMIException: While invoking
org.apache.geode.cache.wan.WANRollingUpgradeCreateGatewaySenderMixedSiteOneCurrentSiteTwo$$Lambda$200/0x000840855440.call
in VM 0 running on Host 7ab3b8a613a7 with 7 VMs
at org.apache.geode.test.dunit.VM.executeMethodOnObject(VM.java:610)
at org.apache.geode.test.dunit.VM.invoke(VM.java:462)
at
org.apache.geode.cache.wan.WANRollingUpgradeCreateGatewaySenderMixedSiteOneCurrentSiteTwo.CreateGatewaySenderMixedSiteOneCurrentSiteTwo(WANRollingUpgradeCreateGatewaySenderMixedSiteOneCurrentSiteTwo.java:92)
Caused by:
java.lang.IllegalStateException: Unable to recover previous membership
view from
/home/geode/geode/geode-wan/build/upgradeTest38/dunit/vm0/locator28263view.dat
at
org.apache.geode.distributed.internal.membership.gms.locator.GMSLocator.recoverFromFile(GMSLocator.java:482)
at
org.apache.geode.distributed.internal.membership.gms.locator.GMSLocator.recover(GMSLocator.java:397)
at
org.apache.geode.distributed.internal.membership.gms.locator.GMSLocator.init(GMSLocator.java:181)
at
org.apache.geode.distributed.internal.membership.adapter.GMSLocatorAdapter.init(GMSLocatorAdapter.java:108)
at
org.apache.geode.distributed.internal.PrimaryHandler.init(PrimaryHandler.java:61)
at
org.apache.geode.distributed.internal.tcpserver.TcpServer.start(TcpServer.java:172)
at
org.apache.geode.distributed.internal.InternalLocator.startTcpServer(InternalLocator.java:563)
at
org.apache.geode.distributed.internal.InternalLocator.startPeerLocation(InternalLocator.java:620)
at
org.apache.geode.distributed.internal.InternalLocator.startLocator(InternalLocator.java:375)
at
org.apache.geode.distributed.internal.InternalLocator.startLocator(InternalLocator.java:330)
at
org.apache.geode.distributed.Locator.startLocator(Locator.java:253)
at
org.apache.geode.distributed.Locator.startLocatorAndDS(Locator.java:140)
at
org.apache.geode.cache.wan.WANRollingUpgradeDUnitTest.startLocatorWithJmxManager(WANRollingUpgradeDUnitTest.java:115)
at
org.apache.geode.cache.wan.WANRollingUpgradeCreateGatewaySenderMixedSiteOneCurrentSiteTwo.lambda$CreateGatewaySenderMixedSiteOneCurrentSiteTwo$e0147a59$1(WANRollingUpgradeCreateGatewaySenderMixedSiteOneCurrentSiteTwo.java:92)
Caused by:
java.io.StreamCorruptedException: invalid type code: 02
at
java.io.ObjectInputStream$BlockDataInputStream.readBlockHeader(ObjectInputStream.java:2973)
at
java.io.ObjectInputStream$BlockDataInputStream.refill(ObjectInputStream.java:3007)
at
java.io.ObjectInputStream$BlockDataInputStream.read(ObjectInputStream.java:3079)
at java.io.ObjectInputStream.read(ObjectInputStream.java:913)
at java.io.DataInputStream.readByte(DataInputStream.java:270)
at
org.apache.geode.internal.InternalDataSerializer.basicReadObject(InternalDataSerializer.java:2556)
at
org.apache.geode.DataSerializer.readObject(DataSerializer.java:2864)
at
org.apache.geode.internal.InternalDataSerializer$1.readObject(InternalDataSerializer.java:304)
at
org.apache.geode.distributed.internal.membership.gms.locator.GMSLocator.recoverFromFile(GMSLocator.java:458)
... 13 more
{noformat}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (GEODE-7583) "status locator --name/--dir" is not working properly when locator ssl is enabled
[
https://issues.apache.org/jira/browse/GEODE-7583?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17009097#comment-17009097
]
Gang Yan commented on GEODE-7583:
-
[~jmcallis...@pivotal.io]
Hi Joey
there might be some docs update for this command.
> "status locator --name/--dir" is not working properly when locator ssl is
> enabled
> -
>
> Key: GEODE-7583
> URL: https://issues.apache.org/jira/browse/GEODE-7583
> Project: Geode
> Issue Type: Bug
> Components: docs, gfsh
>Affects Versions: 1.8.0, 1.9.0, 1.10.0, 1.11.0
>Reporter: Jinmei Liao
>Priority: Major
> Time Spent: 40m
> Remaining Estimate: 0h
>
> in 1.8:
> 1. start a locator with ssl enabled
> 2. "status locator --dir" or "status locator --name" would trigger such error
> messages in the locator log:
> {quote}[info 2019/12/16 08:57:39.958 PST locator
> tid=0x23] Exception in processing request from 10.118.20.75
> javax.net.ssl.SSLException: Unrecognized SSL message, plaintext connection?
> at
> sun.security.ssl.InputRecord.handleUnknownRecord(InputRecord.java:710)
> at sun.security.ssl.InputRecord.read(InputRecord.java:527)
> at sun.security.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java:975)
> at
> sun.security.ssl.SSLSocketImpl.performInitialHandshake(SSLSocketImpl.java:1367)
> at
> sun.security.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:1395)
> at
> sun.security.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:1379)
> at
> org.apache.geode.internal.net.SocketCreator.handshakeIfSocketIsSSL(SocketCreator.java:981)
> at
> org.apache.geode.distributed.internal.tcpserver.TcpServer.lambda$processRequest$0(TcpServer.java:346)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> at java.lang.Thread.run(Thread.java:748)
> {quote}
> In develop branch: the gfsh output would be a strange ClassCastException.
> It's definitely broken on develop
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (GEODE-7583) "status locator --name/--dir" is not working properly when locator ssl is enabled
[
https://issues.apache.org/jira/browse/GEODE-7583?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gang Yan updated GEODE-7583:
Component/s: docs
> "status locator --name/--dir" is not working properly when locator ssl is
> enabled
> -
>
> Key: GEODE-7583
> URL: https://issues.apache.org/jira/browse/GEODE-7583
> Project: Geode
> Issue Type: Bug
> Components: docs, gfsh
>Affects Versions: 1.8.0, 1.9.0, 1.10.0, 1.11.0
>Reporter: Jinmei Liao
>Priority: Major
> Time Spent: 40m
> Remaining Estimate: 0h
>
> in 1.8:
> 1. start a locator with ssl enabled
> 2. "status locator --dir" or "status locator --name" would trigger such error
> messages in the locator log:
> {quote}[info 2019/12/16 08:57:39.958 PST locator
> tid=0x23] Exception in processing request from 10.118.20.75
> javax.net.ssl.SSLException: Unrecognized SSL message, plaintext connection?
> at
> sun.security.ssl.InputRecord.handleUnknownRecord(InputRecord.java:710)
> at sun.security.ssl.InputRecord.read(InputRecord.java:527)
> at sun.security.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java:975)
> at
> sun.security.ssl.SSLSocketImpl.performInitialHandshake(SSLSocketImpl.java:1367)
> at
> sun.security.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:1395)
> at
> sun.security.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:1379)
> at
> org.apache.geode.internal.net.SocketCreator.handshakeIfSocketIsSSL(SocketCreator.java:981)
> at
> org.apache.geode.distributed.internal.tcpserver.TcpServer.lambda$processRequest$0(TcpServer.java:346)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> at java.lang.Thread.run(Thread.java:748)
> {quote}
> In develop branch: the gfsh output would be a strange ClassCastException.
> It's definitely broken on develop
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Resolved] (GEODE-7590) Windows Heavy-Lifters fail to connect after gcloud base image update
[
https://issues.apache.org/jira/browse/GEODE-7590?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Houghton resolved GEODE-7590.
Fix Version/s: 1.12.0
Resolution: Fixed
> Windows Heavy-Lifters fail to connect after gcloud base image update
>
>
> Key: GEODE-7590
> URL: https://issues.apache.org/jira/browse/GEODE-7590
> Project: Geode
> Issue Type: Bug
> Components: ci
>Reporter: Robert Houghton
>Priority: Major
> Fix For: 1.12.0
>
> Time Spent: 1h
> Remaining Estimate: 0h
>
> Google Compute Image family {{windows-2016}} updated to
> {{windows-server-2016-dc-v20191210}} , and the heavy-lifter built by Packer
> was unreachable afterward. CI rebuilds have been paused, and the "broken"
> image has been deleted from the apachegeode-ci google project.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Resolved] (GEODE-7641) Windows instance creation fails in CI
[
https://issues.apache.org/jira/browse/GEODE-7641?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Houghton resolved GEODE-7641.
Fix Version/s: 1.12.0
Resolution: Fixed
> Windows instance creation fails in CI
> -
>
> Key: GEODE-7641
> URL: https://issues.apache.org/jira/browse/GEODE-7641
> Project: Geode
> Issue Type: Bug
> Components: ci
>Reporter: Alexander Murmann
>Assignee: Robert Houghton
>Priority: Major
> Fix For: 1.12.0
>
> Time Spent: 50m
> Remaining Estimate: 0h
>
> Windows job fail with some regularity because they fail to create the
> instance correctly. The pattern seems to be that the job retries for a
> prolonged time. After that it starts failing because the resource already
> exists. (Are we missing when the instance finally gets created?)
> Logs form timed out creation attempts:
> {code:java}
> 11:12:49Updated
> [https://www.googleapis.com/compute/beta/projects/apachegeode-ci/zones/us-central1-f/instances/heavy-lifter-fbdf2e36-c559-5e39-8bb8-9b298c208d83].
> 11:12:50ERROR: (gcloud.beta.compute.reset-windows-password)
> 11:12:50The instance may not be ready for use. This can occur if the instance
> was
> 11:12:50recently created or if the instance is not running Windows.
> 11:12:50Please wait a few minutes and try again.
> 11:12:55.
> 11:12:55This command creates an account and sets an initial password for the
> 11:12:55user [geode] if the account does not already exist.
> 11:12:55If the account already exists, resetting the password can cause the
> 11:12:55LOSS OF ENCRYPTED DATA secured with the current password, including
> 11:12:55files and stored passwords.
> 11:12:55
> 11:12:55For more information, see:
> 11:12:55https://cloud.google.com/compute/docs/operating-systems/windows#reset
> 11:12:55
> 11:12:55Would you like to set or reset the password for [geode] (Y/n)?
> 11:12:55Resetting and retrieving password for [geode] on
> [heavy-lifter-fbdf2e36-c559-5e39-8bb8-9b298c208d83]
> {code}
> The above repeats till the task times out.
> Then it transitions to tasks that fails like shown below:
> {code:java}
> 11:13:09/tmp/build/5ca5b479/geode /tmp/build/5ca5b479
> 11:13:09/tmp/build/5ca5b479
> 11:13:09Hashed
> apache-develop-main-WindowsIntegrationTestOpenJDK11-build8-test11-job#1110
> (74 chars) -> heavy-lifter-fbdf2e36-c559-5e39-8bb8-9b298c208d83 (49 chars)
> 11:13:10Deploying to zone us-central1-a
> 11:13:11Applying the following labels to the instance:
> instance_type=heavy-lifter,time-to-live=1576912391,job-name=windowsintegrationtestopenjdk11,pipeline-name=apache-develop-main,build-name=1110,sha=7ac2c4d24a2ccc45c0ba2b09754f9caeaaa4080f
> 11:13:13ERROR: (gcloud.compute.instances.create) Could not fetch resource:
> 11:13:13 - The resource
> 'projects/apachegeode-ci/zones/us-central1-f/instances/heavy-lifter-fbdf2e36-c559-5e39-8bb8-9b298c208d83'
> already exists
> {code}
> This seems to have been happening since quite a while. See [this
> run|https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/WindowsIntegrationTestOpenJDK11/builds/1110]
> for an example.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Resolved] (GEODE-7091) Add Micrometer binders to default meter registry
[ https://issues.apache.org/jira/browse/GEODE-7091?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aaron Lindsey resolved GEODE-7091. -- Resolution: Fixed > Add Micrometer binders to default meter registry > > > Key: GEODE-7091 > URL: https://issues.apache.org/jira/browse/GEODE-7091 > Project: Geode > Issue Type: Improvement > Components: statistics >Reporter: Aaron Lindsey >Assignee: Aaron Lindsey >Priority: Major > Fix For: 1.11.0 > > Time Spent: 2h 40m > Remaining Estimate: 0h > > As a user, there are specific JVM metrics, GC metrics, Uptime, and > FileDescriptor metrics that help indicate and track down issues with health > of the cluster, that I want to access in order to understand the health of my > cluster. > Add the following Micrometer binders: > * JvmGcMetrics > * ProcessorMetrics > * JvmThreadMetrics > * UptimeMetrics > * FileDescriptorMetrics -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (GEODE-7237) CI failure: ConnectCommandAcceptanceTest.invalidHostname
[
https://issues.apache.org/jira/browse/GEODE-7237?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aaron Lindsey resolved GEODE-7237.
--
Resolution: Fixed
> CI failure: ConnectCommandAcceptanceTest.invalidHostname
>
>
> Key: GEODE-7237
> URL: https://issues.apache.org/jira/browse/GEODE-7237
> Project: Geode
> Issue Type: Bug
> Components: ci, tests
>Reporter: Aaron Lindsey
>Assignee: Aaron Lindsey
>Priority: Major
> Fix For: 1.11.0
>
> Time Spent: 2.5h
> Remaining Estimate: 0h
>
> [https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-develop-main/jobs/AcceptanceTestOpenJDK8/builds/1101]
> {code:java}
> org.apache.geode.management.internal.cli.commands.ConnectCommandAcceptanceTest
> > invalidHostname FAILED
> java.lang.AssertionError:
> Expecting:
> <"">
> to contain:
> <"can't be reached. Hostname or IP address could not be found.">
> at
> org.apache.geode.management.internal.cli.commands.ConnectCommandAcceptanceTest.invalidHostname(ConnectCommandAcceptanceTest.java:59)
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
