[jira] [Deleted] (GEODE-10399) CI: TomcatSessionBackwardsCompatibilityTomcat8WithOldModulesMixedWithCurrentCanDoPutFromOldModuleTest > test[1.8.0] FAILED

2022-08-02 Thread Owen Nichols (Jira)


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

Owen Nichols deleted GEODE-10399:
-


> CI: 
> TomcatSessionBackwardsCompatibilityTomcat8WithOldModulesMixedWithCurrentCanDoPutFromOldModuleTest
>  > test[1.8.0] FAILED
> --
>
> Key: GEODE-10399
> URL: https://issues.apache.org/jira/browse/GEODE-10399
> Project: Geode
>  Issue Type: Bug
>Reporter: Xiaojian Zhou
>Priority: Major
>  Labels: needsTriage
>
> It's probably due to environment. Similar to GEODE-9531. 
> {code:java}
> TomcatSessionBackwardsCompatibilityTomcat8WithOldModulesMixedWithCurrentCanDoPutFromOldModuleTest
>  > test[1.8.0] FAILED
> org.opentest4j.AssertionFailedError: [Locator in 
> /tmp/junit1239217839732739821/locator on 
> heavy-lifter-fbdeb3b6-ac9b-5022-9bde-6fc2316be33d.c.gemfire-dev.internal[10334]
>  is currently not responding.
> ] 
> expected: OK
>  but was: ERROR
> at 
> jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
> at 
> jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
> at 
> jdk.internal.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
> at 
> org.apache.geode.test.junit.assertions.CommandResultAssert.statusIsSuccess(CommandResultAssert.java:108)
> at 
> org.apache.geode.session.tests.TomcatSessionBackwardsCompatibilityTestBase.stop(TomcatSessionBackwardsCompatibilityTestBase.java:194)
> at jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native 
> Method)
> at 
> jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at 
> jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:566)
> at 
> org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:59)
> at 
> org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
> at 
> org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:56)
> at 
> org.junit.internal.runners.statements.RunAfters.invokeMethod(RunAfters.java:46)
> at 
> org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:33)
> at 
> org.apache.geode.test.junit.rules.DescribedExternalResource$1.evaluate(DescribedExternalResource.java:45)
> at 
> org.junit.rules.ExternalResource$1.evaluate(ExternalResource.java:54)
> at org.junit.rules.TestWatcher$1.evaluate(TestWatcher.java:61)
> at org.junit.runners.ParentRunner$3.evaluate(ParentRunner.java:306)
> at 
> org.junit.runners.BlockJUnit4ClassRunner$1.evaluate(BlockJUnit4ClassRunner.java:100)
> at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:366)
> at 
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:103)
> at 
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:63)
> at org.junit.runners.ParentRunner$4.run(ParentRunner.java:331)
> at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:79)
> at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:329)
> at org.junit.runners.ParentRunner.access$100(ParentRunner.java:66)
> at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:293)
> at org.junit.runners.ParentRunner.run(ParentRunner.java:413)
> at org.junit.runners.Suite.runChild(Suite.java:128)
> at org.junit.runners.Suite.runChild(Suite.java:27)
> at org.junit.runners.ParentRunner$4.run(ParentRunner.java:331)
> at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:79)
> at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:329)
> at org.junit.runners.ParentRunner.access$100(ParentRunner.java:66)
> at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:293)
> at org.junit.runners.ParentRunner$3.evaluate(ParentRunner.java:306)
> at org.junit.runners.ParentRunner.run(ParentRunner.java:413)
> at org.junit.runner.JUnitCore.run(JUnitCore.java:137)
> at org.junit.runner.JUnitCore.run(JUnitCore.java:115)
> at 
> org.junit.vintage.engine.execution.RunnerExecutor.execute(RunnerExecutor.java:42)
> at 
> org.junit.vintage.engine.VintageTestEngine.executeAllChildren(VintageTestEngine.java:80)
> at 
> org.junit.vintage.engine.VintageTestEngine.execute(VintageTestEngine.java:72)
> at 
> 

[jira] [Commented] (GEODE-7183) CI Failure: ClientServerFunctionExecutionDUnitTest > testServerExecution_SocketTimeOut_WithoutRegister[ExecuteFunctionById] failed with AssertionError

2022-08-02 Thread Geet Rawat (Jira)


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

Geet Rawat commented on GEODE-7183:
---

