Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id 80C63200BA0 for ; Fri, 30 Sep 2016 02:33:19 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 7F7FC160AE4; Fri, 30 Sep 2016 00:33:19 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id 3B8CF160AED for ; Fri, 30 Sep 2016 02:33:18 +0200 (CEST) Received: (qmail 63200 invoked by uid 500); 30 Sep 2016 00:33:17 -0000 Mailing-List: contact commits-help@geode.incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@geode.incubator.apache.org Delivered-To: mailing list commits@geode.incubator.apache.org Received: (qmail 63183 invoked by uid 99); 30 Sep 2016 00:33:17 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd1-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 30 Sep 2016 00:33:17 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd1-us-west.apache.org (ASF Mail Server at spamd1-us-west.apache.org) with ESMTP id 01959CC069 for ; Fri, 30 Sep 2016 00:33:17 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd1-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -6.219 X-Spam-Level: X-Spam-Status: No, score=-6.219 tagged_above=-999 required=6.31 tests=[KAM_ASCII_DIVIDERS=0.8, KAM_LAZY_DOMAIN_SECURITY=1, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-2.999] autolearn=disabled Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd1-us-west.apache.org [10.40.0.7]) (amavisd-new, port 10024) with ESMTP id 2VU34A9Zde4W for ; Fri, 30 Sep 2016 00:33:15 +0000 (UTC) Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with SMTP id C9E3D60D84 for ; Fri, 30 Sep 2016 00:33:09 +0000 (UTC) Received: (qmail 60313 invoked by uid 99); 30 Sep 2016 00:33:09 -0000 Received: from git1-us-west.apache.org (HELO git1-us-west.apache.org) (140.211.11.23) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 30 Sep 2016 00:33:09 +0000 Received: by git1-us-west.apache.org (ASF Mail Server at git1-us-west.apache.org, from userid 33) id E80BFE08DD; Fri, 30 Sep 2016 00:33:08 +0000 (UTC) Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 8bit From: rvs@apache.org To: commits@geode.incubator.apache.org Date: Fri, 30 Sep 2016 00:33:29 -0000 Message-Id: <17126deae1664f7d8c441e9c888e94fe@git.apache.org> In-Reply-To: <2b89ce6a4ffc4a24b0b200ff5e4148ba@git.apache.org> References: <2b89ce6a4ffc4a24b0b200ff5e4148ba@git.apache.org> X-Mailer: ASF-Git Admin Mailer Subject: [22/50] [abbrv] incubator-geode git commit: GEODE-37 Package renaming [#118023839] archived-at: Fri, 30 Sep 2016 00:33:19 -0000 http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/23e2f5ce/tools_modules/http_session_mgmt/session_state_log_files.html.md.erb ---------------------------------------------------------------------- diff --git a/tools_modules/http_session_mgmt/session_state_log_files.html.md.erb b/tools_modules/http_session_mgmt/session_state_log_files.html.md.erb index 3e925b5..35f849a 100644 --- a/tools_modules/http_session_mgmt/session_state_log_files.html.md.erb +++ b/tools_modules/http_session_mgmt/session_state_log_files.html.md.erb @@ -13,23 +13,23 @@ Several log files are written by the various parts of the session management cod To add Geode-specific FINE logging to the `catalina.log` file, add the following lines to your `/conf/logging.properties` file: ``` pre -com.gemstone.gemfire.modules.session.catalina.DeltaSessionManager.level = FINE -com.gemstone.gemfire.modules.session.catalina.DeltaSession.level = FINE +org.apache.geode.modules.session.catalina.DeltaSessionManager.level = FINE +org.apache.geode.modules.session.catalina.DeltaSession.level = FINE ``` These configurations will add FINE logging to the `catalina.DATE.log` file. The following is an example of FINE logging: ``` pre -06-Sep-2011 15:59:47.250 FINE com.gemstone.gemfire.modules.session.catalina.DeltaSessionManager.start +06-Sep-2011 15:59:47.250 FINE org.apache.geode.modules.session.catalina.DeltaSessionManager.start DeltaSessionManager[container=StandardEngine[Catalina].StandardHost[localhost].StandardContext[/manager]; regionName=gemfire_modules_sessions; regionAttributesId=PARTITION_REDUNDANT]: Starting -06-Sep-2011 15:59:47.254 FINE com.gemstone.gemfire.modules.session.catalina.DeltaSessionManager.registerJvmRouteBinderValve +06-Sep-2011 15:59:47.254 FINE org.apache.geode.modules.session.catalina.DeltaSessionManager.registerJvmRouteBinderValve DeltaSessionManager[container=StandardEngine[Catalina].StandardHost[localhost].StandardContext[/manager]; regionName=gemfire_modules_sessions; regionAttributesId=PARTITION_REDUNDANT]: Registering JVM route binder valve -06-Sep-2011 15:59:47.351 FINE com.gemstone.gemfire.modules.session.catalina.ClientServerSessionCache.createOrRetrieveRegion -Created session region: com.gemstone.gemfire.internal.cache.LocalRegion[path='/gemfire_modules_sessions'; +06-Sep-2011 15:59:47.351 FINE org.apache.geode.modules.session.catalina.ClientServerSessionCache.createOrRetrieveRegion +Created session region: org.apache.geode.internal.cache.LocalRegion[path='/gemfire_modules_sessions'; scope=LOCAL';dataPolicy=EMPTY; gatewayEnabled=false] ``` @@ -77,7 +77,7 @@ To add fine-level logging to the Geode Cache Client, add the 'log-level' propert ``` pre + ```
**enableDebugListener**
http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/23e2f5ce/tools_modules/http_session_mgmt/tomcat_setting_up_the_module.html.md.erb ---------------------------------------------------------------------- diff --git a/tools_modules/http_session_mgmt/tomcat_setting_up_the_module.html.md.erb b/tools_modules/http_session_mgmt/tomcat_setting_up_the_module.html.md.erb index 780b311..a94609e 100644 --- a/tools_modules/http_session_mgmt/tomcat_setting_up_the_module.html.md.erb +++ b/tools_modules/http_session_mgmt/tomcat_setting_up_the_module.html.md.erb @@ -12,7 +12,7 @@ Configuration is slightly different depending on the topology you are setting up To run Geode in a peer-to-peer configuration, add the following line to Tomcat's `$CATALINA_HOME$/conf/server.xml` within the `` tag: ``` pre - ``` @@ -22,14 +22,14 @@ Depending on the version of Tomcat you are using, add one of the following lines For Tomcat 6.0: ``` pre - ``` For Tomcat 7.0 and above: ``` pre - ``` @@ -40,7 +40,7 @@ For Tomcat 7.0 and above: To run Geode in a client/server configuration, the application server will operate as a Geode client. To do this, add the following line to `$CATALINA_HOME$/conf/server.xml` within the `` tag: ``` pre - ``` @@ -49,14 +49,14 @@ Depending on the version of Tomcat you are using, add one of the following lines For Tomcat 6.0: ``` pre - ``` For Tomcat 7.0 and above: ``` pre - ``` @@ -93,7 +93,7 @@ You can verify that Geode has successfully started by inspecting the Tomcat log ``` pre Nov 8, 2010 12:12:12 PM -com.gemstone.gemfire.modules.session.catalina.ClientServerCacheLifecycleListener +org.apache.geode.modules.session.catalina.ClientServerCacheLifecycleListener createOrRetrieveCache INFO: Created GemFireCache[id = 2066231378; isClosing = false; created = Mon Nov 08 12:12:12 PDT 2010; server = false; http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/23e2f5ce/tools_modules/http_session_mgmt/weblogic_changing_gf_default_cfg.html.md.erb ---------------------------------------------------------------------- diff --git a/tools_modules/http_session_mgmt/weblogic_changing_gf_default_cfg.html.md.erb b/tools_modules/http_session_mgmt/weblogic_changing_gf_default_cfg.html.md.erb index cf45c71..d86dca6 100644 --- a/tools_modules/http_session_mgmt/weblogic_changing_gf_default_cfg.html.md.erb +++ b/tools_modules/http_session_mgmt/weblogic_changing_gf_default_cfg.html.md.erb @@ -30,7 +30,7 @@ To edit Geode system properties, you must add properties to Geode Session Filter gemfire-session-filter - com.gemstone.gemfire.modules.session.filter.SessionCachingFilter + org.apache.geode.modules.session.filter.SessionCachingFilter cache-type @@ -82,7 +82,7 @@ To edit Geode cache properties (such as the name and the characteristics of the gemfire-session-filter - com.gemstone.gemfire.modules.session.filter.SessionCachingFilter + org.apache.geode.modules.session.filter.SessionCachingFilter cache-type http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/23e2f5ce/tools_modules/http_session_mgmt/weblogic_setting_up_the_module.html.md.erb ---------------------------------------------------------------------- diff --git a/tools_modules/http_session_mgmt/weblogic_setting_up_the_module.html.md.erb b/tools_modules/http_session_mgmt/weblogic_setting_up_the_module.html.md.erb index 77de1c8..935853f 100644 --- a/tools_modules/http_session_mgmt/weblogic_setting_up_the_module.html.md.erb +++ b/tools_modules/http_session_mgmt/weblogic_setting_up_the_module.html.md.erb @@ -20,7 +20,7 @@ To modify your war or ear file manually, make the following updates: gemfire-session-filter - com.gemstone.gemfire.modules.session.filter.SessionCachingFilter + org.apache.geode.modules.session.filter.SessionCachingFilter cache-type @@ -40,7 +40,7 @@ To modify your war or ear file manually, make the following updates: ERROR - com.gemstone.gemfire.modules.session.filter.SessionListener + org.apache.geode.modules.session.filter.SessionListener ``` @@ -100,7 +100,7 @@ to result in the following `web.xml` content: gemfire-session-filter - com.gemstone.gemfire.modules.session.filter.SessionCachingFilter + org.apache.geode.modules.session.filter.SessionCachingFilter cache-type @@ -127,7 +127,7 @@ to result in the following `web.xml` content: gemfire-session-filter - com.gemstone.gemfire.modules.session.filter.SessionCachingFileter + org.apache.geode.modules.session.filter.SessionCachingFileter cache-type http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/23e2f5ce/tools_modules/pulse/quickstart.html.md.erb ---------------------------------------------------------------------- diff --git a/tools_modules/pulse/quickstart.html.md.erb b/tools_modules/pulse/quickstart.html.md.erb index a452703..22e5b16 100644 --- a/tools_modules/pulse/quickstart.html.md.erb +++ b/tools_modules/pulse/quickstart.html.md.erb @@ -771,7 +771,7 @@ The Pulse Data Browser enables you to query region data. Note that there are two - `QueryResultSetLimit` limits the number of rows that Data Browser queries return. 1000 rows are displayed by default. - `QueryCollectionsDepth` limits the number of elements of a collection that Data Browser queries return. This attribute applies to query results contain collections such as Map, List, and so forth. The default value is 100 elements. -See the `com.gemstone.gemfire.management.DistributedSystemMXBean` JavaDocs for information on available MBean methods and attributes. +See the `org.apache.geode.management.DistributedSystemMXBean` JavaDocs for information on available MBean methods and attributes. The following shows an example Data Browser view: http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/23e2f5ce/topologies_and_comm/cs_configuration/chapter_overview.html.md.erb ---------------------------------------------------------------------- diff --git a/topologies_and_comm/cs_configuration/chapter_overview.html.md.erb b/topologies_and_comm/cs_configuration/chapter_overview.html.md.erb index cacc77e..6fd6574 100644 --- a/topologies_and_comm/cs_configuration/chapter_overview.html.md.erb +++ b/topologies_and_comm/cs_configuration/chapter_overview.html.md.erb @@ -30,6 +30,6 @@ In the client/server architecture, a relatively small server farm manages the ca - **[Fine-Tuning Your Client/Server Configuration](../../topologies_and_comm/cs_configuration/client_server_whats_next.html)** - You can fine-tune your client/server system with server load-balancing and client thread use of pool connections. For example, you can configure how often the servers check their load with the cache server `load-poll-interval` property, or configure your own server load metrics by implementing the `com.gemstone.gemfire.cache.server` package. + You can fine-tune your client/server system with server load-balancing and client thread use of pool connections. For example, you can configure how often the servers check their load with the cache server `load-poll-interval` property, or configure your own server load metrics by implementing the `org.apache.geode.cache.server` package. http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/23e2f5ce/topologies_and_comm/cs_configuration/client_server_whats_next.html.md.erb ---------------------------------------------------------------------- diff --git a/topologies_and_comm/cs_configuration/client_server_whats_next.html.md.erb b/topologies_and_comm/cs_configuration/client_server_whats_next.html.md.erb index 1adcf08..2cd802b 100644 --- a/topologies_and_comm/cs_configuration/client_server_whats_next.html.md.erb +++ b/topologies_and_comm/cs_configuration/client_server_whats_next.html.md.erb @@ -2,7 +2,7 @@ title: Fine-Tuning Your Client/Server Configuration --- -You can fine-tune your client/server system with server load-balancing and client thread use of pool connections. For example, you can configure how often the servers check their load with the cache server `load-poll-interval` property, or configure your own server load metrics by implementing the `com.gemstone.gemfire.cache.server` package. +You can fine-tune your client/server system with server load-balancing and client thread use of pool connections. For example, you can configure how often the servers check their load with the cache server `load-poll-interval` property, or configure your own server load metrics by implementing the `org.apache.geode.cache.server` package. ## How Server Load Conditioning Works @@ -17,7 +17,7 @@ Geode provides a default utility that probes the server and its resource usage t - The pool connection load is the number of connections to the server divided by the server’s `max-connections` setting. This means that servers with a lower `max-connections` setting receives fewer connections than servers with a higher setting. The load is a number between 0 and 1, where 0 means there are no connections, and 1 means the server is at `max-connections`. The load estimate for each additional pool connection is 1/`max-connections`. - The subscription connection load is the number of subscription queues hosted by this server. The load estimate for each additional subscription connection is 1. -To use your own server load metrics instead of the default, implement the `ServerLoadProbe` or `ServerLoadProbeAdapter` and related interfaces and classes in the `com.gemstone.gemfire.cache.server` package. The load for each server is weighed relative to the loads reported by other servers in the system. +To use your own server load metrics instead of the default, implement the `ServerLoadProbe` or `ServerLoadProbeAdapter` and related interfaces and classes in the `org.apache.geode.cache.server` package. The load for each server is weighed relative to the loads reported by other servers in the system. ## Client Thread Use of Pool Connections http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/23e2f5ce/topologies_and_comm/topology_concepts/using_bind_addresses.html.md.erb ---------------------------------------------------------------------- diff --git a/topologies_and_comm/topology_concepts/using_bind_addresses.html.md.erb b/topologies_and_comm/topology_concepts/using_bind_addresses.html.md.erb index 19458a3..617bfdd 100644 --- a/topologies_and_comm/topology_concepts/using_bind_addresses.html.md.erb +++ b/topologies_and_comm/topology_concepts/using_bind_addresses.html.md.erb @@ -90,6 +90,6 @@ Set the locator bind address using one of these methods: - Inside a Geode application, take one of the following actions: - Automatically start a co-located locator using the gemfire property `start-locator`, and specifying the bind address for it in that property setting. - - Use `com.gemstone.gemfire.distributed.LocatorLauncher` API to start the locator inside your code. Use the `LocatorLauncher.Builder` class to construct an instance of the `LocatorLauncher`, use the `setBindAddress` method to specify the IP address to use and then use the start() method to start a Locator service embedded in your Java application process. + - Use `org.apache.geode.distributed.LocatorLauncher` API to start the locator inside your code. Use the `LocatorLauncher.Builder` class to construct an instance of the `LocatorLauncher`, use the `setBindAddress` method to specify the IP address to use and then use the start() method to start a Locator service embedded in your Java application process. If your locator uses a bind address, make sure every process that accesses the locator has the address as well. For peer-to-peer access to the locator, use the locator's bind address and the locator's port in your `gemfire.properties` `locators` list. For server discovery in a client/server installation, use the locator's bind address and the locator's port in the locator list you provide to in the client’s server pool configuration.