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 the expiration time for mutex locks in milliseconds, impacting how long concurrent import processes can hold locks before they are released. |
| What area does it affect? |
Concurrent import operations |
| What does the default mean? |
The default value is "300000", which sets the baseline numeric behavior for this property. |
| When should you review it? |
Review this property when configuring import performance or troubleshooting import-related issues. |
Property record
Facts stated in the ServiceNow documentation. No out of the box record has been read from an instance yet.
| Property name |
com.glide.concurrent_import_set_insert_mutex_expiration |
| Type |
integer |
| Application |
Not stated |
| Default value |
300000 |
| Description |
Not stated |
Sources
Official references and nearby text excerpts where this property appears.
Context preview
Snippet 1
... Location: Add a system property com.glide.concurrent_import_set_insert_mutex_spin_wait Wait time mutex spends if the lock is acquired (in milliseconds). • Type: Integer • Default value: 1000 • Location: Add a system property com.glide.concurrent_import_set_insert_mutex_expiration Mutex expiration time (in milliseconds). • Type: Integer • Default value: 300000 • Location: Add a system property com.glide.concurrent_import_set_mutex_fast_lock Specifies whether to use fast lock (true) or SQL-based slow lock ...
More in com.glide
Other properties in the same namespace.
All 831 properties in com.glide →