Failed again: 
https://concourse.gemfire-ci.info/teams/support-versions/pipelines/gemfire-support-9-15-main/jobs/distributed-test-openjdk8/builds/5

> CI Failure: ClientServerFunctionExecutionDUnitTest > 
> testServerExecution_SocketTimeOut_WithoutRegister[ExecuteFunctionById] failed 
> with AssertionError
> --
>
> Key: GEODE-7183
> URL: https://issues.apache.org/jira/browse/GEODE-7183
> Project: Geode
>  Issue Type: Bug
>  Components: functions
>Reporter: Barrett Oglesby
>Priority: Major
>
> {noformat}
> org.apache.geode.internal.cache.execute.ClientServerFunctionExecutionDUnitTest
>  > testServerExecution_SocketTimeOut_WithoutRegister[ExecuteFunctionById] 
> FAILED
> org.apache.geode.test.dunit.RMIException: While invoking 
> org.apache.geode.internal.cache.execute.ClientServerFunctionExecutionDUnitTest$$Lambda$68/1900027546.run
>  in VM 3 running on Host 6c6dc0c2627c with 4 VMs
> at org.apache.geode.test.dunit.VM.executeMethodOnObject(VM.java:579)
> at org.apache.geode.test.dunit.VM.invoke(VM.java:406)
> at 
> org.apache.geode.internal.cache.execute.ClientServerFunctionExecutionDUnitTest.testServerExecution_SocketTimeOut_WithoutRegister(ClientServerFunctionExecutionDUnitTest.java:339)
> Caused by:
> java.lang.AssertionError: Test failed after the execute operation
> at org.junit.Assert.fail(Assert.java:88)
> at 
> org.apache.geode.internal.cache.execute.ClientServerFunctionExecutionDUnitTest.allServerExecution(ClientServerFunctionExecutionDUnitTest.java:891)
> at 
> org.apache.geode.internal.cache.execute.ClientServerFunctionExecutionDUnitTest.lambda$testServerExecution_SocketTimeOut_WithoutRegister$bb17a952$2(ClientServerFunctionExecutionDUnitTest.java:339)
> {noformat}
> The test logs this exception right before the failure:
> {noformat}
> [vm3] [info 2019/09/09 18:00:10.793 GMT RMI TCP 
> Connection(26)-172.17.0.19 tid=0xb1] Exception : 
> [vm3] org.apache.geode.cache.client.ServerConnectivityException: Pool 
> unexpected SocketException connection=Pooled Connection to 
> 6c6dc0c2627c:25980: Connection[DESTROYED]). Server unreachable: could not 
> connect after 1 attempts
> [vm3] at 
> org.apache.geode.cache.client.internal.OpExecutorImpl.handleException(OpExecutorImpl.java:659)
> [vm3] at 
> org.apache.geode.cache.client.internal.OpExecutorImpl.handleException(OpExecutorImpl.java:501)
> [vm3] at 
> org.apache.geode.cache.client.internal.OpExecutorImpl.executeOnServer(OpExecutorImpl.java:331)
> [vm3] at 
> org.apache.geode.cache.client.internal.OpExecutorImpl.executeOn(OpExecutorImpl.java:300)
> [vm3] at 
> org.apache.geode.cache.client.internal.PoolImpl.executeOn(PoolImpl.java:814)
> [vm3] at 
> org.apache.geode.cache.client.internal.SingleHopOperationCallable.call(SingleHopOperationCallable.java:52)
> [vm3] at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> [vm3] at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> [vm3] at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> [vm3] at java.lang.Thread.run(Thread.java:748)
> [vm3] Caused by: java.net.SocketException: Socket is closed
> [vm3] at java.net.Socket.setSoTimeout(Socket.java:1137)
> [vm3] at 
> org.apache.geode.cache.client.internal.AbstractOpWithTimeout.attempt(AbstractOpWithTimeout.java:48)
> [vm3] at 
> org.apache.geode.cache.client.internal.ConnectionImpl.execute(ConnectionImpl.java:263)
> [vm3] at 
> org.apache.geode.cache.client.internal.pooling.PooledConnection.execute(PooledConnection.java:353)
> [vm3] at 
> org.apache.geode.cache.client.internal.OpExecutorImpl.executeWithPossibleReAuthentication(OpExecutorImpl.java:750)
> [vm3] at 
> org.apache.geode.cache.client.internal.OpExecutorImpl.executeOnServer(OpExecutorImpl.java:329)
> [vm3] ... 7 more
> {noformat}
> https://concourse.gemfire-ci.info/teams/main/pipelines/gemfire-develop-main/jobs/DistributedTestOpenJDK8/builds/952
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=  Test Results URI 
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
> gs://gemfire-test-artifacts/builds/gemfire-develop-main/9.10.0-build.0101/test-results/distributedTest/1568054303/
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
> Test report artifacts from this job are available at:
> 

