[jira] [Assigned] (GEODE-2092) Security examples should not be in the product code
[ https://issues.apache.org/jira/browse/GEODE-2092?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevin Duling reassigned GEODE-2092: --- Assignee: Kevin Duling > Security examples should not be in the product code > --- > > Key: GEODE-2092 > URL: https://issues.apache.org/jira/browse/GEODE-2092 > Project: Geode > Issue Type: Bug > Components: security >Affects Versions: 1.0.0-incubating >Reporter: Kirk Lund >Assignee: Kevin Duling > > These three classes are currently in geode-core product package which implies > they are fully supported user API. They cannot be released in a user API > package. They must be moved to geode-examples: > geode-core/src/main/java/org/apache/geode/security/templates/SampleSecurityManager.java > geode-core/src/main/java/org/apache/geode/security/templates/SamplePostProcessor.java > geode-core/src/main/java/org/apache/geode/security/templates/SimpleSecurityManager.java > If they need to be available within a jar, then geode-examples should be > altered to build a jar can be added to the classpath of a running application. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (GEODE-2066) Log UnauthorizedException message at INFO and stack at DEBUG
[ https://issues.apache.org/jira/browse/GEODE-2066?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15664559#comment-15664559 ] Kevin Duling commented on GEODE-2066: - We ought to adopt this as a general coding practice. Usually, one doesn't expect to see a stack trace unless debugging is enabled. Sometimes, it can confuse the reader if the message is benign. > Log UnauthorizedException message at INFO and stack at DEBUG > > > Key: GEODE-2066 > URL: https://issues.apache.org/jira/browse/GEODE-2066 > Project: Geode > Issue Type: Sub-task > Components: security >Reporter: Jinmei Liao > > 1. First, a similar Stack Trace appears at the INFO log-level every time a > security violation (e.g. authentication or authorization failure) occurs... > [info 2016/10/25 21:09:08.339 PDT > tid=0x24] (tid=36 msgId=0) Could not execute "list members". > org.apache.geode.security.NotAuthorizedException: guest not authorized for > CLUSTER:READ > at > org.apache.geode.internal.security.IntegratedSecurityService.authorize(IntegratedSecurityService.java:303) > at > org.apache.geode.internal.security.IntegratedSecurityService.authorize(IntegratedSecurityService.java:280) > at > org.apache.geode.internal.security.IntegratedSecurityService.authorize(IntegratedSecurityService.java:275) > at > org.apache.geode.internal.security.IntegratedSecurityService.authorize(IntegratedSecurityService.java:217) > at > org.apache.geode.management.internal.cli.remote.CommandProcessor.executeCommand(CommandProcessor.java:116) > at > org.apache.geode.management.internal.cli.remote.CommandStatementImpl.process(CommandStatementImpl.java:66) > at > org.apache.geode.management.internal.cli.remote.MemberCommandService.processCommand(MemberCommandService.java:54) > at > org.apache.geode.management.internal.beans.MemberMBeanBridge.processCommand(MemberMBeanBridge.java:1690) > at > org.apache.geode.management.internal.beans.MemberMBean.processCommand(MemberMBean.java:406) > at > org.apache.geode.management.internal.beans.MemberMBean.processCommand(MemberMBean.java:399) > 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 sun.reflect.misc.Trampoline.invoke(MethodUtil.java:71) > at sun.reflect.GeneratedMethodAccessor8.invoke(Unknown Source) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:497) > at sun.reflect.misc.MethodUtil.invoke(MethodUtil.java:275) > at > com.sun.jmx.mbeanserver.ConvertingMethod.invokeWithOpenReturn(ConvertingMethod.java:193) > at > com.sun.jmx.mbeanserver.ConvertingMethod.invokeWithOpenReturn(ConvertingMethod.java:175) > at > com.sun.jmx.mbeanserver.MXBeanIntrospector.invokeM2(MXBeanIntrospector.java:117) > at > com.sun.jmx.mbeanserver.MXBeanIntrospector.invokeM2(MXBeanIntrospector.java:54) > at > com.sun.jmx.mbeanserver.MBeanIntrospector.invokeM(MBeanIntrospector.java:237) > at com.sun.jmx.mbeanserver.PerInterface.invoke(PerInterface.java:138) > at com.sun.jmx.mbeanserver.MBeanSupport.invoke(MBeanSupport.java:252) > at > com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:819) > at > com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:801) > at > org.apache.geode.management.internal.security.MBeanServerWrapper.invoke(MBeanServerWrapper.java:208) > at > javax.management.remote.rmi.RMIConnectionImpl.doOperation(RMIConnectionImpl.java:1471) > at > javax.management.remote.rmi.RMIConnectionImpl.access$300(RMIConnectionImpl.java:76) > at > javax.management.remote.rmi.RMIConnectionImpl$PrivilegedOperation.run(RMIConnectionImpl.java:1312) > at java.security.AccessController.doPrivileged(Native Method) > at > javax.management.remote.rmi.RMIConnectionImpl.doPrivilegedOperation(RMIConnectionImpl.java:1411) > at > javax.management.remote.rmi.RMIConnectionImpl.invoke(RMIConnectionImpl.java:832) > 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 sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:323) > at sun
[jira] [Resolved] (GEODE-2008) CI Failure: CreateAlterDestroyRegionCommandsDUnitTest.testCreateAlterDestroyUpdatesSharedConfig
[ https://issues.apache.org/jira/browse/GEODE-2008?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevin Duling resolved GEODE-2008. - Resolution: Duplicate > CI Failure: > CreateAlterDestroyRegionCommandsDUnitTest.testCreateAlterDestroyUpdatesSharedConfig > --- > > Key: GEODE-2008 > URL: https://issues.apache.org/jira/browse/GEODE-2008 > Project: Geode > Issue Type: Bug > Components: management, tests >Reporter: Kirk Lund > > org.apache.geode.management.internal.cli.commands.CreateAlterDestroyRegionCommandsDUnitTest > > testCreateAlterDestroyUpdatesSharedConfig FAILED > org.apache.geode.test.dunit.RMIException: While invoking > org.apache.geode.management.internal.cli.commands.CreateAlterDestroyRegionCommandsDUnitTest$$Lambda$33/604398710.run > in VM 1 running on Host fa2d3f616251 with 4 VMs > at org.apache.geode.test.dunit.VM.invoke(VM.java:389) > at org.apache.geode.test.dunit.VM.invoke(VM.java:355) > at org.apache.geode.test.dunit.VM.invoke(VM.java:293) > at > org.apache.geode.management.internal.cli.commands.CreateAlterDestroyRegionCommandsDUnitTest.testCreateAlterDestroyUpdatesSharedConfig(CreateAlterDestroyRegionCommandsDUnitTest.java:856) > Caused by: > java.lang.AssertionError > at org.junit.Assert.fail(Assert.java:86) > at org.junit.Assert.assertTrue(Assert.java:41) > at org.junit.Assert.assertNotNull(Assert.java:712) > at org.junit.Assert.assertNotNull(Assert.java:722) > at > org.apache.geode.management.internal.cli.commands.CreateAlterDestroyRegionCommandsDUnitTest.lambda$testCreateAlterDestroyUpdatesSharedConfig$1e53591e$3(CreateAlterDestroyRegionCommandsDUnitTest.java:871) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (GEODE-2084) When executing a rest api in a browser, the login page presented in the browser is not setting the username/password correctly
[ https://issues.apache.org/jira/browse/GEODE-2084?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevin Duling resolved GEODE-2084. - Resolution: Fixed > When executing a rest api in a browser, the login page presented in the > browser is not setting the username/password correctly > -- > > Key: GEODE-2084 > URL: https://issues.apache.org/jira/browse/GEODE-2084 > Project: Geode > Issue Type: Bug > Components: configuration, rest (dev) >Affects Versions: 1.0.0-incubating >Reporter: Jinmei Liao >Assignee: Kevin Duling > Fix For: 1.1.0-incubating > > > Steps to reproduce: > 1. start up a server with security > 2. in a browser address bar, type in: http:// address>:7070/geode/v1/servers, after putting in username/password, I should > see the result json, but instead, I keep getting the login page. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (GEODE-2084) When executing a rest api in a browser, the login page presented in the browser is not setting the username/password correctly
[ https://issues.apache.org/jira/browse/GEODE-2084?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevin Duling updated GEODE-2084: Component/s: configuration > When executing a rest api in a browser, the login page presented in the > browser is not setting the username/password correctly > -- > > Key: GEODE-2084 > URL: https://issues.apache.org/jira/browse/GEODE-2084 > Project: Geode > Issue Type: Bug > Components: configuration, rest (dev) >Affects Versions: 1.0.0-incubating >Reporter: Jinmei Liao >Assignee: Kevin Duling > Fix For: 1.1.0-incubating > > > Steps to reproduce: > 1. start up a server with security > 2. in a browser address bar, type in: http:// address>:7070/geode/v1/servers, after putting in username/password, I should > see the result json, but instead, I keep getting the login page. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (GEODE-2084) When executing a rest api in a browser, the login page presented in the browser is not setting the username/password correctly
[ https://issues.apache.org/jira/browse/GEODE-2084?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevin Duling updated GEODE-2084: Affects Version/s: 1.0.0-incubating > When executing a rest api in a browser, the login page presented in the > browser is not setting the username/password correctly > -- > > Key: GEODE-2084 > URL: https://issues.apache.org/jira/browse/GEODE-2084 > Project: Geode > Issue Type: Bug > Components: rest (dev) >Affects Versions: 1.0.0-incubating >Reporter: Jinmei Liao >Assignee: Kevin Duling > Fix For: 1.1.0-incubating > > > Steps to reproduce: > 1. start up a server with security > 2. in a browser address bar, type in: http:// address>:7070/geode/v1/servers, after putting in username/password, I should > see the result json, but instead, I keep getting the login page. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Reopened] (GEODE-2084) When executing a rest api in a browser, the login page presented in the browser is not setting the username/password correctly
[ https://issues.apache.org/jira/browse/GEODE-2084?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevin Duling reopened GEODE-2084: - Reopening to import in to tracker > When executing a rest api in a browser, the login page presented in the > browser is not setting the username/password correctly > -- > > Key: GEODE-2084 > URL: https://issues.apache.org/jira/browse/GEODE-2084 > Project: Geode > Issue Type: Bug > Components: rest (dev) >Affects Versions: 1.0.0-incubating >Reporter: Jinmei Liao >Assignee: Kevin Duling > Fix For: 1.1.0-incubating > > > Steps to reproduce: > 1. start up a server with security > 2. in a browser address bar, type in: http:// address>:7070/geode/v1/servers, after putting in username/password, I should > see the result json, but instead, I keep getting the login page. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (GEODE-2084) When executing a rest api in a browser, the login page presented in the browser is not setting the username/password correctly
[ https://issues.apache.org/jira/browse/GEODE-2084?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevin Duling updated GEODE-2084: Component/s: rest (dev) > When executing a rest api in a browser, the login page presented in the > browser is not setting the username/password correctly > -- > > Key: GEODE-2084 > URL: https://issues.apache.org/jira/browse/GEODE-2084 > Project: Geode > Issue Type: Bug > Components: rest (dev) >Reporter: Jinmei Liao >Assignee: Kevin Duling > Fix For: 1.1.0-incubating > > > Steps to reproduce: > 1. start up a server with security > 2. in a browser address bar, type in: http:// address>:7070/geode/v1/servers, after putting in username/password, I should > see the result json, but instead, I keep getting the login page. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (GEODE-2084) When executing a rest api in a browser, the login page presented in the browser is not setting the username/password correctly
[ https://issues.apache.org/jira/browse/GEODE-2084?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevin Duling resolved GEODE-2084. - Resolution: Resolved Fix Version/s: 1.1.0-incubating > When executing a rest api in a browser, the login page presented in the > browser is not setting the username/password correctly > -- > > Key: GEODE-2084 > URL: https://issues.apache.org/jira/browse/GEODE-2084 > Project: Geode > Issue Type: Bug >Reporter: Jinmei Liao >Assignee: Kevin Duling > Fix For: 1.1.0-incubating > > > Steps to reproduce: > 1. start up a server with security > 2. in a browser address bar, type in: http:// address>:7070/geode/v1/servers, after putting in username/password, I should > see the result json, but instead, I keep getting the login page. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (GEODE-2084) When executing a rest api in a browser, the login page presented in the browser is not setting the username/password correctly
[ https://issues.apache.org/jira/browse/GEODE-2084?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15654789#comment-15654789 ] Kevin Duling commented on GEODE-2084: - Modified RestSecurityConfiguration to not bring up the login form. This will generate the normal Authentication login we expect to see. > When executing a rest api in a browser, the login page presented in the > browser is not setting the username/password correctly > -- > > Key: GEODE-2084 > URL: https://issues.apache.org/jira/browse/GEODE-2084 > Project: Geode > Issue Type: Bug >Reporter: Jinmei Liao >Assignee: Kevin Duling > Fix For: 1.1.0-incubating > > > Steps to reproduce: > 1. start up a server with security > 2. in a browser address bar, type in: http:// address>:7070/geode/v1/servers, after putting in username/password, I should > see the result json, but instead, I keep getting the login page. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (GEODE-2084) When executing a rest api in a browser, the login page presented in the browser is not setting the username/password correctly
[ https://issues.apache.org/jira/browse/GEODE-2084?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevin Duling reassigned GEODE-2084: --- Assignee: Kevin Duling > When executing a rest api in a browser, the login page presented in the > browser is not setting the username/password correctly > -- > > Key: GEODE-2084 > URL: https://issues.apache.org/jira/browse/GEODE-2084 > Project: Geode > Issue Type: Bug >Reporter: Jinmei Liao >Assignee: Kevin Duling > > Steps to reproduce: > 1. start up a server with security > 2. in a browser address bar, type in: http:// address>:7070/geode/v1/servers, after putting in username/password, I should > see the result json, but instead, I keep getting the login page. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (GEODE-1993) value returned through /region/key rest service needs to be post processed
[ https://issues.apache.org/jira/browse/GEODE-1993?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevin Duling resolved GEODE-1993. - Resolution: Fixed Fix Version/s: 1.1.0-incubating > value returned through /region/key rest service needs to be post processed > -- > > Key: GEODE-1993 > URL: https://issues.apache.org/jira/browse/GEODE-1993 > Project: Geode > Issue Type: New Feature > Components: management >Reporter: Jinmei Liao >Assignee: Kevin Duling > Fix For: 1.1.0-incubating > > > The new rest security did not use post processor before returning the value > back to the client. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (GEODE-1993) value returned through /region/key rest service needs to be post processed
[ https://issues.apache.org/jira/browse/GEODE-1993?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevin Duling updated GEODE-1993: Assignee: Kevin Duling > value returned through /region/key rest service needs to be post processed > -- > > Key: GEODE-1993 > URL: https://issues.apache.org/jira/browse/GEODE-1993 > Project: Geode > Issue Type: New Feature > Components: management >Reporter: Jinmei Liao >Assignee: Kevin Duling > > The new rest security did not use post processor before returning the value > back to the client. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (GEODE-1959) Prompt for username and password when adding a member
[ https://issues.apache.org/jira/browse/GEODE-1959?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevin Duling resolved GEODE-1959. - Resolution: Fixed Fix Version/s: 1.1.0-incubating > Prompt for username and password when adding a member > - > > Key: GEODE-1959 > URL: https://issues.apache.org/jira/browse/GEODE-1959 > Project: Geode > Issue Type: Improvement > Components: security >Reporter: Diane Hardman >Assignee: Kevin Duling > Fix For: 1.1.0-incubating > > Attachments: gemfire.properties, security.json > > > When you have SecurityManager configured as part of starting a locator, the > administrator currently needs to have either AuthInitialize implemented or > have stored credentials (in plain text) in geode.properties file. In the case > where neither AuthInitialize is implemented NOR are there any credentials > stored in geode.properties, then the administrator should be prompted for > username and password when attempting to start another member in the > distributed system. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (GEODE-2014) Upgrade Swagger libraries
[ https://issues.apache.org/jira/browse/GEODE-2014?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevin Duling resolved GEODE-2014. - Resolution: Fixed Fix Version/s: 1.1.0-incubating > Upgrade Swagger libraries > - > > Key: GEODE-2014 > URL: https://issues.apache.org/jira/browse/GEODE-2014 > Project: Geode > Issue Type: Improvement > Components: docs, rest (dev) >Affects Versions: 1.0.0-incubating >Reporter: Kevin Duling >Assignee: Kevin Duling > Fix For: 1.1.0-incubating > > > Upgrade swagger and swagger-springmvc -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (GEODE-2014) Upgrade Swagger libraries
[ https://issues.apache.org/jira/browse/GEODE-2014?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevin Duling reassigned GEODE-2014: --- Assignee: Kevin Duling > Upgrade Swagger libraries > - > > Key: GEODE-2014 > URL: https://issues.apache.org/jira/browse/GEODE-2014 > Project: Geode > Issue Type: Improvement > Components: rest (dev) >Affects Versions: 1.0.0-incubating >Reporter: Kevin Duling >Assignee: Kevin Duling > > Upgrade swagger and swagger-springmvc -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (GEODE-2014) Upgrade Swagger libraries
[ https://issues.apache.org/jira/browse/GEODE-2014?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevin Duling updated GEODE-2014: Affects Version/s: 1.0.0-incubating > Upgrade Swagger libraries > - > > Key: GEODE-2014 > URL: https://issues.apache.org/jira/browse/GEODE-2014 > Project: Geode > Issue Type: Improvement > Components: rest (dev) >Affects Versions: 1.0.0-incubating >Reporter: Kevin Duling > > Upgrade swagger and swagger-springmvc -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (GEODE-2014) Upgrade Swagger libraries
Kevin Duling created GEODE-2014: --- Summary: Upgrade Swagger libraries Key: GEODE-2014 URL: https://issues.apache.org/jira/browse/GEODE-2014 Project: Geode Issue Type: Improvement Components: rest (dev) Reporter: Kevin Duling Upgrade swagger and swagger-springmvc -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (GEODE-1983) Swagger is broken with integrated security
[ https://issues.apache.org/jira/browse/GEODE-1983?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevin Duling resolved GEODE-1983. - Resolution: Fixed Fix Version/s: 1.1.0-incubating Swagger needed to be excluded from the list of protected geode URLs. > Swagger is broken with integrated security > -- > > Key: GEODE-1983 > URL: https://issues.apache.org/jira/browse/GEODE-1983 > Project: Geode > Issue Type: Bug > Components: rest (dev), security >Reporter: Diane Hardman >Assignee: Kevin Duling > Fix For: 1.1.0-incubating > > > Swagger UI does not work with latest integrated security. After configuring > security manager and attempting up to open up Swagger UI we get a prompt for > username and password. Entering credentials does not bring up the UI, instead > asking for credentials again. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (GEODE-1983) Swagger is broken with integrated security
[ https://issues.apache.org/jira/browse/GEODE-1983?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevin Duling reassigned GEODE-1983: --- Assignee: Kevin Duling > Swagger is broken with integrated security > -- > > Key: GEODE-1983 > URL: https://issues.apache.org/jira/browse/GEODE-1983 > Project: Geode > Issue Type: Bug > Components: rest (dev), security >Reporter: Diane Hardman >Assignee: Kevin Duling > > Swagger UI does not work with latest integrated security. After configuring > security manager and attempting up to open up Swagger UI we get a prompt for > username and password. Entering credentials does not bring up the UI, instead > asking for credentials again. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (GEODE-2004) Create/update/delete query through rest api should require DATA:READ instead of DATA:WRITE
[ https://issues.apache.org/jira/browse/GEODE-2004?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevin Duling updated GEODE-2004: Fix Version/s: 1.0.0-incubating > Create/update/delete query through rest api should require DATA:READ instead > of DATA:WRITE > -- > > Key: GEODE-2004 > URL: https://issues.apache.org/jira/browse/GEODE-2004 > Project: Geode > Issue Type: Bug > Components: management, security >Affects Versions: 1.0.0-incubating >Reporter: Jinmei Liao >Assignee: Kevin Duling > Fix For: 1.0.0-incubating > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (GEODE-2004) Create/update/delete query through rest api should require DATA:READ instead of DATA:WRITE
[ https://issues.apache.org/jira/browse/GEODE-2004?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevin Duling updated GEODE-2004: Affects Version/s: 1.0.0-incubating > Create/update/delete query through rest api should require DATA:READ instead > of DATA:WRITE > -- > > Key: GEODE-2004 > URL: https://issues.apache.org/jira/browse/GEODE-2004 > Project: Geode > Issue Type: Bug > Components: management, security >Affects Versions: 1.0.0-incubating >Reporter: Jinmei Liao >Assignee: Kevin Duling > Fix For: 1.0.0-incubating > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (GEODE-2004) Create/update/delete query through rest api should require DATA:READ instead of DATA:WRITE
[ https://issues.apache.org/jira/browse/GEODE-2004?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevin Duling reassigned GEODE-2004: --- Assignee: Kevin Duling > Create/update/delete query through rest api should require DATA:READ instead > of DATA:WRITE > -- > > Key: GEODE-2004 > URL: https://issues.apache.org/jira/browse/GEODE-2004 > Project: Geode > Issue Type: Bug > Components: management, security >Reporter: Jinmei Liao >Assignee: Kevin Duling > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (GEODE-1959) Prompt for username and password when adding a member
[ https://issues.apache.org/jira/browse/GEODE-1959?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevin Duling updated GEODE-1959: Attachment: security.json gemfire.properties Configuration files needed to reproduce problem > Prompt for username and password when adding a member > - > > Key: GEODE-1959 > URL: https://issues.apache.org/jira/browse/GEODE-1959 > Project: Geode > Issue Type: Improvement > Components: security >Reporter: Diane Hardman >Assignee: Kevin Duling > Attachments: gemfire.properties, security.json > > > When you have SecurityManager configured as part of starting a locator, the > administrator currently needs to have either AuthInitialize implemented or > have stored credentials (in plain text) in geode.properties file. In the case > where neither AuthInitialize is implemented NOR are there any credentials > stored in geode.properties, then the administrator should be prompted for > username and password when attempting to start another member in the > distributed system. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (GEODE-1959) Prompt for username and password when adding a member
[ https://issues.apache.org/jira/browse/GEODE-1959?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevin Duling reassigned GEODE-1959: --- Assignee: Kevin Duling > Prompt for username and password when adding a member > - > > Key: GEODE-1959 > URL: https://issues.apache.org/jira/browse/GEODE-1959 > Project: Geode > Issue Type: Improvement > Components: security >Reporter: Diane Hardman >Assignee: Kevin Duling > > When you have SecurityManager configured as part of starting a locator, the > administrator currently needs to have either AuthInitialize implemented or > have stored credentials (in plain text) in geode.properties file. In the case > where neither AuthInitialize is implemented NOR are there any credentials > stored in geode.properties, then the administrator should be prompted for > username and password when attempting to start another member in the > distributed system. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (GEODE-1570) developer REST API should be secured
[ https://issues.apache.org/jira/browse/GEODE-1570?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevin Duling resolved GEODE-1570. - Resolution: Fixed > developer REST API should be secured > > > Key: GEODE-1570 > URL: https://issues.apache.org/jira/browse/GEODE-1570 > Project: Geode > Issue Type: Sub-task > Components: rest (dev), security >Reporter: Swapnil Bawaskar >Assignee: Kevin Duling > Fix For: 1.0.0-incubating > > > The developer REST API should require authentication when security is > enabled. For authorization, the implementation should use the new > Resource:Operation permissions API that is used by JMX. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (GEODE-1657) Source files should not contain Windows linefeeds
[ https://issues.apache.org/jira/browse/GEODE-1657?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15552589#comment-15552589 ] Kevin Duling commented on GEODE-1657: - Depending on how contributors have their git set up, this can be an ongoing problem. In Geode, there are over 300 files that have Windows linefeeds in them. {code} grep -IlR ^M * | wc -l 319 {code} This article has suggestions on how to address the issue: https://help.github.com/articles/dealing-with-line-endings/ > Source files should not contain Windows linefeeds > - > > Key: GEODE-1657 > URL: https://issues.apache.org/jira/browse/GEODE-1657 > Project: Geode > Issue Type: Bug > Components: general >Reporter: Kirk Lund >Assignee: Kirk Lund >Priority: Minor > > geode-pulse/src/test/java/com/vmware/gemfire/tools/pulse/tests/Server.java > contains ^M (Windows linefeeds). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (GEODE-136) Fix possible NullPointerException in Gfsh's 'list regions' command's GetRegionsFunction.
[ https://issues.apache.org/jira/browse/GEODE-136?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevin Duling resolved GEODE-136. Resolution: Fixed Changed the order of the null test to be sane. Did not change the results as this is not internal, therefore creating a broader discussion. Created the missing unit test for this class. > Fix possible NullPointerException in Gfsh's 'list regions' command's > GetRegionsFunction. > > > Key: GEODE-136 > URL: https://issues.apache.org/jira/browse/GEODE-136 > Project: Geode > Issue Type: Bug > Components: gfsh >Affects Versions: 1.0.0-incubating > Environment: GemFire Manager + Gfsh >Reporter: John Blum >Assignee: Kevin Duling > Labels: ApacheGeode, CLI, GFSH, GetRegionsFunction, list-regions > Fix For: 1.0.0-incubating > > > The following line > ([#48|https://github.com/apache/incubator-geode/blob/develop/gemfire-core/src/main/java/com/gemstone/gemfire/management/internal/cli/functions/GetRegionsFunction.java#L48]) > in the {{GetRegionsFunction}} class could possibly lead to a NPE if the > {{regions}} _Set_ is null since the {{regions.isEmpty()}} call proceeds the > {{regions == null}} check. > Of course, one should argue whether {{Cache.rootRegions()}} should be > returning a null _Set_ at all rather than an empty _Set_ if there are in fact > no "root" _Regions_ in the Geode _Cache_. > But then, one could also argue that this {{GetRegionsFunction}} should not be > returning a null "array" if there are no "root" _Regions_ in the Geode > _Cache_ either. It too should be returning an "empty" array. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (GEODE-136) Fix possible NullPointerException in Gfsh's 'list regions' command's GetRegionsFunction.
[ https://issues.apache.org/jira/browse/GEODE-136?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevin Duling reassigned GEODE-136: -- Assignee: Kevin Duling > Fix possible NullPointerException in Gfsh's 'list regions' command's > GetRegionsFunction. > > > Key: GEODE-136 > URL: https://issues.apache.org/jira/browse/GEODE-136 > Project: Geode > Issue Type: Bug > Components: gfsh >Affects Versions: 1.0.0-incubating > Environment: GemFire Manager + Gfsh >Reporter: John Blum >Assignee: Kevin Duling > Labels: ApacheGeode, CLI, GFSH, GetRegionsFunction, list-regions > Fix For: 1.0.0-incubating > > > The following line > ([#48|https://github.com/apache/incubator-geode/blob/develop/gemfire-core/src/main/java/com/gemstone/gemfire/management/internal/cli/functions/GetRegionsFunction.java#L48]) > in the {{GetRegionsFunction}} class could possibly lead to a NPE if the > {{regions}} _Set_ is null since the {{regions.isEmpty()}} call proceeds the > {{regions == null}} check. > Of course, one should argue whether {{Cache.rootRegions()}} should be > returning a null _Set_ at all rather than an empty _Set_ if there are in fact > no "root" _Regions_ in the Geode _Cache_. > But then, one could also argue that this {{GetRegionsFunction}} should not be > returning a null "array" if there are no "root" _Regions_ in the Geode > _Cache_ either. It too should be returning an "empty" array. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (GEODE-1948) geode.properties should be the default filename
[ https://issues.apache.org/jira/browse/GEODE-1948?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevin Duling updated GEODE-1948: Description: geode.properties should be the new default filename. If geode.properties cannot be located, fall back to look for an old gemfire.properties. (was: geode.properties should be the new default filename. If gemfire.properties is specified on startup and cannot be located, fall back to geode.properties and try to open that file before presenting an error.) > geode.properties should be the default filename > --- > > Key: GEODE-1948 > URL: https://issues.apache.org/jira/browse/GEODE-1948 > Project: Geode > Issue Type: Sub-task > Components: docs >Reporter: Kevin Duling >Assignee: Kevin Duling > Labels: branding, configuration, docs > Fix For: 1.0.0-incubating > > > geode.properties should be the new default filename. If geode.properties > cannot be located, fall back to look for an old gemfire.properties. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (GEODE-1948) geode.properties should be the default filename
[ https://issues.apache.org/jira/browse/GEODE-1948?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevin Duling updated GEODE-1948: Summary: geode.properties should be the default filename (was: Open geode.properties if gemfire.properties is not found) > geode.properties should be the default filename > --- > > Key: GEODE-1948 > URL: https://issues.apache.org/jira/browse/GEODE-1948 > Project: Geode > Issue Type: Sub-task > Components: docs >Reporter: Kevin Duling >Assignee: Kevin Duling > Labels: branding, configuration, docs > Fix For: 1.0.0-incubating > > > geode.properties should be the new default filename. If gemfire.properties > is specified on startup and cannot be located, fall back to geode.properties > and try to open that file before presenting an error. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (GEODE-1948) Open geode.properties if gemfire.properties is not found
[ https://issues.apache.org/jira/browse/GEODE-1948?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevin Duling resolved GEODE-1948. - Resolution: Fixed > Open geode.properties if gemfire.properties is not found > > > Key: GEODE-1948 > URL: https://issues.apache.org/jira/browse/GEODE-1948 > Project: Geode > Issue Type: Sub-task > Components: docs >Reporter: Kevin Duling >Assignee: Kevin Duling > Labels: branding, configuration > Fix For: 1.0.0-incubating > > > geode.properties should be the new default filename. If gemfire.properties > is specified on startup and cannot be located, fall back to geode.properties > and try to open that file before presenting an error. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (GEODE-1948) Open geode.properties if gemfire.properties is not found
[ https://issues.apache.org/jira/browse/GEODE-1948?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevin Duling updated GEODE-1948: Labels: branding configuration (was: ) > Open geode.properties if gemfire.properties is not found > > > Key: GEODE-1948 > URL: https://issues.apache.org/jira/browse/GEODE-1948 > Project: Geode > Issue Type: Sub-task > Components: docs >Reporter: Kevin Duling >Assignee: Kevin Duling > Labels: branding, configuration > Fix For: 1.0.0-incubating > > > geode.properties should be the new default filename. If gemfire.properties > is specified on startup and cannot be located, fall back to geode.properties > and try to open that file before presenting an error. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (GEODE-1948) Open geode.properties if gemfire.properties is not found
[ https://issues.apache.org/jira/browse/GEODE-1948?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevin Duling reassigned GEODE-1948: --- Assignee: Kevin Duling > Open geode.properties if gemfire.properties is not found > > > Key: GEODE-1948 > URL: https://issues.apache.org/jira/browse/GEODE-1948 > Project: Geode > Issue Type: Sub-task > Components: docs >Reporter: Kevin Duling >Assignee: Kevin Duling > Fix For: 1.0.0-incubating > > > geode.properties should be the new default filename. If gemfire.properties > is specified on startup and cannot be located, fall back to geode.properties > and try to open that file before presenting an error. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (GEODE-1466) Branding: rename gemfire.properties file to geode.properties file
[ https://issues.apache.org/jira/browse/GEODE-1466?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevin Duling updated GEODE-1466: Assignee: Kirk Lund (was: Kevin Duling) > Branding: rename gemfire.properties file to geode.properties file > - > > Key: GEODE-1466 > URL: https://issues.apache.org/jira/browse/GEODE-1466 > Project: Geode > Issue Type: Improvement > Components: docs >Reporter: Nitin Lamba >Assignee: Kirk Lund > Labels: branding, configuration > Fix For: 1.0.0-incubating > > > Currently, all runtime properties defined at startup are defined in > gemfire.properties file and the namespace also starts with gemfire. It is > desirable to rename this to geode. > This will affect multiple modules (a lot of string literals) across the > project and may create config migration issues later on, hence is important > for the 1.0 release. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (GEODE-1948) Open geode.properties if gemfire.properties is not found
Kevin Duling created GEODE-1948: --- Summary: Open geode.properties if gemfire.properties is not found Key: GEODE-1948 URL: https://issues.apache.org/jira/browse/GEODE-1948 Project: Geode Issue Type: Sub-task Reporter: Kevin Duling geode.properties should be the new default filename. If gemfire.properties is specified on startup and cannot be located, fall back to geode.properties and try to open that file before presenting an error. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (GEODE-1466) Branding: rename gemfire.properties file to geode.properties file
[ https://issues.apache.org/jira/browse/GEODE-1466?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15530282#comment-15530282 ] Kevin Duling commented on GEODE-1466: - What do you suggest gfsecurity be renamed to? geode-security.properties? > Branding: rename gemfire.properties file to geode.properties file > - > > Key: GEODE-1466 > URL: https://issues.apache.org/jira/browse/GEODE-1466 > Project: Geode > Issue Type: Improvement > Components: docs >Reporter: Nitin Lamba >Assignee: Kirk Lund > Labels: branding, configuration > Fix For: 1.0.0-incubating > > > Currently, all runtime properties defined at startup are defined in > gemfire.properties file and the namespace also starts with gemfire. It is > desirable to rename this to geode. > This will affect multiple modules (a lot of string literals) across the > project and may create config migration issues later on, hence is important > for the 1.0 release. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (GEODE-1466) Branding: rename gemfire.properties file to geode.properties file
[ https://issues.apache.org/jira/browse/GEODE-1466?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevin Duling reassigned GEODE-1466: --- Assignee: Kevin Duling (was: Kirk Lund) > Branding: rename gemfire.properties file to geode.properties file > - > > Key: GEODE-1466 > URL: https://issues.apache.org/jira/browse/GEODE-1466 > Project: Geode > Issue Type: Improvement > Components: docs >Reporter: Nitin Lamba >Assignee: Kevin Duling > Labels: branding, configuration > Fix For: 1.0.0-incubating > > > Currently, all runtime properties defined at startup are defined in > gemfire.properties file and the namespace also starts with gemfire. It is > desirable to rename this to geode. > This will affect multiple modules (a lot of string literals) across the > project and may create config migration issues later on, hence is important > for the 1.0 release. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (GEODE-1902) Add GEMFIRE_VERBOSE LogMarker as alias of GEODE_VERBOSE for backwards compatibility
[ https://issues.apache.org/jira/browse/GEODE-1902?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevin Duling updated GEODE-1902: Component/s: docs > Add GEMFIRE_VERBOSE LogMarker as alias of GEODE_VERBOSE for backwards > compatibility > --- > > Key: GEODE-1902 > URL: https://issues.apache.org/jira/browse/GEODE-1902 > Project: Geode > Issue Type: Improvement > Components: docs, logging >Reporter: Kirk Lund >Assignee: Kevin Duling > Fix For: 1.0.0-incubating > > > If someone has custom log4j2.xml that enables GEMFIRE_VERBOSE marker they > either need to change this to GEODE_VERBOSE or we need to add some sort of > alias so that GEMFIRE_VERBOSE will enable GEODE_VERBOSE. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (GEODE-1902) Add GEMFIRE_VERBOSE LogMarker as alias of GEODE_VERBOSE for backwards compatibility
[ https://issues.apache.org/jira/browse/GEODE-1902?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevin Duling resolved GEODE-1902. - Resolution: Fixed Fix Version/s: 1.0.0-incubating > Add GEMFIRE_VERBOSE LogMarker as alias of GEODE_VERBOSE for backwards > compatibility > --- > > Key: GEODE-1902 > URL: https://issues.apache.org/jira/browse/GEODE-1902 > Project: Geode > Issue Type: Improvement > Components: docs, logging >Reporter: Kirk Lund >Assignee: Kevin Duling > Fix For: 1.0.0-incubating > > > If someone has custom log4j2.xml that enables GEMFIRE_VERBOSE marker they > either need to change this to GEODE_VERBOSE or we need to add some sort of > alias so that GEMFIRE_VERBOSE will enable GEODE_VERBOSE. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (GEODE-1902) Add GEMFIRE_VERBOSE LogMarker as alias of GEODE_VERBOSE for backwards compatibility
[ https://issues.apache.org/jira/browse/GEODE-1902?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15530244#comment-15530244 ] Kevin Duling commented on GEODE-1902: - log4j doesn't allow aliases or synonyms, making two markers behave identically. But it does support a child-parent hierarchy. GEMFIRE_VERBOSE was made the parent of GEODE_VERBOSE so that filtering gemfire would also filter geode. However, if only geode is filters, gemfire messages will not be. GEMFIRE_VERBOSE should be considered to be deprecated and will be removed in the near future. > Add GEMFIRE_VERBOSE LogMarker as alias of GEODE_VERBOSE for backwards > compatibility > --- > > Key: GEODE-1902 > URL: https://issues.apache.org/jira/browse/GEODE-1902 > Project: Geode > Issue Type: Improvement > Components: logging >Reporter: Kirk Lund >Assignee: Kevin Duling > > If someone has custom log4j2.xml that enables GEMFIRE_VERBOSE marker they > either need to change this to GEODE_VERBOSE or we need to add some sort of > alias so that GEMFIRE_VERBOSE will enable GEODE_VERBOSE. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (GEODE-1902) Add GEMFIRE_VERBOSE LogMarker as alias of GEODE_VERBOSE for backwards compatibility
[ https://issues.apache.org/jira/browse/GEODE-1902?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevin Duling reassigned GEODE-1902: --- Assignee: Kevin Duling > Add GEMFIRE_VERBOSE LogMarker as alias of GEODE_VERBOSE for backwards > compatibility > --- > > Key: GEODE-1902 > URL: https://issues.apache.org/jira/browse/GEODE-1902 > Project: Geode > Issue Type: Improvement > Components: logging >Reporter: Kirk Lund >Assignee: Kevin Duling > > If someone has custom log4j2.xml that enables GEMFIRE_VERBOSE marker they > either need to change this to GEODE_VERBOSE or we need to add some sort of > alias so that GEMFIRE_VERBOSE will enable GEODE_VERBOSE. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (GEODE-1570) developer REST API should be secured
[ https://issues.apache.org/jira/browse/GEODE-1570?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevin Duling reassigned GEODE-1570: --- Assignee: Kevin Duling > developer REST API should be secured > > > Key: GEODE-1570 > URL: https://issues.apache.org/jira/browse/GEODE-1570 > Project: Geode > Issue Type: Sub-task > Components: rest (dev), security >Reporter: Swapnil Bawaskar >Assignee: Kevin Duling > > The developer REST API should require authentication when security is > enabled. For authorization, the implementation should use the new > Resource:Operation permissions API that is used by JMX. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (GEODE-1467) Branding: Rename servlet URLs from gemfire to geode
[ https://issues.apache.org/jira/browse/GEODE-1467?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevin Duling resolved GEODE-1467. - Resolution: Fixed Fix Version/s: 1.0.0-incubating > Branding: Rename servlet URLs from gemfire to geode > --- > > Key: GEODE-1467 > URL: https://issues.apache.org/jira/browse/GEODE-1467 > Project: Geode > Issue Type: Improvement > Components: docs, rest (admin), rest (dev) >Reporter: Nitin Lamba >Assignee: Kevin Duling > Fix For: 1.0.0-incubating > > > There are a few locations where gemfire references are used (excluding > package hierarchy covered in GEODE-37): > 1. servlet URLs for Dev REST (gemfire-api) and Mgmt REST (gemfire/v1) > 2. extension modules (http session mgmt) > 3. others (spring-data?) > (2) and (3) can be hairy as it may impact existing applications. A change > post 1.0 would create complexity, therefore, should be carefully considered > for 1.0 release. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (GEODE-746) When starting a locator using --bind-address, gfsh prints incorrect connect message
[ https://issues.apache.org/jira/browse/GEODE-746?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15426829#comment-15426829 ] Kevin Duling commented on GEODE-746: [~swapnil.bawaskar], can you try this again? I just tried it with my 10.x address and did not get the {{Connection refused}} message. {code} _ __ / _/ __/ __/ // / / / __/ /___ /_ / _ / / /__/ / / _/ / // / /__/_/ /__/_//_/1.0.0-incubating-SNAPSHOT Monitor and Manage Apache Geode (incubating) gfsh>start locator --name=l1 --bind-address=10.118.33.209 --J=-Dgemfire.jmx-manager-bind-address=10.118.33.209 --J=-Dgemfire.jmx-manager-hostname-for-clients=10.118.33.209 Starting a Geode Locator in /Users/kduling/Dev/geode/tmp/l1... . Locator in /Users/kduling/Dev/geode/tmp/l1 on 10.118.33.209[10334] as l1 is currently online. Process ID: 7625 Uptime: 3 seconds GemFire Version: 1.0.0-incubating-SNAPSHOT Java Version: 1.8.0_92 Log File: /Users/kduling/Dev/geode/tmp/l1/l1.log JVM Arguments: -Dgemfire.enable-cluster-configuration=true -Dgemfire.load-cluster-configuration-from-dir=false -Dgemfire.jmx-manager-bind-address=10.118.33.209 -Dgemfire.jmx-manager-hostname-for-clients=10.118.33.209 -Dgemfire.launcher.registerSignalHandlers=true -Djava.awt.headless=true -Dsun.rmi.dgc.server.gcInterval=9223372036854775806 Class-Path: /Users/kduling/Dev/geode/open/geode-assembly/build/install/apache-geode/lib/geode-core-1.0.0-incubating-SNAPSHOT.jar:/Users/kduling/Dev/geode/open/geode-assembly/build/install/apache-geode/lib/geode-dependencies.jar Successfully connected to: JMX Manager [host=10.118.33.209, port=1099] Cluster configuration service is up and running. {code} > When starting a locator using --bind-address, gfsh prints incorrect connect > message > --- > > Key: GEODE-746 > URL: https://issues.apache.org/jira/browse/GEODE-746 > Project: Geode > Issue Type: Improvement > Components: gfsh >Reporter: Jens Deppe >Assignee: Kevin Duling > > When starting my locator with {{gfsh start locator --name=locator1 > --port=19991 --bind-address=192.168.103.1}}, the output from gfsh looks like > this: > {noformat} > .. > Locator in /Users/jdeppe/debug/locator1 on 192.168.103.1[19991] as locator1 > is currently online. > Process ID: 2666 > Uptime: 15 seconds > GemFire Version: 8.2.0.Beta > Java Version: 1.7.0_72 > Log File: /Users/jdeppe/debug/locator1/locator1.log > JVM Arguments: -Dgemfire.enable-cluster-configuration=true > -Dgemfire.load-cluster-configuration-from-dir=false > -Dgemfire.launcher.registerSignalHandlers=true -Djava.awt.headless=true > -Dsun.rmi.dgc.server.gcInterval=9223372036854775806 > Class-Path: > /Users/jdeppe/gemfire/82/lib/gemfire.jar:/Users/jdeppe/gemfire/82/lib/locator-dependencies.jar > Please use "connect --locator=192.168.1.10[19991]" to connect Gfsh to the > locator. > Failed to connect; unknown cause: Connection refused > {noformat} > The connect string shown is just displaying my host address and not the bind > address. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Comment Edited] (GEODE-1467) Branding: Rename servlet URLs from gemfire to geode
[ https://issues.apache.org/jira/browse/GEODE-1467?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15397847#comment-15397847 ] Kevin Duling edited comment on GEODE-1467 at 7/28/16 5:34 PM: -- Added the servlets to Jetty twice as a temporary solution in order to support both contexts for a period of time. Updated DUnit tests to test both URL endpoints. gemfire-api became geode gemfire became geode-mgmt was (Author: kduling): Added the servlets to Jetty twice as a temporary solution in order to support both contexts for a period of time. Updated DUnit tests to test both URL endpoints. > Branding: Rename servlet URLs from gemfire to geode > --- > > Key: GEODE-1467 > URL: https://issues.apache.org/jira/browse/GEODE-1467 > Project: Geode > Issue Type: Improvement > Components: docs, rest (admin), rest (dev) >Reporter: Nitin Lamba >Assignee: Kevin Duling > > There are a few locations where gemfire references are used (excluding > package hierarchy covered in GEODE-37): > 1. servlet URLs for Dev REST (gemfire-api) and Mgmt REST (gemfire/v1) > 2. extension modules (http session mgmt) > 3. others (spring-data?) > (2) and (3) can be hairy as it may impact existing applications. A change > post 1.0 would create complexity, therefore, should be carefully considered > for 1.0 release. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (GEODE-1467) Branding: Rename servlet URLs from gemfire to geode
[ https://issues.apache.org/jira/browse/GEODE-1467?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevin Duling updated GEODE-1467: Component/s: docs > Branding: Rename servlet URLs from gemfire to geode > --- > > Key: GEODE-1467 > URL: https://issues.apache.org/jira/browse/GEODE-1467 > Project: Geode > Issue Type: Improvement > Components: docs, rest (admin), rest (dev) >Reporter: Nitin Lamba >Assignee: Kevin Duling > > There are a few locations where gemfire references are used (excluding > package hierarchy covered in GEODE-37): > 1. servlet URLs for Dev REST (gemfire-api) and Mgmt REST (gemfire/v1) > 2. extension modules (http session mgmt) > 3. others (spring-data?) > (2) and (3) can be hairy as it may impact existing applications. A change > post 1.0 would create complexity, therefore, should be carefully considered > for 1.0 release. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Reopened] (GEODE-1467) Branding: Rename servlet URLs from gemfire to geode
[ https://issues.apache.org/jira/browse/GEODE-1467?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevin Duling reopened GEODE-1467: - > Branding: Rename servlet URLs from gemfire to geode > --- > > Key: GEODE-1467 > URL: https://issues.apache.org/jira/browse/GEODE-1467 > Project: Geode > Issue Type: Improvement > Components: rest (admin), rest (dev) >Reporter: Nitin Lamba >Assignee: Kevin Duling > > There are a few locations where gemfire references are used (excluding > package hierarchy covered in GEODE-37): > 1. servlet URLs for Dev REST (gemfire-api) and Mgmt REST (gemfire/v1) > 2. extension modules (http session mgmt) > 3. others (spring-data?) > (2) and (3) can be hairy as it may impact existing applications. A change > post 1.0 would create complexity, therefore, should be carefully considered > for 1.0 release. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (GEODE-1467) Branding: Rename servlet URLs from gemfire to geode
[ https://issues.apache.org/jira/browse/GEODE-1467?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevin Duling resolved GEODE-1467. - Resolution: Fixed Added the servlets to Jetty twice as a temporary solution in order to support both contexts for a period of time. Updated DUnit tests to test both URL endpoints. > Branding: Rename servlet URLs from gemfire to geode > --- > > Key: GEODE-1467 > URL: https://issues.apache.org/jira/browse/GEODE-1467 > Project: Geode > Issue Type: Improvement > Components: rest (admin), rest (dev) >Reporter: Nitin Lamba >Assignee: Kevin Duling > > There are a few locations where gemfire references are used (excluding > package hierarchy covered in GEODE-37): > 1. servlet URLs for Dev REST (gemfire-api) and Mgmt REST (gemfire/v1) > 2. extension modules (http session mgmt) > 3. others (spring-data?) > (2) and (3) can be hairy as it may impact existing applications. A change > post 1.0 would create complexity, therefore, should be carefully considered > for 1.0 release. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (GEODE-1467) Branding: Rename servlet URLs from gemfire to geode
[ https://issues.apache.org/jira/browse/GEODE-1467?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevin Duling reassigned GEODE-1467: --- Assignee: Kevin Duling > Branding: Rename servlet URLs from gemfire to geode > --- > > Key: GEODE-1467 > URL: https://issues.apache.org/jira/browse/GEODE-1467 > Project: Geode > Issue Type: Improvement > Components: rest (admin), rest (dev) >Reporter: Nitin Lamba >Assignee: Kevin Duling > > There are a few locations where gemfire references are used (excluding > package hierarchy covered in GEODE-37): > 1. servlet URLs for Dev REST (gemfire-api) and Mgmt REST (gemfire/v1) > 2. extension modules (http session mgmt) > 3. others (spring-data?) > (2) and (3) can be hairy as it may impact existing applications. A change > post 1.0 would create complexity, therefore, should be carefully considered > for 1.0 release. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (GEODE-1711) PersistentRVVRecoveryDUnitTest.testWriteCorrectVersionToKrf
[ https://issues.apache.org/jira/browse/GEODE-1711?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevin Duling updated GEODE-1711: Labels: CI (was: ) > PersistentRVVRecoveryDUnitTest.testWriteCorrectVersionToKrf > --- > > Key: GEODE-1711 > URL: https://issues.apache.org/jira/browse/GEODE-1711 > Project: Geode > Issue Type: Bug >Reporter: Kevin Duling > Labels: CI > > In Geode_develop_DistributedTests/3421: > {noformat} > Error Message > com.gemstone.gemfire.cache.DiskAccessException: For DiskStore: > PersistentRVVRecoveryDUnitTest_testWriteCorrectVersionToKrfRegion: Could not > schedule asynchronous write because the flusher thread had been terminated. > Stacktrace > com.gemstone.gemfire.cache.DiskAccessException: For DiskStore: > PersistentRVVRecoveryDUnitTest_testWriteCorrectVersionToKrfRegion: Could not > schedule asynchronous write because the flusher thread had been terminated. > at > com.gemstone.gemfire.internal.cache.DiskStoreImpl.checkForFlusherThreadTermination(DiskStoreImpl.java:1223) > at > com.gemstone.gemfire.internal.cache.DiskStoreImpl.addAsyncItem(DiskStoreImpl.java:1271) > at > com.gemstone.gemfire.internal.cache.DiskStoreImpl.scheduleAsyncWrite(DiskStoreImpl.java:1335) > at > com.gemstone.gemfire.internal.cache.DiskRegion.scheduleAsyncWrite(DiskRegion.java:483) > at > com.gemstone.gemfire.internal.cache.DiskEntry$Helper.scheduleAsyncWrite(DiskEntry.java:1494) > at > com.gemstone.gemfire.internal.cache.DiskEntry$Helper.update(DiskEntry.java:1034) > at > com.gemstone.gemfire.internal.cache.AbstractDiskRegionEntry.setValue(AbstractDiskRegionEntry.java:42) > at > com.gemstone.gemfire.internal.cache.AbstractRegionEntry.setValueWithTombstoneCheck(AbstractRegionEntry.java:241) > at > com.gemstone.gemfire.internal.cache.EntryEventImpl.setNewValueInRegion(EntryEventImpl.java:1614) > at > com.gemstone.gemfire.internal.cache.EntryEventImpl.putExistingEntry(EntryEventImpl.java:1482) > at > com.gemstone.gemfire.internal.cache.AbstractRegionMap.updateEntry(AbstractRegionMap.java:2882) > at > com.gemstone.gemfire.internal.cache.AbstractRegionMap.basicPut(AbstractRegionMap.java:2713) > at > com.gemstone.gemfire.internal.cache.LocalRegion.virtualPut(LocalRegion.java:5955) > at > com.gemstone.gemfire.internal.cache.DistributedRegion.virtualPut(DistributedRegion.java:348) > at > com.gemstone.gemfire.internal.cache.LocalRegionDataView.putEntry(LocalRegionDataView.java:132) > at > com.gemstone.gemfire.internal.cache.LocalRegion.basicPut(LocalRegion.java:5350) > at > com.gemstone.gemfire.internal.cache.LocalRegion.validatedPut(LocalRegion.java:1668) > at > com.gemstone.gemfire.internal.cache.LocalRegion.put(LocalRegion.java:1655) > at > com.gemstone.gemfire.internal.cache.AbstractRegion.put(AbstractRegion.java:288) > at > com.gemstone.gemfire.internal.cache.persistence.PersistentRVVRecoveryDUnitTest.testWriteCorrectVersionToKrf(PersistentRVVRecoveryDUnitTest.java:824) > 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.rules.TestWatcher$1.evaluate(TestWatcher.java:55) > at org.junit.rules.RunRules.evaluate(RunRules.java:20) > 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.internal.runners.statements.RunBefores.eva
[jira] [Created] (GEODE-1711) PersistentRVVRecoveryDUnitTest.testWriteCorrectVersionToKrf
Kevin Duling created GEODE-1711: --- Summary: PersistentRVVRecoveryDUnitTest.testWriteCorrectVersionToKrf Key: GEODE-1711 URL: https://issues.apache.org/jira/browse/GEODE-1711 Project: Geode Issue Type: Bug Reporter: Kevin Duling In Geode_develop_DistributedTests/3421: {noformat} Error Message com.gemstone.gemfire.cache.DiskAccessException: For DiskStore: PersistentRVVRecoveryDUnitTest_testWriteCorrectVersionToKrfRegion: Could not schedule asynchronous write because the flusher thread had been terminated. Stacktrace com.gemstone.gemfire.cache.DiskAccessException: For DiskStore: PersistentRVVRecoveryDUnitTest_testWriteCorrectVersionToKrfRegion: Could not schedule asynchronous write because the flusher thread had been terminated. at com.gemstone.gemfire.internal.cache.DiskStoreImpl.checkForFlusherThreadTermination(DiskStoreImpl.java:1223) at com.gemstone.gemfire.internal.cache.DiskStoreImpl.addAsyncItem(DiskStoreImpl.java:1271) at com.gemstone.gemfire.internal.cache.DiskStoreImpl.scheduleAsyncWrite(DiskStoreImpl.java:1335) at com.gemstone.gemfire.internal.cache.DiskRegion.scheduleAsyncWrite(DiskRegion.java:483) at com.gemstone.gemfire.internal.cache.DiskEntry$Helper.scheduleAsyncWrite(DiskEntry.java:1494) at com.gemstone.gemfire.internal.cache.DiskEntry$Helper.update(DiskEntry.java:1034) at com.gemstone.gemfire.internal.cache.AbstractDiskRegionEntry.setValue(AbstractDiskRegionEntry.java:42) at com.gemstone.gemfire.internal.cache.AbstractRegionEntry.setValueWithTombstoneCheck(AbstractRegionEntry.java:241) at com.gemstone.gemfire.internal.cache.EntryEventImpl.setNewValueInRegion(EntryEventImpl.java:1614) at com.gemstone.gemfire.internal.cache.EntryEventImpl.putExistingEntry(EntryEventImpl.java:1482) at com.gemstone.gemfire.internal.cache.AbstractRegionMap.updateEntry(AbstractRegionMap.java:2882) at com.gemstone.gemfire.internal.cache.AbstractRegionMap.basicPut(AbstractRegionMap.java:2713) at com.gemstone.gemfire.internal.cache.LocalRegion.virtualPut(LocalRegion.java:5955) at com.gemstone.gemfire.internal.cache.DistributedRegion.virtualPut(DistributedRegion.java:348) at com.gemstone.gemfire.internal.cache.LocalRegionDataView.putEntry(LocalRegionDataView.java:132) at com.gemstone.gemfire.internal.cache.LocalRegion.basicPut(LocalRegion.java:5350) at com.gemstone.gemfire.internal.cache.LocalRegion.validatedPut(LocalRegion.java:1668) at com.gemstone.gemfire.internal.cache.LocalRegion.put(LocalRegion.java:1655) at com.gemstone.gemfire.internal.cache.AbstractRegion.put(AbstractRegion.java:288) at com.gemstone.gemfire.internal.cache.persistence.PersistentRVVRecoveryDUnitTest.testWriteCorrectVersionToKrf(PersistentRVVRecoveryDUnitTest.java:824) 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.rules.TestWatcher$1.evaluate(TestWatcher.java:55) at org.junit.rules.RunRules.evaluate(RunRules.java:20) 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.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26) at org.junit.runners.ParentRunner.run(ParentRunner.java:363) at org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecuter.runTestClass(JUnitTestClassExecuter.java:112) at org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecuter.exe
[jira] [Updated] (GEODE-1710) CompiledInDUnitTest.whenMultipleTypeBindParameterIsUsedWithInQueryAndMapIndexIsPresentReturnCorrectResults
[ https://issues.apache.org/jira/browse/GEODE-1710?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevin Duling updated GEODE-1710: Labels: CI (was: ) > CompiledInDUnitTest.whenMultipleTypeBindParameterIsUsedWithInQueryAndMapIndexIsPresentReturnCorrectResults > -- > > Key: GEODE-1710 > URL: https://issues.apache.org/jira/browse/GEODE-1710 > Project: Geode > Issue Type: Bug >Reporter: Kevin Duling > Labels: CI > > In Geode_develop_DistributedTests/3430: > {noformat} > Error Message > com.gemstone.gemfire.test.dunit.RMIException: While invoking > com.gemstone.gemfire.cache.query.dunit.CompiledInDUnitTest$25.run in VM 1 > running on Host kuwait.gemstone.com with 4 VMs > Stacktrace > com.gemstone.gemfire.test.dunit.RMIException: While invoking > com.gemstone.gemfire.cache.query.dunit.CompiledInDUnitTest$25.run in VM 1 > running on Host kuwait.gemstone.com with 4 VMs > at com.gemstone.gemfire.test.dunit.VM.invoke(VM.java:389) > at com.gemstone.gemfire.test.dunit.VM.invoke(VM.java:355) > at com.gemstone.gemfire.test.dunit.VM.invoke(VM.java:293) > at > com.gemstone.gemfire.cache.query.dunit.CompiledInDUnitTest.whenMultipleTypeBindParameterIsUsedWithInQueryAndMapIndexIsPresentReturnCorrectResults(CompiledInDUnitTest.java:236) > 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.rules.TestWatcher$1.evaluate(TestWatcher.java:55) > at org.junit.rules.RunRules.evaluate(RunRules.java:20) > 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.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26) > at org.junit.runners.ParentRunner.run(ParentRunner.java:363) > at > org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecuter.runTestClass(JUnitTestClassExecuter.java:112) > 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:66) > at > org.gradle.api.internal.tasks.testing.SuiteTestClassProcessor.processTestClass(SuiteTestClassProcessor.java:51) > at sun.reflect.GeneratedMethodAccessor15.invoke(Unknown Source) > 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:109) > at sun.reflect.GeneratedMethodAccessor14.invoke(Unknown Source) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:497) > at > org.gradle.messaging.dispatch.ReflectionDispatch
[jira] [Created] (GEODE-1710) CompiledInDUnitTest.whenMultipleTypeBindParameterIsUsedWithInQueryAndMapIndexIsPresentReturnCorrectResults
Kevin Duling created GEODE-1710: --- Summary: CompiledInDUnitTest.whenMultipleTypeBindParameterIsUsedWithInQueryAndMapIndexIsPresentReturnCorrectResults Key: GEODE-1710 URL: https://issues.apache.org/jira/browse/GEODE-1710 Project: Geode Issue Type: Bug Reporter: Kevin Duling In Geode_develop_DistributedTests/3430: {noformat} Error Message com.gemstone.gemfire.test.dunit.RMIException: While invoking com.gemstone.gemfire.cache.query.dunit.CompiledInDUnitTest$25.run in VM 1 running on Host kuwait.gemstone.com with 4 VMs Stacktrace com.gemstone.gemfire.test.dunit.RMIException: While invoking com.gemstone.gemfire.cache.query.dunit.CompiledInDUnitTest$25.run in VM 1 running on Host kuwait.gemstone.com with 4 VMs at com.gemstone.gemfire.test.dunit.VM.invoke(VM.java:389) at com.gemstone.gemfire.test.dunit.VM.invoke(VM.java:355) at com.gemstone.gemfire.test.dunit.VM.invoke(VM.java:293) at com.gemstone.gemfire.cache.query.dunit.CompiledInDUnitTest.whenMultipleTypeBindParameterIsUsedWithInQueryAndMapIndexIsPresentReturnCorrectResults(CompiledInDUnitTest.java:236) 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.rules.TestWatcher$1.evaluate(TestWatcher.java:55) at org.junit.rules.RunRules.evaluate(RunRules.java:20) 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.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26) at org.junit.runners.ParentRunner.run(ParentRunner.java:363) at org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecuter.runTestClass(JUnitTestClassExecuter.java:112) 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:66) at org.gradle.api.internal.tasks.testing.SuiteTestClassProcessor.processTestClass(SuiteTestClassProcessor.java:51) at sun.reflect.GeneratedMethodAccessor15.invoke(Unknown Source) 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:109) at sun.reflect.GeneratedMethodAccessor14.invoke(Unknown Source) 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(ExecutorPol
[jira] [Created] (GEODE-1709) LuceneIndexCommandsDUnitTest.describeIndexShouldNotReturnResultWhenIndexNotFound
Kevin Duling created GEODE-1709: --- Summary: LuceneIndexCommandsDUnitTest.describeIndexShouldNotReturnResultWhenIndexNotFound Key: GEODE-1709 URL: https://issues.apache.org/jira/browse/GEODE-1709 Project: Geode Issue Type: Bug Reporter: Kevin Duling In Geode_develop_DistributedTests/3421: {noformat} Error Message com.gemstone.gemfire.test.dunit.RMIException: While invoking com.gemstone.gemfire.test.dunit.NamedCallable.call in VM 0 running on Host venezuela.gemstone.com with 4 VMs Stacktrace com.gemstone.gemfire.test.dunit.RMIException: While invoking com.gemstone.gemfire.test.dunit.NamedCallable.call in VM 0 running on Host venezuela.gemstone.com with 4 VMs at com.gemstone.gemfire.test.dunit.VM.invoke(VM.java:389) at com.gemstone.gemfire.test.dunit.VM.invoke(VM.java:355) at com.gemstone.gemfire.test.dunit.VM.invoke(VM.java:308) at com.gemstone.gemfire.management.internal.cli.commands.CliCommandTestBase.setUpJMXManagerOnVM(CliCommandTestBase.java:125) at com.gemstone.gemfire.management.internal.cli.commands.CliCommandTestBase.setUpJMXManagerOnVM(CliCommandTestBase.java:118) at com.gemstone.gemfire.management.internal.cli.commands.CliCommandTestBase.setUpJmxManagerOnVm0ThenConnect(CliCommandTestBase.java:109) at com.gemstone.gemfire.cache.lucene.internal.cli.LuceneIndexCommandsDUnitTest.createJMXManager(LuceneIndexCommandsDUnitTest.java:65) 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.RunBefores.evaluate(RunBefores.java:24) at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27) at org.junit.rules.ExternalResource$1.evaluate(ExternalResource.java:48) at org.junit.rules.ExternalResource$1.evaluate(ExternalResource.java:48) at org.junit.rules.TestWatcher$1.evaluate(TestWatcher.java:55) at org.junit.rules.RunRules.evaluate(RunRules.java:20) 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.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26) at org.junit.runners.ParentRunner.run(ParentRunner.java:363) at org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecuter.runTestClass(JUnitTestClassExecuter.java:112) 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:66) at org.gradle.api.internal.tasks.testing.SuiteTestClassProcessor.processTestClass(SuiteTestClassProcessor.java:51) at sun.reflect.GeneratedMethodAccessor14.invoke(Unknown Source) 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:109) at sun.reflect.GeneratedMethodAccessor13.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:497)
[jira] [Updated] (GEODE-1709) LuceneIndexCommandsDUnitTest.describeIndexShouldNotReturnResultWhenIndexNotFound
[ https://issues.apache.org/jira/browse/GEODE-1709?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevin Duling updated GEODE-1709: Labels: CI (was: ) > LuceneIndexCommandsDUnitTest.describeIndexShouldNotReturnResultWhenIndexNotFound > > > Key: GEODE-1709 > URL: https://issues.apache.org/jira/browse/GEODE-1709 > Project: Geode > Issue Type: Bug >Reporter: Kevin Duling > Labels: CI > > In Geode_develop_DistributedTests/3421: > {noformat} > Error Message > com.gemstone.gemfire.test.dunit.RMIException: While invoking > com.gemstone.gemfire.test.dunit.NamedCallable.call in VM 0 running on Host > venezuela.gemstone.com with 4 VMs > Stacktrace > com.gemstone.gemfire.test.dunit.RMIException: While invoking > com.gemstone.gemfire.test.dunit.NamedCallable.call in VM 0 running on Host > venezuela.gemstone.com with 4 VMs > at com.gemstone.gemfire.test.dunit.VM.invoke(VM.java:389) > at com.gemstone.gemfire.test.dunit.VM.invoke(VM.java:355) > at com.gemstone.gemfire.test.dunit.VM.invoke(VM.java:308) > at > com.gemstone.gemfire.management.internal.cli.commands.CliCommandTestBase.setUpJMXManagerOnVM(CliCommandTestBase.java:125) > at > com.gemstone.gemfire.management.internal.cli.commands.CliCommandTestBase.setUpJMXManagerOnVM(CliCommandTestBase.java:118) > at > com.gemstone.gemfire.management.internal.cli.commands.CliCommandTestBase.setUpJmxManagerOnVm0ThenConnect(CliCommandTestBase.java:109) > at > com.gemstone.gemfire.cache.lucene.internal.cli.LuceneIndexCommandsDUnitTest.createJMXManager(LuceneIndexCommandsDUnitTest.java:65) > 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.RunBefores.evaluate(RunBefores.java:24) > at > org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27) > at org.junit.rules.ExternalResource$1.evaluate(ExternalResource.java:48) > at org.junit.rules.ExternalResource$1.evaluate(ExternalResource.java:48) > at org.junit.rules.TestWatcher$1.evaluate(TestWatcher.java:55) > at org.junit.rules.RunRules.evaluate(RunRules.java:20) > 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.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26) > at org.junit.runners.ParentRunner.run(ParentRunner.java:363) > at > org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecuter.runTestClass(JUnitTestClassExecuter.java:112) > 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:66) > at > org.gradle.api.internal.tasks.testing.SuiteTestClassProcessor.processTestClass(SuiteTestClassProcessor.java:51) > at sun.reflect.GeneratedMethodAccessor14.invoke(Unknown Source) > 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
[jira] [Created] (GEODE-1708) CompiledInDUnitTest.whenASingleEnumBindParameterIsUsedWithInQueryAndMapIndexIsPresentReturnCorrectResults
Kevin Duling created GEODE-1708: --- Summary: CompiledInDUnitTest.whenASingleEnumBindParameterIsUsedWithInQueryAndMapIndexIsPresentReturnCorrectResults Key: GEODE-1708 URL: https://issues.apache.org/jira/browse/GEODE-1708 Project: Geode Issue Type: Bug Reporter: Kevin Duling In Geode_develop_DistributedTests/3423: {noformat} Error Message com.gemstone.gemfire.test.dunit.RMIException: While invoking com.gemstone.gemfire.cache.query.dunit.CompiledInDUnitTest$25.run in VM 1 running on Host cc2-rh6.gemstone.com with 4 VMs Stacktrace com.gemstone.gemfire.test.dunit.RMIException: While invoking com.gemstone.gemfire.cache.query.dunit.CompiledInDUnitTest$25.run in VM 1 running on Host cc2-rh6.gemstone.com with 4 VMs at com.gemstone.gemfire.test.dunit.VM.invoke(VM.java:389) at com.gemstone.gemfire.test.dunit.VM.invoke(VM.java:355) at com.gemstone.gemfire.test.dunit.VM.invoke(VM.java:293) at com.gemstone.gemfire.cache.query.dunit.CompiledInDUnitTest.whenASingleEnumBindParameterIsUsedWithInQueryAndMapIndexIsPresentReturnCorrectResults(CompiledInDUnitTest.java:197) 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.rules.TestWatcher$1.evaluate(TestWatcher.java:55) at org.junit.rules.RunRules.evaluate(RunRules.java:20) 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.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26) at org.junit.runners.ParentRunner.run(ParentRunner.java:363) at org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecuter.runTestClass(JUnitTestClassExecuter.java:112) 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:66) at org.gradle.api.internal.tasks.testing.SuiteTestClassProcessor.processTestClass(SuiteTestClassProcessor.java:51) 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:109) 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.gradl
[jira] [Updated] (GEODE-1708) CompiledInDUnitTest.whenASingleEnumBindParameterIsUsedWithInQueryAndMapIndexIsPresentReturnCorrectResults
[ https://issues.apache.org/jira/browse/GEODE-1708?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevin Duling updated GEODE-1708: Labels: CI (was: ) > CompiledInDUnitTest.whenASingleEnumBindParameterIsUsedWithInQueryAndMapIndexIsPresentReturnCorrectResults > - > > Key: GEODE-1708 > URL: https://issues.apache.org/jira/browse/GEODE-1708 > Project: Geode > Issue Type: Bug >Reporter: Kevin Duling > Labels: CI > > In Geode_develop_DistributedTests/3423: > {noformat} > Error Message > com.gemstone.gemfire.test.dunit.RMIException: While invoking > com.gemstone.gemfire.cache.query.dunit.CompiledInDUnitTest$25.run in VM 1 > running on Host cc2-rh6.gemstone.com with 4 VMs > Stacktrace > com.gemstone.gemfire.test.dunit.RMIException: While invoking > com.gemstone.gemfire.cache.query.dunit.CompiledInDUnitTest$25.run in VM 1 > running on Host cc2-rh6.gemstone.com with 4 VMs > at com.gemstone.gemfire.test.dunit.VM.invoke(VM.java:389) > at com.gemstone.gemfire.test.dunit.VM.invoke(VM.java:355) > at com.gemstone.gemfire.test.dunit.VM.invoke(VM.java:293) > at > com.gemstone.gemfire.cache.query.dunit.CompiledInDUnitTest.whenASingleEnumBindParameterIsUsedWithInQueryAndMapIndexIsPresentReturnCorrectResults(CompiledInDUnitTest.java:197) > 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.rules.TestWatcher$1.evaluate(TestWatcher.java:55) > at org.junit.rules.RunRules.evaluate(RunRules.java:20) > 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.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26) > at org.junit.runners.ParentRunner.run(ParentRunner.java:363) > at > org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecuter.runTestClass(JUnitTestClassExecuter.java:112) > 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:66) > at > org.gradle.api.internal.tasks.testing.SuiteTestClassProcessor.processTestClass(SuiteTestClassProcessor.java:51) > 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:109) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at > sun.reflect.DelegatingMetho
[jira] [Updated] (GEODE-1706) miscellaneouscommandsdunittest.testshutdownwithouttime...@com.gemstone.gemfire.management.internal.cli.commands.CommandOverHttpDUnitTest
[ https://issues.apache.org/jira/browse/GEODE-1706?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevin Duling updated GEODE-1706: Labels: ci (was: ) > miscellaneouscommandsdunittest.testshutdownwithouttime...@com.gemstone.gemfire.management.internal.cli.commands.CommandOverHttpDUnitTest > > > Key: GEODE-1706 > URL: https://issues.apache.org/jira/browse/GEODE-1706 > Project: Geode > Issue Type: Bug >Reporter: Kevin Duling > Labels: ci > > In Geode_develop_DistributedTests/3411: > {noformat} > Error Message > java.lang.AssertionError: Event never occurred after 1000 ms: Waits for the > shell to disconnect! > Stacktrace > java.lang.AssertionError: Event never occurred after 1000 ms: Waits for the > shell to disconnect! > at org.junit.Assert.fail(Assert.java:88) > at com.gemstone.gemfire.test.dunit.Wait.waitForCriterion(Wait.java:185) > at > com.gemstone.gemfire.management.internal.cli.commands.MiscellaneousCommandsDUnitTest.testShutDownWithoutTimeout(MiscellaneousCommandsDUnitTest.java:245) > 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.rules.ExternalResource$1.evaluate(ExternalResource.java:48) > at org.junit.rules.ExternalResource$1.evaluate(ExternalResource.java:48) > at org.junit.rules.TestWatcher$1.evaluate(TestWatcher.java:55) > at org.junit.rules.RunRules.evaluate(RunRules.java:20) > 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.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26) > at org.junit.runners.ParentRunner.run(ParentRunner.java:363) > at org.junit.runners.Suite.runChild(Suite.java:128) > at org.junit.runners.Suite.runChild(Suite.java:27) > 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.rules.ExternalResource$1.evaluate(ExternalResource.java:48) > at org.junit.rules.RunRules.evaluate(RunRules.java:20) > at org.junit.runners.ParentRunner.run(ParentRunner.java:363) > at > org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecuter.runTestClass(JUnitTestClassExecuter.java:112) > 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:66) > at > org.gradle.api.internal.tasks.testing.SuiteTestClassProcessor.processTestClass(SuiteTestClassProcessor.java:51) > 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.d
[jira] [Updated] (GEODE-1704) FixedPartitioningDUnitTest.testPut_ValidateDataOnMember_PrimarySecondary_Datastore
[ https://issues.apache.org/jira/browse/GEODE-1704?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevin Duling updated GEODE-1704: Labels: ci (was: ) > FixedPartitioningDUnitTest.testPut_ValidateDataOnMember_PrimarySecondary_Datastore > -- > > Key: GEODE-1704 > URL: https://issues.apache.org/jira/browse/GEODE-1704 > Project: Geode > Issue Type: Bug >Reporter: Kevin Duling > Labels: ci > > In Geode_develop_DistributedTests/3414: > {noformat} > Error Message > com.gemstone.gemfire.test.dunit.RMIException: While invoking > com.gemstone.gemfire.internal.cache.partitioned.fixed.FixedPartitioningDUnitTest$$Lambda$132/528994226.run > in VM 3 running on Host japan.gemstone.com with 4 VMs > Stacktrace > com.gemstone.gemfire.test.dunit.RMIException: While invoking > com.gemstone.gemfire.internal.cache.partitioned.fixed.FixedPartitioningDUnitTest$$Lambda$132/528994226.run > in VM 3 running on Host japan.gemstone.com with 4 VMs > at com.gemstone.gemfire.test.dunit.VM.invoke(VM.java:389) > at com.gemstone.gemfire.test.dunit.VM.invoke(VM.java:355) > at com.gemstone.gemfire.test.dunit.VM.invoke(VM.java:293) > at > com.gemstone.gemfire.internal.cache.partitioned.fixed.FixedPartitioningDUnitTest.testPut_ValidateDataOnMember_PrimarySecondary_Datastore(FixedPartitioningDUnitTest.java:1029) > 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.rules.TestWatcher$1.evaluate(TestWatcher.java:55) > at org.junit.rules.RunRules.evaluate(RunRules.java:20) > 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.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26) > at org.junit.runners.ParentRunner.run(ParentRunner.java:363) > at > org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecuter.runTestClass(JUnitTestClassExecuter.java:112) > 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:66) > at > org.gradle.api.internal.tasks.testing.SuiteTestClassProcessor.processTestClass(SuiteTestClassProcessor.java:51) > 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:109) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > a
[jira] [Updated] (GEODE-1705) DurableClientCommandsDUnitTest.testCloseDurableCQ
[ https://issues.apache.org/jira/browse/GEODE-1705?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevin Duling updated GEODE-1705: Labels: ci (was: ) > DurableClientCommandsDUnitTest.testCloseDurableCQ > - > > Key: GEODE-1705 > URL: https://issues.apache.org/jira/browse/GEODE-1705 > Project: Geode > Issue Type: Bug >Reporter: Kevin Duling > Labels: ci > > In Geode_develop_DistributedTests/3414: > {noformat} > Error Message > java.lang.AssertionError > Stacktrace > java.lang.AssertionError > at org.junit.Assert.fail(Assert.java:86) > at org.junit.Assert.assertTrue(Assert.java:41) > at org.junit.Assert.assertTrue(Assert.java:52) > at > com.gemstone.gemfire.management.internal.cli.commands.DurableClientCommandsDUnitTest.testCloseDurableCQ(DurableClientCommandsDUnitTest.java:138) > 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.rules.ExternalResource$1.evaluate(ExternalResource.java:48) > at org.junit.rules.ExternalResource$1.evaluate(ExternalResource.java:48) > at org.junit.rules.TestWatcher$1.evaluate(TestWatcher.java:55) > at org.junit.rules.RunRules.evaluate(RunRules.java:20) > 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.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26) > at org.junit.runners.ParentRunner.run(ParentRunner.java:363) > at > org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecuter.runTestClass(JUnitTestClassExecuter.java:112) > 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:66) > at > org.gradle.api.internal.tasks.testing.SuiteTestClassProcessor.processTestClass(SuiteTestClassProcessor.java:51) > at sun.reflect.GeneratedMethodAccessor377.invoke(Unknown Source) > 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:109) > at sun.reflect.GeneratedMethodAccessor376.invoke(Unknown Source) > 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.j
[jira] [Created] (GEODE-1706) miscellaneouscommandsdunittest.testshutdownwithouttime...@com.gemstone.gemfire.management.internal.cli.commands.CommandOverHttpDUnitTest
Kevin Duling created GEODE-1706: --- Summary: miscellaneouscommandsdunittest.testshutdownwithouttime...@com.gemstone.gemfire.management.internal.cli.commands.CommandOverHttpDUnitTest Key: GEODE-1706 URL: https://issues.apache.org/jira/browse/GEODE-1706 Project: Geode Issue Type: Bug Reporter: Kevin Duling In Geode_develop_DistributedTests/3411: {noformat} Error Message java.lang.AssertionError: Event never occurred after 1000 ms: Waits for the shell to disconnect! Stacktrace java.lang.AssertionError: Event never occurred after 1000 ms: Waits for the shell to disconnect! at org.junit.Assert.fail(Assert.java:88) at com.gemstone.gemfire.test.dunit.Wait.waitForCriterion(Wait.java:185) at com.gemstone.gemfire.management.internal.cli.commands.MiscellaneousCommandsDUnitTest.testShutDownWithoutTimeout(MiscellaneousCommandsDUnitTest.java:245) 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.rules.ExternalResource$1.evaluate(ExternalResource.java:48) at org.junit.rules.ExternalResource$1.evaluate(ExternalResource.java:48) at org.junit.rules.TestWatcher$1.evaluate(TestWatcher.java:55) at org.junit.rules.RunRules.evaluate(RunRules.java:20) 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.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26) at org.junit.runners.ParentRunner.run(ParentRunner.java:363) at org.junit.runners.Suite.runChild(Suite.java:128) at org.junit.runners.Suite.runChild(Suite.java:27) 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.rules.ExternalResource$1.evaluate(ExternalResource.java:48) at org.junit.rules.RunRules.evaluate(RunRules.java:20) at org.junit.runners.ParentRunner.run(ParentRunner.java:363) at org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecuter.runTestClass(JUnitTestClassExecuter.java:112) 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:66) at org.gradle.api.internal.tasks.testing.SuiteTestClassProcessor.processTestClass(SuiteTestClassProcessor.java:51) 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)
[jira] [Created] (GEODE-1705) DurableClientCommandsDUnitTest.testCloseDurableCQ
Kevin Duling created GEODE-1705: --- Summary: DurableClientCommandsDUnitTest.testCloseDurableCQ Key: GEODE-1705 URL: https://issues.apache.org/jira/browse/GEODE-1705 Project: Geode Issue Type: Bug Reporter: Kevin Duling In Geode_develop_DistributedTests/3414: {noformat} Error Message java.lang.AssertionError Stacktrace java.lang.AssertionError at org.junit.Assert.fail(Assert.java:86) at org.junit.Assert.assertTrue(Assert.java:41) at org.junit.Assert.assertTrue(Assert.java:52) at com.gemstone.gemfire.management.internal.cli.commands.DurableClientCommandsDUnitTest.testCloseDurableCQ(DurableClientCommandsDUnitTest.java:138) 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.rules.ExternalResource$1.evaluate(ExternalResource.java:48) at org.junit.rules.ExternalResource$1.evaluate(ExternalResource.java:48) at org.junit.rules.TestWatcher$1.evaluate(TestWatcher.java:55) at org.junit.rules.RunRules.evaluate(RunRules.java:20) 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.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26) at org.junit.runners.ParentRunner.run(ParentRunner.java:363) at org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecuter.runTestClass(JUnitTestClassExecuter.java:112) 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:66) at org.gradle.api.internal.tasks.testing.SuiteTestClassProcessor.processTestClass(SuiteTestClassProcessor.java:51) at sun.reflect.GeneratedMethodAccessor377.invoke(Unknown Source) 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:109) at sun.reflect.GeneratedMethodAccessor376.invoke(Unknown Source) 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 java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolEx
[jira] [Created] (GEODE-1704) FixedPartitioningDUnitTest.testPut_ValidateDataOnMember_PrimarySecondary_Datastore
Kevin Duling created GEODE-1704: --- Summary: FixedPartitioningDUnitTest.testPut_ValidateDataOnMember_PrimarySecondary_Datastore Key: GEODE-1704 URL: https://issues.apache.org/jira/browse/GEODE-1704 Project: Geode Issue Type: Bug Reporter: Kevin Duling In Geode_develop_DistributedTests/3414: {noformat} Error Message com.gemstone.gemfire.test.dunit.RMIException: While invoking com.gemstone.gemfire.internal.cache.partitioned.fixed.FixedPartitioningDUnitTest$$Lambda$132/528994226.run in VM 3 running on Host japan.gemstone.com with 4 VMs Stacktrace com.gemstone.gemfire.test.dunit.RMIException: While invoking com.gemstone.gemfire.internal.cache.partitioned.fixed.FixedPartitioningDUnitTest$$Lambda$132/528994226.run in VM 3 running on Host japan.gemstone.com with 4 VMs at com.gemstone.gemfire.test.dunit.VM.invoke(VM.java:389) at com.gemstone.gemfire.test.dunit.VM.invoke(VM.java:355) at com.gemstone.gemfire.test.dunit.VM.invoke(VM.java:293) at com.gemstone.gemfire.internal.cache.partitioned.fixed.FixedPartitioningDUnitTest.testPut_ValidateDataOnMember_PrimarySecondary_Datastore(FixedPartitioningDUnitTest.java:1029) 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.rules.TestWatcher$1.evaluate(TestWatcher.java:55) at org.junit.rules.RunRules.evaluate(RunRules.java:20) 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.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26) at org.junit.runners.ParentRunner.run(ParentRunner.java:363) at org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecuter.runTestClass(JUnitTestClassExecuter.java:112) 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:66) at org.gradle.api.internal.tasks.testing.SuiteTestClassProcessor.processTestClass(SuiteTestClassProcessor.java:51) 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:109) 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.dis
[jira] [Updated] (GEODE-1699) LuceneQueriesPeerPRRedundancyDUnitTest.returnCorrectResultsWhenRebalanceHappensWhileSenderIsPaused
[ https://issues.apache.org/jira/browse/GEODE-1699?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevin Duling updated GEODE-1699: Labels: ci (was: ) > LuceneQueriesPeerPRRedundancyDUnitTest.returnCorrectResultsWhenRebalanceHappensWhileSenderIsPaused > -- > > Key: GEODE-1699 > URL: https://issues.apache.org/jira/browse/GEODE-1699 > Project: Geode > Issue Type: Bug >Reporter: Kevin Duling > Labels: ci > > In Geode_develop_DistributedTests/3402: > {noformat} > Error Message > java.lang.AssertionError > Stacktrace > java.lang.AssertionError > at org.junit.Assert.fail(Assert.java:86) > at org.junit.Assert.assertTrue(Assert.java:41) > at org.junit.Assert.assertTrue(Assert.java:52) > at > com.gemstone.gemfire.cache.lucene.LuceneQueriesPRBase.returnCorrectResultsWhenRebalanceHappensWhileSenderIsPaused(LuceneQueriesPRBase.java:120) > 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.rules.TestWatcher$1.evaluate(TestWatcher.java:55) > at org.junit.rules.RunRules.evaluate(RunRules.java:20) > 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.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26) > at org.junit.runners.ParentRunner.run(ParentRunner.java:363) > at > org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecuter.runTestClass(JUnitTestClassExecuter.java:112) > 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:66) > at > org.gradle.api.internal.tasks.testing.SuiteTestClassProcessor.processTestClass(SuiteTestClassProcessor.java:51) > at sun.reflect.GeneratedMethodAccessor4.invoke(Unknown Source) > 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:109) > at sun.reflect.GeneratedMethodAccessor3.invoke(Unknown Source) > 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.StoppableExecuto
[jira] [Created] (GEODE-1699) LuceneQueriesPeerPRRedundancyDUnitTest.returnCorrectResultsWhenRebalanceHappensWhileSenderIsPaused
Kevin Duling created GEODE-1699: --- Summary: LuceneQueriesPeerPRRedundancyDUnitTest.returnCorrectResultsWhenRebalanceHappensWhileSenderIsPaused Key: GEODE-1699 URL: https://issues.apache.org/jira/browse/GEODE-1699 Project: Geode Issue Type: Bug Reporter: Kevin Duling In Geode_develop_DistributedTests/3402: {noformat} Error Message java.lang.AssertionError Stacktrace java.lang.AssertionError at org.junit.Assert.fail(Assert.java:86) at org.junit.Assert.assertTrue(Assert.java:41) at org.junit.Assert.assertTrue(Assert.java:52) at com.gemstone.gemfire.cache.lucene.LuceneQueriesPRBase.returnCorrectResultsWhenRebalanceHappensWhileSenderIsPaused(LuceneQueriesPRBase.java:120) 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.rules.TestWatcher$1.evaluate(TestWatcher.java:55) at org.junit.rules.RunRules.evaluate(RunRules.java:20) 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.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26) at org.junit.runners.ParentRunner.run(ParentRunner.java:363) at org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecuter.runTestClass(JUnitTestClassExecuter.java:112) 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:66) at org.gradle.api.internal.tasks.testing.SuiteTestClassProcessor.processTestClass(SuiteTestClassProcessor.java:51) at sun.reflect.GeneratedMethodAccessor4.invoke(Unknown Source) 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:109) at sun.reflect.GeneratedMethodAccessor3.invoke(Unknown Source) 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 java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:745) Standard Output Previously run tests: [LuceneIndex
[jira] [Created] (GEODE-1698) PRColocationDUnitTest.testColocationPartitionedRegionWithNullColocationSpecifiedOnOneNode
Kevin Duling created GEODE-1698: --- Summary: PRColocationDUnitTest.testColocationPartitionedRegionWithNullColocationSpecifiedOnOneNode Key: GEODE-1698 URL: https://issues.apache.org/jira/browse/GEODE-1698 Project: Geode Issue Type: Bug Reporter: Kevin Duling In Geode_develop_DistributedTests/3398: {noformat} Error Message com.gemstone.gemfire.distributed.DistributedSystemDisconnectedException: This connection to a distributed system has been disconnected., caused by com.gemstone.gemfire.ForcedDisconnectException: Member isn't responding to heartbeat requests Stacktrace com.gemstone.gemfire.distributed.DistributedSystemDisconnectedException: This connection to a distributed system has been disconnected., caused by com.gemstone.gemfire.ForcedDisconnectException: Member isn't responding to heartbeat requests at com.gemstone.gemfire.distributed.internal.InternalDistributedSystem.checkConnected(InternalDistributedSystem.java:790) at com.gemstone.gemfire.distributed.internal.InternalDistributedSystem.getDistributionManager(InternalDistributedSystem.java:1384) at com.gemstone.gemfire.distributed.internal.ReplyProcessor21.getDistributionManager(ReplyProcessor21.java:369) at com.gemstone.gemfire.distributed.internal.ReplyProcessor21.postWait(ReplyProcessor21.java:603) at com.gemstone.gemfire.distributed.internal.ReplyProcessor21.waitForRepliesUninterruptibly(ReplyProcessor21.java:844) at com.gemstone.gemfire.distributed.internal.ReplyProcessor21.waitForRepliesUninterruptibly(ReplyProcessor21.java:796) at com.gemstone.gemfire.distributed.internal.ReplyProcessor21.waitForRepliesUninterruptibly(ReplyProcessor21.java:886) at com.gemstone.gemfire.internal.cache.UpdateAttributesProcessor.waitForProfileResponse(UpdateAttributesProcessor.java:111) at com.gemstone.gemfire.internal.cache.UpdateAttributesProcessor.distribute(UpdateAttributesProcessor.java:99) at com.gemstone.gemfire.distributed.internal.DistributionAdvisor.exchangeProfiles(DistributionAdvisor.java:1131) at com.gemstone.gemfire.distributed.internal.DistributionAdvisor.initializationGate(DistributionAdvisor.java:458) at com.gemstone.gemfire.internal.cache.GemFireCacheImpl.initialize(GemFireCacheImpl.java:1096) at com.gemstone.gemfire.internal.cache.GemFireCacheImpl.basicCreate(GemFireCacheImpl.java:763) at com.gemstone.gemfire.internal.cache.GemFireCacheImpl.create(GemFireCacheImpl.java:751) at com.gemstone.gemfire.cache.CacheFactory.create(CacheFactory.java:181) at com.gemstone.gemfire.cache.CacheFactory.create(CacheFactory.java:172) at com.gemstone.gemfire.test.dunit.cache.internal.JUnit4CacheTestCase.createCache(JUnit4CacheTestCase.java:120) at com.gemstone.gemfire.test.dunit.cache.internal.JUnit4CacheTestCase.getCache(JUnit4CacheTestCase.java:263) at com.gemstone.gemfire.test.dunit.cache.internal.JUnit4CacheTestCase.getCache(JUnit4CacheTestCase.java:242) at com.gemstone.gemfire.test.dunit.cache.internal.JUnit4CacheTestCase.getCache(JUnit4CacheTestCase.java:234) at com.gemstone.gemfire.internal.cache.execute.PRColocationDUnitTest.testColocationPartitionedRegionWithNullColocationSpecifiedOnOneNode(PRColocationDUnitTest.java:1309) 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.rules.TestWatcher$1.evaluate(TestWatcher.java:55) at org.junit.rules.RunRules.evaluate(RunRules.java:20) 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(
[jira] [Updated] (GEODE-1698) PRColocationDUnitTest.testColocationPartitionedRegionWithNullColocationSpecifiedOnOneNode
[ https://issues.apache.org/jira/browse/GEODE-1698?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevin Duling updated GEODE-1698: Labels: ci (was: ) > PRColocationDUnitTest.testColocationPartitionedRegionWithNullColocationSpecifiedOnOneNode > - > > Key: GEODE-1698 > URL: https://issues.apache.org/jira/browse/GEODE-1698 > Project: Geode > Issue Type: Bug >Reporter: Kevin Duling > Labels: ci > > In Geode_develop_DistributedTests/3398: > {noformat} > Error Message > com.gemstone.gemfire.distributed.DistributedSystemDisconnectedException: This > connection to a distributed system has been disconnected., caused by > com.gemstone.gemfire.ForcedDisconnectException: Member isn't responding to > heartbeat requests > Stacktrace > com.gemstone.gemfire.distributed.DistributedSystemDisconnectedException: This > connection to a distributed system has been disconnected., caused by > com.gemstone.gemfire.ForcedDisconnectException: Member isn't responding to > heartbeat requests > at > com.gemstone.gemfire.distributed.internal.InternalDistributedSystem.checkConnected(InternalDistributedSystem.java:790) > at > com.gemstone.gemfire.distributed.internal.InternalDistributedSystem.getDistributionManager(InternalDistributedSystem.java:1384) > at > com.gemstone.gemfire.distributed.internal.ReplyProcessor21.getDistributionManager(ReplyProcessor21.java:369) > at > com.gemstone.gemfire.distributed.internal.ReplyProcessor21.postWait(ReplyProcessor21.java:603) > at > com.gemstone.gemfire.distributed.internal.ReplyProcessor21.waitForRepliesUninterruptibly(ReplyProcessor21.java:844) > at > com.gemstone.gemfire.distributed.internal.ReplyProcessor21.waitForRepliesUninterruptibly(ReplyProcessor21.java:796) > at > com.gemstone.gemfire.distributed.internal.ReplyProcessor21.waitForRepliesUninterruptibly(ReplyProcessor21.java:886) > at > com.gemstone.gemfire.internal.cache.UpdateAttributesProcessor.waitForProfileResponse(UpdateAttributesProcessor.java:111) > at > com.gemstone.gemfire.internal.cache.UpdateAttributesProcessor.distribute(UpdateAttributesProcessor.java:99) > at > com.gemstone.gemfire.distributed.internal.DistributionAdvisor.exchangeProfiles(DistributionAdvisor.java:1131) > at > com.gemstone.gemfire.distributed.internal.DistributionAdvisor.initializationGate(DistributionAdvisor.java:458) > at > com.gemstone.gemfire.internal.cache.GemFireCacheImpl.initialize(GemFireCacheImpl.java:1096) > at > com.gemstone.gemfire.internal.cache.GemFireCacheImpl.basicCreate(GemFireCacheImpl.java:763) > at > com.gemstone.gemfire.internal.cache.GemFireCacheImpl.create(GemFireCacheImpl.java:751) > at com.gemstone.gemfire.cache.CacheFactory.create(CacheFactory.java:181) > at com.gemstone.gemfire.cache.CacheFactory.create(CacheFactory.java:172) > at > com.gemstone.gemfire.test.dunit.cache.internal.JUnit4CacheTestCase.createCache(JUnit4CacheTestCase.java:120) > at > com.gemstone.gemfire.test.dunit.cache.internal.JUnit4CacheTestCase.getCache(JUnit4CacheTestCase.java:263) > at > com.gemstone.gemfire.test.dunit.cache.internal.JUnit4CacheTestCase.getCache(JUnit4CacheTestCase.java:242) > at > com.gemstone.gemfire.test.dunit.cache.internal.JUnit4CacheTestCase.getCache(JUnit4CacheTestCase.java:234) > at > com.gemstone.gemfire.internal.cache.execute.PRColocationDUnitTest.testColocationPartitionedRegionWithNullColocationSpecifiedOnOneNode(PRColocationDUnitTest.java:1309) > 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.rules.TestWatcher$1.evaluate(TestWatcher.java:55) > at org.junit.rules.RunRules.evaluate(RunRules.java:20) > at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325) > at > org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78) > at > org.junit.runners.BlockJUn
[jira] [Created] (GEODE-1697) RedisDistDUnitTest.testConcOps
Kevin Duling created GEODE-1697: --- Summary: RedisDistDUnitTest.testConcOps Key: GEODE-1697 URL: https://issues.apache.org/jira/browse/GEODE-1697 Project: Geode Issue Type: Bug Reporter: Kevin Duling In Geode_develop_DistributedTests/3405: {noformat} Error Message java.lang.AssertionError: An exception occurred during asynchronous invocation. Stacktrace java.lang.AssertionError: An exception occurred during asynchronous invocation. at com.gemstone.gemfire.test.dunit.AsyncInvocation.checkException(AsyncInvocation.java:155) at com.gemstone.gemfire.test.dunit.AsyncInvocation.getResult(AsyncInvocation.java:178) at org.apache.geode.redis.RedisDistDUnitTest.testConcOps(RedisDistDUnitTest.java:256) 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.rules.TestWatcher$1.evaluate(TestWatcher.java:55) at org.junit.rules.RunRules.evaluate(RunRules.java:20) 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.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26) at org.junit.runners.ParentRunner.run(ParentRunner.java:363) at org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecuter.runTestClass(JUnitTestClassExecuter.java:112) 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:66) at org.gradle.api.internal.tasks.testing.SuiteTestClassProcessor.processTestClass(SuiteTestClassProcessor.java:51) 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:109) 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 java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:
[jira] [Updated] (GEODE-1697) RedisDistDUnitTest.testConcOps
[ https://issues.apache.org/jira/browse/GEODE-1697?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevin Duling updated GEODE-1697: Labels: ci (was: ) > RedisDistDUnitTest.testConcOps > -- > > Key: GEODE-1697 > URL: https://issues.apache.org/jira/browse/GEODE-1697 > Project: Geode > Issue Type: Bug >Reporter: Kevin Duling > Labels: ci > > In Geode_develop_DistributedTests/3405: > {noformat} > Error Message > java.lang.AssertionError: An exception occurred during asynchronous > invocation. > Stacktrace > java.lang.AssertionError: An exception occurred during asynchronous > invocation. > at > com.gemstone.gemfire.test.dunit.AsyncInvocation.checkException(AsyncInvocation.java:155) > at > com.gemstone.gemfire.test.dunit.AsyncInvocation.getResult(AsyncInvocation.java:178) > at > org.apache.geode.redis.RedisDistDUnitTest.testConcOps(RedisDistDUnitTest.java:256) > 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.rules.TestWatcher$1.evaluate(TestWatcher.java:55) > at org.junit.rules.RunRules.evaluate(RunRules.java:20) > 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.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26) > at org.junit.runners.ParentRunner.run(ParentRunner.java:363) > at > org.gradle.api.internal.tasks.testing.junit.JUnitTestClassExecuter.runTestClass(JUnitTestClassExecuter.java:112) > 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:66) > at > org.gradle.api.internal.tasks.testing.SuiteTestClassProcessor.processTestClass(SuiteTestClassProcessor.java:51) > 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:109) > 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
[jira] [Resolved] (GEODE-1680) Change "list regions" to DATA:READ permissions
[ https://issues.apache.org/jira/browse/GEODE-1680?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevin Duling resolved GEODE-1680. - Resolution: Fixed > Change "list regions" to DATA:READ permissions > -- > > Key: GEODE-1680 > URL: https://issues.apache.org/jira/browse/GEODE-1680 > Project: Geode > Issue Type: Task > Components: gfsh, security >Reporter: Kevin Duling >Assignee: Kevin Duling > > Currently, "list regions" requires CLUSTER:READ permissions. This should be > DATA:READ -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (GEODE-1680) Change "list regions" to DATA:READ permissions
[ https://issues.apache.org/jira/browse/GEODE-1680?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevin Duling reassigned GEODE-1680: --- Assignee: Kevin Duling > Change "list regions" to DATA:READ permissions > -- > > Key: GEODE-1680 > URL: https://issues.apache.org/jira/browse/GEODE-1680 > Project: Geode > Issue Type: Task > Components: gfsh, security >Reporter: Kevin Duling >Assignee: Kevin Duling > > Currently, "list regions" requires CLUSTER:READ permissions. This should be > DATA:READ -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (GEODE-1680) Change "list regions" to DATA:READ permissions
Kevin Duling created GEODE-1680: --- Summary: Change "list regions" to DATA:READ permissions Key: GEODE-1680 URL: https://issues.apache.org/jira/browse/GEODE-1680 Project: Geode Issue Type: Task Components: gfsh, security Reporter: Kevin Duling Currently, "list regions" requires CLUSTER:READ permissions. This should be DATA:READ -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (GEODE-746) When starting a locator using --bind-address, gfsh prints incorrect connect message
[ https://issues.apache.org/jira/browse/GEODE-746?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevin Duling resolved GEODE-746. Resolution: Fixed > When starting a locator using --bind-address, gfsh prints incorrect connect > message > --- > > Key: GEODE-746 > URL: https://issues.apache.org/jira/browse/GEODE-746 > Project: Geode > Issue Type: Improvement > Components: gfsh >Reporter: Jens Deppe >Assignee: Kevin Duling > > When starting my locator with {{gfsh start locator --name=locator1 > --port=19991 --bind-address=192.168.103.1}}, the output from gfsh looks like > this: > {noformat} > .. > Locator in /Users/jdeppe/debug/locator1 on 192.168.103.1[19991] as locator1 > is currently online. > Process ID: 2666 > Uptime: 15 seconds > GemFire Version: 8.2.0.Beta > Java Version: 1.7.0_72 > Log File: /Users/jdeppe/debug/locator1/locator1.log > JVM Arguments: -Dgemfire.enable-cluster-configuration=true > -Dgemfire.load-cluster-configuration-from-dir=false > -Dgemfire.launcher.registerSignalHandlers=true -Djava.awt.headless=true > -Dsun.rmi.dgc.server.gcInterval=9223372036854775806 > Class-Path: > /Users/jdeppe/gemfire/82/lib/gemfire.jar:/Users/jdeppe/gemfire/82/lib/locator-dependencies.jar > Please use "connect --locator=192.168.1.10[19991]" to connect Gfsh to the > locator. > Failed to connect; unknown cause: Connection refused > {noformat} > The connect string shown is just displaying my host address and not the bind > address. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Comment Edited] (GEODE-746) When starting a locator using --bind-address, gfsh prints incorrect connect message
[ https://issues.apache.org/jira/browse/GEODE-746?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15377423#comment-15377423 ] Kevin Duling edited comment on GEODE-746 at 7/14/16 10:45 PM: -- Grace and I tracked the first part of this down to a problem in {{LauncherLifecycleCommands}}: {{String locatorHostName = StringUtils.defaultIfBlank(locatorLauncher.getHostnameForClients(), getLocalHost());}} We've changed this to look instead at the bind address first: {code} String locatorHostName; InetAddress bindAddr = locatorLauncher.getBindAddress(); if (bindAddr != null){ locatorHostName = bindAddr.getCanonicalHostName(); } else { locatorHostName = StringUtils.defaultIfBlank(locatorLauncher.getHostnameForClients(), getLocalHost()); } {code} This resolved the problem. The system will now connect: {{gfsh start locator --name=locator1 --port=19991 --bind-address=192.168.1.187}} {noformat} Listening for transport dt_socket at address: 3 ... Locator in /gemfire/open/locator1 on 192.168.1.187[19991] as locator1 is currently online. Process ID: 2765 Uptime: 1 minute 23 seconds GemFire Version: 1.0.0-incubating-SNAPSHOT Java Version: 1.8.0_92 Log File: /gemfire/open/locator1/locator1.log JVM Arguments: -Dgemfire.enable-cluster-configuration=true -Dgemfire.load-cluster-configuration-from-dir=false -agentlib:jdwp=transport=dt_socket,server=y,suspend=y,address=2 -Dgemfire.launcher.registerSignalHandlers=true -Djava.awt.headless=true -Dsun.rmi.dgc.server.gcInterval=9223372036854775806 Class-Path: /gemfire/open/geode-assembly/build/install/apache-geode/lib/geode-core-1.0.0-incubating-SNAPSHOT.jar:/gemfire/open/geode-assembly/build/install/apache-geode/lib/geode-dependencies.jar Successfully connected to: [host=pdx2-office-dhcp9.eng.vmware.com, port=1099] Cluster configuration service is up and running. {noformat} The successfully connected message appears to be showing the wrong IP address. Looking at netstat, we can see that the listener is correctly bound to the IP address specified: {noformat} $ netstat -an | grep 19991 tcp4 0 0 192.168.1.187.19991*.*LISTEN {noformat} The "successfully connected" hostname reports a different NIC: {{ping pdx2-office-dhcp9.eng.vmware.com}} {noformat} PING pdx2-office-dhcp9.eng.vmware.com (10.118.33.209): 56 data bytes {noformat} Both NICs exist on this machine: {{nestat -rn}} {noformat} Routing tables Internet: DestinationGatewayFlagsRefs Use Netif Expire default10.118.33.253 UGSc 3600 en4 default192.168.1.253 UGScI 350 en0 {noformat} Tracing this down, the address is coming from this line in {{ShellCommands.connectToLocator(String host, int port, int timeout, Map props)}} {code} JmxManagerLocatorResponse locatorResponse = JmxManagerLocatorRequest.send(host, port, timeout, props); // locatorResponse: “JmxManagerLocatorResponse [host=10.118.33.209, port=1099, ssl=false, ex=null]” // host: “192.168.1.187” // port: 19991 // timeout: 15000 // props: size = 0 {code} So the confusion here now is that this is the JMX address, not the locator address. The formatting of this message lends one to believe it's supposed to be the locator. Yet, if you look at the original response from the system, it correctly reports the Locator's address: {noformat} Locator in /gemfire/open/locator1 on 192.168.1.187[19991] as locator1 is currently online. {noformat} I've added JMX to the "successfully connected" message to reduce confusion. was (Author: kduling): Grace and I tracked the first part of this down to a problem in {{LauncherLifecycleCommands}}: {{String locatorHostName = StringUtils.defaultIfBlank(locatorLauncher.getHostnameForClients(), getLocalHost());}} We've changed this to look instead at the bind address first: {code} String locatorHostName; InetAddress bindAddr = locatorLauncher.getBindAddress(); if (bindAddr != null){ locatorHostName = bindAddr.getCanonicalHostName(); } else { locatorHostName = StringUtils.defaultIfBlank(locatorLauncher.getHostnameForClients(), getLocalHost()); } {code} This improved things a little. The system will now connect: {{gfsh start locator --name=locator1 --port=19991 --bind-address=192.168.1.187}} {noformat} Listening for transport dt_socket at address: 3 ... Locator in /gemfire/open/locator1 on 192.168.1.187[19991] as locator1 is currently online. Process ID: 2765 Uptime: 1 minute 23 seconds GemFire Version: 1.0.0-incubating-SNAPSHOT Java Version: 1.8.0_92 Log File: /gemfire/open/locator1/locator1.log JVM Arguments: -Dgemfire.enable-cluster-configuration=true -Dgemfire.load-cluster-configuration-from-dir=false -a
[jira] [Commented] (GEODE-746) When starting a locator using --bind-address, gfsh prints incorrect connect message
[ https://issues.apache.org/jira/browse/GEODE-746?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15377423#comment-15377423 ] Kevin Duling commented on GEODE-746: Grace and I tracked the first part of this down to a problem in {{LauncherLifecycleCommands}}: {{String locatorHostName = StringUtils.defaultIfBlank(locatorLauncher.getHostnameForClients(), getLocalHost());}} We've changed this to look instead at the bind address first: {code} String locatorHostName; InetAddress bindAddr = locatorLauncher.getBindAddress(); if (bindAddr != null){ locatorHostName = bindAddr.getCanonicalHostName(); } else { locatorHostName = StringUtils.defaultIfBlank(locatorLauncher.getHostnameForClients(), getLocalHost()); } {code} This improved things a little. The system will now connect: {{gfsh start locator --name=locator1 --port=19991 --bind-address=192.168.1.187}} {noformat} Listening for transport dt_socket at address: 3 ... Locator in /gemfire/open/locator1 on 192.168.1.187[19991] as locator1 is currently online. Process ID: 2765 Uptime: 1 minute 23 seconds GemFire Version: 1.0.0-incubating-SNAPSHOT Java Version: 1.8.0_92 Log File: /gemfire/open/locator1/locator1.log JVM Arguments: -Dgemfire.enable-cluster-configuration=true -Dgemfire.load-cluster-configuration-from-dir=false -agentlib:jdwp=transport=dt_socket,server=y,suspend=y,address=2 -Dgemfire.launcher.registerSignalHandlers=true -Djava.awt.headless=true -Dsun.rmi.dgc.server.gcInterval=9223372036854775806 Class-Path: /gemfire/open/geode-assembly/build/install/apache-geode/lib/geode-core-1.0.0-incubating-SNAPSHOT.jar:/gemfire/open/geode-assembly/build/install/apache-geode/lib/geode-dependencies.jar Successfully connected to: [host=pdx2-office-dhcp9.eng.vmware.com, port=1099] Cluster configuration service is up and running. {noformat} But now the successfully connected message is showing the wrong IP address. Looking at netstat, we can see that the listener is correctly bound to the IP address specified: {noformat} $ netstat -an | grep 19991 tcp4 0 0 192.168.1.187.19991*.*LISTEN {noformat} Yet the hostname actually resolves to a different NIC: {{ping pdx2-office-dhcp9.eng.vmware.com}} {noformat} PING pdx2-office-dhcp9.eng.vmware.com (10.118.33.209): 56 data bytes {noformat} Both NICs exist on this machine, just one is being erroneously reported: {{nestat -rn}} {noformat} Routing tables Internet: DestinationGatewayFlagsRefs Use Netif Expire default10.118.33.253 UGSc 3600 en4 default192.168.1.253 UGScI 350 en0 {noformat} Tracing this down, it appears to be an incorrect response from the locator in {{ShellCommands.connectToLocator(String host, int port, int timeout, Map props)}} {code} JmxManagerLocatorResponse locatorResponse = JmxManagerLocatorRequest.send(host, port, timeout, props); // locatorResponse: “JmxManagerLocatorResponse [host=10.118.33.209, port=1099, ssl=false, ex=null]” // host: “192.168.1.187” // port: 19991 // timeout: 15000 // props: size = 0 {code} > When starting a locator using --bind-address, gfsh prints incorrect connect > message > --- > > Key: GEODE-746 > URL: https://issues.apache.org/jira/browse/GEODE-746 > Project: Geode > Issue Type: Improvement > Components: gfsh >Reporter: Jens Deppe >Assignee: Kevin Duling > > When starting my locator with {{gfsh start locator --name=locator1 > --port=19991 --bind-address=192.168.103.1}}, the output from gfsh looks like > this: > {noformat} > .. > Locator in /Users/jdeppe/debug/locator1 on 192.168.103.1[19991] as locator1 > is currently online. > Process ID: 2666 > Uptime: 15 seconds > GemFire Version: 8.2.0.Beta > Java Version: 1.7.0_72 > Log File: /Users/jdeppe/debug/locator1/locator1.log > JVM Arguments: -Dgemfire.enable-cluster-configuration=true > -Dgemfire.load-cluster-configuration-from-dir=false > -Dgemfire.launcher.registerSignalHandlers=true -Djava.awt.headless=true > -Dsun.rmi.dgc.server.gcInterval=9223372036854775806 > Class-Path: > /Users/jdeppe/gemfire/82/lib/gemfire.jar:/Users/jdeppe/gemfire/82/lib/locator-dependencies.jar > Please use "connect --locator=192.168.1.10[19991]" to connect Gfsh to the > locator. > Failed to connect; unknown cause: Connection refused > {noformat} > The connect string shown is just displaying my host address and not the bind > address. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (GEODE-746) When starting a locator using --bind-address, gfsh prints incorrect connect message
[ https://issues.apache.org/jira/browse/GEODE-746?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevin Duling reassigned GEODE-746: -- Assignee: Kevin Duling > When starting a locator using --bind-address, gfsh prints incorrect connect > message > --- > > Key: GEODE-746 > URL: https://issues.apache.org/jira/browse/GEODE-746 > Project: Geode > Issue Type: Improvement > Components: gfsh >Reporter: Jens Deppe >Assignee: Kevin Duling > > When starting my locator with {{gfsh start locator --name=locator1 > --port=19991 --bind-address=192.168.103.1}}, the output from gfsh looks like > this: > {noformat} > .. > Locator in /Users/jdeppe/debug/locator1 on 192.168.103.1[19991] as locator1 > is currently online. > Process ID: 2666 > Uptime: 15 seconds > GemFire Version: 8.2.0.Beta > Java Version: 1.7.0_72 > Log File: /Users/jdeppe/debug/locator1/locator1.log > JVM Arguments: -Dgemfire.enable-cluster-configuration=true > -Dgemfire.load-cluster-configuration-from-dir=false > -Dgemfire.launcher.registerSignalHandlers=true -Djava.awt.headless=true > -Dsun.rmi.dgc.server.gcInterval=9223372036854775806 > Class-Path: > /Users/jdeppe/gemfire/82/lib/gemfire.jar:/Users/jdeppe/gemfire/82/lib/locator-dependencies.jar > Please use "connect --locator=192.168.1.10[19991]" to connect Gfsh to the > locator. > Failed to connect; unknown cause: Connection refused > {noformat} > The connect string shown is just displaying my host address and not the bind > address. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (GEODE-1617) Regions can be created with a variety of characters that are unsupported
[ https://issues.apache.org/jira/browse/GEODE-1617?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevin Duling resolved GEODE-1617. - Resolution: Fixed Added a test at creation for valid characters in region names for all non-internal regions. > Regions can be created with a variety of characters that are unsupported > > > Key: GEODE-1617 > URL: https://issues.apache.org/jira/browse/GEODE-1617 > Project: Geode > Issue Type: Bug > Components: gfsh >Affects Versions: 1.0.0-incubating.M2 >Reporter: Kevin Duling >Assignee: Kevin Duling > > Per this > [thread|https://www.mail-archive.com/dev@geode.incubator.apache.org/msg04046.html], > and this > [thread|https://www.mail-archive.com/dev@geode.incubator.apache.org/msg07079.html] > on the dev forums and [geode > documentation|http://docs-geode-develop.cfapps.io/docs/basic_config/data_regions/region_naming.html], > region names may only consist of alphanumeric characters, an underscore, and > a hyphen. These rules are not enforced. > E.g., it is possible to create a region with: > {{gfsh> create region --name=not^good --type=REPLICATE}} > Some of these regions may be removed with the {{destroy}} command, while > others cannot be located. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (GEODE-1617) Regions can be created with a variety of characters that are unsupported
[ https://issues.apache.org/jira/browse/GEODE-1617?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevin Duling updated GEODE-1617: Affects Version/s: 1.0.0-incubating.M2 > Regions can be created with a variety of characters that are unsupported > > > Key: GEODE-1617 > URL: https://issues.apache.org/jira/browse/GEODE-1617 > Project: Geode > Issue Type: Bug > Components: gfsh >Affects Versions: 1.0.0-incubating.M2 >Reporter: Kevin Duling >Assignee: Kevin Duling > > Per this > [thread|https://www.mail-archive.com/dev@geode.incubator.apache.org/msg04046.html], > and this > [thread|https://www.mail-archive.com/dev@geode.incubator.apache.org/msg07079.html] > on the dev forums and [geode > documentation|http://docs-geode-develop.cfapps.io/docs/basic_config/data_regions/region_naming.html], > region names may only consist of alphanumeric characters, an underscore, and > a hyphen. These rules are not enforced. > E.g., it is possible to create a region with: > {{gfsh> create region --name=not^good --type=REPLICATE}} > Some of these regions may be removed with the {{destroy}} command, while > others cannot be located. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (GEODE-1615) gfsh unable to destroy region that has an hyphen in its name
[ https://issues.apache.org/jira/browse/GEODE-1615?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevin Duling resolved GEODE-1615. - Resolution: Fixed > gfsh unable to destroy region that has an hyphen in its name > > > Key: GEODE-1615 > URL: https://issues.apache.org/jira/browse/GEODE-1615 > Project: Geode > Issue Type: Bug > Components: gfsh >Reporter: Swapnil Bawaskar >Assignee: Kevin Duling > > Can be reproduced as follows: > {noformat} > gfsh>list regions > List of regions > --- > region-name > region_name > gfsh>destroy region --name=region_name > "region_name" destroyed successfully. > gfsh>list regions > List of regions > --- > region-name > gfsh>destroy region --name=region-name > Could not find a Region with Region path "region-name" in this Geode cluster. > If region was recently > {noformat} -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (GEODE-1617) Regions can be created with a variety of characters that are unsupported
Kevin Duling created GEODE-1617: --- Summary: Regions can be created with a variety of characters that are unsupported Key: GEODE-1617 URL: https://issues.apache.org/jira/browse/GEODE-1617 Project: Geode Issue Type: Bug Components: gfsh Reporter: Kevin Duling Per this [thread|https://www.mail-archive.com/dev@geode.incubator.apache.org/msg04046.html], and this [thread|https://www.mail-archive.com/dev@geode.incubator.apache.org/msg07079.html] on the dev forums and [geode documentation|http://docs-geode-develop.cfapps.io/docs/basic_config/data_regions/region_naming.html], region names may only consist of alphanumeric characters, an underscore, and a hyphen. These rules are not enforced. E.g., it is possible to create a region with: {{gfsh> create region --name=not^good --type=REPLICATE}} Some of these regions may be removed with the {{destroy}} command, while others cannot be located. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (GEODE-1617) Regions can be created with a variety of characters that are unsupported
[ https://issues.apache.org/jira/browse/GEODE-1617?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevin Duling reassigned GEODE-1617: --- Assignee: Kevin Duling > Regions can be created with a variety of characters that are unsupported > > > Key: GEODE-1617 > URL: https://issues.apache.org/jira/browse/GEODE-1617 > Project: Geode > Issue Type: Bug > Components: gfsh >Reporter: Kevin Duling >Assignee: Kevin Duling > > Per this > [thread|https://www.mail-archive.com/dev@geode.incubator.apache.org/msg04046.html], > and this > [thread|https://www.mail-archive.com/dev@geode.incubator.apache.org/msg07079.html] > on the dev forums and [geode > documentation|http://docs-geode-develop.cfapps.io/docs/basic_config/data_regions/region_naming.html], > region names may only consist of alphanumeric characters, an underscore, and > a hyphen. These rules are not enforced. > E.g., it is possible to create a region with: > {{gfsh> create region --name=not^good --type=REPLICATE}} > Some of these regions may be removed with the {{destroy}} command, while > others cannot be located. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Comment Edited] (GEODE-1615) gfsh unable to destroy region that has an hyphen in its name
[ https://issues.apache.org/jira/browse/GEODE-1615?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15357762#comment-15357762 ] Kevin Duling edited comment on GEODE-1615 at 6/30/16 8:02 PM: -- Found that internally, the region is stored as {{service=Region, name="/region-name", type=Member}} and the query to find it is not placing quotes around the name. Conversely, non-hyphenated regions do not contain quotes. E.g., {{service=Region, name=/good, type=Member}} The mechanism that added quotes during creation is not being triggered when destroying, therefore the lookup fails. was (Author: kduling): Found that internally, the region is stored as {{service=Region, name="/region-name", type=Member}} and the query to find it is not placing quotes around the name. Conversely, non-hyphenated regions do not contain quotes. E.g., {{service=Region, name=good, type=Member}} The mechanism that added quotes during creation is not being triggered when destroying, therefore the lookup fails. > gfsh unable to destroy region that has an hyphen in its name > > > Key: GEODE-1615 > URL: https://issues.apache.org/jira/browse/GEODE-1615 > Project: Geode > Issue Type: Bug > Components: gfsh >Reporter: Swapnil Bawaskar >Assignee: Kevin Duling > > Can be reproduced as follows: > {noformat} > gfsh>list regions > List of regions > --- > region-name > region_name > gfsh>destroy region --name=region_name > "region_name" destroyed successfully. > gfsh>list regions > List of regions > --- > region-name > gfsh>destroy region --name=region-name > Could not find a Region with Region path "region-name" in this Geode cluster. > If region was recently > {noformat} -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (GEODE-1615) gfsh unable to destroy region that has an hyphen in its name
[ https://issues.apache.org/jira/browse/GEODE-1615?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15357762#comment-15357762 ] Kevin Duling commented on GEODE-1615: - Found that internally, the region is stored as {{service=Region, name="/region-name", type=Member}} and the query to find it is not placing quotes around the name. Conversely, non-hyphenated regions do not contain quotes. E.g., {{service=Region, name=good, type=Member}} The mechanism that added quotes during creation is not being triggered when destroying, therefore the lookup fails. > gfsh unable to destroy region that has an hyphen in its name > > > Key: GEODE-1615 > URL: https://issues.apache.org/jira/browse/GEODE-1615 > Project: Geode > Issue Type: Bug > Components: gfsh >Reporter: Swapnil Bawaskar >Assignee: Kevin Duling > > Can be reproduced as follows: > {noformat} > gfsh>list regions > List of regions > --- > region-name > region_name > gfsh>destroy region --name=region_name > "region_name" destroyed successfully. > gfsh>list regions > List of regions > --- > region-name > gfsh>destroy region --name=region-name > Could not find a Region with Region path "region-name" in this Geode cluster. > If region was recently > {noformat} -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (GEODE-1615) gfsh unable to destroy region that has an hyphen in its name
[ https://issues.apache.org/jira/browse/GEODE-1615?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevin Duling updated GEODE-1615: Summary: gfsh unable to destroy region that has an hyphen in its name (was: gfsh unable to destroy region that has an hyphen in it's name) > gfsh unable to destroy region that has an hyphen in its name > > > Key: GEODE-1615 > URL: https://issues.apache.org/jira/browse/GEODE-1615 > Project: Geode > Issue Type: Bug > Components: gfsh >Reporter: Swapnil Bawaskar >Assignee: Kevin Duling > > Can be reproduced as follows: > {noformat} > gfsh>list regions > List of regions > --- > region-name > region_name > gfsh>destroy region --name=region_name > "region_name" destroyed successfully. > gfsh>list regions > List of regions > --- > region-name > gfsh>destroy region --name=region-name > Could not find a Region with Region path "region-name" in this Geode cluster. > If region was recently > {noformat} -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (GEODE-1615) gfsh unable to destroy region that has an hyphen in it's name
[ https://issues.apache.org/jira/browse/GEODE-1615?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevin Duling reassigned GEODE-1615: --- Assignee: Kevin Duling > gfsh unable to destroy region that has an hyphen in it's name > - > > Key: GEODE-1615 > URL: https://issues.apache.org/jira/browse/GEODE-1615 > Project: Geode > Issue Type: Bug > Components: gfsh >Reporter: Swapnil Bawaskar >Assignee: Kevin Duling > > Can be reproduced as follows: > {noformat} > gfsh>list regions > List of regions > --- > region-name > region_name > gfsh>destroy region --name=region_name > "region_name" destroyed successfully. > gfsh>list regions > List of regions > --- > region-name > gfsh>destroy region --name=region-name > Could not find a Region with Region path "region-name" in this Geode cluster. > If region was recently > {noformat} -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (GEODE-1575) Unhandled NoClassDefFound Exception when creating regions
[ https://issues.apache.org/jira/browse/GEODE-1575?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevin Duling updated GEODE-1575: Component/s: gfsh > Unhandled NoClassDefFound Exception when creating regions > - > > Key: GEODE-1575 > URL: https://issues.apache.org/jira/browse/GEODE-1575 > Project: Geode > Issue Type: Bug > Components: configuration, gfsh >Reporter: Kevin Duling >Assignee: Kevin Duling > Fix For: 1.0.0-incubating.M3 > > > The wrong error message is being displayed when encountering a > {{NoClassDefFoundError}} > {panel:title=gfsh} > {noformat} > Executing - create region --name=replicatedRegion --type=REPLICATE > --cache-loader=com.example.TestCacheLoader > Could not process command due to GemFire error. > java.lang.ClassNotFoundException cannot be cast to > com.gemstone.gemfire.management.internal.cli.functions.CliFunctionResult > {noformat} > {panel} > {panel:title=server.log} > {noformat} > [fine 2016/06/21 10:02:02.745 PDT host1-server1 Processor1> tid=0x41] Replying with exception: ReplyMessage processorId=13 > from null with exception > com.gemstone.gemfire.distributed.internal.ReplyException: > java.lang.NoClassDefFoundError: org/apache/log4j/Logger > com.gemstone.gemfire.distributed.internal.ReplyException: > java.lang.NoClassDefFoundError: org/apache/log4j/Logger > at > com.gemstone.gemfire.internal.cache.MemberFunctionStreamingMessage.process(MemberFunctionStreamingMessage.java:248) > at > com.gemstone.gemfire.distributed.internal.DistributionMessage.scheduleAction(DistributionMessage.java:379) > at > com.gemstone.gemfire.distributed.internal.DistributionMessage$1.run(DistributionMessage.java:450) > at > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) > at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > at > com.gemstone.gemfire.distributed.internal.DistributionManager.runUntilShutdown(DistributionManager.java:611) > at > com.gemstone.gemfire.distributed.internal.DistributionManager$9$1.run(DistributionManager.java:1071) > at java.lang.Thread.run(Thread.java:745) > Caused by: java.lang.NoClassDefFoundError: org/apache/log4j/Logger > at > io.pivotal.support.cases.server.TestCacheLoader.(TestCacheLoader.java:14) > at java.lang.Class.forName0(Native Method) > at java.lang.Class.forName(Class.java:348) > at > com.gemstone.gemfire.internal.ClassPathLoader.forName(ClassPathLoader.java:408) > at > com.gemstone.gemfire.management.internal.cli.functions.RegionCreateFunction.forName(RegionCreateFunction.java:386) > at > com.gemstone.gemfire.management.internal.cli.functions.RegionCreateFunction.createRegion(RegionCreateFunction.java:312) > at > com.gemstone.gemfire.management.internal.cli.functions.RegionCreateFunction.execute(RegionCreateFunction.java:89) > at > com.gemstone.gemfire.internal.cache.MemberFunctionStreamingMessage.process(MemberFunctionStreamingMessage.java:194) > ... 7 more > Caused by: java.lang.ClassNotFoundException: org.apache.log4j.Logger > at > com.gemstone.gemfire.internal.JarClassLoader.forName(JarClassLoader.java:568) > at > com.gemstone.gemfire.internal.JarClassLoader.loadClass(JarClassLoader.java:413) > at > com.gemstone.gemfire.internal.JarClassLoader.loadClass(JarClassLoader.java:389) > at > com.gemstone.gemfire.internal.JarClassLoader.loadClass(JarClassLoader.java:384) > ... 15 more > {noformat} > {panel} -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (GEODE-1575) Unhandled NoClassDefFound Exception when creating regions
[ https://issues.apache.org/jira/browse/GEODE-1575?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevin Duling resolved GEODE-1575. - Resolution: Fixed > Unhandled NoClassDefFound Exception when creating regions > - > > Key: GEODE-1575 > URL: https://issues.apache.org/jira/browse/GEODE-1575 > Project: Geode > Issue Type: Bug > Components: configuration, gfsh >Reporter: Kevin Duling >Assignee: Kevin Duling > Fix For: 1.0.0-incubating.M3 > > > The wrong error message is being displayed when encountering a > {{NoClassDefFoundError}} > {panel:title=gfsh} > {noformat} > Executing - create region --name=replicatedRegion --type=REPLICATE > --cache-loader=com.example.TestCacheLoader > Could not process command due to GemFire error. > java.lang.ClassNotFoundException cannot be cast to > com.gemstone.gemfire.management.internal.cli.functions.CliFunctionResult > {noformat} > {panel} > {panel:title=server.log} > {noformat} > [fine 2016/06/21 10:02:02.745 PDT host1-server1 Processor1> tid=0x41] Replying with exception: ReplyMessage processorId=13 > from null with exception > com.gemstone.gemfire.distributed.internal.ReplyException: > java.lang.NoClassDefFoundError: org/apache/log4j/Logger > com.gemstone.gemfire.distributed.internal.ReplyException: > java.lang.NoClassDefFoundError: org/apache/log4j/Logger > at > com.gemstone.gemfire.internal.cache.MemberFunctionStreamingMessage.process(MemberFunctionStreamingMessage.java:248) > at > com.gemstone.gemfire.distributed.internal.DistributionMessage.scheduleAction(DistributionMessage.java:379) > at > com.gemstone.gemfire.distributed.internal.DistributionMessage$1.run(DistributionMessage.java:450) > at > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) > at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > at > com.gemstone.gemfire.distributed.internal.DistributionManager.runUntilShutdown(DistributionManager.java:611) > at > com.gemstone.gemfire.distributed.internal.DistributionManager$9$1.run(DistributionManager.java:1071) > at java.lang.Thread.run(Thread.java:745) > Caused by: java.lang.NoClassDefFoundError: org/apache/log4j/Logger > at > io.pivotal.support.cases.server.TestCacheLoader.(TestCacheLoader.java:14) > at java.lang.Class.forName0(Native Method) > at java.lang.Class.forName(Class.java:348) > at > com.gemstone.gemfire.internal.ClassPathLoader.forName(ClassPathLoader.java:408) > at > com.gemstone.gemfire.management.internal.cli.functions.RegionCreateFunction.forName(RegionCreateFunction.java:386) > at > com.gemstone.gemfire.management.internal.cli.functions.RegionCreateFunction.createRegion(RegionCreateFunction.java:312) > at > com.gemstone.gemfire.management.internal.cli.functions.RegionCreateFunction.execute(RegionCreateFunction.java:89) > at > com.gemstone.gemfire.internal.cache.MemberFunctionStreamingMessage.process(MemberFunctionStreamingMessage.java:194) > ... 7 more > Caused by: java.lang.ClassNotFoundException: org.apache.log4j.Logger > at > com.gemstone.gemfire.internal.JarClassLoader.forName(JarClassLoader.java:568) > at > com.gemstone.gemfire.internal.JarClassLoader.loadClass(JarClassLoader.java:413) > at > com.gemstone.gemfire.internal.JarClassLoader.loadClass(JarClassLoader.java:389) > at > com.gemstone.gemfire.internal.JarClassLoader.loadClass(JarClassLoader.java:384) > ... 15 more > {noformat} > {panel} -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Reopened] (GEODE-1575) Unhandled NoClassDefFound Exception when creating regions
[ https://issues.apache.org/jira/browse/GEODE-1575?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevin Duling reopened GEODE-1575: - > Unhandled NoClassDefFound Exception when creating regions > - > > Key: GEODE-1575 > URL: https://issues.apache.org/jira/browse/GEODE-1575 > Project: Geode > Issue Type: Bug > Components: configuration, gfsh >Reporter: Kevin Duling >Assignee: Kevin Duling > Fix For: 1.0.0-incubating.M3 > > > The wrong error message is being displayed when encountering a > {{NoClassDefFoundError}} > {panel:title=gfsh} > {noformat} > Executing - create region --name=replicatedRegion --type=REPLICATE > --cache-loader=com.example.TestCacheLoader > Could not process command due to GemFire error. > java.lang.ClassNotFoundException cannot be cast to > com.gemstone.gemfire.management.internal.cli.functions.CliFunctionResult > {noformat} > {panel} > {panel:title=server.log} > {noformat} > [fine 2016/06/21 10:02:02.745 PDT host1-server1 Processor1> tid=0x41] Replying with exception: ReplyMessage processorId=13 > from null with exception > com.gemstone.gemfire.distributed.internal.ReplyException: > java.lang.NoClassDefFoundError: org/apache/log4j/Logger > com.gemstone.gemfire.distributed.internal.ReplyException: > java.lang.NoClassDefFoundError: org/apache/log4j/Logger > at > com.gemstone.gemfire.internal.cache.MemberFunctionStreamingMessage.process(MemberFunctionStreamingMessage.java:248) > at > com.gemstone.gemfire.distributed.internal.DistributionMessage.scheduleAction(DistributionMessage.java:379) > at > com.gemstone.gemfire.distributed.internal.DistributionMessage$1.run(DistributionMessage.java:450) > at > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) > at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > at > com.gemstone.gemfire.distributed.internal.DistributionManager.runUntilShutdown(DistributionManager.java:611) > at > com.gemstone.gemfire.distributed.internal.DistributionManager$9$1.run(DistributionManager.java:1071) > at java.lang.Thread.run(Thread.java:745) > Caused by: java.lang.NoClassDefFoundError: org/apache/log4j/Logger > at > io.pivotal.support.cases.server.TestCacheLoader.(TestCacheLoader.java:14) > at java.lang.Class.forName0(Native Method) > at java.lang.Class.forName(Class.java:348) > at > com.gemstone.gemfire.internal.ClassPathLoader.forName(ClassPathLoader.java:408) > at > com.gemstone.gemfire.management.internal.cli.functions.RegionCreateFunction.forName(RegionCreateFunction.java:386) > at > com.gemstone.gemfire.management.internal.cli.functions.RegionCreateFunction.createRegion(RegionCreateFunction.java:312) > at > com.gemstone.gemfire.management.internal.cli.functions.RegionCreateFunction.execute(RegionCreateFunction.java:89) > at > com.gemstone.gemfire.internal.cache.MemberFunctionStreamingMessage.process(MemberFunctionStreamingMessage.java:194) > ... 7 more > Caused by: java.lang.ClassNotFoundException: org.apache.log4j.Logger > at > com.gemstone.gemfire.internal.JarClassLoader.forName(JarClassLoader.java:568) > at > com.gemstone.gemfire.internal.JarClassLoader.loadClass(JarClassLoader.java:413) > at > com.gemstone.gemfire.internal.JarClassLoader.loadClass(JarClassLoader.java:389) > at > com.gemstone.gemfire.internal.JarClassLoader.loadClass(JarClassLoader.java:384) > ... 15 more > {noformat} > {panel} -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (GEODE-1575) Unhandled NoClassDefFound Exception when creating regions
[ https://issues.apache.org/jira/browse/GEODE-1575?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevin Duling updated GEODE-1575: Description: The wrong error message is being displayed when encountering a {{NoClassDefFoundError}} {panel:title=gfsh} {noformat} Executing - create region --name=replicatedRegion --type=REPLICATE --cache-loader=com.example.TestCacheLoader Could not process command due to GemFire error. java.lang.ClassNotFoundException cannot be cast to com.gemstone.gemfire.management.internal.cli.functions.CliFunctionResult {noformat} {panel} {panel:title=server.log} {noformat} [fine 2016/06/21 10:02:02.745 PDT host1-server1 tid=0x41] Replying with exception: ReplyMessage processorId=13 from null with exception com.gemstone.gemfire.distributed.internal.ReplyException: java.lang.NoClassDefFoundError: org/apache/log4j/Logger com.gemstone.gemfire.distributed.internal.ReplyException: java.lang.NoClassDefFoundError: org/apache/log4j/Logger at com.gemstone.gemfire.internal.cache.MemberFunctionStreamingMessage.process(MemberFunctionStreamingMessage.java:248) at com.gemstone.gemfire.distributed.internal.DistributionMessage.scheduleAction(DistributionMessage.java:379) at com.gemstone.gemfire.distributed.internal.DistributionMessage$1.run(DistributionMessage.java:450) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at com.gemstone.gemfire.distributed.internal.DistributionManager.runUntilShutdown(DistributionManager.java:611) at com.gemstone.gemfire.distributed.internal.DistributionManager$9$1.run(DistributionManager.java:1071) at java.lang.Thread.run(Thread.java:745) Caused by: java.lang.NoClassDefFoundError: org/apache/log4j/Logger at io.pivotal.support.cases.server.TestCacheLoader.(TestCacheLoader.java:14) at java.lang.Class.forName0(Native Method) at java.lang.Class.forName(Class.java:348) at com.gemstone.gemfire.internal.ClassPathLoader.forName(ClassPathLoader.java:408) at com.gemstone.gemfire.management.internal.cli.functions.RegionCreateFunction.forName(RegionCreateFunction.java:386) at com.gemstone.gemfire.management.internal.cli.functions.RegionCreateFunction.createRegion(RegionCreateFunction.java:312) at com.gemstone.gemfire.management.internal.cli.functions.RegionCreateFunction.execute(RegionCreateFunction.java:89) at com.gemstone.gemfire.internal.cache.MemberFunctionStreamingMessage.process(MemberFunctionStreamingMessage.java:194) ... 7 more Caused by: java.lang.ClassNotFoundException: org.apache.log4j.Logger at com.gemstone.gemfire.internal.JarClassLoader.forName(JarClassLoader.java:568) at com.gemstone.gemfire.internal.JarClassLoader.loadClass(JarClassLoader.java:413) at com.gemstone.gemfire.internal.JarClassLoader.loadClass(JarClassLoader.java:389) at com.gemstone.gemfire.internal.JarClassLoader.loadClass(JarClassLoader.java:384) ... 15 more {noformat} {panel} was: {panel:title=gfsh} Executing - create region --name=replicatedRegion --type=REPLICATE --cache-loader=com.example.TestCacheLoader Could not process command due to GemFire error. java.lang.ClassNotFoundException cannot be cast to com.gemstone.gemfire.management.internal.cli.functions.CliFunctionResult {panel} {panel:title=server.log} [fine 2016/06/21 10:02:02.745 PDT host1-server1 tid=0x41] Replying with exception: ReplyMessage processorId=13 from null with exception com.gemstone.gemfire.distributed.internal.ReplyE xception: java.lang.NoClassDefFoundError: org/apache/log4j/Logger com.gemstone.gemfire.distributed.internal.ReplyException: java.lang.NoClassDefFoundError: org/apache/log4j/Logger at com.gemstone.gemfire.internal.cache.MemberFunctionStreamingMessage.process(MemberFunctionStreamingMessage.java:248) at com.gemstone.gemfire.distributed.internal.DistributionMessage.scheduleAction(DistributionMessage.java:379) at com.gemstone.gemfire.distributed.internal.DistributionMessage$1.run(DistributionMessage.java:450) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at com.gemstone.gemfire.distributed.internal.DistributionManager.runUntilShutdown(DistributionManager.java:611) at com.gemstone.gemfire.distributed.internal.DistributionManager$9$1.run(DistributionManager.java:1071) at java.lang.Thread.run(Thread.java:745) Caused by: java.lang.NoClassDefFoundError: org/apache/log4j/Logger at io.pivotal.support.cases.server.TestCacheLoader.(TestCacheLoader.java:14) at java.lang.Class.forName0(Native Method) at java.lang.Class.forName(Cl
[jira] [Comment Edited] (GEODE-1575) Unhandled NoClassDefFound Exception when creating regions
[ https://issues.apache.org/jira/browse/GEODE-1575?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15342192#comment-15342192 ] Kevin Duling edited comment on GEODE-1575 at 6/21/16 5:07 PM: -- Added a catch clause for the exception. Now the error message reads: {panel:title=gfsh} {noformat} (2) Executing - create region --name=replicatedRegion --type=REPLICATE --cache-loader=com.example.TestCacheLoader Member | Status - | --- host1-server1 | ERROR: Could not find class "com.example.TestCacheLoader" specified for "cache-loader". {noformat} {panel} was (Author: kduling): Added a catch clause for the exception. Now the error message reads: {panel:title=gfsh} (2) Executing - create region --name=replicatedRegion --type=REPLICATE --cache-loader=com.example.TestCacheLoader Member | Status - | --- host1-server1 | ERROR: Could not find class "com.example.TestCacheLoader" specified for "cache-loader". {panel} > Unhandled NoClassDefFound Exception when creating regions > - > > Key: GEODE-1575 > URL: https://issues.apache.org/jira/browse/GEODE-1575 > Project: Geode > Issue Type: Bug > Components: configuration >Reporter: Kevin Duling >Assignee: Kevin Duling > Fix For: 1.0.0-incubating.M3 > > > {panel:title=gfsh} > Executing - create region --name=replicatedRegion --type=REPLICATE > --cache-loader=com.example.TestCacheLoader > Could not process command due to GemFire error. > java.lang.ClassNotFoundException cannot be cast to > com.gemstone.gemfire.management.internal.cli.functions.CliFunctionResult > {panel} > {panel:title=server.log} > [fine 2016/06/21 10:02:02.745 PDT host1-server1 Processor1> tid=0x41] Replying with exception: ReplyMessage processorId=13 > from null with exception com.gemstone.gemfire.distributed.internal.ReplyE > xception: java.lang.NoClassDefFoundError: org/apache/log4j/Logger > com.gemstone.gemfire.distributed.internal.ReplyException: > java.lang.NoClassDefFoundError: org/apache/log4j/Logger > at > com.gemstone.gemfire.internal.cache.MemberFunctionStreamingMessage.process(MemberFunctionStreamingMessage.java:248) > at > com.gemstone.gemfire.distributed.internal.DistributionMessage.scheduleAction(DistributionMessage.java:379) > at > com.gemstone.gemfire.distributed.internal.DistributionMessage$1.run(DistributionMessage.java:450) > at > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) > at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > at > com.gemstone.gemfire.distributed.internal.DistributionManager.runUntilShutdown(DistributionManager.java:611) > at > com.gemstone.gemfire.distributed.internal.DistributionManager$9$1.run(DistributionManager.java:1071) > at java.lang.Thread.run(Thread.java:745) > Caused by: java.lang.NoClassDefFoundError: org/apache/log4j/Logger > at > io.pivotal.support.cases.server.TestCacheLoader.(TestCacheLoader.java:14) > at java.lang.Class.forName0(Native Method) > at java.lang.Class.forName(Class.java:348) > at > com.gemstone.gemfire.internal.ClassPathLoader.forName(ClassPathLoader.java:408) > at > com.gemstone.gemfire.management.internal.cli.functions.RegionCreateFunction.forName(RegionCreateFunction.java:386) > at > com.gemstone.gemfire.management.internal.cli.functions.RegionCreateFunction.createRegion(RegionCreateFunction.java:312) > at > com.gemstone.gemfire.management.internal.cli.functions.RegionCreateFunction.execute(RegionCreateFunction.java:89) > at > com.gemstone.gemfire.internal.cache.MemberFunctionStreamingMessage.process(MemberFunctionStreamingMessage.java:194) > ... 7 more > Caused by: java.lang.ClassNotFoundException: org.apache.log4j.Logger > at > com.gemstone.gemfire.internal.JarClassLoader.forName(JarClassLoader.java:568) > at > com.gemstone.gemfire.internal.JarClassLoader.loadClass(JarClassLoader.java:413) > at > com.gemstone.gemfire.internal.JarClassLoader.loadClass(JarClassLoader.java:389) > at > com.gemstone.gemfire.internal.JarClassLoader.loadClass(JarClassLoader.java:384) > ... 15 more > {panel} > The wrong error message is being displayed. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (GEODE-1575) Unhandled NoClassDefFound Exception when creating regions
[ https://issues.apache.org/jira/browse/GEODE-1575?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevin Duling resolved GEODE-1575. - Resolution: Fixed Fix Version/s: 1.0.0-incubating.M3 Added a catch clause for the exception. Now the error message reads: {panel:title=gfsh} (2) Executing - create region --name=replicatedRegion --type=REPLICATE --cache-loader=com.example.TestCacheLoader Member | Status - | --- host1-server1 | ERROR: Could not find class "com.example.TestCacheLoader" specified for "cache-loader". {panel} > Unhandled NoClassDefFound Exception when creating regions > - > > Key: GEODE-1575 > URL: https://issues.apache.org/jira/browse/GEODE-1575 > Project: Geode > Issue Type: Bug > Components: configuration >Reporter: Kevin Duling >Assignee: Kevin Duling > Fix For: 1.0.0-incubating.M3 > > > {panel:title=gfsh} > Executing - create region --name=replicatedRegion --type=REPLICATE > --cache-loader=com.example.TestCacheLoader > Could not process command due to GemFire error. > java.lang.ClassNotFoundException cannot be cast to > com.gemstone.gemfire.management.internal.cli.functions.CliFunctionResult > {panel} > {panel:title=server.log} > [fine 2016/06/21 10:02:02.745 PDT host1-server1 Processor1> tid=0x41] Replying with exception: ReplyMessage processorId=13 > from null with exception com.gemstone.gemfire.distributed.internal.ReplyE > xception: java.lang.NoClassDefFoundError: org/apache/log4j/Logger > com.gemstone.gemfire.distributed.internal.ReplyException: > java.lang.NoClassDefFoundError: org/apache/log4j/Logger > at > com.gemstone.gemfire.internal.cache.MemberFunctionStreamingMessage.process(MemberFunctionStreamingMessage.java:248) > at > com.gemstone.gemfire.distributed.internal.DistributionMessage.scheduleAction(DistributionMessage.java:379) > at > com.gemstone.gemfire.distributed.internal.DistributionMessage$1.run(DistributionMessage.java:450) > at > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) > at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > at > com.gemstone.gemfire.distributed.internal.DistributionManager.runUntilShutdown(DistributionManager.java:611) > at > com.gemstone.gemfire.distributed.internal.DistributionManager$9$1.run(DistributionManager.java:1071) > at java.lang.Thread.run(Thread.java:745) > Caused by: java.lang.NoClassDefFoundError: org/apache/log4j/Logger > at > io.pivotal.support.cases.server.TestCacheLoader.(TestCacheLoader.java:14) > at java.lang.Class.forName0(Native Method) > at java.lang.Class.forName(Class.java:348) > at > com.gemstone.gemfire.internal.ClassPathLoader.forName(ClassPathLoader.java:408) > at > com.gemstone.gemfire.management.internal.cli.functions.RegionCreateFunction.forName(RegionCreateFunction.java:386) > at > com.gemstone.gemfire.management.internal.cli.functions.RegionCreateFunction.createRegion(RegionCreateFunction.java:312) > at > com.gemstone.gemfire.management.internal.cli.functions.RegionCreateFunction.execute(RegionCreateFunction.java:89) > at > com.gemstone.gemfire.internal.cache.MemberFunctionStreamingMessage.process(MemberFunctionStreamingMessage.java:194) > ... 7 more > Caused by: java.lang.ClassNotFoundException: org.apache.log4j.Logger > at > com.gemstone.gemfire.internal.JarClassLoader.forName(JarClassLoader.java:568) > at > com.gemstone.gemfire.internal.JarClassLoader.loadClass(JarClassLoader.java:413) > at > com.gemstone.gemfire.internal.JarClassLoader.loadClass(JarClassLoader.java:389) > at > com.gemstone.gemfire.internal.JarClassLoader.loadClass(JarClassLoader.java:384) > ... 15 more > {panel} > The wrong error message is being displayed. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (GEODE-1575) Unhandled NoClassDefFound Exception when creating regions
[ https://issues.apache.org/jira/browse/GEODE-1575?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevin Duling reassigned GEODE-1575: --- Assignee: Kevin Duling > Unhandled NoClassDefFound Exception when creating regions > - > > Key: GEODE-1575 > URL: https://issues.apache.org/jira/browse/GEODE-1575 > Project: Geode > Issue Type: Bug > Components: configuration >Reporter: Kevin Duling >Assignee: Kevin Duling > > {panel:title=gfsh} > Executing - create region --name=replicatedRegion --type=REPLICATE > --cache-loader=com.example.TestCacheLoader > Could not process command due to GemFire error. > java.lang.ClassNotFoundException cannot be cast to > com.gemstone.gemfire.management.internal.cli.functions.CliFunctionResult > {panel} > {panel:title=server.log} > [fine 2016/06/21 10:02:02.745 PDT host1-server1 Processor1> tid=0x41] Replying with exception: ReplyMessage processorId=13 > from null with exception com.gemstone.gemfire.distributed.internal.ReplyE > xception: java.lang.NoClassDefFoundError: org/apache/log4j/Logger > com.gemstone.gemfire.distributed.internal.ReplyException: > java.lang.NoClassDefFoundError: org/apache/log4j/Logger > at > com.gemstone.gemfire.internal.cache.MemberFunctionStreamingMessage.process(MemberFunctionStreamingMessage.java:248) > at > com.gemstone.gemfire.distributed.internal.DistributionMessage.scheduleAction(DistributionMessage.java:379) > at > com.gemstone.gemfire.distributed.internal.DistributionMessage$1.run(DistributionMessage.java:450) > at > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) > at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > at > com.gemstone.gemfire.distributed.internal.DistributionManager.runUntilShutdown(DistributionManager.java:611) > at > com.gemstone.gemfire.distributed.internal.DistributionManager$9$1.run(DistributionManager.java:1071) > at java.lang.Thread.run(Thread.java:745) > Caused by: java.lang.NoClassDefFoundError: org/apache/log4j/Logger > at > io.pivotal.support.cases.server.TestCacheLoader.(TestCacheLoader.java:14) > at java.lang.Class.forName0(Native Method) > at java.lang.Class.forName(Class.java:348) > at > com.gemstone.gemfire.internal.ClassPathLoader.forName(ClassPathLoader.java:408) > at > com.gemstone.gemfire.management.internal.cli.functions.RegionCreateFunction.forName(RegionCreateFunction.java:386) > at > com.gemstone.gemfire.management.internal.cli.functions.RegionCreateFunction.createRegion(RegionCreateFunction.java:312) > at > com.gemstone.gemfire.management.internal.cli.functions.RegionCreateFunction.execute(RegionCreateFunction.java:89) > at > com.gemstone.gemfire.internal.cache.MemberFunctionStreamingMessage.process(MemberFunctionStreamingMessage.java:194) > ... 7 more > Caused by: java.lang.ClassNotFoundException: org.apache.log4j.Logger > at > com.gemstone.gemfire.internal.JarClassLoader.forName(JarClassLoader.java:568) > at > com.gemstone.gemfire.internal.JarClassLoader.loadClass(JarClassLoader.java:413) > at > com.gemstone.gemfire.internal.JarClassLoader.loadClass(JarClassLoader.java:389) > at > com.gemstone.gemfire.internal.JarClassLoader.loadClass(JarClassLoader.java:384) > ... 15 more > {panel} > The wrong error message is being displayed. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (GEODE-1575) Unhandled NoClassDefFound Exception when creating regions
Kevin Duling created GEODE-1575: --- Summary: Unhandled NoClassDefFound Exception when creating regions Key: GEODE-1575 URL: https://issues.apache.org/jira/browse/GEODE-1575 Project: Geode Issue Type: Bug Components: configuration Reporter: Kevin Duling {panel:title=gfsh} Executing - create region --name=replicatedRegion --type=REPLICATE --cache-loader=com.example.TestCacheLoader Could not process command due to GemFire error. java.lang.ClassNotFoundException cannot be cast to com.gemstone.gemfire.management.internal.cli.functions.CliFunctionResult {panel} {panel:title=server.log} [fine 2016/06/21 10:02:02.745 PDT host1-server1 tid=0x41] Replying with exception: ReplyMessage processorId=13 from null with exception com.gemstone.gemfire.distributed.internal.ReplyE xception: java.lang.NoClassDefFoundError: org/apache/log4j/Logger com.gemstone.gemfire.distributed.internal.ReplyException: java.lang.NoClassDefFoundError: org/apache/log4j/Logger at com.gemstone.gemfire.internal.cache.MemberFunctionStreamingMessage.process(MemberFunctionStreamingMessage.java:248) at com.gemstone.gemfire.distributed.internal.DistributionMessage.scheduleAction(DistributionMessage.java:379) at com.gemstone.gemfire.distributed.internal.DistributionMessage$1.run(DistributionMessage.java:450) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at com.gemstone.gemfire.distributed.internal.DistributionManager.runUntilShutdown(DistributionManager.java:611) at com.gemstone.gemfire.distributed.internal.DistributionManager$9$1.run(DistributionManager.java:1071) at java.lang.Thread.run(Thread.java:745) Caused by: java.lang.NoClassDefFoundError: org/apache/log4j/Logger at io.pivotal.support.cases.server.TestCacheLoader.(TestCacheLoader.java:14) at java.lang.Class.forName0(Native Method) at java.lang.Class.forName(Class.java:348) at com.gemstone.gemfire.internal.ClassPathLoader.forName(ClassPathLoader.java:408) at com.gemstone.gemfire.management.internal.cli.functions.RegionCreateFunction.forName(RegionCreateFunction.java:386) at com.gemstone.gemfire.management.internal.cli.functions.RegionCreateFunction.createRegion(RegionCreateFunction.java:312) at com.gemstone.gemfire.management.internal.cli.functions.RegionCreateFunction.execute(RegionCreateFunction.java:89) at com.gemstone.gemfire.internal.cache.MemberFunctionStreamingMessage.process(MemberFunctionStreamingMessage.java:194) ... 7 more Caused by: java.lang.ClassNotFoundException: org.apache.log4j.Logger at com.gemstone.gemfire.internal.JarClassLoader.forName(JarClassLoader.java:568) at com.gemstone.gemfire.internal.JarClassLoader.loadClass(JarClassLoader.java:413) at com.gemstone.gemfire.internal.JarClassLoader.loadClass(JarClassLoader.java:389) at com.gemstone.gemfire.internal.JarClassLoader.loadClass(JarClassLoader.java:384) ... 15 more {panel} The wrong error message is being displayed. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (GEODE-117) gfsh put ignores --skip-if-exists flag
[ https://issues.apache.org/jira/browse/GEODE-117?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevin Duling resolved GEODE-117. Resolution: Fixed Fix Version/s: 1.0.0-incubating.M3 Fixed test, which erroneously reported that the --skip-if-exists flag is honored. Implemented check for flag within the put operation. > gfsh put ignores --skip-if-exists flag > -- > > Key: GEODE-117 > URL: https://issues.apache.org/jira/browse/GEODE-117 > Project: Geode > Issue Type: Bug > Components: gfsh >Reporter: Dan Smith >Assignee: Kevin Duling > Labels: gfsh, starter > Fix For: 1.0.0-incubating.M3 > > > Someone hit this on a forum post: > https://support.pivotal.io/hc/communities/public/questions/204414098-put-in-gfsh-doesn-t-honor-skip-if-exists-true-flag-?flash_digest=f2441b8a96ac363d6da205c6f90a62035b1a3c21 > I looked into the code, and it looks like the flag gets lost somewhere along > the way. If you look at DataCommandFunction.put, it has a putIfAbsent flag, > but that flag is not used; the function just does a normal put. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (GEODE-1521) APP_FETCH_SIZE in GFSH should not be applied to COUNT queries
[ https://issues.apache.org/jira/browse/GEODE-1521?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevin Duling resolved GEODE-1521. - Resolution: Fixed Delivered > APP_FETCH_SIZE in GFSH should not be applied to COUNT queries > - > > Key: GEODE-1521 > URL: https://issues.apache.org/jira/browse/GEODE-1521 > Project: Geode > Issue Type: Bug > Components: gfsh >Reporter: Kevin Duling >Assignee: Kevin Duling > Fix For: 1.0.0-incubating.M3 > > > There are more varieties of count than simply * within the count(). > Specifically, one can do: {{count(distinct(field))}} or {{count(field)}} > This makes checking for only {{count( * )}} incorrect. Instead, the search > to apply the limt should look for {{" count("}} -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (GEODE-68) GFSH SYS_HOST_NAME variable should report hostname if available
[ https://issues.apache.org/jira/browse/GEODE-68?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevin Duling resolved GEODE-68. --- Resolution: Fixed Delivered > GFSH SYS_HOST_NAME variable should report hostname if available > --- > > Key: GEODE-68 > URL: https://issues.apache.org/jira/browse/GEODE-68 > Project: Geode > Issue Type: Bug > Components: gfsh >Reporter: William Markito Oliveira >Assignee: Kevin Duling >Priority: Minor > Labels: gfsh > Fix For: 1.0.0-incubating.M3 > > > SYS_HOST_NAME is actually displaying SYS_USER_HOME. > This is very useful for automation scripts. > {code} > gfsh>echo --string=$* >Property| Value > -- | > -- > APP_COLLECTION_LIMIT | 20 > APP_FETCH_SIZE | 1000 > APP_LAST_EXIT_STATUS | 0 > APP_LOGGING_ENABLED| false > APP_LOG_FILE | /Users/wmarkito/gfsh-%u_%g.log > APP_NAME | gfsh > APP_PWD| /Users/wmarkito > APP_QUERY_RESULTS_DISPLAY_MODE | table > APP_QUIET_EXECUTION| false > APP_RESULT_VIEWER | basic > SYS_CLASSPATH | > /Users/wmarkito/Pivotal/GemFire/sources/github/gemfire/build-artifacts/mac/product/lib/gfsh-dependencies.jar:/Library/Java/JavaVirtualMachines/jdk1.7.0_71.jdk/Contents/Home/lib/tools.jar > SYS_GEMFIRE_DIR| /Users/wmarkito/... > SYS_HOST_NAME | wmarkito > SYS_JAVA_VERSION | 1.7.0_72 > SYS_OS | Mac OS X > SYS_OS_LINE_SEPARATOR | > SYS_USER | wmarkito > SYS_USER_HOME | /Users/wmarkito > {code} -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (GEODE-744) Incorrect use of APP_FETCH_SIZE in GFSH
[ https://issues.apache.org/jira/browse/GEODE-744?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15334670#comment-15334670 ] Kevin Duling commented on GEODE-744: Delivered > Incorrect use of APP_FETCH_SIZE in GFSH > --- > > Key: GEODE-744 > URL: https://issues.apache.org/jira/browse/GEODE-744 > Project: Geode > Issue Type: Bug > Components: gfsh >Reporter: Jens Deppe >Assignee: Kevin Duling > Fix For: 1.0.0-incubating.M3 > > Attachments: workspace (1).zip > > > A customer is facing an easily reproducible issue when executing queries from > GFSH. It appears that the APP_FETCH_SIZE is being set only when parts of the > query are in lower case. It happens in 7.0.X, 8.0.X and 8.1.X. > Attached to the TRAC is the reproducible scenario, steps to reproduce: > Uncompress the file. > Modify variables "GEMFIRE" and "JAVA_HOME" in file setenv.txt. > Execute "./start_cluster.sh". > Exceute "./run.sh". This script inserts 1500 entries in the region and, > afterwards, executes two queries, one using lower case and other using upper > case. You can see from the console that ouput is different, one returns the > actual size (1500) and the other one returns the default APP_FETCH_SIZE > (1000). > Exceute "./stop_cluster.sh". > The fix seems pretty easy to implement, the method "addLimit" of the inner > class "SelectExecStep?" in "DataCommandFunction?" class should be modified to > compare strings without using the actual word case. Is not enough to add more > "or" to the comparison like we are currently doing with since keywords like > "Count" or "coUn" will still break the functionallity. We should compare > everything using lower case or upper case, it doesn't matter which one, or at > least make sure that gfsh converts the query to upper/lower case before > actually executing them. > The actual code with the problem is below: > {noformat} > private String addLimit(String query) { > boolean containsLimitOrAggregate = query.contains(" limit") > query.contains(" LIMIT") query.contains("count(*)"); > if (!containsLimitOrAggregate){ > String limitQuery = query + " limit " + getFetchSize(); > return limitQuery; > } else { > return query; > } > } > {noformat} -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (GEODE-744) Incorrect use of APP_FETCH_SIZE in GFSH
[ https://issues.apache.org/jira/browse/GEODE-744?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevin Duling resolved GEODE-744. Resolution: Fixed > Incorrect use of APP_FETCH_SIZE in GFSH > --- > > Key: GEODE-744 > URL: https://issues.apache.org/jira/browse/GEODE-744 > Project: Geode > Issue Type: Bug > Components: gfsh >Reporter: Jens Deppe >Assignee: Kevin Duling > Fix For: 1.0.0-incubating.M3 > > Attachments: workspace (1).zip > > > A customer is facing an easily reproducible issue when executing queries from > GFSH. It appears that the APP_FETCH_SIZE is being set only when parts of the > query are in lower case. It happens in 7.0.X, 8.0.X and 8.1.X. > Attached to the TRAC is the reproducible scenario, steps to reproduce: > Uncompress the file. > Modify variables "GEMFIRE" and "JAVA_HOME" in file setenv.txt. > Execute "./start_cluster.sh". > Exceute "./run.sh". This script inserts 1500 entries in the region and, > afterwards, executes two queries, one using lower case and other using upper > case. You can see from the console that ouput is different, one returns the > actual size (1500) and the other one returns the default APP_FETCH_SIZE > (1000). > Exceute "./stop_cluster.sh". > The fix seems pretty easy to implement, the method "addLimit" of the inner > class "SelectExecStep?" in "DataCommandFunction?" class should be modified to > compare strings without using the actual word case. Is not enough to add more > "or" to the comparison like we are currently doing with since keywords like > "Count" or "coUn" will still break the functionallity. We should compare > everything using lower case or upper case, it doesn't matter which one, or at > least make sure that gfsh converts the query to upper/lower case before > actually executing them. > The actual code with the problem is below: > {noformat} > private String addLimit(String query) { > boolean containsLimitOrAggregate = query.contains(" limit") > query.contains(" LIMIT") query.contains("count(*)"); > if (!containsLimitOrAggregate){ > String limitQuery = query + " limit " + getFetchSize(); > return limitQuery; > } else { > return query; > } > } > {noformat} -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (GEODE-117) gfsh put ignores --skip-if-exists flag
[ https://issues.apache.org/jira/browse/GEODE-117?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevin Duling reassigned GEODE-117: -- Assignee: Kevin Duling (was: Srikanth Manvi) > gfsh put ignores --skip-if-exists flag > -- > > Key: GEODE-117 > URL: https://issues.apache.org/jira/browse/GEODE-117 > Project: Geode > Issue Type: Bug > Components: gfsh >Reporter: Dan Smith >Assignee: Kevin Duling > Labels: gfsh, starter > > Someone hit this on a forum post: > https://support.pivotal.io/hc/communities/public/questions/204414098-put-in-gfsh-doesn-t-honor-skip-if-exists-true-flag-?flash_digest=f2441b8a96ac363d6da205c6f90a62035b1a3c21 > I looked into the code, and it looks like the flag gets lost somewhere along > the way. If you look at DataCommandFunction.put, it has a putIfAbsent flag, > but that flag is not used; the function just does a normal put. -- This message was sent by Atlassian JIRA (v6.3.4#6332)