[jira] [Commented] (GEODE-4497) Command help create gateway-sender returns error if window size is 80 columns wide
[
https://issues.apache.org/jira/browse/GEODE-4497?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16403285#comment-16403285
]
ASF subversion and git services commented on GEODE-4497:
Commit c74a83f4ca76c1b3cc45f3545876e967413c7296 in geode's branch
refs/heads/develop from [~jinmeiliao]
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=c74a83f ]
GEODE-4497: fix Gfsh text wrapping error
> Command help create gateway-sender returns error if window size is 80 columns
> wide
> --
>
> Key: GEODE-4497
> URL: https://issues.apache.org/jira/browse/GEODE-4497
> Project: Geode
> Issue Type: Bug
> Components: gfsh
>Reporter: Barbara Pruijn
>Priority: Major
> Labels: pull-request-available
> Time Spent: 10m
> Remaining Estimate: 0h
>
> If you use the standard window size (25 rows; 80 columns) and run the
> following command in gfsh:
> {code}help create gateway-sender{code}
> you get the following error:
> {noformat}
> gfsh>help create gateway-sender
> [error 2018/02/01 14:35:22.359 PST tid=0x20] Could not
> execute "help create gateway-sender".
> java.lang.StringIndexOutOfBoundsException: String index out of range: -1
> at java.lang.String.substring(String.java:1967)
> at
> org.apache.geode.management.internal.cli.shell.Gfsh.wrapText(Gfsh.java:418)
> at
> org.apache.geode.management.internal.cli.help.HelpBlock.toString(HelpBlock.java:79)
> at
> org.apache.geode.management.internal.cli.help.HelpBlock.toString(HelpBlock.java:83)
> at
> org.apache.geode.management.internal.cli.help.HelpBlock.toString(HelpBlock.java:83)
> at
> org.apache.geode.management.internal.cli.help.HelpBlock.toString(HelpBlock.java:83)
> at
> org.apache.geode.management.internal.cli.help.Helper.getHelp(Helper.java:145)
> at
> org.apache.geode.management.internal.cli.CommandManager.obtainHelp(CommandManager.java:310)
> at
> org.apache.geode.management.internal.cli.commands.GfshHelpCommand.obtainHelp(GfshHelpCommand.java:42)
> 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
> org.springframework.util.ReflectionUtils.invokeMethod(ReflectionUtils.java:216)
> at
> org.apache.geode.management.internal.cli.remote.CommandExecutor.invokeCommand(CommandExecutor.java:97)
> at
> org.apache.geode.management.internal.cli.remote.CommandExecutor.execute(CommandExecutor.java:45)
> at
> org.apache.geode.management.internal.cli.remote.CommandExecutor.execute(CommandExecutor.java:39)
> at
> org.apache.geode.management.internal.cli.shell.GfshExecutionStrategy.execute(GfshExecutionStrategy.java:81)
> at
> org.springframework.shell.core.AbstractShell.executeCommand(AbstractShell.java:134)
> at
> org.apache.geode.management.internal.cli.shell.Gfsh.promptLoop(Gfsh.java:1008)
> at org.springframework.shell.core.JLineShell.run(JLineShell.java:179)
> at java.lang.Thread.run(Thread.java:748)
> Could not process command due to error. Error while processing command create gateway-sender> Reason : String index out of range: -1
> {noformat}
> If you make the window wider and run the command again, it runs fine.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (GEODE-4169) Update ACE to 6.4.7
[ https://issues.apache.org/jira/browse/GEODE-4169?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jacob S. Barrett resolved GEODE-4169. - Resolution: Fixed > Update ACE to 6.4.7 > --- > > Key: GEODE-4169 > URL: https://issues.apache.org/jira/browse/GEODE-4169 > Project: Geode > Issue Type: Task > Components: native client >Reporter: Jacob S. Barrett >Assignee: Jacob S. Barrett >Priority: Major > Labels: pull-request-available > Time Spent: 20m > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-4169) Update ACE to 6.4.7
[ https://issues.apache.org/jira/browse/GEODE-4169?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16403238#comment-16403238 ] ASF subversion and git services commented on GEODE-4169: Commit ab695094ba35e954837f54288b37a6194804ed99 in geode-native's branch refs/heads/develop from Jacob Barrett [ https://gitbox.apache.org/repos/asf?p=geode-native.git;h=ab69509 ] GEODE-4169: Updates ACE to 6.4.7 (#241) > Update ACE to 6.4.7 > --- > > Key: GEODE-4169 > URL: https://issues.apache.org/jira/browse/GEODE-4169 > Project: Geode > Issue Type: Task > Components: native client >Reporter: Jacob S. Barrett >Assignee: Jacob S. Barrett >Priority: Major > Labels: pull-request-available > Time Spent: 20m > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-4880) Ignore Pulse UI acceptance tests that are flaky
[ https://issues.apache.org/jira/browse/GEODE-4880?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16403163#comment-16403163 ] ASF subversion and git services commented on GEODE-4880: Commit bf079a17850f32b7a3ae3260eb173a5028f9d68c in geode's branch refs/heads/develop from [~sai.boorlaga...@gmail.com] [ https://gitbox.apache.org/repos/asf?p=geode.git;h=bf079a1 ] GEODE-4880: Ignore Pulse UI acceptance tests that are flaky (#1635) > Ignore Pulse UI acceptance tests that are flaky > --- > > Key: GEODE-4880 > URL: https://issues.apache.org/jira/browse/GEODE-4880 > Project: Geode > Issue Type: Test > Components: pulse >Reporter: Sai Boorlagadda >Assignee: Sai Boorlagadda >Priority: Major > Labels: pull-request-available > Time Spent: 20m > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (GEODE-4882) AnalyzeConnectorsSerializablesJUnitTest failing intermittently with CacheClosedException
Darrel Schneider created GEODE-4882:
---
Summary: AnalyzeConnectorsSerializablesJUnitTest failing
intermittently with CacheClosedException
Key: GEODE-4882
URL: https://issues.apache.org/jira/browse/GEODE-4882
Project: Geode
Issue Type: Bug
Components: extensions, regions
Reporter: Darrel Schneider
The following failure has happened twice this week but not in a row. So this
test is intermittently failing.
{noformat}
:geode-connectors:integrationTest
org.apache.geode.codeAnalysis.AnalyzeConnectorsSerializablesJUnitTest >
testSanctionedClassesExistAndDoDeserialize FAILED
org.apache.geode.cache.CacheClosedException: Could not PDX serialize because
the cache was closed
{noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (GEODE-4875) JdbcLoader will not always find an existing pdx field type if it is not all lower case
[ https://issues.apache.org/jira/browse/GEODE-4875?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated GEODE-4875: -- Labels: pull-request-available (was: ) > JdbcLoader will not always find an existing pdx field type if it is not all > lower case > -- > > Key: GEODE-4875 > URL: https://issues.apache.org/jira/browse/GEODE-4875 > Project: Geode > Issue Type: Bug > Components: extensions, regions >Affects Versions: 1.6.0 >Reporter: Darrel Schneider >Priority: Major > Labels: pull-request-available > > When doing a read using the JdbcLoader, if the region mapping has a > pdx-class-name and does not have a pdx-field to column-name mapping, then it > will only find the existing pdx field type if the field name is all lower > case. > You will see a JdbcConnectorException with this message when you hit this bug: > "Could not find PdxType for field " + fieldName + ". Add class " + > pdxClassName + " with " + fieldName + " to pdx registry." -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-4875) JdbcLoader will not always find an existing pdx field type if it is not all lower case
[ https://issues.apache.org/jira/browse/GEODE-4875?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16403139#comment-16403139 ] ASF subversion and git services commented on GEODE-4875: Commit 6073a15b6cc33b93ee0fb40c1aa880d2b7af8d61 in geode's branch refs/heads/develop from Sai Boorlagadda [ https://gitbox.apache.org/repos/asf?p=geode.git;h=6073a15 ] GEODE-4875: make a public ClusterConfigurationService interface * rename the current ClusterConfigurationService to InternalClusterConfigurationService * make a public interface and have the internal implementation implements it. > JdbcLoader will not always find an existing pdx field type if it is not all > lower case > -- > > Key: GEODE-4875 > URL: https://issues.apache.org/jira/browse/GEODE-4875 > Project: Geode > Issue Type: Bug > Components: extensions, regions >Affects Versions: 1.6.0 >Reporter: Darrel Schneider >Priority: Major > > When doing a read using the JdbcLoader, if the region mapping has a > pdx-class-name and does not have a pdx-field to column-name mapping, then it > will only find the existing pdx field type if the field name is all lower > case. > You will see a JdbcConnectorException with this message when you hit this bug: > "Could not find PdxType for field " + fieldName + ". Add class " + > pdxClassName + " with " + fieldName + " to pdx registry." -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (GEODE-4833) JdbcWriter and JdbcAsyncWriter may fail to write null fields to database
[ https://issues.apache.org/jira/browse/GEODE-4833?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated GEODE-4833: -- Labels: pull-request-available (was: ) > JdbcWriter and JdbcAsyncWriter may fail to write null fields to database > > > Key: GEODE-4833 > URL: https://issues.apache.org/jira/browse/GEODE-4833 > Project: Geode > Issue Type: Bug > Components: extensions, regions >Affects Versions: 1.4.0 >Reporter: Darrel Schneider >Assignee: Darrel Schneider >Priority: Major > Labels: pull-request-available > > Both JdbcWriter and JdbcAsyncWriter end up calling the JDBC method > PreparedStatement.setObject with a value of "null" if the pdx field contains > "null". > This will work with jdbc drivers that support sending "non-typed Null" to the > backend database. > But some drivers do not support this and these puts will fail with a > SQLException. > For portability the jdbc connector should be changed to not pass "null" to > setObject without a type. > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (GEODE-1139) CI failure: ShorteningExpirationTimeRegressionTest.testPut
[ https://issues.apache.org/jira/browse/GEODE-1139?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kirk Lund updated GEODE-1139: - Summary: CI failure: ShorteningExpirationTimeRegressionTest.testPut (was: CI failure: Bug44418JUnitTest.testPut) > CI failure: ShorteningExpirationTimeRegressionTest.testPut > -- > > Key: GEODE-1139 > URL: https://issues.apache.org/jira/browse/GEODE-1139 > Project: Geode > Issue Type: Bug > Components: expiration >Reporter: Bruce Schuchardt >Priority: Major > Labels: CI, Flaky > > This test failed in revision 274f67cae769fbba1f6e63ff866f7f761b9a4229 > java.lang.AssertionError: 1 ms expire did not happen after waiting 1000 ms > at org.junit.Assert.fail(Assert.java:88) > at > com.gemstone.gemfire.cache30.Bug44418JUnitTest.testPut(Bug44418JUnitTest.java:96) > 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:497) > at > org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50) > at > org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12) > at > org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47) > at > org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17) > at > org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26) > at > org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27) > at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325) > at > org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78) > at > org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57) > at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290) > at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71) > at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288) > at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58) > at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268) > at org.junit.runners.ParentRunner.run(ParentRunner.java:363) > at > org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecuter.runTestClass(JUnitTestClassExecuter.java:105) > at > org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecuter.execute(JUnitTestClassExecuter.java:56) > at > org.gradle.api.internal.tasks.testing.junit.JUnitTestClassProcessor.processTestClass(JUnitTestClassProcessor.java:64) > at > org.gradle.api.internal.tasks.testing.SuiteTestClassProcessor.processTestClass(SuiteTestClassProcessor.java:50) > 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:497) > at > org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:35) > at > org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:24) > at > org.gradle.messaging.dispatch.ContextClassLoaderDispatch.dispatch(ContextClassLoaderDispatch.java:32) > at > org.gradle.messaging.dispatch.ProxyDispatchAdapter$DispatchingInvocationHandler.invoke(ProxyDispatchAdapter.java:93) > at com.sun.proxy.$Proxy2.processTestClass(Unknown Source) > at > org.gradle.api.internal.tasks.testing.worker.TestWorker.processTestClass(TestWorker.java:106) > 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:497) > at > org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:35) > at > org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:24) > at > org.gradle.messaging.remote.internal.hub.MessageHub$Handler.run(MessageHub.java:360) > at > org.gradle.internal.concurrent.ExecutorPolicy$CatchAndRecordFailures.onExecute(ExecutorPolicy.java:54) > at > org.gradle.internal.concurrent.StoppableExecutorImpl$1.run(StoppableExecutorImpl.java:40) > at >
[jira] [Updated] (GEODE-924) CI failure: ShorteningExpirationTimeRegressionTest.testGet
[
https://issues.apache.org/jira/browse/GEODE-924?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kirk Lund updated GEODE-924:
Summary: CI failure: ShorteningExpirationTimeRegressionTest.testGet (was:
CI failure: Bug44418JUnitTest.testGet)
> CI failure: ShorteningExpirationTimeRegressionTest.testGet
> --
>
> Key: GEODE-924
> URL: https://issues.apache.org/jira/browse/GEODE-924
> Project: Geode
> Issue Type: Bug
> Components: expiration
>Reporter: Sai Boorlagadda
>Priority: Major
> Labels: CI, Flaky
>
> {noformat}
> Error Message
> java.lang.AssertionError: 1 ms expire did not happen after waiting 1000 ms
> Stacktrace
> java.lang.AssertionError: 1 ms expire did not happen after waiting 1000 ms
> at org.junit.Assert.fail(Assert.java:88)
> at
> com.gemstone.gemfire.cache30.Bug44418JUnitTest.testGet(Bug44418JUnitTest.java:145)
> 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:497)
> at
> org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
> at
> org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
> at
> org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
> at
> org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
> at
> org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
> at
> org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
> at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325)
> at
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78)
> at
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57)
> at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
> at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
> at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
> at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
> at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
> at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
> at
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecuter.runTestClass(JUnitTestClassExecuter.java:105)
> at
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecuter.execute(JUnitTestClassExecuter.java:56)
> at
> org.gradle.api.internal.tasks.testing.junit.JUnitTestClassProcessor.processTestClass(JUnitTestClassProcessor.java:64)
> at
> org.gradle.api.internal.tasks.testing.SuiteTestClassProcessor.processTestClass(SuiteTestClassProcessor.java:50)
> 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:497)
> at
> org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:35)
> at
> org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:24)
> at
> org.gradle.messaging.dispatch.ContextClassLoaderDispatch.dispatch(ContextClassLoaderDispatch.java:32)
> at
> org.gradle.messaging.dispatch.ProxyDispatchAdapter$DispatchingInvocationHandler.invoke(ProxyDispatchAdapter.java:93)
> at com.sun.proxy.$Proxy2.processTestClass(Unknown Source)
> at
> org.gradle.api.internal.tasks.testing.worker.TestWorker.processTestClass(TestWorker.java:106)
> 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:497)
> at
> org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:35)
> at
> org.gradle.messaging.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:24)
> at
> org.gradle.messaging.remote.internal.hub.MessageHub$Handler.run(MessageHub.java:360)
> at
> org.gradle.internal.concurrent.ExecutorPolicy$CatchAndRecordFailures.onExecute(ExecutorPolicy.java:54)
> at
> org.gradle.internal.concurrent.StoppableExecutorImpl$1.run(StoppableExecutorImpl.java:40)
> at
>
[jira] [Created] (GEODE-4881) handle concurrent lucene indexing (after region created) with rebalance
Shelley Lynn Hughes-Godfrey created GEODE-4881:
--
Summary: handle concurrent lucene indexing (after region created)
with rebalance
Key: GEODE-4881
URL: https://issues.apache.org/jira/browse/GEODE-4881
Project: Geode
Issue Type: New Feature
Components: lucene
Reporter: Shelley Lynn Hughes-Godfrey
{noformat}
While adding a Lucene index to a region with data, if a rebalance is triggered
during re-indexing, the index should complete successfully and match the region
data.
If I add a Lucene index while a rebalance is in progress, the index should
successfully complete and match the region data. (*)
(*) Note: It may be acceptable to detect a rebalance in progress before
starting and wait for it to finish before adding the Lucene index.
{noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (GEODE-3875) gfsh command to create jndi binding
[
https://issues.apache.org/jira/browse/GEODE-3875?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16403080#comment-16403080
]
ASF subversion and git services commented on GEODE-3875:
Commit ad77bde78300797b6dd26bfcae9e0ce8ad6f1ad5 in geode's branch
refs/heads/develop from [~jinmeiliao]
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=ad77bde ]
GEODE-4384/3875: refactor create/destroy jndi binding commands to use
CacheConfig objects (#1627)
* GEODE-3875: refactor create jndi binding
* GEODE-4384: refactor destroy jndi binding
* refactored xml manipulation using jaxb
* Eliminate the need for RegionElement
> gfsh command to create jndi binding
> ---
>
> Key: GEODE-3875
> URL: https://issues.apache.org/jira/browse/GEODE-3875
> Project: Geode
> Issue Type: Sub-task
> Components: docs, gfsh
>Reporter: Swapnil Bawaskar
>Priority: Major
> Labels: pull-request-available
> Fix For: 1.5.0
>
> Time Spent: 4h 50m
> Remaining Estimate: 0h
>
> In cache.xml user can specify jndi binding like so:
> {code:java}
>
> jdbc-driver-class="org.postgresql.Driver" user-name="gpadmin"
> password="changeme"
> connection-url="jdbc:postgresql://localhost:5432/gemfire_db">
>
>
> {code}
> A user should be able to create a datasource using the gfsh command {{create
> jndi-binding }}
> Then a datasource will be created with the supplied options and the binding
> will be created without the user having to restart the existing server(s)
> Please look at Geode's schema for a list of attributes that can be set:
> [https://github.com/apache/geode-site/blob/master/website/content/schema/cache/cache-1.0.xsd#L1331]
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (GEODE-4384) gfsh command to destroy jndi binding
[
https://issues.apache.org/jira/browse/GEODE-4384?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16403081#comment-16403081
]
ASF subversion and git services commented on GEODE-4384:
Commit ad77bde78300797b6dd26bfcae9e0ce8ad6f1ad5 in geode's branch
refs/heads/develop from [~jinmeiliao]
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=ad77bde ]
GEODE-4384/3875: refactor create/destroy jndi binding commands to use
CacheConfig objects (#1627)
* GEODE-3875: refactor create jndi binding
* GEODE-4384: refactor destroy jndi binding
* refactored xml manipulation using jaxb
* Eliminate the need for RegionElement
> gfsh command to destroy jndi binding
>
>
> Key: GEODE-4384
> URL: https://issues.apache.org/jira/browse/GEODE-4384
> Project: Geode
> Issue Type: Sub-task
> Components: docs, gfsh
>Reporter: Barbara Pruijn
>Priority: Major
> Labels: pull-request-available
> Fix For: 1.6.0
>
> Time Spent: 3h 50m
> Remaining Estimate: 0h
>
> In cache.xml user can specify jndi binding like so:
> {code:java}
>
> jdbc-driver-class="org.postgresql.Driver" user-name="gpadmin"
> password="changeme"
> connection-url="jdbc:postgresql://localhost:5432/gemfire_db">
>
>
> {code}
> A user should be able to delete a datasource using the gfsh command {{destroy
> jndi-binding --name=jndi-binding-name}}
> Then the datasource will be deleted from the cluster and the binding will be
> deleted without the user having to restart the existing server(s).
> Please look at Geode's schema for a list of attributes that can be set:
> [https://github.com/apache/geode-site/blob/master/website/content/schema/cache/cache-1.0.xsd#L1331]
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (GEODE-4384) gfsh command to destroy jndi binding
[
https://issues.apache.org/jira/browse/GEODE-4384?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16403079#comment-16403079
]
ASF subversion and git services commented on GEODE-4384:
Commit ad77bde78300797b6dd26bfcae9e0ce8ad6f1ad5 in geode's branch
refs/heads/develop from [~jinmeiliao]
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=ad77bde ]
GEODE-4384/3875: refactor create/destroy jndi binding commands to use
CacheConfig objects (#1627)
* GEODE-3875: refactor create jndi binding
* GEODE-4384: refactor destroy jndi binding
* refactored xml manipulation using jaxb
* Eliminate the need for RegionElement
> gfsh command to destroy jndi binding
>
>
> Key: GEODE-4384
> URL: https://issues.apache.org/jira/browse/GEODE-4384
> Project: Geode
> Issue Type: Sub-task
> Components: docs, gfsh
>Reporter: Barbara Pruijn
>Priority: Major
> Labels: pull-request-available
> Fix For: 1.6.0
>
> Time Spent: 3h 50m
> Remaining Estimate: 0h
>
> In cache.xml user can specify jndi binding like so:
> {code:java}
>
> jdbc-driver-class="org.postgresql.Driver" user-name="gpadmin"
> password="changeme"
> connection-url="jdbc:postgresql://localhost:5432/gemfire_db">
>
>
> {code}
> A user should be able to delete a datasource using the gfsh command {{destroy
> jndi-binding --name=jndi-binding-name}}
> Then the datasource will be deleted from the cluster and the binding will be
> deleted without the user having to restart the existing server(s).
> Please look at Geode's schema for a list of attributes that can be set:
> [https://github.com/apache/geode-site/blob/master/website/content/schema/cache/cache-1.0.xsd#L1331]
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (GEODE-4846) Javadocs on ExecutorServiceRule are incorrect
[ https://issues.apache.org/jira/browse/GEODE-4846?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kirk Lund resolved GEODE-4846. -- Resolution: Fixed Fix Version/s: 1.5.0 > Javadocs on ExecutorServiceRule are incorrect > - > > Key: GEODE-4846 > URL: https://issues.apache.org/jira/browse/GEODE-4846 > Project: Geode > Issue Type: Bug > Components: tests >Reporter: Kirk Lund >Assignee: Kirk Lund >Priority: Trivial > Fix For: 1.5.0 > > > The Javadocs on ExecutorServiceRule incorrectly refer to AsynchronousRule > instead of ExecutorServiceRule. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-4783) Categorize Management tests
[ https://issues.apache.org/jira/browse/GEODE-4783?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16403061#comment-16403061 ] ASF subversion and git services commented on GEODE-4783: Commit 740212207d377abef7537d30ee557473c3de08b8 in geode's branch refs/heads/develop from [~khowe] [ https://gitbox.apache.org/repos/asf?p=geode.git;h=7402122 ] GEODE-4783: Add categor annotation for Management tests (#1629) > Categorize Management tests > --- > > Key: GEODE-4783 > URL: https://issues.apache.org/jira/browse/GEODE-4783 > Project: Geode > Issue Type: Bug > Components: management >Affects Versions: 1.5.0 >Reporter: Kenneth Howe >Priority: Major > Labels: pull-request-available > Time Spent: 20m > Remaining Estimate: 0h > > Add Category annotation for management integration and distributed tests -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-4782) Categorize Gfsh tests
[ https://issues.apache.org/jira/browse/GEODE-4782?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16403060#comment-16403060 ] ASF subversion and git services commented on GEODE-4782: Commit 6e2a7540190f281b95ad0bfe5bc0db4ec00c2bbd in geode's branch refs/heads/develop from [~khowe] [ https://gitbox.apache.org/repos/asf?p=geode.git;h=6e2a754 ] GEODE-4782: Add category annotation for Gfsh tests (#1630) > Categorize Gfsh tests > - > > Key: GEODE-4782 > URL: https://issues.apache.org/jira/browse/GEODE-4782 > Project: Geode > Issue Type: Bug > Components: gfsh >Affects Versions: 1.5.0 >Reporter: Kenneth Howe >Priority: Major > Labels: pull-request-available > Time Spent: 20m > Remaining Estimate: 0h > > Add Category annotation for gfsh integration and distributed tests. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (GEODE-4871) Add key to earlyEntryEventSerialization
[ https://issues.apache.org/jira/browse/GEODE-4871?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kirk Lund updated GEODE-4871: - Summary: Add key to earlyEntryEventSerialization (was: Add EntryEvent key to earlyEntryEventSerialization) > Add key to earlyEntryEventSerialization > --- > > Key: GEODE-4871 > URL: https://issues.apache.org/jira/browse/GEODE-4871 > Project: Geode > Issue Type: Improvement > Components: regions >Reporter: Kirk Lund >Assignee: Kirk Lund >Priority: Major > > This is a follow-up to GEODE-4769 which performs early serialization of the > EntryEvent new value. We should also perform early serialization of the > EntryEvent key. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (GEODE-4789) Update system-rules dependency from 1.16.1 to 1.17.1
[ https://issues.apache.org/jira/browse/GEODE-4789?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kirk Lund resolved GEODE-4789. -- Resolution: Fixed Fix Version/s: 1.5.0 > Update system-rules dependency from 1.16.1 to 1.17.1 > > > Key: GEODE-4789 > URL: https://issues.apache.org/jira/browse/GEODE-4789 > Project: Geode > Issue Type: Improvement > Components: build, tests >Reporter: Kirk Lund >Assignee: Kirk Lund >Priority: Minor > Labels: pull-request-available > Fix For: 1.5.0 > > Time Spent: 2h 10m > Remaining Estimate: 0h > > com.github.stefanbirkner:system-rules releases are now up to 1.17.1. We > should update our dependency from 1.16.1 to 1.17.1. > System-Rules is a library of JUnit Rules used in UnitTests, IntegrationTests > and DistributedTests for controlling System properties, stdout, stderr, etc. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (GEODE-4821) RegisterInterestIntegrationTest should be categorized as DistributedTest
[ https://issues.apache.org/jira/browse/GEODE-4821?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kirk Lund resolved GEODE-4821. -- Resolution: Fixed Fix Version/s: 1.5.0 > RegisterInterestIntegrationTest should be categorized as DistributedTest > > > Key: GEODE-4821 > URL: https://issues.apache.org/jira/browse/GEODE-4821 > Project: Geode > Issue Type: Bug > Components: client queues, tests >Reporter: Kirk Lund >Assignee: Kirk Lund >Priority: Trivial > Fix For: 1.5.0 > > > ClusterStarterRule is a DistributedTest rule and launches DUnit child VMs. > RegisterInterestIntegrationTest should either change to be a DistributedTest > or change to not use ClusterStarterRule. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (GEODE-4820) Non-DistributedTests should use RestoreSystemProperties instead of DistributedRestoreSystemProperties
[ https://issues.apache.org/jira/browse/GEODE-4820?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kirk Lund resolved GEODE-4820. -- Resolution: Fixed Fix Version/s: 1.5.0 > Non-DistributedTests should use RestoreSystemProperties instead of > DistributedRestoreSystemProperties > - > > Key: GEODE-4820 > URL: https://issues.apache.org/jira/browse/GEODE-4820 > Project: Geode > Issue Type: Bug > Components: tests >Reporter: Kirk Lund >Assignee: Kirk Lund >Priority: Trivial > Fix For: 1.5.0 > > > Two IntegrationTests are using DistributedRestoreSystemProperties. These > tests should be changed to use the original RestoreSystemProperties. > * HARegionQueueJUnitTest > * BlockingHARegionQueueJUnitTest -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (GEODE-4658) Expose how much time it takes to write to disk and what is the disk store size
[
https://issues.apache.org/jira/browse/GEODE-4658?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kirk Lund updated GEODE-4658:
-
Description:
*Given* I have a persistent region with a default disk store
*When* I write data on the region
*Then* I can see 2 new metrics {{average write time to disk}} ns time and
{{size of disk store}} in bytes
h3. Documentation
Add these new metrics to the docs.
was:
*Given* I have a persistent region with a default disk store
*When* I write data on the region
*Then* I can see 2 new metrics {{average write time to disk}} ns time and
{{size of disk store}} in bytes
h3. Documentation
Add this new metric to the docs
This should be a matter of altering the ShowMetricsCommand.java
> Expose how much time it takes to write to disk and what is the disk store size
> --
>
> Key: GEODE-4658
> URL: https://issues.apache.org/jira/browse/GEODE-4658
> Project: Geode
> Issue Type: Improvement
> Components: docs, gfsh
>Reporter: Fred Krone
>Priority: Major
> Labels: starter++
>
> *Given* I have a persistent region with a default disk store
> *When* I write data on the region
> *Then* I can see 2 new metrics {{average write time to disk}} ns time and
> {{size of disk store}} in bytes
> h3. Documentation
> Add these new metrics to the docs.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (GEODE-4880) Ignore Pulse UI acceptance tests that are flaky
[ https://issues.apache.org/jira/browse/GEODE-4880?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated GEODE-4880: -- Labels: pull-request-available (was: ) > Ignore Pulse UI acceptance tests that are flaky > --- > > Key: GEODE-4880 > URL: https://issues.apache.org/jira/browse/GEODE-4880 > Project: Geode > Issue Type: Test > Components: pulse >Reporter: Sai Boorlagadda >Assignee: Sai Boorlagadda >Priority: Major > Labels: pull-request-available > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (GEODE-4880) Ignore Pulse UI acceptance tests that are flaky
[ https://issues.apache.org/jira/browse/GEODE-4880?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sai Boorlagadda reassigned GEODE-4880: -- Assignee: Sai Boorlagadda > Ignore Pulse UI acceptance tests that are flaky > --- > > Key: GEODE-4880 > URL: https://issues.apache.org/jira/browse/GEODE-4880 > Project: Geode > Issue Type: Test > Components: pulse >Reporter: Sai Boorlagadda >Assignee: Sai Boorlagadda >Priority: Major > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (GEODE-4880) Ignore Pulse UI acceptance tests that are flaky
Sai Boorlagadda created GEODE-4880: -- Summary: Ignore Pulse UI acceptance tests that are flaky Key: GEODE-4880 URL: https://issues.apache.org/jira/browse/GEODE-4880 Project: Geode Issue Type: Test Components: pulse Reporter: Sai Boorlagadda -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-4647) Add a new stat for AyncEventQueue/GatewaySender to track secondaryEventsQueueSize
[ https://issues.apache.org/jira/browse/GEODE-4647?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16402638#comment-16402638 ] ASF subversion and git services commented on GEODE-4647: Commit cf104e2235f681eb9fdca1ba8a4f8cfb3fb7b979 in geode's branch refs/heads/feature/GEODE-4647 from zhouxh [ https://gitbox.apache.org/repos/asf?p=geode.git;h=cf104e2 ] GEODE-4647: add a stats eventSecondaryQueueSizeId to track events in secondary gateway sender queue > Add a new stat for AyncEventQueue/GatewaySender to track > secondaryEventsQueueSize > - > > Key: GEODE-4647 > URL: https://issues.apache.org/jira/browse/GEODE-4647 > Project: Geode > Issue Type: Bug > Components: docs, wan >Reporter: Jason Huynh >Assignee: xiaojian zhou >Priority: Major > Labels: pull-request-available > Time Spent: 4h 20m > Remaining Estimate: 0h > > Currently we have eventsQueueSize which tells us how big the queue is based > on how many primary events are in the queue. > It would be nice to have the same type of stat for how many secondary events > are in the queue. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-4820) Non-DistributedTests should use RestoreSystemProperties instead of DistributedRestoreSystemProperties
[ https://issues.apache.org/jira/browse/GEODE-4820?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16402635#comment-16402635 ] ASF subversion and git services commented on GEODE-4820: Commit 62f83e32574a1d4300715c4ebc686e77e167c71b in geode's branch refs/heads/develop from [~apa...@the9muses.net] [ https://gitbox.apache.org/repos/asf?p=geode.git;h=62f83e3 ] GEODE-4820: use RestoreSystemProperties instead of DistributedRestoreSystemProperties Update TODO comment and minor cleanup. > Non-DistributedTests should use RestoreSystemProperties instead of > DistributedRestoreSystemProperties > - > > Key: GEODE-4820 > URL: https://issues.apache.org/jira/browse/GEODE-4820 > Project: Geode > Issue Type: Bug > Components: tests >Reporter: Kirk Lund >Assignee: Kirk Lund >Priority: Trivial > > Two IntegrationTests are using DistributedRestoreSystemProperties. These > tests should be changed to use the original RestoreSystemProperties. > * HARegionQueueJUnitTest > * BlockingHARegionQueueJUnitTest -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-4789) Update system-rules dependency from 1.16.1 to 1.17.1
[ https://issues.apache.org/jira/browse/GEODE-4789?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16402633#comment-16402633 ] ASF subversion and git services commented on GEODE-4789: Commit 886338624e7dc375521d94d0f7ef51b38b98c5dc in geode's branch refs/heads/develop from [~apa...@the9muses.net] [ https://gitbox.apache.org/repos/asf?p=geode.git;h=8863386 ] GEODE-4789: fix static usage of DistributedRestoreSystemProperties > Update system-rules dependency from 1.16.1 to 1.17.1 > > > Key: GEODE-4789 > URL: https://issues.apache.org/jira/browse/GEODE-4789 > Project: Geode > Issue Type: Improvement > Components: build, tests >Reporter: Kirk Lund >Assignee: Kirk Lund >Priority: Minor > Labels: pull-request-available > Time Spent: 2h 10m > Remaining Estimate: 0h > > com.github.stefanbirkner:system-rules releases are now up to 1.17.1. We > should update our dependency from 1.16.1 to 1.17.1. > System-Rules is a library of JUnit Rules used in UnitTests, IntegrationTests > and DistributedTests for controlling System properties, stdout, stderr, etc. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-4789) Update system-rules dependency from 1.16.1 to 1.17.1
[ https://issues.apache.org/jira/browse/GEODE-4789?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16402631#comment-16402631 ] ASF subversion and git services commented on GEODE-4789: Commit 71d1d8a29a90f98f1017cb3714151b8acc22b8c6 in geode's branch refs/heads/develop from [~apa...@the9muses.net] [ https://gitbox.apache.org/repos/asf?p=geode.git;h=71d1d8a ] GEODE-4789: add VM count constructor to ClusterStartupRule Any DUnit test that uses more than 4 VMs should always specify the total VM count via the ClusterStartupRule constructor so that "bundled" Rules such as DistributedRestoreSystemProperties which has a before that needs to know about all the VMs can be setup properly. > Update system-rules dependency from 1.16.1 to 1.17.1 > > > Key: GEODE-4789 > URL: https://issues.apache.org/jira/browse/GEODE-4789 > Project: Geode > Issue Type: Improvement > Components: build, tests >Reporter: Kirk Lund >Assignee: Kirk Lund >Priority: Minor > Labels: pull-request-available > Time Spent: 2h 10m > Remaining Estimate: 0h > > com.github.stefanbirkner:system-rules releases are now up to 1.17.1. We > should update our dependency from 1.16.1 to 1.17.1. > System-Rules is a library of JUnit Rules used in UnitTests, IntegrationTests > and DistributedTests for controlling System properties, stdout, stderr, etc. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-4821) RegisterInterestIntegrationTest should be categorized as DistributedTest
[ https://issues.apache.org/jira/browse/GEODE-4821?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16402634#comment-16402634 ] ASF subversion and git services commented on GEODE-4821: Commit 1298f765b14cd7ea1747a14b8e873f0dea9de054 in geode's branch refs/heads/develop from [~apa...@the9muses.net] [ https://gitbox.apache.org/repos/asf?p=geode.git;h=1298f76 ] GEODE-4821: rename RegisterInterestIntegrationTest as RegisterInterestDistributedTest * change category to DistributedTest * change from using old and new JUnit Assert to AssertJ > RegisterInterestIntegrationTest should be categorized as DistributedTest > > > Key: GEODE-4821 > URL: https://issues.apache.org/jira/browse/GEODE-4821 > Project: Geode > Issue Type: Bug > Components: client queues, tests >Reporter: Kirk Lund >Assignee: Kirk Lund >Priority: Trivial > > ClusterStarterRule is a DistributedTest rule and launches DUnit child VMs. > RegisterInterestIntegrationTest should either change to be a DistributedTest > or change to not use ClusterStarterRule. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-4789) Update system-rules dependency from 1.16.1 to 1.17.1
[ https://issues.apache.org/jira/browse/GEODE-4789?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16402632#comment-16402632 ] ASF subversion and git services commented on GEODE-4789: Commit 6b56b5ff6d426cc0b42372c578b2dd85d85362a0 in geode's branch refs/heads/develop from [~apa...@the9muses.net] [ https://gitbox.apache.org/repos/asf?p=geode.git;h=6b56b5f ] GEODE-4789: fixup tests that use more than 4 VMs with ClusterStarterRule Cleanup some of these tests: * change to use AssertJ * change from using Thread sleeps to Awaitility > Update system-rules dependency from 1.16.1 to 1.17.1 > > > Key: GEODE-4789 > URL: https://issues.apache.org/jira/browse/GEODE-4789 > Project: Geode > Issue Type: Improvement > Components: build, tests >Reporter: Kirk Lund >Assignee: Kirk Lund >Priority: Minor > Labels: pull-request-available > Time Spent: 2h 10m > Remaining Estimate: 0h > > com.github.stefanbirkner:system-rules releases are now up to 1.17.1. We > should update our dependency from 1.16.1 to 1.17.1. > System-Rules is a library of JUnit Rules used in UnitTests, IntegrationTests > and DistributedTests for controlling System properties, stdout, stderr, etc. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-4845) FieldSerializationUtils should be package-private
[ https://issues.apache.org/jira/browse/GEODE-4845?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16402629#comment-16402629 ] ASF subversion and git services commented on GEODE-4845: Commit f8bab2a2d451be944baa802814e9f05e0807ed8b in geode's branch refs/heads/develop from [~apa...@the9muses.net] [ https://gitbox.apache.org/repos/asf?p=geode.git;h=f8bab2a ] GEODE-4845: make FieldSerializationUtils package-private > FieldSerializationUtils should be package-private > - > > Key: GEODE-4845 > URL: https://issues.apache.org/jira/browse/GEODE-4845 > Project: Geode > Issue Type: Improvement > Components: tests >Reporter: Kirk Lund >Assignee: Kirk Lund >Priority: Major > > FieldSerializationUtils is currently public but should be package-private. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-4789) Update system-rules dependency from 1.16.1 to 1.17.1
[ https://issues.apache.org/jira/browse/GEODE-4789?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16402630#comment-16402630 ] ASF subversion and git services commented on GEODE-4789: Commit ae25c7b8f8db29f498c9c064a340d39200639209 in geode's branch refs/heads/develop from [~apa...@the9muses.net] [ https://gitbox.apache.org/repos/asf?p=geode.git;h=ae25c7b ] GEODE-4789: upgrade system-rules from 1.16.1 to 1.17.1 Make DistributedRestoreSystemProperties delegate to RestoreSystemProperties > Update system-rules dependency from 1.16.1 to 1.17.1 > > > Key: GEODE-4789 > URL: https://issues.apache.org/jira/browse/GEODE-4789 > Project: Geode > Issue Type: Improvement > Components: build, tests >Reporter: Kirk Lund >Assignee: Kirk Lund >Priority: Minor > Labels: pull-request-available > Time Spent: 2h 10m > Remaining Estimate: 0h > > com.github.stefanbirkner:system-rules releases are now up to 1.17.1. We > should update our dependency from 1.16.1 to 1.17.1. > System-Rules is a library of JUnit Rules used in UnitTests, IntegrationTests > and DistributedTests for controlling System properties, stdout, stderr, etc. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-4846) Javadocs on ExecutorServiceRule are incorrect
[ https://issues.apache.org/jira/browse/GEODE-4846?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16402628#comment-16402628 ] ASF subversion and git services commented on GEODE-4846: Commit 42ad145553fb1524528a2bac9b3df1bcc02acf6e in geode's branch refs/heads/develop from [~apa...@the9muses.net] [ https://gitbox.apache.org/repos/asf?p=geode.git;h=42ad145 ] GEODE-4846: fixup javadocs on ExecutorServiceRule > Javadocs on ExecutorServiceRule are incorrect > - > > Key: GEODE-4846 > URL: https://issues.apache.org/jira/browse/GEODE-4846 > Project: Geode > Issue Type: Bug > Components: tests >Reporter: Kirk Lund >Assignee: Kirk Lund >Priority: Trivial > > The Javadocs on ExecutorServiceRule incorrectly refer to AsynchronousRule > instead of ExecutorServiceRule. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-4647) Add a new stat for AyncEventQueue/GatewaySender to track secondaryEventsQueueSize
[ https://issues.apache.org/jira/browse/GEODE-4647?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16402627#comment-16402627 ] ASF subversion and git services commented on GEODE-4647: Commit 4f580b27ac38bab4215c6f2afc61a7870274834f in geode's branch refs/heads/feature/GEODE-4647 from zhouxh [ https://gitbox.apache.org/repos/asf?p=geode.git;h=4f580b2 ] GEODE-4647: fix a test case > Add a new stat for AyncEventQueue/GatewaySender to track > secondaryEventsQueueSize > - > > Key: GEODE-4647 > URL: https://issues.apache.org/jira/browse/GEODE-4647 > Project: Geode > Issue Type: Bug > Components: docs, wan >Reporter: Jason Huynh >Assignee: xiaojian zhou >Priority: Major > Labels: pull-request-available > Time Spent: 4h 20m > Remaining Estimate: 0h > > Currently we have eventsQueueSize which tells us how big the queue is based > on how many primary events are in the queue. > It would be nice to have the same type of stat for how many secondary events > are in the queue. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (GEODE-4868) when member deposed primary buckets, it did not decrease the queue size
[
https://issues.apache.org/jira/browse/GEODE-4868?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
xiaojian zhou resolved GEODE-4868.
--
Resolution: Fixed
Fix Version/s: 1.6.0
> when member deposed primary buckets, it did not decrease the queue size
> ---
>
> Key: GEODE-4868
> URL: https://issues.apache.org/jira/browse/GEODE-4868
> Project: Geode
> Issue Type: Bug
> Components: wan
>Reporter: xiaojian zhou
>Assignee: xiaojian zhou
>Priority: Major
> Labels: pull-request-available
> Fix For: 1.6.0
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> {noformat}
> It can use following test code to reproduce the issue:
> diff --git
> a/geode-core/src/test/java/org/apache/geode/internal/cache/wan/AsyncEventQueueTestBase.java
>
> b/geode-core/src/test/java/org/apache/geode/internal/cache/wan/AsyncEventQueueTestBase.java
> index 545d0cac4..fbc0dc015 100644
> ---
> a/geode-core/src/test/java/org/apache/geode/internal/cache/wan/AsyncEventQueueTestBase.java
> +++
> b/geode-core/src/test/java/org/apache/geode/internal/cache/wan/AsyncEventQueueTestBase.java
> @@ -717,6 +717,10 @@ public class AsyncEventQueueTestBase extends
> JUnit4DistributedTestCase {
> }
> }
> final AsyncEventQueueStats statistics = ((AsyncEventQueueImpl)
> queue).getStatistics();
> + Awaitility.await().atMost(60, TimeUnit.SECONDS)
> + .until(() -> assertEquals("Expected queue entries: " + queueSize
> + + " but actual entries: " + statistics.getEventQueueSize(),
> queueSize,
> + statistics.getEventQueueSize()));
> assertEquals(queueSize, statistics.getEventQueueSize());
> assertEquals(eventsReceived, statistics.getEventsReceived());
> diff --git
> a/geode-core/src/test/java/org/apache/geode/internal/cache/wan/asyncqueue/AsyncEventListenerDUnitTest.java
>
> b/geode-core/src/test/java/org/apache/geode/internal/cache/wan/asyncqueue/AsyncEventListenerDUnitTest.java
> index 465f35a87..058bf19cc 100644
> ---
> a/geode-core/src/test/java/org/apache/geode/internal/cache/wan/asyncqueue/AsyncEventListenerDUnitTest.java
> +++
> b/geode-core/src/test/java/org/apache/geode/internal/cache/wan/asyncqueue/AsyncEventListenerDUnitTest.java
> @@ -1519,6 +1519,11 @@ public class AsyncEventListenerDUnitTest extends
> AsyncEventQueueTestBase {
> () ->
> AsyncEventQueueTestBase.getAllPrimaryBucketsOnTheNode(getTestMethodName() +
> "_PR"));
>
> LogWriterUtils.getLogWriter().info("Primary buckets on vm2: " +
> primaryBucketsvm2);
> +
> + // before shutdown vm2, both vm1 and vm2 should have 40 events in
> primary queue
> + vm1.invoke(()->AsyncEventQueueTestBase.checkAsyncEventQueueStats("ln",
> 40,
> 80, 80, 0));
> + vm2.invoke(()->AsyncEventQueueTestBase.checkAsyncEventQueueStats("ln",
> 40, 80, 80, 0));
> +
> // Kill vm2 --
> vm2.invoke(() -> AsyncEventQueueTestBase.killSender());
> //
> @@ -1527,15 +1532,26 @@ public class AsyncEventListenerDUnitTest extends
> AsyncEventQueueTestBase {
> vm3.invoke(createCacheRunnable(lnPort));
> vm3.invoke(() ->
> AsyncEventQueueTestBase.createAsyncEventQueueWithListener2("ln", true, 100, 5,
> false, null));
> + // vm3 will move some primary buckets from vm1, but vm1's primary queue
> size did not reduce
> + vm3.invoke(pauseAsyncEventQueueRunnable());
> vm3.invoke(() ->
> AsyncEventQueueTestBase.createPRWithRedundantCopyWithAsyncEventQueue(
> getTestMethodName() + "_PR", "ln", isOffHeap()));
> -
> +
> // --
> String regionName = getTestMethodName() + "_PR";
> Set primaryBucketsvm3 = (Set) vm3
> .invoke(() ->
> AsyncEventQueueTestBase.getAllPrimaryBucketsOnTheNode(regionName));
> + LogWriterUtils.getLogWriter().info("Primary buckets on vm3: " +
> primaryBucketsvm3);
> + Set primaryBucketsvm1 = (Set) vm1.invoke(
> + () ->
> AsyncEventQueueTestBase.getAllPrimaryBucketsOnTheNode(getTestMethodName() +
> "_PR"));
> + LogWriterUtils.getLogWriter().info("After shutdown vm2, started vm3,
> Primary buckets on vm1: " + primaryBucketsvm1);
>
> +// vm1.invoke(()->AsyncEventQueueTestBase.checkAsyncEventQueueStats("ln",
> 80, 80, 80, 0));
> + vm1.invoke(()->AsyncEventQueueTestBase.checkAsyncEventQueueStats("ln",
> 40, 80, 80, 0));
> + vm3.invoke(()->AsyncEventQueueTestBase.checkAsyncEventQueueStats("ln",
> 40, 0, 0, 0));
> +
> + vm3.invoke(() -> AsyncEventQueueTestBase.resumeAsyncEventQueue("ln"));
> vm1.invoke(() -> AsyncEventQueueTestBase.resumeAsyncEventQueue("ln"));
>
>
[jira] [Commented] (GEODE-4874) Inconsistency in gfsh help for create jndi-binding
[ https://issues.apache.org/jira/browse/GEODE-4874?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16402617#comment-16402617 ] Karen Smoler Miller commented on GEODE-4874: When fixing this, please correct 2 typos in the help info for this command: # Option conn-pooled-datasource-class says "This is the fully qualified name of the connection pool implementation to hold XS datasource connections." It should be "XA," not "XS." # Option type says "Type of the XA datasource. Type of region to create. The following types are pre-defined by the product: MANAGED, SIMPLE, POOLED, XAPOOLED." Please remove the irrelevant sentence "Type of region to create." > Inconsistency in gfsh help for create jndi-binding > --- > > Key: GEODE-4874 > URL: https://issues.apache.org/jira/browse/GEODE-4874 > Project: Geode > Issue Type: Bug > Components: gfsh >Affects Versions: 1.5.0 >Reporter: Karen Smoler Miller >Priority: Minor > > I see an error and an inconsistency when trying to use the gfsh help > functionality for create jndi-binding. > Tab completion of > create jndi-binding > outputs > gfsh>create jndi-binding – > create jndi-binding --connection-url > create jndi-binding --jdbc-driver-class > create jndi-binding --name > create jndi-binding --type > This is inconsistent with the output of other tab completions, which just > give the options, and do not repeat the "create jndi-binding" portion of the > command. > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-4844) JdbcWriter and JdbcAsyncWriter will write rows loaded by the JdbcLoader
[ https://issues.apache.org/jira/browse/GEODE-4844?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16402604#comment-16402604 ] ASF subversion and git services commented on GEODE-4844: Commit 5dc08bf0878c9cef38fa9c321a638656531beb09 in geode's branch refs/heads/feature/GEODE-4647 from [~dschneider] [ https://gitbox.apache.org/repos/asf?p=geode.git;h=5dc08bf ] GEODE-4844: JdbcWriter and JdbcAsyncWriter will write rows loaded by the JdbcLoader (#1618) * JdbcWriter and JdbcAsyncWriter will no longer write to sql if the event was from a load. This will cause them to never write back out events from the JdbcLoader. It also means that if someone is using one of the jdbc writers on a region that uses some other loader that the jdbc writer will ignore data loaded by it. We think the common use case will be if you have a jdbc writer you will either also have the JdbcLoader or no loader. In the future we may need to add a feature so that a user can tell the jdbc writer to not ignore load events. > JdbcWriter and JdbcAsyncWriter will write rows loaded by the JdbcLoader > --- > > Key: GEODE-4844 > URL: https://issues.apache.org/jira/browse/GEODE-4844 > Project: Geode > Issue Type: Bug > Components: extensions, regions >Affects Versions: 1.4.0 >Reporter: Darrel Schneider >Assignee: Darrel Schneider >Priority: Major > Labels: pull-request-available > Fix For: 1.6.0 > > Time Spent: 20m > Remaining Estimate: 0h > > If a region has both the JdbcLoader and JdbcWriter on it then every time the > JdbcLoader loads something from jdbc, it is also rewritten to jdbc by the > JdbcWriter. > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-4830) Modify list jndi-binding gfsh command
[
https://issues.apache.org/jira/browse/GEODE-4830?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16402605#comment-16402605
]
ASF subversion and git services commented on GEODE-4830:
Commit 9aa83fedba637be57ae3de8d0f4db19a243316dc in geode's branch
refs/heads/feature/GEODE-4647 from [~jinmeiliao]
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=9aa83fe ]
GEODE-4830: use POJOs to represent cache configuration allowed by cache-1.0.xsd
* add methods in ClusterConfigurationService to use POJOs to manipulate the
cache xml content.
> Modify list jndi-binding gfsh command
> --
>
> Key: GEODE-4830
> URL: https://issues.apache.org/jira/browse/GEODE-4830
> Project: Geode
> Issue Type: Sub-task
> Components: docs, gfsh
>Reporter: Barbara Pruijn
>Priority: Major
> Labels: pull-request-available
> Time Spent: 1h 20m
> Remaining Estimate: 0h
>
> The list jndi-binding command currently displays jndi-bindings that are
> active.
> We need to modify the output of this command to list all jndi-bindings that
> are listed in the cluster config and indicate in the output of this command
> whether the binding is active or configured.
> We should update the help text to reflect this change. A suggested help text
> is:
> {code:java}
> List all jndi bindings, active and configured. An active binding is one that
> is bound to the server's jndi context (and also listed in the cluster
> config). A configured binding is one that is listed in the cluster config,
> but is not active.{code}
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (GEODE-4870) Categorize AlterAsyncEventQueueCommandDUnitTest as DistributedTest
[
https://issues.apache.org/jira/browse/GEODE-4870?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16402608#comment-16402608
]
ASF subversion and git services commented on GEODE-4870:
Commit 44dc6970f44bb7a5424920d4dc205b0d3c5cd341 in geode's branch
refs/heads/feature/GEODE-4647 from [~jens.deppe]
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=44dc697 ]
GEODE-4870: Categorize AlterAsyncEventQueueCommandDUnitTest as DistributedTest
(#1626)
> Categorize AlterAsyncEventQueueCommandDUnitTest as DistributedTest
> --
>
> Key: GEODE-4870
> URL: https://issues.apache.org/jira/browse/GEODE-4870
> Project: Geode
> Issue Type: Bug
> Components: gfsh
>Reporter: Jens Deppe
>Assignee: Jens Deppe
>Priority: Major
> Labels: pull-request-available
> Time Spent: 20m
> Remaining Estimate: 0h
>
> Currently categorized as {{AcceptanceTest}} which is not correct.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (GEODE-4622) Update library dependencies
[
https://issues.apache.org/jira/browse/GEODE-4622?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16402614#comment-16402614
]
ASF subversion and git services commented on GEODE-4622:
Commit 9655e402c584acfe7061ec3404dcf9a46d5f3cb2 in geode's branch
refs/heads/feature/GEODE-4647 from [~amb]
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=9655e40 ]
GEODE-4622 Revert jna upgrade
jna >4.1 has some issues with process management on windows. Revert
back to jna 4.1.0 until this is resolved.
> Update library dependencies
> ---
>
> Key: GEODE-4622
> URL: https://issues.apache.org/jira/browse/GEODE-4622
> Project: Geode
> Issue Type: Improvement
> Components: build
>Reporter: Anthony Baker
>Assignee: Anthony Baker
>Priority: Major
> Labels: pull-request-available
> Fix For: 1.5.0
>
> Time Spent: 1h 10m
> Remaining Estimate: 0h
>
> Using \{{com.github.ben-manes:gradle-versions-plugin}} we can determine which
> libraries have newer versions and update libraries where appropriate. Some
> major version updates (like spring) may be deferred since those are larger
> efforts.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (GEODE-4769) Serialize region entry before putting in local cache
[ https://issues.apache.org/jira/browse/GEODE-4769?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16402609#comment-16402609 ] ASF subversion and git services commented on GEODE-4769: Commit be9d99da1bb9beb077e9339d0742706ba5d3b96b in geode's branch refs/heads/feature/GEODE-4647 from [~apa...@the9muses.net] [ https://gitbox.apache.org/repos/asf?p=geode.git;h=be9d99d ] GEODE-4769: optional early serialization of EntryEvent key and new value If enabled, Regions and Transactions will serialize key and value before updating the local cache. This prevents inconsistency between distributed members caused by any failure to serialize the key or value. This feature is disabled by default. To enable it, specify the system property geode.earlyEntryEventSerialization=true. > Serialize region entry before putting in local cache > > > Key: GEODE-4769 > URL: https://issues.apache.org/jira/browse/GEODE-4769 > Project: Geode > Issue Type: Improvement > Components: regions >Reporter: Kirk Lund >Assignee: Kirk Lund >Priority: Major > Labels: pull-request-available > Fix For: 1.6.0 > > Time Spent: 2h 20m > Remaining Estimate: 0h > > This will prevent cache inconsistency when dealing with key or value objects > that have broken serialization. > Test should create two members with a REPLICATE region. If one member > performs a put, but the serialization fails then the region entry currently > ends up existing in only the cache of the member that performed the put > locally. The change will prevent this from occurring. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-4769) Serialize region entry before putting in local cache
[ https://issues.apache.org/jira/browse/GEODE-4769?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16402610#comment-16402610 ] ASF subversion and git services commented on GEODE-4769: Commit 076d9abfc2aa2d365adfead168f05e054bea0248 in geode's branch refs/heads/feature/GEODE-4647 from [~apa...@the9muses.net] [ https://gitbox.apache.org/repos/asf?p=geode.git;h=076d9ab ] GEODE-4769: fix tests using non-Serializable value objects Cleanup all test classes touched for this change. > Serialize region entry before putting in local cache > > > Key: GEODE-4769 > URL: https://issues.apache.org/jira/browse/GEODE-4769 > Project: Geode > Issue Type: Improvement > Components: regions >Reporter: Kirk Lund >Assignee: Kirk Lund >Priority: Major > Labels: pull-request-available > Fix For: 1.6.0 > > Time Spent: 2h 20m > Remaining Estimate: 0h > > This will prevent cache inconsistency when dealing with key or value objects > that have broken serialization. > Test should create two members with a REPLICATE region. If one member > performs a put, but the serialization fails then the region entry currently > ends up existing in only the cache of the member that performed the put > locally. The change will prevent this from occurring. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-4868) when member deposed primary buckets, it did not decrease the queue size
[
https://issues.apache.org/jira/browse/GEODE-4868?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16402613#comment-16402613
]
ASF subversion and git services commented on GEODE-4868:
Commit d48607d51f718a6c497d7e6b14a8dc9b87fe2e67 in geode's branch
refs/heads/feature/GEODE-4647 from Xiaojian Zhou
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=d48607d ]
GEODE-4868: depose primary should reduce brq's size in
deposePrimaryForColocatedChildren (#1625)
> when member deposed primary buckets, it did not decrease the queue size
> ---
>
> Key: GEODE-4868
> URL: https://issues.apache.org/jira/browse/GEODE-4868
> Project: Geode
> Issue Type: Bug
> Components: wan
>Reporter: xiaojian zhou
>Assignee: xiaojian zhou
>Priority: Major
> Labels: pull-request-available
> Time Spent: 20m
> Remaining Estimate: 0h
>
> {noformat}
> It can use following test code to reproduce the issue:
> diff --git
> a/geode-core/src/test/java/org/apache/geode/internal/cache/wan/AsyncEventQueueTestBase.java
>
> b/geode-core/src/test/java/org/apache/geode/internal/cache/wan/AsyncEventQueueTestBase.java
> index 545d0cac4..fbc0dc015 100644
> ---
> a/geode-core/src/test/java/org/apache/geode/internal/cache/wan/AsyncEventQueueTestBase.java
> +++
> b/geode-core/src/test/java/org/apache/geode/internal/cache/wan/AsyncEventQueueTestBase.java
> @@ -717,6 +717,10 @@ public class AsyncEventQueueTestBase extends
> JUnit4DistributedTestCase {
> }
> }
> final AsyncEventQueueStats statistics = ((AsyncEventQueueImpl)
> queue).getStatistics();
> + Awaitility.await().atMost(60, TimeUnit.SECONDS)
> + .until(() -> assertEquals("Expected queue entries: " + queueSize
> + + " but actual entries: " + statistics.getEventQueueSize(),
> queueSize,
> + statistics.getEventQueueSize()));
> assertEquals(queueSize, statistics.getEventQueueSize());
> assertEquals(eventsReceived, statistics.getEventsReceived());
> diff --git
> a/geode-core/src/test/java/org/apache/geode/internal/cache/wan/asyncqueue/AsyncEventListenerDUnitTest.java
>
> b/geode-core/src/test/java/org/apache/geode/internal/cache/wan/asyncqueue/AsyncEventListenerDUnitTest.java
> index 465f35a87..058bf19cc 100644
> ---
> a/geode-core/src/test/java/org/apache/geode/internal/cache/wan/asyncqueue/AsyncEventListenerDUnitTest.java
> +++
> b/geode-core/src/test/java/org/apache/geode/internal/cache/wan/asyncqueue/AsyncEventListenerDUnitTest.java
> @@ -1519,6 +1519,11 @@ public class AsyncEventListenerDUnitTest extends
> AsyncEventQueueTestBase {
> () ->
> AsyncEventQueueTestBase.getAllPrimaryBucketsOnTheNode(getTestMethodName() +
> "_PR"));
>
> LogWriterUtils.getLogWriter().info("Primary buckets on vm2: " +
> primaryBucketsvm2);
> +
> + // before shutdown vm2, both vm1 and vm2 should have 40 events in
> primary queue
> + vm1.invoke(()->AsyncEventQueueTestBase.checkAsyncEventQueueStats("ln",
> 40,
> 80, 80, 0));
> + vm2.invoke(()->AsyncEventQueueTestBase.checkAsyncEventQueueStats("ln",
> 40, 80, 80, 0));
> +
> // Kill vm2 --
> vm2.invoke(() -> AsyncEventQueueTestBase.killSender());
> //
> @@ -1527,15 +1532,26 @@ public class AsyncEventListenerDUnitTest extends
> AsyncEventQueueTestBase {
> vm3.invoke(createCacheRunnable(lnPort));
> vm3.invoke(() ->
> AsyncEventQueueTestBase.createAsyncEventQueueWithListener2("ln", true, 100, 5,
> false, null));
> + // vm3 will move some primary buckets from vm1, but vm1's primary queue
> size did not reduce
> + vm3.invoke(pauseAsyncEventQueueRunnable());
> vm3.invoke(() ->
> AsyncEventQueueTestBase.createPRWithRedundantCopyWithAsyncEventQueue(
> getTestMethodName() + "_PR", "ln", isOffHeap()));
> -
> +
> // --
> String regionName = getTestMethodName() + "_PR";
> Set primaryBucketsvm3 = (Set) vm3
> .invoke(() ->
> AsyncEventQueueTestBase.getAllPrimaryBucketsOnTheNode(regionName));
> + LogWriterUtils.getLogWriter().info("Primary buckets on vm3: " +
> primaryBucketsvm3);
> + Set primaryBucketsvm1 = (Set) vm1.invoke(
> + () ->
> AsyncEventQueueTestBase.getAllPrimaryBucketsOnTheNode(getTestMethodName() +
> "_PR"));
> + LogWriterUtils.getLogWriter().info("After shutdown vm2, started vm3,
> Primary buckets on vm1: " + primaryBucketsvm1);
>
> +// vm1.invoke(()->AsyncEventQueueTestBase.checkAsyncEventQueueStats("ln",
> 80, 80, 80, 0));
> + vm1.invoke(()->AsyncEventQueueTestBase.checkAsyncEventQueueStats("ln",
> 40, 80,
[jira] [Commented] (GEODE-4830) Modify list jndi-binding gfsh command
[
https://issues.apache.org/jira/browse/GEODE-4830?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16402606#comment-16402606
]
ASF subversion and git services commented on GEODE-4830:
Commit 7f8eedcc5f495e6da2fb5e01d9855929d6df49fa in geode's branch
refs/heads/feature/GEODE-4647 from [~jinmeiliao]
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=7f8eedc ]
GEODE-4830: use CacheConfig to access the jndi list in ListJNDIBindingCommand
* updated the CacheConfig to hold only one JNDIBindingsType instead of a list
* make sure xml created by those POJOs can be used to start a server
* the service will keep a list of bind classes for clearer xml generation.
* the service will keep a reference to the marshaer/unmarsher for faster
operation
> Modify list jndi-binding gfsh command
> --
>
> Key: GEODE-4830
> URL: https://issues.apache.org/jira/browse/GEODE-4830
> Project: Geode
> Issue Type: Sub-task
> Components: docs, gfsh
>Reporter: Barbara Pruijn
>Priority: Major
> Labels: pull-request-available
> Time Spent: 1h 20m
> Remaining Estimate: 0h
>
> The list jndi-binding command currently displays jndi-bindings that are
> active.
> We need to modify the output of this command to list all jndi-bindings that
> are listed in the cluster config and indicate in the output of this command
> whether the binding is active or configured.
> We should update the help text to reflect this change. A suggested help text
> is:
> {code:java}
> List all jndi bindings, active and configured. An active binding is one that
> is bound to the server's jndi context (and also listed in the cluster
> config). A configured binding is one that is listed in the cluster config,
> but is not active.{code}
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (GEODE-4827) Cq should not be added to the cq map if cq's base region is null
[
https://issues.apache.org/jira/browse/GEODE-4827?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16402611#comment-16402611
]
ASF subversion and git services commented on GEODE-4827:
Commit c5b44019dd21847f9f79fc1fbfcf78df70f660e0 in geode's branch
refs/heads/feature/GEODE-4647 from [~nabarunnag]
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=c5b4401 ]
GEODE-4827: CQ not added to cq map on exception (#1602)
* Log level set to info when FilterProfile gets an exception while
registering CQ
* Before, when there is an exception while registering cq like while
cache closing the cq's base region is null
* There is an exception which is logged in debug level but execution
continues and adds the cq to the cp map with base region set to null
* This results in a NullPointerException while closing cq as methods
are executed on null region
* Now the operation to put the cq into the cq map is inside a if check
for null cq base region.
> Cq should not be added to the cq map if cq's base region is null
>
>
> Key: GEODE-4827
> URL: https://issues.apache.org/jira/browse/GEODE-4827
> Project: Geode
> Issue Type: Bug
> Components: cq
>Reporter: nabarun
>Priority: Major
> Labels: pull-request-available
> Fix For: 1.6.0
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> Currently while registering a cq if the cache is closing down , it throws an
> exception. but we ignore the exception and continue adding the cq to the map.
> While processing the closing of cq it will ask for the cq's base region which
> will be null. Thus ends with NPE because we end up calling methods on null
> region.
> Solution:
> put the addition of the cq to the cqMap inside a if check for base region
> {code:java}
> void processRegisterCq(String serverCqName, ServerCQ ServerCQ, boolean
> addToCqMap,
> GemFireCacheImpl cache) {
> ServerCQ cq = (ServerCQ) ServerCQ;
> try {
> CqService cqService = cache.getCqService();
> cqService.start();
> cq.setCqService(cqService);
> CqStateImpl cqState = (CqStateImpl) cq.getState();
> cq.setName(generateCqName(serverCqName));
> cq.registerCq(null, null, cqState.getState());
> } catch (Exception ex) {
> // Change it to Info level.
> logger.info("Error while initializing the CQs with FilterProfile for CQ
> {}, Error : {}",
> serverCqName, ex.getMessage(), ex);
> }
> if (logger.isDebugEnabled()) {
> logger.debug("Adding CQ to remote members FilterProfile using name:
> {}", serverCqName);
> }
> // The region's FilterProfile is accessed through CQ reference as the
> // region is not set on the FilterProfile created for the peer nodes.
> if (cq.getCqBaseRegion() != null) {
> if (addToCqMap) {
> this.cqs.put(serverCqName, cq);
> }
> FilterProfile pf = cq.getCqBaseRegion().getFilterProfile();
> if (pf != null) {
> pf.incCqCount();
> }
> }
> }
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (GEODE-4497) Command help create gateway-sender returns error if window size is 80 columns wide
[
https://issues.apache.org/jira/browse/GEODE-4497?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ASF GitHub Bot updated GEODE-4497:
--
Labels: pull-request-available (was: )
> Command help create gateway-sender returns error if window size is 80 columns
> wide
> --
>
> Key: GEODE-4497
> URL: https://issues.apache.org/jira/browse/GEODE-4497
> Project: Geode
> Issue Type: Bug
> Components: gfsh
>Reporter: Barbara Pruijn
>Priority: Major
> Labels: pull-request-available
>
> If you use the standard window size (25 rows; 80 columns) and run the
> following command in gfsh:
> {code}help create gateway-sender{code}
> you get the following error:
> {noformat}
> gfsh>help create gateway-sender
> [error 2018/02/01 14:35:22.359 PST tid=0x20] Could not
> execute "help create gateway-sender".
> java.lang.StringIndexOutOfBoundsException: String index out of range: -1
> at java.lang.String.substring(String.java:1967)
> at
> org.apache.geode.management.internal.cli.shell.Gfsh.wrapText(Gfsh.java:418)
> at
> org.apache.geode.management.internal.cli.help.HelpBlock.toString(HelpBlock.java:79)
> at
> org.apache.geode.management.internal.cli.help.HelpBlock.toString(HelpBlock.java:83)
> at
> org.apache.geode.management.internal.cli.help.HelpBlock.toString(HelpBlock.java:83)
> at
> org.apache.geode.management.internal.cli.help.HelpBlock.toString(HelpBlock.java:83)
> at
> org.apache.geode.management.internal.cli.help.Helper.getHelp(Helper.java:145)
> at
> org.apache.geode.management.internal.cli.CommandManager.obtainHelp(CommandManager.java:310)
> at
> org.apache.geode.management.internal.cli.commands.GfshHelpCommand.obtainHelp(GfshHelpCommand.java:42)
> 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
> org.springframework.util.ReflectionUtils.invokeMethod(ReflectionUtils.java:216)
> at
> org.apache.geode.management.internal.cli.remote.CommandExecutor.invokeCommand(CommandExecutor.java:97)
> at
> org.apache.geode.management.internal.cli.remote.CommandExecutor.execute(CommandExecutor.java:45)
> at
> org.apache.geode.management.internal.cli.remote.CommandExecutor.execute(CommandExecutor.java:39)
> at
> org.apache.geode.management.internal.cli.shell.GfshExecutionStrategy.execute(GfshExecutionStrategy.java:81)
> at
> org.springframework.shell.core.AbstractShell.executeCommand(AbstractShell.java:134)
> at
> org.apache.geode.management.internal.cli.shell.Gfsh.promptLoop(Gfsh.java:1008)
> at org.springframework.shell.core.JLineShell.run(JLineShell.java:179)
> at java.lang.Thread.run(Thread.java:748)
> Could not process command due to error. Error while processing command create gateway-sender> Reason : String index out of range: -1
> {noformat}
> If you make the window wider and run the command again, it runs fine.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (GEODE-3696) New protocol - create region message
[ https://issues.apache.org/jira/browse/GEODE-3696?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Baynes resolved GEODE-3696. - Resolution: Won't Do This will be available in the REST API which should be sufficient. > New protocol - create region message > > > Key: GEODE-3696 > URL: https://issues.apache.org/jira/browse/GEODE-3696 > Project: Geode > Issue Type: New Feature > Components: client/server >Reporter: Brian Baynes >Priority: Major > > As a dev using the new protocol, I'd like to be able to create new regions > using the protocol. > [Scope/additional details forthcoming] -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (GEODE-3697) New protocol - destroy region message
[ https://issues.apache.org/jira/browse/GEODE-3697?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Baynes resolved GEODE-3697. - Resolution: Won't Do This will be available in the REST API which should be sufficient. > New protocol - destroy region message > - > > Key: GEODE-3697 > URL: https://issues.apache.org/jira/browse/GEODE-3697 > Project: Geode > Issue Type: New Feature > Components: client/server >Reporter: Brian Baynes >Priority: Major > > As a dev using the new protocol, I'd like to be able to destroy regions using > the protocol. > [Scope/additional details forthcoming] -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (GEODE-4879) Move geode-core/src/test/java/hydra into dunit packages
Kirk Lund created GEODE-4879: Summary: Move geode-core/src/test/java/hydra into dunit packages Key: GEODE-4879 URL: https://issues.apache.org/jira/browse/GEODE-4879 Project: Geode Issue Type: Improvement Components: tests Reporter: Kirk Lund We have 3 classes in hydra package: * MethExecutor * MethExecutorResult * SchedulingOrder I'd like to move these under the dunit package and rename them. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (GEODE-4879) Move geode-core/src/test/java/hydra into dunit packages
[ https://issues.apache.org/jira/browse/GEODE-4879?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kirk Lund reassigned GEODE-4879: Assignee: Kirk Lund > Move geode-core/src/test/java/hydra into dunit packages > --- > > Key: GEODE-4879 > URL: https://issues.apache.org/jira/browse/GEODE-4879 > Project: Geode > Issue Type: Improvement > Components: tests >Reporter: Kirk Lund >Assignee: Kirk Lund >Priority: Major > > We have 3 classes in hydra package: > * MethExecutor > * MethExecutorResult > * SchedulingOrder > I'd like to move these under the dunit package and rename them. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (GEODE-4878) Remove Thread.sleep from ClusterConfigLocatorRestartDUnitTest
[ https://issues.apache.org/jira/browse/GEODE-4878?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated GEODE-4878: -- Labels: pull-request-available (was: ) > Remove Thread.sleep from ClusterConfigLocatorRestartDUnitTest > - > > Key: GEODE-4878 > URL: https://issues.apache.org/jira/browse/GEODE-4878 > Project: Geode > Issue Type: Test > Components: gfsh >Reporter: Jens Deppe >Assignee: Jens Deppe >Priority: Major > Labels: pull-request-available > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (GEODE-4874) Inconsistency in gfsh help for create jndi-binding
[ https://issues.apache.org/jira/browse/GEODE-4874?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Barbara Pruijn updated GEODE-4874: -- Summary: Inconsistency in gfsh help for create jndi-binding (was: errors in gfsh help for create jndi-binding ) > Inconsistency in gfsh help for create jndi-binding > --- > > Key: GEODE-4874 > URL: https://issues.apache.org/jira/browse/GEODE-4874 > Project: Geode > Issue Type: Bug > Components: gfsh >Affects Versions: 1.5.0 >Reporter: Karen Smoler Miller >Priority: Minor > > I see an error and an inconsistency when trying to use the gfsh help > functionality for create jndi-binding. > Tab completion of > create jndi-binding > outputs > gfsh>create jndi-binding – > create jndi-binding --connection-url > create jndi-binding --jdbc-driver-class > create jndi-binding --name > create jndi-binding --type > This is inconsistent with the output of other tab completions, which just > give the options, and do not repeat the "create jndi-binding" portion of the > command. > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (GEODE-4878) Remove Thread.sleep from ClusterConfigLocatorRestartDUnitTest
[ https://issues.apache.org/jira/browse/GEODE-4878?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jens Deppe reassigned GEODE-4878: - Assignee: Jens Deppe > Remove Thread.sleep from ClusterConfigLocatorRestartDUnitTest > - > > Key: GEODE-4878 > URL: https://issues.apache.org/jira/browse/GEODE-4878 > Project: Geode > Issue Type: Test > Components: gfsh >Reporter: Jens Deppe >Assignee: Jens Deppe >Priority: Major > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (GEODE-4878) Remove Thread.sleep from ClusterConfigLocatorRestartDUnitTest
Jens Deppe created GEODE-4878: - Summary: Remove Thread.sleep from ClusterConfigLocatorRestartDUnitTest Key: GEODE-4878 URL: https://issues.apache.org/jira/browse/GEODE-4878 Project: Geode Issue Type: Test Components: gfsh Reporter: Jens Deppe -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (GEODE-4169) Update ACE to 6.4.7
[ https://issues.apache.org/jira/browse/GEODE-4169?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated GEODE-4169: -- Labels: pull-request-available (was: ) > Update ACE to 6.4.7 > --- > > Key: GEODE-4169 > URL: https://issues.apache.org/jira/browse/GEODE-4169 > Project: Geode > Issue Type: Task > Components: native client >Reporter: Jacob S. Barrett >Assignee: Jacob S. Barrett >Priority: Major > Labels: pull-request-available > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (GEODE-4821) RegisterInterestIntegrationTest should be categorized as DistributedTest
[ https://issues.apache.org/jira/browse/GEODE-4821?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kirk Lund updated GEODE-4821: - Priority: Trivial (was: Major) > RegisterInterestIntegrationTest should be categorized as DistributedTest > > > Key: GEODE-4821 > URL: https://issues.apache.org/jira/browse/GEODE-4821 > Project: Geode > Issue Type: Bug > Components: client queues, tests >Reporter: Kirk Lund >Assignee: Kirk Lund >Priority: Trivial > > ClusterStarterRule is a DistributedTest rule and launches DUnit child VMs. > RegisterInterestIntegrationTest should either change to be a DistributedTest > or change to not use ClusterStarterRule. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (GEODE-4820) Non-DistributedTests should use RestoreSystemProperties instead of DistributedRestoreSystemProperties
[ https://issues.apache.org/jira/browse/GEODE-4820?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kirk Lund updated GEODE-4820: - Priority: Trivial (was: Major) > Non-DistributedTests should use RestoreSystemProperties instead of > DistributedRestoreSystemProperties > - > > Key: GEODE-4820 > URL: https://issues.apache.org/jira/browse/GEODE-4820 > Project: Geode > Issue Type: Bug > Components: tests >Reporter: Kirk Lund >Assignee: Kirk Lund >Priority: Trivial > > Two IntegrationTests are using DistributedRestoreSystemProperties. These > tests should be changed to use the original RestoreSystemProperties. > * HARegionQueueJUnitTest > * BlockingHARegionQueueJUnitTest -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (GEODE-4169) Update ACE to 6.4.7
[ https://issues.apache.org/jira/browse/GEODE-4169?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jacob S. Barrett reassigned GEODE-4169: --- Assignee: Jacob S. Barrett > Update ACE to 6.4.7 > --- > > Key: GEODE-4169 > URL: https://issues.apache.org/jira/browse/GEODE-4169 > Project: Geode > Issue Type: Task > Components: native client >Reporter: Jacob S. Barrett >Assignee: Jacob S. Barrett >Priority: Major > Labels: pull-request-available > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (GEODE-4846) Javadocs on ExecutorServiceRule are incorrect
[ https://issues.apache.org/jira/browse/GEODE-4846?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kirk Lund updated GEODE-4846: - Priority: Trivial (was: Major) > Javadocs on ExecutorServiceRule are incorrect > - > > Key: GEODE-4846 > URL: https://issues.apache.org/jira/browse/GEODE-4846 > Project: Geode > Issue Type: Bug > Components: tests >Reporter: Kirk Lund >Assignee: Kirk Lund >Priority: Trivial > > The Javadocs on ExecutorServiceRule incorrectly refer to AsynchronousRule > instead of ExecutorServiceRule. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (GEODE-4789) Update system-rules dependency from 1.16.1 to 1.17.1
[ https://issues.apache.org/jira/browse/GEODE-4789?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kirk Lund updated GEODE-4789: - Priority: Minor (was: Major) > Update system-rules dependency from 1.16.1 to 1.17.1 > > > Key: GEODE-4789 > URL: https://issues.apache.org/jira/browse/GEODE-4789 > Project: Geode > Issue Type: Improvement > Components: build, tests >Reporter: Kirk Lund >Assignee: Kirk Lund >Priority: Minor > Labels: pull-request-available > Time Spent: 2h > Remaining Estimate: 0h > > com.github.stefanbirkner:system-rules releases are now up to 1.17.1. We > should update our dependency from 1.16.1 to 1.17.1. > System-Rules is a library of JUnit Rules used in UnitTests, IntegrationTests > and DistributedTests for controlling System properties, stdout, stderr, etc. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (GEODE-4876) Add static VM APIs from Host to VM
[ https://issues.apache.org/jira/browse/GEODE-4876?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kirk Lund updated GEODE-4876: - Priority: Trivial (was: Major) > Add static VM APIs from Host to VM > -- > > Key: GEODE-4876 > URL: https://issues.apache.org/jira/browse/GEODE-4876 > Project: Geode > Issue Type: Improvement > Components: tests >Reporter: Kirk Lund >Assignee: Kirk Lund >Priority: Trivial > > Add getVM(int), getAllVMs(), getVMCount(), getLocator(), getHostName() to VM. > Change tests that use DistributedTestRule to invoke methods on VM instead of > Host. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (GEODE-4876) Add static VM APIs from Host to VM
[ https://issues.apache.org/jira/browse/GEODE-4876?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kirk Lund updated GEODE-4876: - Description: Add getVM(int), getAllVMs(), getVMCount(), getLocator(), getHostName() to VM. Change tests that use DistributedTestRule to invoke methods on VM instead of Host. was: Add DistributedTestRule constructor which accepts vmCount so that DistributedTestRule can provision DUnit VMs for other rules, such as DistributedRestoreSystemProperties, to use. Add getVM(int), getAllVMs() to DistributedTestRule. Change tests that use DistributedTestRule to use its new APIs instead of Host. > Add static VM APIs from Host to VM > -- > > Key: GEODE-4876 > URL: https://issues.apache.org/jira/browse/GEODE-4876 > Project: Geode > Issue Type: Improvement > Components: tests >Reporter: Kirk Lund >Assignee: Kirk Lund >Priority: Major > > Add getVM(int), getAllVMs(), getVMCount(), getLocator(), getHostName() to VM. > Change tests that use DistributedTestRule to invoke methods on VM instead of > Host. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (GEODE-4876) Add static VM APIs from Host to VM
[ https://issues.apache.org/jira/browse/GEODE-4876?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kirk Lund updated GEODE-4876: - Summary: Add static VM APIs from Host to VM (was: Add VM APIs from Host to DistributedTestRule) > Add static VM APIs from Host to VM > -- > > Key: GEODE-4876 > URL: https://issues.apache.org/jira/browse/GEODE-4876 > Project: Geode > Issue Type: Improvement > Components: tests >Reporter: Kirk Lund >Assignee: Kirk Lund >Priority: Major > > Add DistributedTestRule constructor which accepts vmCount so that > DistributedTestRule can provision DUnit VMs for other rules, such as > DistributedRestoreSystemProperties, to use. > Add getVM(int), getAllVMs() to DistributedTestRule. > Change tests that use DistributedTestRule to use its new APIs instead of Host. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-4622) Update library dependencies
[
https://issues.apache.org/jira/browse/GEODE-4622?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16402472#comment-16402472
]
ASF subversion and git services commented on GEODE-4622:
Commit 52f5efdf1009cd13107b53d232f5529aab34d4da in geode's branch
refs/heads/release/1.5.0 from [~amb]
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=52f5efd ]
GEODE-4622 Revert jna upgrade
jna >4.1 has some issues with process management on windows. Revert
back to jna 4.1.0 until this is resolved.
(cherry picked from commit 9655e402c584acfe7061ec3404dcf9a46d5f3cb2)
> Update library dependencies
> ---
>
> Key: GEODE-4622
> URL: https://issues.apache.org/jira/browse/GEODE-4622
> Project: Geode
> Issue Type: Improvement
> Components: build
>Reporter: Anthony Baker
>Assignee: Anthony Baker
>Priority: Major
> Labels: pull-request-available
> Fix For: 1.5.0
>
> Time Spent: 1h 10m
> Remaining Estimate: 0h
>
> Using \{{com.github.ben-manes:gradle-versions-plugin}} we can determine which
> libraries have newer versions and update libraries where appropriate. Some
> major version updates (like spring) may be deferred since those are larger
> efforts.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (GEODE-4622) Update library dependencies
[
https://issues.apache.org/jira/browse/GEODE-4622?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16402471#comment-16402471
]
ASF subversion and git services commented on GEODE-4622:
Commit 9655e402c584acfe7061ec3404dcf9a46d5f3cb2 in geode's branch
refs/heads/develop from [~amb]
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=9655e40 ]
GEODE-4622 Revert jna upgrade
jna >4.1 has some issues with process management on windows. Revert
back to jna 4.1.0 until this is resolved.
> Update library dependencies
> ---
>
> Key: GEODE-4622
> URL: https://issues.apache.org/jira/browse/GEODE-4622
> Project: Geode
> Issue Type: Improvement
> Components: build
>Reporter: Anthony Baker
>Assignee: Anthony Baker
>Priority: Major
> Labels: pull-request-available
> Fix For: 1.5.0
>
> Time Spent: 1h 10m
> Remaining Estimate: 0h
>
> Using \{{com.github.ben-manes:gradle-versions-plugin}} we can determine which
> libraries have newer versions and update libraries where appropriate. Some
> major version updates (like spring) may be deferred since those are larger
> efforts.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (GEODE-4169) Update ACE to 6.4.7
[ https://issues.apache.org/jira/browse/GEODE-4169?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jacob S. Barrett updated GEODE-4169: Summary: Update ACE to 6.4.7 (was: Update ACE to 6.4.6) > Update ACE to 6.4.7 > --- > > Key: GEODE-4169 > URL: https://issues.apache.org/jira/browse/GEODE-4169 > Project: Geode > Issue Type: Task > Components: native client >Reporter: Jacob S. Barrett >Priority: Major > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (GEODE-4754) remove com.sun.proxy from the serialization white-list
[ https://issues.apache.org/jira/browse/GEODE-4754?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bruce Schuchardt resolved GEODE-4754. - Resolution: Won't Fix I'm closing this as there is already a mechanism in the JDK to prevent the only hypothetical attack that can be launched with proxy and invocation handler classes. > remove com.sun.proxy from the serialization white-list > -- > > Key: GEODE-4754 > URL: https://issues.apache.org/jira/browse/GEODE-4754 > Project: Geode > Issue Type: Bug > Components: serialization >Reporter: Bruce Schuchardt >Priority: Major > > Someone added com.sun.proxy.* to the serialization whitelist in > InternalDataSerializer. It looks like it was part of the jar deployer work > that introduced RMIIO. We should remove this from the whitelist. > I removed it and ran precheckin, and found that only one test, > LuceneIndexCommandsDUnitTest.searchShouldReturnCorrectResults, failed. That > test was using as cache values instances of an inner class. That caused the > whole test instance to be serialized and put in the cache, including > instances of VM. These are RMI stubs that reference com.sun.proxy.Proxy > instances. Changing the value class to be static will make it pass without > needing com.sun.proxy to be whitelisted. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (GEODE-4754) remove com.sun.proxy from the serialization white-list
[ https://issues.apache.org/jira/browse/GEODE-4754?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bruce Schuchardt closed GEODE-4754. --- > remove com.sun.proxy from the serialization white-list > -- > > Key: GEODE-4754 > URL: https://issues.apache.org/jira/browse/GEODE-4754 > Project: Geode > Issue Type: Bug > Components: serialization >Reporter: Bruce Schuchardt >Priority: Major > > Someone added com.sun.proxy.* to the serialization whitelist in > InternalDataSerializer. It looks like it was part of the jar deployer work > that introduced RMIIO. We should remove this from the whitelist. > I removed it and ran precheckin, and found that only one test, > LuceneIndexCommandsDUnitTest.searchShouldReturnCorrectResults, failed. That > test was using as cache values instances of an inner class. That caused the > whole test instance to be serialized and put in the cache, including > instances of VM. These are RMI stubs that reference com.sun.proxy.Proxy > instances. Changing the value class to be static will make it pass without > needing com.sun.proxy to be whitelisted. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-4822) The second server instance startup error: Could not create an instance of PartitionRegionConfig
[
https://issues.apache.org/jira/browse/GEODE-4822?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16402396#comment-16402396
]
Bruce Schuchardt commented on GEODE-4822:
-
A fix is up for review:
[https://github.com/apache/geode/pull/1632]
> The second server instance startup error: Could not create an instance of
> PartitionRegionConfig
> ---
>
> Key: GEODE-4822
> URL: https://issues.apache.org/jira/browse/GEODE-4822
> Project: Geode
> Issue Type: Bug
> Components: serialization
>Reporter: Vlad Ermolaev
>Assignee: Bruce Schuchardt
>Priority: Major
> Labels: pull-request-available
> Time Spent: 10m
> Remaining Estimate: 0h
>
> I have a simple configuration containing a partitioned persistent region and
> an async queue:
> {code:xml}
> dispatcher-threads="1" enable-batch-conflation="true" batch-size="10"
> batch-time-interval="10">
>
> test.geode.UserQueueListener
>
>
>
>
> test.geode.util.PdxSerializerWrapper
>
>
>
> async-event-queue-ids="userQueue">
> java.lang.Long
> test.geode.domain.User
>
>
> {code}
>
> The first server instance successfully started.
> But the second one in always failing on startup. The problem disappears if I
> remove the config or disable PDX serialization.
> Here is the stacktrace of the failed instance:
> {code}
> [info 2018/03/12 11:01:43.880 CET server2 tid=0x1] Initializing region
> PdxTypes
> [info 2018/03/12 11:01:43.893 CET server2 tid=0x1] Region PdxTypes
> requesting initial image from 192.168.178.159(server1:23330):1025
> [info 2018/03/12 11:01:43.897 CET server2 tid=0x1] PdxTypes is done
> getting image from 192.168.178.159(server1:23330):1025. isDeltaGII is true
> [info 2018/03/12 11:01:43.897 CET server2 tid=0x1] Region PdxTypes
> initialized persistent id:
> /192.168.178.159:/u01/home/chet/projects/geode/server2/store/pdx created at
> timestamp 1520848903878 version 0 diskStoreId
> 9d7c3e96b525418d-ae5b85e1966f3a51 name server2 with data from
> 192.168.178.159(server1:23330):1025.
> [info 2018/03/12 11:01:43.897 CET server2 tid=0x1] Initialization of
> region PdxTypes completed
> [info 2018/03/12 11:01:43.901 CET server2 tid=0x1] Recovered disk
> store mainStore with unique id 11c1012c13d04a3e-9309c26560d9fd33
> [info 2018/03/12 11:01:43.902 CET server2 tid=0x1] recovery region
> initialization took 0 ms
> [info 2018/03/12 11:01:43.907 CET server2 tid=0x1] Created disk store
> queueStore with unique id 308f63b00ee045f9-a6cfaea88f894c7a
> [info 2018/03/12 11:01:43.908 CET server2 tid=0x1] recovery region
> initialization took 0 ms
> [info 2018/03/12 11:01:43.929 CET server2 tid=0x1] Initializing region
> gatewayEventIdIndexMetaData
> [info 2018/03/12 11:01:43.933 CET server2 tid=0x1] Region
> gatewayEventIdIndexMetaData requesting initial image from
> 192.168.178.159(server1:23330):1025
> [info 2018/03/12 11:01:43.935 CET server2 tid=0x1]
> gatewayEventIdIndexMetaData is done getting image from
> 192.168.178.159(server1:23330):1025. isDeltaGII is false
> [info 2018/03/12 11:01:43.935 CET server2 tid=0x1] Initialization of
> region gatewayEventIdIndexMetaData completed
> [info 2018/03/12 11:01:43.944 CET server2 tid=0x1]
> ConcurrentParallelGatewaySenderEventProcessor: dispatcher threads 1
> [info 2018/03/12 11:01:43.953 CET server2 tid=0x1] Started
> ParallelGatewaySender{id=AsyncEventQueue_userQueue,remoteDsId=-1,isRunning
> =true}
> [info 2018/03/12 11:01:43.985 CET server2 tid=0x1] Initializing region
> __PR
> [info 2018/03/12 11:01:43.989 CET server2 tid=0x1] Region __PR
> requesting initial image from 192.168.178.159(server1:23330):1025
> [info 2018/03/12 11:01:44.001 CET server2 Processor 2> tid=0x32] Adding: PdxType[dsid=0, typenum=2161953
> name=java.util.Collections$UnmodifiableSet
> fields=[
> c:Object:0:idx0(relativeOffset)=0:idx1(vlfOffsetIndex)=-1
> empty:boolean:1:idx0(relativeOffset)=-1:idx1(vlfOffsetIndex)=-1]]
> [info 2018/03/12 11:01:44.005 CET server2 tid=0x1] __PR failed to get
> image from 192.168.178.159(server1:23330):1025
> [warning 2018/03/12 11:01:44.006 CET server2 tid=0x1] Initialization
> failed for Region /__PR
> org.apache.geode.SerializationException: Could not create an instance of
> org.apache.geode.internal.cache.PartitionRegionConfig .
> at Remote Member '192.168.178.159(server2:24615):1026' in
> org.apache.geode.internal.InternalDataSerializer.invokeFromData(InternalDataSerializer.java:2474)
> at Remote Member '192.168.178.159(server2:24615):1026' in
> org.apache.geode.internal.DSFIDFactory.create(DSFIDFactory.java:990)
> at Remote Member '192.168.178.159(server2:24615):1026' in
>
[jira] [Assigned] (GEODE-4822) The second server instance startup error: Could not create an instance of PartitionRegionConfig
[
https://issues.apache.org/jira/browse/GEODE-4822?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bruce Schuchardt reassigned GEODE-4822:
---
Assignee: Bruce Schuchardt
> The second server instance startup error: Could not create an instance of
> PartitionRegionConfig
> ---
>
> Key: GEODE-4822
> URL: https://issues.apache.org/jira/browse/GEODE-4822
> Project: Geode
> Issue Type: Bug
> Components: serialization
>Reporter: Vlad Ermolaev
>Assignee: Bruce Schuchardt
>Priority: Major
> Labels: pull-request-available
> Time Spent: 10m
> Remaining Estimate: 0h
>
> I have a simple configuration containing a partitioned persistent region and
> an async queue:
> {code:xml}
> dispatcher-threads="1" enable-batch-conflation="true" batch-size="10"
> batch-time-interval="10">
>
> test.geode.UserQueueListener
>
>
>
>
> test.geode.util.PdxSerializerWrapper
>
>
>
> async-event-queue-ids="userQueue">
> java.lang.Long
> test.geode.domain.User
>
>
> {code}
>
> The first server instance successfully started.
> But the second one in always failing on startup. The problem disappears if I
> remove the config or disable PDX serialization.
> Here is the stacktrace of the failed instance:
> {code}
> [info 2018/03/12 11:01:43.880 CET server2 tid=0x1] Initializing region
> PdxTypes
> [info 2018/03/12 11:01:43.893 CET server2 tid=0x1] Region PdxTypes
> requesting initial image from 192.168.178.159(server1:23330):1025
> [info 2018/03/12 11:01:43.897 CET server2 tid=0x1] PdxTypes is done
> getting image from 192.168.178.159(server1:23330):1025. isDeltaGII is true
> [info 2018/03/12 11:01:43.897 CET server2 tid=0x1] Region PdxTypes
> initialized persistent id:
> /192.168.178.159:/u01/home/chet/projects/geode/server2/store/pdx created at
> timestamp 1520848903878 version 0 diskStoreId
> 9d7c3e96b525418d-ae5b85e1966f3a51 name server2 with data from
> 192.168.178.159(server1:23330):1025.
> [info 2018/03/12 11:01:43.897 CET server2 tid=0x1] Initialization of
> region PdxTypes completed
> [info 2018/03/12 11:01:43.901 CET server2 tid=0x1] Recovered disk
> store mainStore with unique id 11c1012c13d04a3e-9309c26560d9fd33
> [info 2018/03/12 11:01:43.902 CET server2 tid=0x1] recovery region
> initialization took 0 ms
> [info 2018/03/12 11:01:43.907 CET server2 tid=0x1] Created disk store
> queueStore with unique id 308f63b00ee045f9-a6cfaea88f894c7a
> [info 2018/03/12 11:01:43.908 CET server2 tid=0x1] recovery region
> initialization took 0 ms
> [info 2018/03/12 11:01:43.929 CET server2 tid=0x1] Initializing region
> gatewayEventIdIndexMetaData
> [info 2018/03/12 11:01:43.933 CET server2 tid=0x1] Region
> gatewayEventIdIndexMetaData requesting initial image from
> 192.168.178.159(server1:23330):1025
> [info 2018/03/12 11:01:43.935 CET server2 tid=0x1]
> gatewayEventIdIndexMetaData is done getting image from
> 192.168.178.159(server1:23330):1025. isDeltaGII is false
> [info 2018/03/12 11:01:43.935 CET server2 tid=0x1] Initialization of
> region gatewayEventIdIndexMetaData completed
> [info 2018/03/12 11:01:43.944 CET server2 tid=0x1]
> ConcurrentParallelGatewaySenderEventProcessor: dispatcher threads 1
> [info 2018/03/12 11:01:43.953 CET server2 tid=0x1] Started
> ParallelGatewaySender{id=AsyncEventQueue_userQueue,remoteDsId=-1,isRunning
> =true}
> [info 2018/03/12 11:01:43.985 CET server2 tid=0x1] Initializing region
> __PR
> [info 2018/03/12 11:01:43.989 CET server2 tid=0x1] Region __PR
> requesting initial image from 192.168.178.159(server1:23330):1025
> [info 2018/03/12 11:01:44.001 CET server2 Processor 2> tid=0x32] Adding: PdxType[dsid=0, typenum=2161953
> name=java.util.Collections$UnmodifiableSet
> fields=[
> c:Object:0:idx0(relativeOffset)=0:idx1(vlfOffsetIndex)=-1
> empty:boolean:1:idx0(relativeOffset)=-1:idx1(vlfOffsetIndex)=-1]]
> [info 2018/03/12 11:01:44.005 CET server2 tid=0x1] __PR failed to get
> image from 192.168.178.159(server1:23330):1025
> [warning 2018/03/12 11:01:44.006 CET server2 tid=0x1] Initialization
> failed for Region /__PR
> org.apache.geode.SerializationException: Could not create an instance of
> org.apache.geode.internal.cache.PartitionRegionConfig .
> at Remote Member '192.168.178.159(server2:24615):1026' in
> org.apache.geode.internal.InternalDataSerializer.invokeFromData(InternalDataSerializer.java:2474)
> at Remote Member '192.168.178.159(server2:24615):1026' in
> org.apache.geode.internal.DSFIDFactory.create(DSFIDFactory.java:990)
> at Remote Member '192.168.178.159(server2:24615):1026' in
> org.apache.geode.internal.InternalDataSerializer.basicReadObject(InternalDataSerializer.java:2784)
>
[jira] [Updated] (GEODE-4822) The second server instance startup error: Could not create an instance of PartitionRegionConfig
[
https://issues.apache.org/jira/browse/GEODE-4822?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ASF GitHub Bot updated GEODE-4822:
--
Labels: pull-request-available (was: )
> The second server instance startup error: Could not create an instance of
> PartitionRegionConfig
> ---
>
> Key: GEODE-4822
> URL: https://issues.apache.org/jira/browse/GEODE-4822
> Project: Geode
> Issue Type: Bug
> Components: serialization
>Reporter: Vlad Ermolaev
>Priority: Major
> Labels: pull-request-available
>
> I have a simple configuration containing a partitioned persistent region and
> an async queue:
> {code:xml}
> dispatcher-threads="1" enable-batch-conflation="true" batch-size="10"
> batch-time-interval="10">
>
> test.geode.UserQueueListener
>
>
>
>
> test.geode.util.PdxSerializerWrapper
>
>
>
> async-event-queue-ids="userQueue">
> java.lang.Long
> test.geode.domain.User
>
>
> {code}
>
> The first server instance successfully started.
> But the second one in always failing on startup. The problem disappears if I
> remove the config or disable PDX serialization.
> Here is the stacktrace of the failed instance:
> {code}
> [info 2018/03/12 11:01:43.880 CET server2 tid=0x1] Initializing region
> PdxTypes
> [info 2018/03/12 11:01:43.893 CET server2 tid=0x1] Region PdxTypes
> requesting initial image from 192.168.178.159(server1:23330):1025
> [info 2018/03/12 11:01:43.897 CET server2 tid=0x1] PdxTypes is done
> getting image from 192.168.178.159(server1:23330):1025. isDeltaGII is true
> [info 2018/03/12 11:01:43.897 CET server2 tid=0x1] Region PdxTypes
> initialized persistent id:
> /192.168.178.159:/u01/home/chet/projects/geode/server2/store/pdx created at
> timestamp 1520848903878 version 0 diskStoreId
> 9d7c3e96b525418d-ae5b85e1966f3a51 name server2 with data from
> 192.168.178.159(server1:23330):1025.
> [info 2018/03/12 11:01:43.897 CET server2 tid=0x1] Initialization of
> region PdxTypes completed
> [info 2018/03/12 11:01:43.901 CET server2 tid=0x1] Recovered disk
> store mainStore with unique id 11c1012c13d04a3e-9309c26560d9fd33
> [info 2018/03/12 11:01:43.902 CET server2 tid=0x1] recovery region
> initialization took 0 ms
> [info 2018/03/12 11:01:43.907 CET server2 tid=0x1] Created disk store
> queueStore with unique id 308f63b00ee045f9-a6cfaea88f894c7a
> [info 2018/03/12 11:01:43.908 CET server2 tid=0x1] recovery region
> initialization took 0 ms
> [info 2018/03/12 11:01:43.929 CET server2 tid=0x1] Initializing region
> gatewayEventIdIndexMetaData
> [info 2018/03/12 11:01:43.933 CET server2 tid=0x1] Region
> gatewayEventIdIndexMetaData requesting initial image from
> 192.168.178.159(server1:23330):1025
> [info 2018/03/12 11:01:43.935 CET server2 tid=0x1]
> gatewayEventIdIndexMetaData is done getting image from
> 192.168.178.159(server1:23330):1025. isDeltaGII is false
> [info 2018/03/12 11:01:43.935 CET server2 tid=0x1] Initialization of
> region gatewayEventIdIndexMetaData completed
> [info 2018/03/12 11:01:43.944 CET server2 tid=0x1]
> ConcurrentParallelGatewaySenderEventProcessor: dispatcher threads 1
> [info 2018/03/12 11:01:43.953 CET server2 tid=0x1] Started
> ParallelGatewaySender{id=AsyncEventQueue_userQueue,remoteDsId=-1,isRunning
> =true}
> [info 2018/03/12 11:01:43.985 CET server2 tid=0x1] Initializing region
> __PR
> [info 2018/03/12 11:01:43.989 CET server2 tid=0x1] Region __PR
> requesting initial image from 192.168.178.159(server1:23330):1025
> [info 2018/03/12 11:01:44.001 CET server2 Processor 2> tid=0x32] Adding: PdxType[dsid=0, typenum=2161953
> name=java.util.Collections$UnmodifiableSet
> fields=[
> c:Object:0:idx0(relativeOffset)=0:idx1(vlfOffsetIndex)=-1
> empty:boolean:1:idx0(relativeOffset)=-1:idx1(vlfOffsetIndex)=-1]]
> [info 2018/03/12 11:01:44.005 CET server2 tid=0x1] __PR failed to get
> image from 192.168.178.159(server1:23330):1025
> [warning 2018/03/12 11:01:44.006 CET server2 tid=0x1] Initialization
> failed for Region /__PR
> org.apache.geode.SerializationException: Could not create an instance of
> org.apache.geode.internal.cache.PartitionRegionConfig .
> at Remote Member '192.168.178.159(server2:24615):1026' in
> org.apache.geode.internal.InternalDataSerializer.invokeFromData(InternalDataSerializer.java:2474)
> at Remote Member '192.168.178.159(server2:24615):1026' in
> org.apache.geode.internal.DSFIDFactory.create(DSFIDFactory.java:990)
> at Remote Member '192.168.178.159(server2:24615):1026' in
> org.apache.geode.internal.InternalDataSerializer.basicReadObject(InternalDataSerializer.java:2784)
> at Remote Member '192.168.178.159(server2:24615):1026' in
>
[jira] [Resolved] (GEODE-4851) Update minimum CMake to 3.10
[ https://issues.apache.org/jira/browse/GEODE-4851?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jacob S. Barrett resolved GEODE-4851. - Resolution: Fixed > Update minimum CMake to 3.10 > > > Key: GEODE-4851 > URL: https://issues.apache.org/jira/browse/GEODE-4851 > Project: Geode > Issue Type: Improvement > Components: native client >Reporter: Jacob S. Barrett >Assignee: Jacob S. Barrett >Priority: Major > > * Adds support for discovering and running gtests without duplicating logic. > * Previous releases add support for CSharp language. > Update packer scripts to get latest CMake on all platforms if not already > doing so. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-4851) Update minimum CMake to 3.10
[ https://issues.apache.org/jira/browse/GEODE-4851?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16402391#comment-16402391 ] Jacob S. Barrett commented on GEODE-4851: - Fixed in 60705358a0e777c24f6f3ee4e95fdb5e1ef50baf > Update minimum CMake to 3.10 > > > Key: GEODE-4851 > URL: https://issues.apache.org/jira/browse/GEODE-4851 > Project: Geode > Issue Type: Improvement > Components: native client >Reporter: Jacob S. Barrett >Assignee: Jacob S. Barrett >Priority: Major > > * Adds support for discovering and running gtests without duplicating logic. > * Previous releases add support for CSharp language. > Update packer scripts to get latest CMake on all platforms if not already > doing so. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (GEODE-4874) errors in gfsh help for create jndi-binding
[
https://issues.apache.org/jira/browse/GEODE-4874?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Barbara Pruijn updated GEODE-4874:
--
Description:
I see an error and an inconsistency when trying to use the gfsh help
functionality for create jndi-binding.
Tab completion of
create jndi-binding
outputs
gfsh>create jndi-binding –
create jndi-binding --connection-url
create jndi-binding --jdbc-driver-class
create jndi-binding --name
create jndi-binding --type
This is inconsistent with the output of other tab completions, which just give
the options, and do not repeat the "create jndi-binding" portion of the command.
was:
I see an error and an inconsistency when trying to use the gfsh help
functionality for create jndi-binding.
Tab completion of
create jndi-binding
outputs
gfsh>create jndi-binding –
create jndi-binding --connection-url
create jndi-binding --jdbc-driver-class
create jndi-binding --name
create jndi-binding --type
This is inconsistent with the output of other tab completions, which just give
the options, and do not repeat the "create jndi-binding" portion of the command.
All 3 of
# help create jndi-binding
# help "create jndi-binding"
# help --command="create jndi-binding"
cause this error output
{quote}gfsh>help create jndi-binding
[error 2018/03/16 10:02:15.956 PDT tid=0x1e] Could not execute
"help create jndi-binding".
java.lang.StringIndexOutOfBoundsException: String index out of range: -1
at java.lang.String.substring(String.java:1967)
at org.apache.geode.management.internal.cli.shell.Gfsh.wrapText(Gfsh.java:421)
at
org.apache.geode.management.internal.cli.help.HelpBlock.toString(HelpBlock.java:79)
at
org.apache.geode.management.internal.cli.help.HelpBlock.toString(HelpBlock.java:83)
at
org.apache.geode.management.internal.cli.help.HelpBlock.toString(HelpBlock.java:83)
at
org.apache.geode.management.internal.cli.help.HelpBlock.toString(HelpBlock.java:83)
at org.apache.geode.management.internal.cli.help.Helper.getHelp(Helper.java:145)
at
org.apache.geode.management.internal.cli.CommandManager.obtainHelp(CommandManager.java:311)
at
org.apache.geode.management.internal.cli.commands.GfshHelpCommand.obtainHelp(GfshHelpCommand.java:42)
at sun.reflect.GeneratedMethodAccessor7.invoke(Unknown Source)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at
org.springframework.util.ReflectionUtils.invokeMethod(ReflectionUtils.java:216)
at
org.apache.geode.management.internal.cli.remote.CommandExecutor.invokeCommand(CommandExecutor.java:97)
at
org.apache.geode.management.internal.cli.remote.CommandExecutor.execute(CommandExecutor.java:45)
at
org.apache.geode.management.internal.cli.remote.CommandExecutor.execute(CommandExecutor.java:39)
at
org.apache.geode.management.internal.cli.shell.GfshExecutionStrategy.execute(GfshExecutionStrategy.java:81)
at
org.springframework.shell.core.AbstractShell.executeCommand(AbstractShell.java:134)
at
org.apache.geode.management.internal.cli.shell.Gfsh.promptLoop(Gfsh.java:1011)
at org.springframework.shell.core.JLineShell.run(JLineShell.java:179)
at java.lang.Thread.run(Thread.java:748)
Could not process command due to error. Error while processing command Reason : String index out of range: -1
{quote}
> errors in gfsh help for create jndi-binding
>
>
> Key: GEODE-4874
> URL: https://issues.apache.org/jira/browse/GEODE-4874
> Project: Geode
> Issue Type: Bug
> Components: gfsh
>Affects Versions: 1.5.0
>Reporter: Karen Smoler Miller
>Priority: Minor
>
> I see an error and an inconsistency when trying to use the gfsh help
> functionality for create jndi-binding.
> Tab completion of
> create jndi-binding
> outputs
> gfsh>create jndi-binding –
> create jndi-binding --connection-url
> create jndi-binding --jdbc-driver-class
> create jndi-binding --name
> create jndi-binding --type
> This is inconsistent with the output of other tab completions, which just
> give the options, and do not repeat the "create jndi-binding" portion of the
> command.
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Comment Edited] (GEODE-4497) Command help create gateway-sender returns error if window size is 80 columns wide
[
https://issues.apache.org/jira/browse/GEODE-4497?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16402377#comment-16402377
]
Barbara Pruijn edited comment on GEODE-4497 at 3/16/18 7:28 PM:
This is especially pronounced in the command:
{code:java}
create jndi-binding{code}
All 3 of
help create jndi-binding
help "create jndi-binding"
help --command="create jndi-binding"
cause this error output
was (Author: bpruijn):
This is especially pronounced in the command:
{code:java}
create jndi-binding{code}
> Command help create gateway-sender returns error if window size is 80 columns
> wide
> --
>
> Key: GEODE-4497
> URL: https://issues.apache.org/jira/browse/GEODE-4497
> Project: Geode
> Issue Type: Bug
> Components: gfsh
>Reporter: Barbara Pruijn
>Priority: Major
>
> If you use the standard window size (25 rows; 80 columns) and run the
> following command in gfsh:
> {code}help create gateway-sender{code}
> you get the following error:
> {noformat}
> gfsh>help create gateway-sender
> [error 2018/02/01 14:35:22.359 PST tid=0x20] Could not
> execute "help create gateway-sender".
> java.lang.StringIndexOutOfBoundsException: String index out of range: -1
> at java.lang.String.substring(String.java:1967)
> at
> org.apache.geode.management.internal.cli.shell.Gfsh.wrapText(Gfsh.java:418)
> at
> org.apache.geode.management.internal.cli.help.HelpBlock.toString(HelpBlock.java:79)
> at
> org.apache.geode.management.internal.cli.help.HelpBlock.toString(HelpBlock.java:83)
> at
> org.apache.geode.management.internal.cli.help.HelpBlock.toString(HelpBlock.java:83)
> at
> org.apache.geode.management.internal.cli.help.HelpBlock.toString(HelpBlock.java:83)
> at
> org.apache.geode.management.internal.cli.help.Helper.getHelp(Helper.java:145)
> at
> org.apache.geode.management.internal.cli.CommandManager.obtainHelp(CommandManager.java:310)
> at
> org.apache.geode.management.internal.cli.commands.GfshHelpCommand.obtainHelp(GfshHelpCommand.java:42)
> 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
> org.springframework.util.ReflectionUtils.invokeMethod(ReflectionUtils.java:216)
> at
> org.apache.geode.management.internal.cli.remote.CommandExecutor.invokeCommand(CommandExecutor.java:97)
> at
> org.apache.geode.management.internal.cli.remote.CommandExecutor.execute(CommandExecutor.java:45)
> at
> org.apache.geode.management.internal.cli.remote.CommandExecutor.execute(CommandExecutor.java:39)
> at
> org.apache.geode.management.internal.cli.shell.GfshExecutionStrategy.execute(GfshExecutionStrategy.java:81)
> at
> org.springframework.shell.core.AbstractShell.executeCommand(AbstractShell.java:134)
> at
> org.apache.geode.management.internal.cli.shell.Gfsh.promptLoop(Gfsh.java:1008)
> at org.springframework.shell.core.JLineShell.run(JLineShell.java:179)
> at java.lang.Thread.run(Thread.java:748)
> Could not process command due to error. Error while processing command create gateway-sender> Reason : String index out of range: -1
> {noformat}
> If you make the window wider and run the command again, it runs fine.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (GEODE-4497) Command help create gateway-sender returns error if window size is 80 columns wide
[
https://issues.apache.org/jira/browse/GEODE-4497?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16402377#comment-16402377
]
Barbara Pruijn commented on GEODE-4497:
---
This is especially pronounced in the command:
{code:java}
create jndi-binding{code}
> Command help create gateway-sender returns error if window size is 80 columns
> wide
> --
>
> Key: GEODE-4497
> URL: https://issues.apache.org/jira/browse/GEODE-4497
> Project: Geode
> Issue Type: Bug
> Components: gfsh
>Reporter: Barbara Pruijn
>Priority: Major
>
> If you use the standard window size (25 rows; 80 columns) and run the
> following command in gfsh:
> {code}help create gateway-sender{code}
> you get the following error:
> {noformat}
> gfsh>help create gateway-sender
> [error 2018/02/01 14:35:22.359 PST tid=0x20] Could not
> execute "help create gateway-sender".
> java.lang.StringIndexOutOfBoundsException: String index out of range: -1
> at java.lang.String.substring(String.java:1967)
> at
> org.apache.geode.management.internal.cli.shell.Gfsh.wrapText(Gfsh.java:418)
> at
> org.apache.geode.management.internal.cli.help.HelpBlock.toString(HelpBlock.java:79)
> at
> org.apache.geode.management.internal.cli.help.HelpBlock.toString(HelpBlock.java:83)
> at
> org.apache.geode.management.internal.cli.help.HelpBlock.toString(HelpBlock.java:83)
> at
> org.apache.geode.management.internal.cli.help.HelpBlock.toString(HelpBlock.java:83)
> at
> org.apache.geode.management.internal.cli.help.Helper.getHelp(Helper.java:145)
> at
> org.apache.geode.management.internal.cli.CommandManager.obtainHelp(CommandManager.java:310)
> at
> org.apache.geode.management.internal.cli.commands.GfshHelpCommand.obtainHelp(GfshHelpCommand.java:42)
> 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
> org.springframework.util.ReflectionUtils.invokeMethod(ReflectionUtils.java:216)
> at
> org.apache.geode.management.internal.cli.remote.CommandExecutor.invokeCommand(CommandExecutor.java:97)
> at
> org.apache.geode.management.internal.cli.remote.CommandExecutor.execute(CommandExecutor.java:45)
> at
> org.apache.geode.management.internal.cli.remote.CommandExecutor.execute(CommandExecutor.java:39)
> at
> org.apache.geode.management.internal.cli.shell.GfshExecutionStrategy.execute(GfshExecutionStrategy.java:81)
> at
> org.springframework.shell.core.AbstractShell.executeCommand(AbstractShell.java:134)
> at
> org.apache.geode.management.internal.cli.shell.Gfsh.promptLoop(Gfsh.java:1008)
> at org.springframework.shell.core.JLineShell.run(JLineShell.java:179)
> at java.lang.Thread.run(Thread.java:748)
> Could not process command due to error. Error while processing command create gateway-sender> Reason : String index out of range: -1
> {noformat}
> If you make the window wider and run the command again, it runs fine.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (GEODE-4872) JdbcReader throws serialization exception for byte[] when the field type is Object
[
https://issues.apache.org/jira/browse/GEODE-4872?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Darrel Schneider updated GEODE-4872:
Affects Version/s: (was: 1.4.0)
1.6.0
> JdbcReader throws serialization exception for byte[] when the field type is
> Object
> --
>
> Key: GEODE-4872
> URL: https://issues.apache.org/jira/browse/GEODE-4872
> Project: Geode
> Issue Type: Bug
> Components: extensions, regions
>Affects Versions: 1.6.0
>Reporter: Anilkumar Gingade
>Priority: Major
>
> JdbcReader when creating PdxInstance throws serialization exception for
> byte[] when its field type is treated as Object. This field is mapped in the
> table as blob column.
> {noformat}
> Caused by: org.apache.geode.cache.client.ServerOperationException: remote
> server on 10.118.33.196(66546:loner):64576:da7cbe2f:
> org.apache.geode.pdx.PdxSerializationException: Exception while serializing a
> PDX field
> at
> org.apache.geode.cache.client.internal.OpExecutorImpl.handleException(OpExecutorImpl.java:680)
> at
> org.apache.geode.cache.client.internal.OpExecutorImpl.handleException(OpExecutorImpl.java:739)
> at
> org.apache.geode.cache.client.internal.OpExecutorImpl.handleException(OpExecutorImpl.java:622)
> at
> org.apache.geode.cache.client.internal.OpExecutorImpl.execute(OpExecutorImpl.java:179)
> at
> org.apache.geode.cache.client.internal.OpExecutorImpl.execute(OpExecutorImpl.java:127)
> at
> org.apache.geode.cache.client.internal.PoolImpl.execute(PoolImpl.java:782)
> at org.apache.geode.cache.client.internal.GetOp.execute(GetOp.java:91)
> at
> org.apache.geode.cache.client.internal.ServerRegionProxy.get(ServerRegionProxy.java:113)
> at
> org.apache.geode.internal.cache.LocalRegion.findObjectInSystem(LocalRegion.java:2768)
> at
> org.apache.geode.internal.cache.LocalRegion.nonTxnFindObject(LocalRegion.java:1490)
> at
> org.apache.geode.internal.cache.LocalRegionDataView.findObject(LocalRegionDataView.java:176)
> at org.apache.geode.internal.cache.LocalRegion.get(LocalRegion.java:1379)
> at org.apache.geode.internal.cache.LocalRegion.get(LocalRegion.java:1313)
> at org.apache.geode.internal.cache.LocalRegion.get(LocalRegion.java:1298)
> at
> org.apache.geode.internal.cache.AbstractRegion.get(AbstractRegion.java:313)
> at
> org.apache.geode.connectors.jdbc.JdbcDUnitTest.lambda$clientGetReadsFromDBWithPdxClassName$bb17a952$1(JdbcDUnitTest.java:348)
> 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 hydra.MethExecutor.executeObject(MethExecutor.java:244)
> at
> org.apache.geode.test.dunit.standalone.RemoteDUnitVM.executeMethodOnObject(RemoteDUnitVM.java:70)
> 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 sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:357)
> at sun.rmi.transport.Transport$1.run(Transport.java:200)
> at sun.rmi.transport.Transport$1.run(Transport.java:197)
> at java.security.AccessController.doPrivileged(Native Method)
> at sun.rmi.transport.Transport.serviceCall(Transport.java:196)
> at
> sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:568)
> at
> sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run0(TCPTransport.java:826)
> at
> sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.lambda$run$0(TCPTransport.java:683)
> at java.security.AccessController.doPrivileged(Native Method)
> at
> sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:682)
> 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)
> Caused by: org.apache.geode.pdx.PdxSerializationException: Exception while
> serializing a PDX field
> at
> org.apache.geode.pdx.internal.PdxOutputStream.writeObject(PdxOutputStream.java:84)
> at
> org.apache.geode.pdx.internal.PdxWriterImpl.writeObject(PdxWriterImpl.java:329)
> at
> org.apache.geode.pdx.internal.PdxInstanceFactoryImpl.writeObject(PdxInstanceFactoryImpl.java:210)
> at
>
[jira] [Updated] (GEODE-4865) JdbcConnector to allow pdx-field and table-column to be excluded
[ https://issues.apache.org/jira/browse/GEODE-4865?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Darrel Schneider updated GEODE-4865: Issue Type: Improvement (was: Bug) > JdbcConnector to allow pdx-field and table-column to be excluded > > > Key: GEODE-4865 > URL: https://issues.apache.org/jira/browse/GEODE-4865 > Project: Geode > Issue Type: Improvement > Components: extensions, regions >Reporter: Anilkumar Gingade >Priority: Major > > The user should be able to choose the pdx fields whose values to be written > to the table. And specify the columns whose values to be read to build Pdx > object. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (GEODE-4865) JdbcConnector to allow pdx-field and table-column to be excluded
[ https://issues.apache.org/jira/browse/GEODE-4865?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Darrel Schneider updated GEODE-4865: Affects Version/s: (was: 1.5.0) > JdbcConnector to allow pdx-field and table-column to be excluded > > > Key: GEODE-4865 > URL: https://issues.apache.org/jira/browse/GEODE-4865 > Project: Geode > Issue Type: Bug > Components: extensions, regions >Reporter: Anilkumar Gingade >Priority: Major > > The user should be able to choose the pdx fields whose values to be written > to the table. And specify the columns whose values to be read to build Pdx > object. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (GEODE-4876) Add VM APIs from Host to DistributedTestRule
Kirk Lund created GEODE-4876: Summary: Add VM APIs from Host to DistributedTestRule Key: GEODE-4876 URL: https://issues.apache.org/jira/browse/GEODE-4876 Project: Geode Issue Type: Improvement Components: tests Reporter: Kirk Lund Add DistributedTestRule constructor which accepts vmCount so that DistributedTestRule can provision DUnit VMs for other rules, such as DistributedRestoreSystemProperties, to use. Add getVM(int), getAllVMs() to DistributedTestRule. Change tests that use DistributedTestRule to use its new APIs instead of Host. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (GEODE-4876) Add VM APIs from Host to DistributedTestRule
[ https://issues.apache.org/jira/browse/GEODE-4876?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kirk Lund reassigned GEODE-4876: Assignee: Kirk Lund > Add VM APIs from Host to DistributedTestRule > > > Key: GEODE-4876 > URL: https://issues.apache.org/jira/browse/GEODE-4876 > Project: Geode > Issue Type: Improvement > Components: tests >Reporter: Kirk Lund >Assignee: Kirk Lund >Priority: Major > > Add DistributedTestRule constructor which accepts vmCount so that > DistributedTestRule can provision DUnit VMs for other rules, such as > DistributedRestoreSystemProperties, to use. > Add getVM(int), getAllVMs() to DistributedTestRule. > Change tests that use DistributedTestRule to use its new APIs instead of Host. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (GEODE-4769) Serialize region entry before putting in local cache
[ https://issues.apache.org/jira/browse/GEODE-4769?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Fred Krone updated GEODE-4769: -- Fix Version/s: (was: 1.5.0) 1.6.0 > Serialize region entry before putting in local cache > > > Key: GEODE-4769 > URL: https://issues.apache.org/jira/browse/GEODE-4769 > Project: Geode > Issue Type: Improvement > Components: regions >Reporter: Kirk Lund >Assignee: Kirk Lund >Priority: Major > Labels: pull-request-available > Fix For: 1.6.0 > > Time Spent: 2h 20m > Remaining Estimate: 0h > > This will prevent cache inconsistency when dealing with key or value objects > that have broken serialization. > Test should create two members with a REPLICATE region. If one member > performs a put, but the serialization fails then the region entry currently > ends up existing in only the cache of the member that performed the put > locally. The change will prevent this from occurring. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-4868) when member deposed primary buckets, it did not decrease the queue size
[
https://issues.apache.org/jira/browse/GEODE-4868?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16402283#comment-16402283
]
ASF subversion and git services commented on GEODE-4868:
Commit d48607d51f718a6c497d7e6b14a8dc9b87fe2e67 in geode's branch
refs/heads/develop from Xiaojian Zhou
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=d48607d ]
GEODE-4868: depose primary should reduce brq's size in
deposePrimaryForColocatedChildren (#1625)
> when member deposed primary buckets, it did not decrease the queue size
> ---
>
> Key: GEODE-4868
> URL: https://issues.apache.org/jira/browse/GEODE-4868
> Project: Geode
> Issue Type: Bug
> Components: wan
>Reporter: xiaojian zhou
>Assignee: xiaojian zhou
>Priority: Major
> Labels: pull-request-available
> Time Spent: 20m
> Remaining Estimate: 0h
>
> {noformat}
> It can use following test code to reproduce the issue:
> diff --git
> a/geode-core/src/test/java/org/apache/geode/internal/cache/wan/AsyncEventQueueTestBase.java
>
> b/geode-core/src/test/java/org/apache/geode/internal/cache/wan/AsyncEventQueueTestBase.java
> index 545d0cac4..fbc0dc015 100644
> ---
> a/geode-core/src/test/java/org/apache/geode/internal/cache/wan/AsyncEventQueueTestBase.java
> +++
> b/geode-core/src/test/java/org/apache/geode/internal/cache/wan/AsyncEventQueueTestBase.java
> @@ -717,6 +717,10 @@ public class AsyncEventQueueTestBase extends
> JUnit4DistributedTestCase {
> }
> }
> final AsyncEventQueueStats statistics = ((AsyncEventQueueImpl)
> queue).getStatistics();
> + Awaitility.await().atMost(60, TimeUnit.SECONDS)
> + .until(() -> assertEquals("Expected queue entries: " + queueSize
> + + " but actual entries: " + statistics.getEventQueueSize(),
> queueSize,
> + statistics.getEventQueueSize()));
> assertEquals(queueSize, statistics.getEventQueueSize());
> assertEquals(eventsReceived, statistics.getEventsReceived());
> diff --git
> a/geode-core/src/test/java/org/apache/geode/internal/cache/wan/asyncqueue/AsyncEventListenerDUnitTest.java
>
> b/geode-core/src/test/java/org/apache/geode/internal/cache/wan/asyncqueue/AsyncEventListenerDUnitTest.java
> index 465f35a87..058bf19cc 100644
> ---
> a/geode-core/src/test/java/org/apache/geode/internal/cache/wan/asyncqueue/AsyncEventListenerDUnitTest.java
> +++
> b/geode-core/src/test/java/org/apache/geode/internal/cache/wan/asyncqueue/AsyncEventListenerDUnitTest.java
> @@ -1519,6 +1519,11 @@ public class AsyncEventListenerDUnitTest extends
> AsyncEventQueueTestBase {
> () ->
> AsyncEventQueueTestBase.getAllPrimaryBucketsOnTheNode(getTestMethodName() +
> "_PR"));
>
> LogWriterUtils.getLogWriter().info("Primary buckets on vm2: " +
> primaryBucketsvm2);
> +
> + // before shutdown vm2, both vm1 and vm2 should have 40 events in
> primary queue
> + vm1.invoke(()->AsyncEventQueueTestBase.checkAsyncEventQueueStats("ln",
> 40,
> 80, 80, 0));
> + vm2.invoke(()->AsyncEventQueueTestBase.checkAsyncEventQueueStats("ln",
> 40, 80, 80, 0));
> +
> // Kill vm2 --
> vm2.invoke(() -> AsyncEventQueueTestBase.killSender());
> //
> @@ -1527,15 +1532,26 @@ public class AsyncEventListenerDUnitTest extends
> AsyncEventQueueTestBase {
> vm3.invoke(createCacheRunnable(lnPort));
> vm3.invoke(() ->
> AsyncEventQueueTestBase.createAsyncEventQueueWithListener2("ln", true, 100, 5,
> false, null));
> + // vm3 will move some primary buckets from vm1, but vm1's primary queue
> size did not reduce
> + vm3.invoke(pauseAsyncEventQueueRunnable());
> vm3.invoke(() ->
> AsyncEventQueueTestBase.createPRWithRedundantCopyWithAsyncEventQueue(
> getTestMethodName() + "_PR", "ln", isOffHeap()));
> -
> +
> // --
> String regionName = getTestMethodName() + "_PR";
> Set primaryBucketsvm3 = (Set) vm3
> .invoke(() ->
> AsyncEventQueueTestBase.getAllPrimaryBucketsOnTheNode(regionName));
> + LogWriterUtils.getLogWriter().info("Primary buckets on vm3: " +
> primaryBucketsvm3);
> + Set primaryBucketsvm1 = (Set) vm1.invoke(
> + () ->
> AsyncEventQueueTestBase.getAllPrimaryBucketsOnTheNode(getTestMethodName() +
> "_PR"));
> + LogWriterUtils.getLogWriter().info("After shutdown vm2, started vm3,
> Primary buckets on vm1: " + primaryBucketsvm1);
>
> +// vm1.invoke(()->AsyncEventQueueTestBase.checkAsyncEventQueueStats("ln",
> 80, 80, 80, 0));
> + vm1.invoke(()->AsyncEventQueueTestBase.checkAsyncEventQueueStats("ln",
> 40, 80, 80, 0));
>
[jira] [Updated] (GEODE-4874) errors in gfsh help for create jndi-binding
[
https://issues.apache.org/jira/browse/GEODE-4874?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Barbara Pruijn updated GEODE-4874:
--
Priority: Minor (was: Major)
> errors in gfsh help for create jndi-binding
>
>
> Key: GEODE-4874
> URL: https://issues.apache.org/jira/browse/GEODE-4874
> Project: Geode
> Issue Type: Bug
> Components: gfsh
>Affects Versions: 1.5.0
>Reporter: Karen Smoler Miller
>Priority: Minor
>
> I see an error and an inconsistency when trying to use the gfsh help
> functionality for create jndi-binding.
> Tab completion of
> create jndi-binding
> outputs
> gfsh>create jndi-binding –
> create jndi-binding --connection-url
> create jndi-binding --jdbc-driver-class
> create jndi-binding --name
> create jndi-binding --type
> This is inconsistent with the output of other tab completions, which just
> give the options, and do not repeat the "create jndi-binding" portion of the
> command.
> All 3 of
> # help create jndi-binding
> # help "create jndi-binding"
> # help --command="create jndi-binding"
> cause this error output
> {quote}gfsh>help create jndi-binding
> [error 2018/03/16 10:02:15.956 PDT tid=0x1e] Could not
> execute "help create jndi-binding".
> java.lang.StringIndexOutOfBoundsException: String index out of range: -1
> at java.lang.String.substring(String.java:1967)
> at org.apache.geode.management.internal.cli.shell.Gfsh.wrapText(Gfsh.java:421)
> at
> org.apache.geode.management.internal.cli.help.HelpBlock.toString(HelpBlock.java:79)
> at
> org.apache.geode.management.internal.cli.help.HelpBlock.toString(HelpBlock.java:83)
> at
> org.apache.geode.management.internal.cli.help.HelpBlock.toString(HelpBlock.java:83)
> at
> org.apache.geode.management.internal.cli.help.HelpBlock.toString(HelpBlock.java:83)
> at
> org.apache.geode.management.internal.cli.help.Helper.getHelp(Helper.java:145)
> at
> org.apache.geode.management.internal.cli.CommandManager.obtainHelp(CommandManager.java:311)
> at
> org.apache.geode.management.internal.cli.commands.GfshHelpCommand.obtainHelp(GfshHelpCommand.java:42)
> at sun.reflect.GeneratedMethodAccessor7.invoke(Unknown Source)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at
> org.springframework.util.ReflectionUtils.invokeMethod(ReflectionUtils.java:216)
> at
> org.apache.geode.management.internal.cli.remote.CommandExecutor.invokeCommand(CommandExecutor.java:97)
> at
> org.apache.geode.management.internal.cli.remote.CommandExecutor.execute(CommandExecutor.java:45)
> at
> org.apache.geode.management.internal.cli.remote.CommandExecutor.execute(CommandExecutor.java:39)
> at
> org.apache.geode.management.internal.cli.shell.GfshExecutionStrategy.execute(GfshExecutionStrategy.java:81)
> at
> org.springframework.shell.core.AbstractShell.executeCommand(AbstractShell.java:134)
> at
> org.apache.geode.management.internal.cli.shell.Gfsh.promptLoop(Gfsh.java:1011)
> at org.springframework.shell.core.JLineShell.run(JLineShell.java:179)
> at java.lang.Thread.run(Thread.java:748)
>
> Could not process command due to error. Error while processing command create jndi-binding> Reason : String index out of range: -1
>
> {quote}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (GEODE-4782) Categorize Gfsh tests
[ https://issues.apache.org/jira/browse/GEODE-4782?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated GEODE-4782: -- Labels: pull-request-available (was: ) > Categorize Gfsh tests > - > > Key: GEODE-4782 > URL: https://issues.apache.org/jira/browse/GEODE-4782 > Project: Geode > Issue Type: Bug > Components: gfsh >Affects Versions: 1.5.0 >Reporter: Kenneth Howe >Priority: Major > Labels: pull-request-available > > Add Category annotation for gfsh integration and distributed tests. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (GEODE-4874) errors in gfsh help for create jndi-binding
[
https://issues.apache.org/jira/browse/GEODE-4874?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Karen Smoler Miller updated GEODE-4874:
---
Affects Version/s: 1.5.0
> errors in gfsh help for create jndi-binding
>
>
> Key: GEODE-4874
> URL: https://issues.apache.org/jira/browse/GEODE-4874
> Project: Geode
> Issue Type: Bug
> Components: gfsh
>Affects Versions: 1.5.0
>Reporter: Karen Smoler Miller
>Priority: Major
>
> I see an error and an inconsistency when trying to use the gfsh help
> functionality for create jndi-binding.
> Tab completion of
> create jndi-binding
> outputs
> gfsh>create jndi-binding –
> create jndi-binding --connection-url
> create jndi-binding --jdbc-driver-class
> create jndi-binding --name
> create jndi-binding --type
> This is inconsistent with the output of other tab completions, which just
> give the options, and do not repeat the "create jndi-binding" portion of the
> command.
> All 3 of
> # help create jndi-binding
> # help "create jndi-binding"
> # help --command="create jndi-binding"
> cause this error output
> {quote}gfsh>help create jndi-binding
> [error 2018/03/16 10:02:15.956 PDT tid=0x1e] Could not
> execute "help create jndi-binding".
> java.lang.StringIndexOutOfBoundsException: String index out of range: -1
> at java.lang.String.substring(String.java:1967)
> at org.apache.geode.management.internal.cli.shell.Gfsh.wrapText(Gfsh.java:421)
> at
> org.apache.geode.management.internal.cli.help.HelpBlock.toString(HelpBlock.java:79)
> at
> org.apache.geode.management.internal.cli.help.HelpBlock.toString(HelpBlock.java:83)
> at
> org.apache.geode.management.internal.cli.help.HelpBlock.toString(HelpBlock.java:83)
> at
> org.apache.geode.management.internal.cli.help.HelpBlock.toString(HelpBlock.java:83)
> at
> org.apache.geode.management.internal.cli.help.Helper.getHelp(Helper.java:145)
> at
> org.apache.geode.management.internal.cli.CommandManager.obtainHelp(CommandManager.java:311)
> at
> org.apache.geode.management.internal.cli.commands.GfshHelpCommand.obtainHelp(GfshHelpCommand.java:42)
> at sun.reflect.GeneratedMethodAccessor7.invoke(Unknown Source)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at
> org.springframework.util.ReflectionUtils.invokeMethod(ReflectionUtils.java:216)
> at
> org.apache.geode.management.internal.cli.remote.CommandExecutor.invokeCommand(CommandExecutor.java:97)
> at
> org.apache.geode.management.internal.cli.remote.CommandExecutor.execute(CommandExecutor.java:45)
> at
> org.apache.geode.management.internal.cli.remote.CommandExecutor.execute(CommandExecutor.java:39)
> at
> org.apache.geode.management.internal.cli.shell.GfshExecutionStrategy.execute(GfshExecutionStrategy.java:81)
> at
> org.springframework.shell.core.AbstractShell.executeCommand(AbstractShell.java:134)
> at
> org.apache.geode.management.internal.cli.shell.Gfsh.promptLoop(Gfsh.java:1011)
> at org.springframework.shell.core.JLineShell.run(JLineShell.java:179)
> at java.lang.Thread.run(Thread.java:748)
>
> Could not process command due to error. Error while processing command create jndi-binding> Reason : String index out of range: -1
>
> {quote}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (GEODE-4874) errors in gfsh help for create jndi-binding
Karen Smoler Miller created GEODE-4874:
--
Summary: errors in gfsh help for create jndi-binding
Key: GEODE-4874
URL: https://issues.apache.org/jira/browse/GEODE-4874
Project: Geode
Issue Type: Bug
Components: gfsh
Reporter: Karen Smoler Miller
I see an error and an inconsistency when trying to use the gfsh help
functionality for create jndi-binding.
Tab completion of
create jndi-binding
outputs
gfsh>create jndi-binding –
create jndi-binding --connection-url
create jndi-binding --jdbc-driver-class
create jndi-binding --name
create jndi-binding --type
This is inconsistent with the output of other tab completions, which just give
the options, and do not repeat the "create jndi-binding" portion of the command.
All 3 of
# help create jndi-binding
# help "create jndi-binding"
# help --command="create jndi-binding"
cause this error output
{quote}gfsh>help create jndi-binding
[error 2018/03/16 10:02:15.956 PDT tid=0x1e] Could not execute
"help create jndi-binding".
java.lang.StringIndexOutOfBoundsException: String index out of range: -1
at java.lang.String.substring(String.java:1967)
at org.apache.geode.management.internal.cli.shell.Gfsh.wrapText(Gfsh.java:421)
at
org.apache.geode.management.internal.cli.help.HelpBlock.toString(HelpBlock.java:79)
at
org.apache.geode.management.internal.cli.help.HelpBlock.toString(HelpBlock.java:83)
at
org.apache.geode.management.internal.cli.help.HelpBlock.toString(HelpBlock.java:83)
at
org.apache.geode.management.internal.cli.help.HelpBlock.toString(HelpBlock.java:83)
at org.apache.geode.management.internal.cli.help.Helper.getHelp(Helper.java:145)
at
org.apache.geode.management.internal.cli.CommandManager.obtainHelp(CommandManager.java:311)
at
org.apache.geode.management.internal.cli.commands.GfshHelpCommand.obtainHelp(GfshHelpCommand.java:42)
at sun.reflect.GeneratedMethodAccessor7.invoke(Unknown Source)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at
org.springframework.util.ReflectionUtils.invokeMethod(ReflectionUtils.java:216)
at
org.apache.geode.management.internal.cli.remote.CommandExecutor.invokeCommand(CommandExecutor.java:97)
at
org.apache.geode.management.internal.cli.remote.CommandExecutor.execute(CommandExecutor.java:45)
at
org.apache.geode.management.internal.cli.remote.CommandExecutor.execute(CommandExecutor.java:39)
at
org.apache.geode.management.internal.cli.shell.GfshExecutionStrategy.execute(GfshExecutionStrategy.java:81)
at
org.springframework.shell.core.AbstractShell.executeCommand(AbstractShell.java:134)
at
org.apache.geode.management.internal.cli.shell.Gfsh.promptLoop(Gfsh.java:1011)
at org.springframework.shell.core.JLineShell.run(JLineShell.java:179)
at java.lang.Thread.run(Thread.java:748)
Could not process command due to error. Error while processing command Reason : String index out of range: -1
{quote}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (GEODE-4873) Javadocs on ProtobufUtilities are generating a warning
Kirk Lund created GEODE-4873:
Summary: Javadocs on ProtobufUtilities are generating a warning
Key: GEODE-4873
URL: https://issues.apache.org/jira/browse/GEODE-4873
Project: Geode
Issue Type: Bug
Components: client/server
Reporter: Kirk Lund
Javadocs on ProtobufUtilities are generating a warning:
{noformat}
/Users/klund/dev/gemfire_CLEAN/open/geode-protobuf/src/main/java/org/apache/geode/internal/protocol/protobuf/v1/utilities/ProtobufUtilities.java:33:
warning - Tag @link: reference not found: ProtobufRequestUtilities
{noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (GEODE-4715) ReconnectDUnitTest calls static methods to obtain cache and distributed system
[ https://issues.apache.org/jira/browse/GEODE-4715?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated GEODE-4715: -- Labels: pull-request-available (was: ) > ReconnectDUnitTest calls static methods to obtain cache and distributed system > -- > > Key: GEODE-4715 > URL: https://issues.apache.org/jira/browse/GEODE-4715 > Project: Geode > Issue Type: Sub-task > Components: membership >Reporter: Darrel Schneider >Assignee: Bruce Schuchardt >Priority: Major > Labels: pull-request-available > > Correct the component if "reconnect" is not a membership issue. > ReconnectDUnitTest calls static methods to obtain cache and distributed > system: > CacheFactory.getAnyInstance() > InternalDistributedSystem.getAnyInstance() > InternalDistributedSystem.getConnectedInstance() > It does this to verify that a reconnect completed and created a new cache and > system. > I think the existing "reconnect" feature has problems if geode gets rid of > the concept of a singleton cache. The current "reconnect" feature closes the > old cache and then creates a new one, that it thinks can be discovered using > the methods that return the static singleton. > So fixing this test may require a redesign of the reconnect feature. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (GEODE-4827) Cq should not be added to the cq map if cq's base region is null
[
https://issues.apache.org/jira/browse/GEODE-4827?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
nabarun closed GEODE-4827.
--
> Cq should not be added to the cq map if cq's base region is null
>
>
> Key: GEODE-4827
> URL: https://issues.apache.org/jira/browse/GEODE-4827
> Project: Geode
> Issue Type: Bug
> Components: cq
>Reporter: nabarun
>Priority: Major
> Labels: pull-request-available
> Fix For: 1.6.0
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> Currently while registering a cq if the cache is closing down , it throws an
> exception. but we ignore the exception and continue adding the cq to the map.
> While processing the closing of cq it will ask for the cq's base region which
> will be null. Thus ends with NPE because we end up calling methods on null
> region.
> Solution:
> put the addition of the cq to the cqMap inside a if check for base region
> {code:java}
> void processRegisterCq(String serverCqName, ServerCQ ServerCQ, boolean
> addToCqMap,
> GemFireCacheImpl cache) {
> ServerCQ cq = (ServerCQ) ServerCQ;
> try {
> CqService cqService = cache.getCqService();
> cqService.start();
> cq.setCqService(cqService);
> CqStateImpl cqState = (CqStateImpl) cq.getState();
> cq.setName(generateCqName(serverCqName));
> cq.registerCq(null, null, cqState.getState());
> } catch (Exception ex) {
> // Change it to Info level.
> logger.info("Error while initializing the CQs with FilterProfile for CQ
> {}, Error : {}",
> serverCqName, ex.getMessage(), ex);
> }
> if (logger.isDebugEnabled()) {
> logger.debug("Adding CQ to remote members FilterProfile using name:
> {}", serverCqName);
> }
> // The region's FilterProfile is accessed through CQ reference as the
> // region is not set on the FilterProfile created for the peer nodes.
> if (cq.getCqBaseRegion() != null) {
> if (addToCqMap) {
> this.cqs.put(serverCqName, cq);
> }
> FilterProfile pf = cq.getCqBaseRegion().getFilterProfile();
> if (pf != null) {
> pf.incCqCount();
> }
> }
> }
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (GEODE-4827) Cq should not be added to the cq map if cq's base region is null
[
https://issues.apache.org/jira/browse/GEODE-4827?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
nabarun resolved GEODE-4827.
Resolution: Fixed
Fix Version/s: 1.6.0
> Cq should not be added to the cq map if cq's base region is null
>
>
> Key: GEODE-4827
> URL: https://issues.apache.org/jira/browse/GEODE-4827
> Project: Geode
> Issue Type: Bug
> Components: cq
>Reporter: nabarun
>Priority: Major
> Labels: pull-request-available
> Fix For: 1.6.0
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> Currently while registering a cq if the cache is closing down , it throws an
> exception. but we ignore the exception and continue adding the cq to the map.
> While processing the closing of cq it will ask for the cq's base region which
> will be null. Thus ends with NPE because we end up calling methods on null
> region.
> Solution:
> put the addition of the cq to the cqMap inside a if check for base region
> {code:java}
> void processRegisterCq(String serverCqName, ServerCQ ServerCQ, boolean
> addToCqMap,
> GemFireCacheImpl cache) {
> ServerCQ cq = (ServerCQ) ServerCQ;
> try {
> CqService cqService = cache.getCqService();
> cqService.start();
> cq.setCqService(cqService);
> CqStateImpl cqState = (CqStateImpl) cq.getState();
> cq.setName(generateCqName(serverCqName));
> cq.registerCq(null, null, cqState.getState());
> } catch (Exception ex) {
> // Change it to Info level.
> logger.info("Error while initializing the CQs with FilterProfile for CQ
> {}, Error : {}",
> serverCqName, ex.getMessage(), ex);
> }
> if (logger.isDebugEnabled()) {
> logger.debug("Adding CQ to remote members FilterProfile using name:
> {}", serverCqName);
> }
> // The region's FilterProfile is accessed through CQ reference as the
> // region is not set on the FilterProfile created for the peer nodes.
> if (cq.getCqBaseRegion() != null) {
> if (addToCqMap) {
> this.cqs.put(serverCqName, cq);
> }
> FilterProfile pf = cq.getCqBaseRegion().getFilterProfile();
> if (pf != null) {
> pf.incCqCount();
> }
> }
> }
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (GEODE-4827) Cq should not be added to the cq map if cq's base region is null
[
https://issues.apache.org/jira/browse/GEODE-4827?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16402213#comment-16402213
]
ASF subversion and git services commented on GEODE-4827:
Commit c5b44019dd21847f9f79fc1fbfcf78df70f660e0 in geode's branch
refs/heads/develop from [~nabarunnag]
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=c5b4401 ]
GEODE-4827: CQ not added to cq map on exception (#1602)
* Log level set to info when FilterProfile gets an exception while
registering CQ
* Before, when there is an exception while registering cq like while
cache closing the cq's base region is null
* There is an exception which is logged in debug level but execution
continues and adds the cq to the cp map with base region set to null
* This results in a NullPointerException while closing cq as methods
are executed on null region
* Now the operation to put the cq into the cq map is inside a if check
for null cq base region.
> Cq should not be added to the cq map if cq's base region is null
>
>
> Key: GEODE-4827
> URL: https://issues.apache.org/jira/browse/GEODE-4827
> Project: Geode
> Issue Type: Bug
> Components: cq
>Reporter: nabarun
>Priority: Major
> Labels: pull-request-available
> Time Spent: 20m
> Remaining Estimate: 0h
>
> Currently while registering a cq if the cache is closing down , it throws an
> exception. but we ignore the exception and continue adding the cq to the map.
> While processing the closing of cq it will ask for the cq's base region which
> will be null. Thus ends with NPE because we end up calling methods on null
> region.
> Solution:
> put the addition of the cq to the cqMap inside a if check for base region
> {code:java}
> void processRegisterCq(String serverCqName, ServerCQ ServerCQ, boolean
> addToCqMap,
> GemFireCacheImpl cache) {
> ServerCQ cq = (ServerCQ) ServerCQ;
> try {
> CqService cqService = cache.getCqService();
> cqService.start();
> cq.setCqService(cqService);
> CqStateImpl cqState = (CqStateImpl) cq.getState();
> cq.setName(generateCqName(serverCqName));
> cq.registerCq(null, null, cqState.getState());
> } catch (Exception ex) {
> // Change it to Info level.
> logger.info("Error while initializing the CQs with FilterProfile for CQ
> {}, Error : {}",
> serverCqName, ex.getMessage(), ex);
> }
> if (logger.isDebugEnabled()) {
> logger.debug("Adding CQ to remote members FilterProfile using name:
> {}", serverCqName);
> }
> // The region's FilterProfile is accessed through CQ reference as the
> // region is not set on the FilterProfile created for the peer nodes.
> if (cq.getCqBaseRegion() != null) {
> if (addToCqMap) {
> this.cqs.put(serverCqName, cq);
> }
> FilterProfile pf = cq.getCqBaseRegion().getFilterProfile();
> if (pf != null) {
> pf.incCqCount();
> }
> }
> }
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (GEODE-4872) JdbcReader throws serialization exception for byte[] when the field type is Object
[
https://issues.apache.org/jira/browse/GEODE-4872?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anilkumar Gingade updated GEODE-4872:
-
Affects Version/s: 1.5.0
> JdbcReader throws serialization exception for byte[] when the field type is
> Object
> --
>
> Key: GEODE-4872
> URL: https://issues.apache.org/jira/browse/GEODE-4872
> Project: Geode
> Issue Type: Bug
> Components: extensions, regions
>Affects Versions: 1.5.0
>Reporter: Anilkumar Gingade
>Priority: Major
>
> JdbcReader when creating PdxInstance throws serialization exception for
> byte[] when its field type is treated as Object. This field is mapped in the
> table as blob column.
> {noformat}
> Caused by: org.apache.geode.cache.client.ServerOperationException: remote
> server on 10.118.33.196(66546:loner):64576:da7cbe2f:
> org.apache.geode.pdx.PdxSerializationException: Exception while serializing a
> PDX field
> at
> org.apache.geode.cache.client.internal.OpExecutorImpl.handleException(OpExecutorImpl.java:680)
> at
> org.apache.geode.cache.client.internal.OpExecutorImpl.handleException(OpExecutorImpl.java:739)
> at
> org.apache.geode.cache.client.internal.OpExecutorImpl.handleException(OpExecutorImpl.java:622)
> at
> org.apache.geode.cache.client.internal.OpExecutorImpl.execute(OpExecutorImpl.java:179)
> at
> org.apache.geode.cache.client.internal.OpExecutorImpl.execute(OpExecutorImpl.java:127)
> at
> org.apache.geode.cache.client.internal.PoolImpl.execute(PoolImpl.java:782)
> at org.apache.geode.cache.client.internal.GetOp.execute(GetOp.java:91)
> at
> org.apache.geode.cache.client.internal.ServerRegionProxy.get(ServerRegionProxy.java:113)
> at
> org.apache.geode.internal.cache.LocalRegion.findObjectInSystem(LocalRegion.java:2768)
> at
> org.apache.geode.internal.cache.LocalRegion.nonTxnFindObject(LocalRegion.java:1490)
> at
> org.apache.geode.internal.cache.LocalRegionDataView.findObject(LocalRegionDataView.java:176)
> at org.apache.geode.internal.cache.LocalRegion.get(LocalRegion.java:1379)
> at org.apache.geode.internal.cache.LocalRegion.get(LocalRegion.java:1313)
> at org.apache.geode.internal.cache.LocalRegion.get(LocalRegion.java:1298)
> at
> org.apache.geode.internal.cache.AbstractRegion.get(AbstractRegion.java:313)
> at
> org.apache.geode.connectors.jdbc.JdbcDUnitTest.lambda$clientGetReadsFromDBWithPdxClassName$bb17a952$1(JdbcDUnitTest.java:348)
> 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 hydra.MethExecutor.executeObject(MethExecutor.java:244)
> at
> org.apache.geode.test.dunit.standalone.RemoteDUnitVM.executeMethodOnObject(RemoteDUnitVM.java:70)
> 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 sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:357)
> at sun.rmi.transport.Transport$1.run(Transport.java:200)
> at sun.rmi.transport.Transport$1.run(Transport.java:197)
> at java.security.AccessController.doPrivileged(Native Method)
> at sun.rmi.transport.Transport.serviceCall(Transport.java:196)
> at
> sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:568)
> at
> sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run0(TCPTransport.java:826)
> at
> sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.lambda$run$0(TCPTransport.java:683)
> at java.security.AccessController.doPrivileged(Native Method)
> at
> sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:682)
> 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)
> Caused by: org.apache.geode.pdx.PdxSerializationException: Exception while
> serializing a PDX field
> at
> org.apache.geode.pdx.internal.PdxOutputStream.writeObject(PdxOutputStream.java:84)
> at
> org.apache.geode.pdx.internal.PdxWriterImpl.writeObject(PdxWriterImpl.java:329)
> at
> org.apache.geode.pdx.internal.PdxInstanceFactoryImpl.writeObject(PdxInstanceFactoryImpl.java:210)
> at
>
[jira] [Updated] (GEODE-4821) RegisterInterestIntegrationTest should be categorized as DistributedTest
[ https://issues.apache.org/jira/browse/GEODE-4821?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kirk Lund updated GEODE-4821: - Summary: RegisterInterestIntegrationTest should be categorized as DistributedTest (was: RegisterInterestIntegrationTest should not use ClusterStarterRule) > RegisterInterestIntegrationTest should be categorized as DistributedTest > > > Key: GEODE-4821 > URL: https://issues.apache.org/jira/browse/GEODE-4821 > Project: Geode > Issue Type: Bug > Components: client queues, tests >Reporter: Kirk Lund >Priority: Major > > ClusterStarterRule is a DistributedTest rule and launches DUnit child VMs. > RegisterInterestIntegrationTest should either change to be a DistributedTest > or change to not use ClusterStarterRule. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (GEODE-4821) RegisterInterestIntegrationTest should be categorized as DistributedTest
[ https://issues.apache.org/jira/browse/GEODE-4821?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kirk Lund reassigned GEODE-4821: Assignee: Kirk Lund > RegisterInterestIntegrationTest should be categorized as DistributedTest > > > Key: GEODE-4821 > URL: https://issues.apache.org/jira/browse/GEODE-4821 > Project: Geode > Issue Type: Bug > Components: client queues, tests >Reporter: Kirk Lund >Assignee: Kirk Lund >Priority: Major > > ClusterStarterRule is a DistributedTest rule and launches DUnit child VMs. > RegisterInterestIntegrationTest should either change to be a DistributedTest > or change to not use ClusterStarterRule. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (GEODE-4871) Add EntryEvent key to earlyEntryEventSerialization
[ https://issues.apache.org/jira/browse/GEODE-4871?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kirk Lund reassigned GEODE-4871: Assignee: Kirk Lund > Add EntryEvent key to earlyEntryEventSerialization > -- > > Key: GEODE-4871 > URL: https://issues.apache.org/jira/browse/GEODE-4871 > Project: Geode > Issue Type: Improvement > Components: regions >Reporter: Kirk Lund >Assignee: Kirk Lund >Priority: Major > > This is a follow-up to GEODE-4769 which performs early serialization of the > EntryEvent new value. We should also perform early serialization of the > EntryEvent key. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (GEODE-4871) Add EntryEvent key to earlyEntryEventSerialization
Kirk Lund created GEODE-4871: Summary: Add EntryEvent key to earlyEntryEventSerialization Key: GEODE-4871 URL: https://issues.apache.org/jira/browse/GEODE-4871 Project: Geode Issue Type: Improvement Components: regions Reporter: Kirk Lund This is a follow-up to GEODE-4769 which performs early serialization of the EntryEvent new value. We should also perform early serialization of the EntryEvent key. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (GEODE-4769) Serialize region entry before putting in local cache
[ https://issues.apache.org/jira/browse/GEODE-4769?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kirk Lund resolved GEODE-4769. -- Resolution: Fixed Fix Version/s: 1.5.0 > Serialize region entry before putting in local cache > > > Key: GEODE-4769 > URL: https://issues.apache.org/jira/browse/GEODE-4769 > Project: Geode > Issue Type: Improvement > Components: regions >Reporter: Kirk Lund >Assignee: Kirk Lund >Priority: Major > Labels: pull-request-available > Fix For: 1.5.0 > > Time Spent: 2h 20m > Remaining Estimate: 0h > > This will prevent cache inconsistency when dealing with key or value objects > that have broken serialization. > Test should create two members with a REPLICATE region. If one member > performs a put, but the serialization fails then the region entry currently > ends up existing in only the cache of the member that performed the put > locally. The change will prevent this from occurring. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (GEODE-4769) Serialize region entry before putting in local cache
[ https://issues.apache.org/jira/browse/GEODE-4769?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16402135#comment-16402135 ] ASF subversion and git services commented on GEODE-4769: Commit 076d9abfc2aa2d365adfead168f05e054bea0248 in geode's branch refs/heads/develop from [~apa...@the9muses.net] [ https://gitbox.apache.org/repos/asf?p=geode.git;h=076d9ab ] GEODE-4769: fix tests using non-Serializable value objects Cleanup all test classes touched for this change. > Serialize region entry before putting in local cache > > > Key: GEODE-4769 > URL: https://issues.apache.org/jira/browse/GEODE-4769 > Project: Geode > Issue Type: Improvement > Components: regions >Reporter: Kirk Lund >Assignee: Kirk Lund >Priority: Major > Labels: pull-request-available > Time Spent: 2h 20m > Remaining Estimate: 0h > > This will prevent cache inconsistency when dealing with key or value objects > that have broken serialization. > Test should create two members with a REPLICATE region. If one member > performs a put, but the serialization fails then the region entry currently > ends up existing in only the cache of the member that performed the put > locally. The change will prevent this from occurring. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