[jira] [Commented] (GEODE-10404) Fix compilation for Java 11

2022-08-02 Thread ASF GitHub Bot (Jira)


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

ASF GitHub Bot commented on GEODE-10404:


gaussianrecurrence opened a new pull request, #980:
URL: https://github.com/apache/geode-native/pull/980

- After merging #973, javaobject compilation was broken for Java 11.
  The build passed since packer images uses Java 8, but as docker build
  images uses Java 11, compilation is failing there.
- Root cause of the compilation issue is the difference in UTF-8 string
  handling between Java 8 and Java 11.
- So, the issue was fixed by using unicode hexcode codepoint
  characters, rather than the actual codepoint.




> Fix compilation for Java 11
> ---
>
> Key: GEODE-10404
> URL: https://issues.apache.org/jira/browse/GEODE-10404
> Project: Geode
>  Issue Type: Bug
>  Components: native client
>Reporter: Mario Salazar de Torres
>Assignee: Mario Salazar de Torres
>Priority: Major
>  Labels: needsTriage
>
> It seems that after merging 
> [#973|https://github.com/apache/geode-native/pull/973], compilation with 
> Geode Native Docker build image for version 1.15.0 is broken. This is the 
> compilation error:
> {noformat}
> tests/javaobject/ComparePdxInstanceFunction.java:42: error: unmappable 
> character (0xAC) for encoding US-ASCII
> pdxInstanceFactory.writeString("utfHugeField", longString + "???");
> {noformat}
> As it seems, the latest docker image is using Java 11, which handles UTF-8 
> strings in a different way to Java 8, so that's why compilation is working 
> with packer images and not with Docker build image.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)


[jira] [Updated] (GEODE-10404) Fix compilation for Java 11

2022-08-02 Thread ASF GitHub Bot (Jira)


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

ASF GitHub Bot updated GEODE-10404:
---
Labels: needsTriage pull-request-available  (was: needsTriage)

> Fix compilation for Java 11
> ---
>
> Key: GEODE-10404
> URL: https://issues.apache.org/jira/browse/GEODE-10404
> Project: Geode
>  Issue Type: Bug
>  Components: native client
>Reporter: Mario Salazar de Torres
>Assignee: Mario Salazar de Torres
>Priority: Major
>  Labels: needsTriage, pull-request-available
>
> It seems that after merging 
> [#973|https://github.com/apache/geode-native/pull/973], compilation with 
> Geode Native Docker build image for version 1.15.0 is broken. This is the 
> compilation error:
> {noformat}
> tests/javaobject/ComparePdxInstanceFunction.java:42: error: unmappable 
> character (0xAC) for encoding US-ASCII
> pdxInstanceFactory.writeString("utfHugeField", longString + "???");
> {noformat}
> As it seems, the latest docker image is using Java 11, which handles UTF-8 
> strings in a different way to Java 8, so that's why compilation is working 
> with packer images and not with Docker build image.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)


[jira] [Updated] (GEODE-10404) Fix compilation for Java 11

2022-08-02 Thread Mario Salazar de Torres (Jira)


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

Mario Salazar de Torres updated GEODE-10404:

