API Data Store
API Gateway package is not accessible from Integration Server.
The following error message appears:
com.softwareag.apigateway.core.exceptions.DataStoreException
This problem could be because the defaultEncoding extended setting is modified.
CAUTION:
Do not modify this value. If you modify this value, your API Gateway instance will not function as this value is used in encoding all API Gateway transactions. If you migrate from one setup to another, ensure you have specified the same value for the defaultEncoding setting as the source instance. If this values are not same, the target API Gateway instance does not start.
This error message appears: com.softwareag.apigateway.core.exceptions.DataStoreException: com.softwareag.apigateway.core.exceptions.DataStoreException:
Resolution:
Set the value of the defaultEncoding extended setting as UTF-8.
The Event data store on API Gateway is using a lot of disk space.
The Elasticsearch JVM is unable to allocate memory for internal objects. Either other process in the machine are consuming more memory or Elasticsearch is not given sufficient heap space.
Also JVM has written these information in write.lock file, which is solely used by Elasticsearch for its internal purpose. Elasticsearch expects this file to be of size 0 and should not be modified. Since jvm has written the data, it is showing that as error and filling the disk with log.
Resolution:
Increase the Event data store JVM heap size.
I have exceeded the limit for total fields [1000] in index [gateway_default_analytics_]
I am getting the following error:
2019-09-19 00:29:02 UTC [YAI.0300.9999E] error while saving doc Index - gateway_default_analytics, typeName - transactionalEvents: POST http://10.177.129.5:9241/gateway_default_analytics/transactionalEvents: HTTP/1.1 400 Bad Request {"error":{"root_cause":[{"type":"illegal_argument_exception","reason":"Limit of total fields [1000] in index [gateway_default_analytics] has been exceeded"}],"type":"illegal_argument_exception","reason":"Limit of total fields [1000] in index [gateway_default_analytics] has been exceeded"},"status":400}
Resolution:
Increase the limit for total fields.
PUT /gateway_default_analytics_/_settings{"index.mapping.total_fields.limit": 20000}
I experienced a low disk space issue and my API Gateway has stopped working for WRITE operations.
I am getting the following issue
Exception: [WARN ][o.e.c.r.a.DiskThresholdMonitor] [localhost1568897216386] flood stage disk watermark [95%] exceeded on [BOf6SQe2SwyI93vi4RlBNQ][localhost1568897216386][C:\SoftwareAG\InternalDataStore\data\nodes\0] free: 2.4gb[2.4%], all indices on this node will be marked read-onlySaving an API -> error message ("Saving API failed. com.softwareag.apigateway.core.exceptions.DataStoreException: Error while saving the document. doc Id - 6d5c7ac0-574a-4a53-acba-a738f21e3142, type name - _doc, message - "index [gateway_default_policy] blocked by: [FORBIDDEN/12/index read-only / allow delete (api)];" ")
Resolution:
You can clean up the disk space by using the following CURL command:
curl -XPUT -H "Content-Type:
application/json"
http://localhost:9200/_all/_settings
-d '{"index.blocks.read_only_allow_delete":
null}'
My Elasticsearch server is not starting. I get a "bootstrap checks failed" error.
I am getting the following error:
[2020-03-25T09:09:20,298][INFO ][o.e.b.BootstrapChecks ] [itsbebel00471.jnj.com1585050877659] bound or publishing to a non-loopback address, enforcing bootstrap checks [2020-03-25T09:09:20,299][ERROR][o.e.b.Bootstrap ] [itsbebel00471.jnj.com1585050877659] node validation exception [1] bootstrap checks failed [1]: system call filters failed to install; check the logs and fix your configuration or disable system call filters at your own risk.
Resolution:
Add bootstrap.system_call_filter: false setting to elasticsearch.yml
When I access the audit logs, the internal datastore, crashes.
You get the following error
[2020-03-03T10:03:33,857][ERROR][o.e.ExceptionsHelper ] [ daeipresal43558.eur.ad
.sag1580968109910] fatal error at org.elasticsearch.ExceptionsHelper.lambda$maybeDieOnAnotherThread$2(ExceptionsHelper.java:310) at java.util.Optional.ifPresent(Optional.java:159) at org.elasticsearch.ExceptionsHelper.maybeDieOnAnotherThread(ExceptionsHelper.java:300) at org.elasticsearch.http.netty4.Netty4HttpRequestHandler.exceptionCaught(Netty4HttpRequestHandler.java:76) [2020-03-03T10:03:33,858][ERROR][o.e.ExceptionsHelper ] [ daeipresal43558.eur.ad .sag1580968109910] fatal error at org.elasticsearch.ExceptionsHelper.lambda$maybeDieOnAnotherThread$2(ExceptionsHelper.java:310) at java.util.Optional.ifPresent(Optional.java:159) at org.elasticsearch.ExceptionsHelper.maybeDieOnAnotherThread(ExceptionsHelper.java:300) at org.elasticsearch.http.netty4.Netty4HttpRequestHandler.exceptionCaught(Netty4HttpRequestHandler.java:76) [2020-03-03T10:03:33,867][ERROR][o.e.b.ElasticsearchUncaughtExceptionHandler] [ daeipresal43558.eur.ad .sag1580968109910] fatal error in thread [Thread-176], exiting java.lang.OutOfMemoryError: Java heap space
Resolution:
Set the -XX:MaxDirectMemorySize property to 4095m.