Key questions about this property
The answers below summarize the purpose, scope, default effect, and review scenarios for this property.
| What does it do? |
This property defines a comma-separated list of GIG gateway endpoints in host:port format, determining where the instance connects for GIG services. |
| What area does it affect? |
GIG gateway connections |
| What does the default mean? |
No default value is documented in this property record. |
| When should you review it? |
Review this property when configuring GIG connections or troubleshooting connectivity issues. |
Out of the box property record
Raw metadata from the property record.
| Property name |
glide.gig.client.endpoints |
| Sys ID |
5199789dff510310f0b8ffffffffffb3 |
| Type |
string |
| Application |
Global |
| Default value |
Not set |
| Description |
The list of GIG gateway endpoints this instance connects to. Comma-separated, with each entry in host:port form (e.g. pod-0.gig.ycg0.service-now.com:443); a legacy id:host:port form is also accepted but the id is ignored. Empty by default, in which case the GIG client starts no connections. The parsed list is further narrowed by datacenter-proximity filtering (see glide.gig.endpoints.local_gigs_only) before connections are opened. |
| Updated |
2026-06-04 17:58:14 |
Sources
Official references and nearby text excerpts where this property appears.
Context preview
Snippet 1
... exit cleanly. Non- daemon threads from the gateway fixed thread pool remain alive because Glide.destroy() never calls into JettyClientManager to tear down GIG resources. 1. Enable GIG (glide.gig.enable=true) with valid glide.gig.client.endpoints so the gateway connection and gateway fixed thread pool become active. 2. Shut down the Glide servlet (Tomcat stop / graceful JVM shutdown). Observe that the JVM doesn't exit cleanly. ...
More in glide (other)
Other properties in the same namespace.
All 405 properties in glide (other) →