Description: 
It seems that after merging 
[#973|https://github.com/apache/geode-native/pull/973], compilation with Geode 
Native Docker build image for version 1.15.0 is broken. This is the compilation 
error:

{noformat}
tests/javaobject/ComparePdxInstanceFunction.java:42: error: unmappable 
character (0xAC) for encoding US-ASCII
pdxInstanceFactory.writeString("utfHugeField", longString + "???");
{noformat}

As it seems, the latest docker image is using Java 11, which handles UTF-8 
strings in a different way to Java 8, so that's why compilation is working with 
packer images and not with Docker build image.

  was:
It seems that after merging #973, compilation with Geode Native Docker build 
image for version 1.15.0 is broken. This is the compilation error:

{noformat}
tests/javaobject/ComparePdxInstanceFunction.java:42: error: unmappable 
character (0xAC) for encoding US-ASCII
pdxInstanceFactory.writeString("utfHugeField", longString + "???");
{noformat}

As it seems, the latest docker image is using Java 11, which handles UTF-8 
strings in a different way to Java 8, so that's why compilation is working with 
packer images and not with Docker build image.


> Fix compilation for Java 11
> ---
>
> Key: GEODE-10404
> URL: https://issues.apache.org/jira/browse/GEODE-10404
> Project: Geode
>  Issue Type: Bug
>  Components: native client
>Reporter: Mario Salazar de Torres
>Assignee: Mario Salazar de Torres
>Priority: Major
>  Labels: needsTriage
>
> It seems that after merging 
> [#973|https://github.com/apache/geode-native/pull/973], compilation with 
> Geode Native Docker build image for version 1.15.0 is broken. This is the 
> compilation error:
> {noformat}
> tests/javaobject/ComparePdxInstanceFunction.java:42: error: unmappable 
> character (0xAC) for encoding US-ASCII
> pdxInstanceFactory.writeString("utfHugeField", longString + "???");
> {noformat}
> As it seems, the latest docker image is using Java 11, which handles UTF-8 
> strings in a different way to Java 8, so that's why compilation is working 
> with packer images and not with Docker build image.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)


[jira] [Created] (GEODE-10404) Fix compilation for Java 11

2022-08-02 Thread Mario Salazar de Torres (Jira)
Mario Salazar de Torres created GEODE-10404:
---

 Summary: Fix compilation for Java 11
 Key: GEODE-10404
 URL: https://issues.apache.org/jira/browse/GEODE-10404
 Project: Geode
  Issue Type: Bug
  Components: native client
Reporter: Mario Salazar de Torres


It seems that after merging #973, compilation with Geode Native Docker build 
image for version 1.15.0 is broken. This is the compilation error:

{noformat}
tests/javaobject/ComparePdxInstanceFunction.java:42: error: unmappable 
character (0xAC) for encoding US-ASCII
pdxInstanceFactory.writeString("utfHugeField", longString + "???");
{noformat}

As it seems, the latest docker image is using Java 11, which handles UTF-8 
strings in a different way to Java 8, so that's why compilation is working with 
packer images and not with Docker build image.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)


[jira] [Assigned] (GEODE-10404) Fix compilation for Java 11

2022-08-02 Thread Mario Salazar de Torres (Jira)


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

Mario Salazar de Torres reassigned GEODE-10404:
---

Assignee: Mario Salazar de Torres

> Fix compilation for Java 11
> ---
>
> Key: GEODE-10404
> URL: https://issues.apache.org/jira/browse/GEODE-10404
> Project: Geode
>  Issue Type: Bug
>  Components: native client
>Reporter: Mario Salazar de Torres
>Assignee: Mario Salazar de Torres
>Priority: Major
>  Labels: needsTriage
>
> It seems that after merging #973, compilation with Geode Native Docker build 
> image for version 1.15.0 is broken. This is the compilation error:
> {noformat}
> tests/javaobject/ComparePdxInstanceFunction.java:42: error: unmappable 
> character (0xAC) for encoding US-ASCII
> pdxInstanceFactory.writeString("utfHugeField", longString + "???");
> {noformat}
> As it seems, the latest docker image is using Java 11, which handles UTF-8 
> strings in a different way to Java 8, so that's why compilation is working 
> with packer images and not with Docker build image.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)


[jira] [Updated] (GEODE-10404) Fix compilation for Java 11

2022-08-02 Thread Alexander Murmann (Jira)


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

Alexander Murmann updated GEODE-10404:
--
Labels: needsTriage  (was: )

> Fix compilation for Java 11
> ---
>
> Key: GEODE-10404
> URL: https://issues.apache.org/jira/browse/GEODE-10404
> Project: Geode
>  Issue Type: Bug
>  Components: native client
>Reporter: Mario Salazar de Torres
>Priority: Major
>  Labels: needsTriage
>
> It seems that after merging #973, compilation with Geode Native Docker build 
> image for version 1.15.0 is broken. This is the compilation error:
> {noformat}
> tests/javaobject/ComparePdxInstanceFunction.java:42: error: unmappable 
> character (0xAC) for encoding US-ASCII
> pdxInstanceFactory.writeString("utfHugeField", longString + "???");
> {noformat}
> As it seems, the latest docker image is using Java 11, which handles UTF-8 
> strings in a different way to Java 8, so that's why compilation is working 
> with packer images and not with Docker build image.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)