webMethods

webMethods

Join this online group to communicate across IBM product users and experts by sharing advice and best practices with peers and staying up to date regarding product enhancements.

 View Only
Expand all | Collapse all

Login issue with the API gateway page

  • 1.  Login issue with the API gateway page

    Posted Fri January 18, 2019 01:16 AM

    Hi Experts,

    I have recently installed the WMAPIGateway in my pc. Being a newbie to the product, I am unable to figure out the reason behind the following error being displayed while i’m trying to access the same through default credentials. Please find the screenshot attached and help me out with the same.

    Thanks in advance, would really appreciate a sooner reply. :slight_smile:


    #webMethods
    #API-Gateway
    #API-Management


  • 2.  RE: Login issue with the API gateway page

    Posted Fri January 18, 2019 01:45 AM

    Can you please attach a screenshot as I am not able to see any screenshot here?


    #API-Gateway
    #webMethods
    #API-Management


  • 3.  RE: Login issue with the API gateway page

    Posted Fri January 18, 2019 01:51 AM

    Hey, I have already attached a .jpg file with my post. Anyway, if you are not able to view the same, I am not able to attach the pic with this reply as there is no option being displayed for the same thus i would like to describe the same.

    So, when ever i am trying to login to wmAPIGateway page with default Administrator credentials the error i am getting is

    The username/password you have entered is invalid


    #API-Management
    #API-Gateway
    #webMethods


  • 4.  RE: Login issue with the API gateway page

    Posted Fri January 18, 2019 02:06 AM

    Hi Udish Kumar,

    The error message you have mentioned is very generic. Can you please let us know you API Gateway version and if any error message in the below log files \IntegrationServer\instances\default\logs\server.log,
    \IntegrationServer\instances\default\logs\APIGateway.log


    #API-Management
    #API-Gateway
    #webMethods


  • 5.  RE: Login issue with the API gateway page

    Posted Fri January 18, 2019 02:07 AM

    Hi Udish,

    Please check that Internal Data Store/ Elastic search is started or not with API Gateway IS startup.
    WmAPIGateway package might be partially loaded if Internal data store is not started.

    Your WmAPIGateway package should completely loaded if Internal data store is started successfully.

    Hope this helps.

    Thanks,
    Shiv


    #webMethods
    #API-Gateway
    #API-Management


  • 6.  RE: Login issue with the API gateway page

    Posted Mon July 06, 2020 05:25 PM

    Thank you! This reply solved a similar issue II had.


    #webMethods
    #API-Management
    #API-Gateway


  • 7.  RE: Login issue with the API gateway page

    Posted Fri January 18, 2019 02:13 AM

    2019-01-18 10:53:32 IST [ISS.0012.0022C] Access Denied. Authentication resolved to user “GatewayInternalTechnicalUser”. User is not defined in any of the available user stores.
    2019-01-18 10:53:32 IST [ISS.0053.0002C] Access denied for user GatewayInternalTechnicalUser on port 9525 → ‘invoke/apigateway.ui:getSolutionDetails’ from 127.0.0.1.
    2019-01-18 10:53:47 IST [ISS.0012.0022C] Access Denied. Authentication resolved to user “GatewayInternalTechnicalUser”. User is not defined in any of the available user stores.
    2019-01-18 10:53:47 IST [ISS.0053.0002C] Access denied for user GatewayInternalTechnicalUser on port 9525 → ‘invoke/apigateway.ui:getSolutionDetails’ from 127.0.0.1.
    2019-01-18 10:54:02 IST [ISS.0012.0022C] Access Denied. Authentication resolved to user “GatewayInternalTechnicalUser”. User is not defined in any of the available user stores.

    The logfile statements


    #API-Management
    #webMethods
    #API-Gateway


  • 8.  RE: Login issue with the API gateway page

    Posted Fri January 18, 2019 02:19 AM

    2019-01-18 11:36:58 IST [ISS.0028.0012I] WmAPIGateway: Startup service (apigateway:startup)
    2019-01-18 11:36:58 IST [YAI.0300.0001I] [default][SAG-DNHP6C2] Gateway Logger successfully registered and initialized.
    2019-01-18 11:36:58 IST [YAI.0300.0109I] [default][SAG-DNHP6C2] Setting watt properties.
    2019-01-18 11:36:59 IST [YAI.0300.0105I] [default][SAG-DNHP6C2] Starting ElasticSearch. API Gateway will wait for 300 seconds for ElasticSearch availability
    2019-01-18 11:43:43 IST [YAI.0300.0130E] [default][SAG-DNHP6C2] Elasticsearch failed to start at http://sag-dnhp6c2.eur.ad.sag:9240 in 300 seconds. Please check the Elasticsearch logs.
    2019-01-18 11:43:43 IST [ISS.0028.0012I] WmXSLT: Startup service (wm.xslt.Admin:startup)
    2019-01-18 11:43:43 IST [ISS.0028.0012I] WmAssetPublisher: Startup service (wm.server.metadata.Admin:startup)
    2019-01-18 11:43:43 IST [ISS.0138.0050I] Asset Publisher package initializing
    2019-01-18 11:43:43 IST [ISS.0028.0012I] WmJSONAPI: Startup service (wm.jsonapi.mediatype:addSupport)
    2019-01-18 11:43:43 IST [ISS.0028.0012I] WmJSONAPI: Startup service (wm.jsonapi.logging:init)
    2019-01-18 11:43:43 IST [ISS.0028.0012I] WmISExtDC: Startup service (com.wm.isextdc.PkgInit:init)
    2019-01-18 11:43:43 IST [ISS.0028.0012I] WmCloud: Startup service (wm.client.integrationlive.admin:createDefaultILiveTrustStoreAlias)
    2019-01-18 11:43:44 IST [ISS.0028.0012I] WmCloud: Startup service (wm.client.integrationlive.admin:loadTenantAccountInfo)
    2019-01-18 11:43:44 IST [ISS.0021.6005I] webMethods Cloud information was not loaded because the settings are not specified.
    2019-01-18 11:43:44 IST [ISS.0028.0012I] WmCloud: Startup service (wm.client.integrationlive.connector:initConnectors)
    2019-01-18 11:43:44 IST [ISS.0028.0012I] WmART: Startup service (wm.art.admin:startup)
    2019-01-18 11:43:44 IST [ISS.0028.0012I] WmVCS: Startup service (wm.server.vcsadmin:startup)
    2019-01-18 11:43:44 IST [VCS.0132.0050I] VCS package initializing
    2019-01-18 11:43:44 IST [ISS.0028.0012I] WmVCS: Startup service (wm.server.vcsui:addSolutions)
    2019-01-18 11:43:44 IST [ISS.0028.0012I] WmFlatFile: Startup service (wm.server.ff:init)
    2019-01-18 11:43:44 IST [ISS.0028.0012I] WmFlatFile: Startup service (wm.server.ff:setACLs)
    2019-01-18 11:43:44 IST [ISS.0028.0012I] WmARTExtDC: Startup service (com.wm.artextdc.pkginit:init)
    2019-01-18 11:43:44 IST [ISP.0046.0012I] Enabling HTTP Listener on port 9999
    2019-01-18 11:43:44 IST [ISS.0070.0013W] Failed to start listener HTTPListener@9999. The following error was encountered: Address already in use: JVM_Bind
    2019-01-18 11:43:44 IST [ISP.0046.0012I] Enabling HTTP Listener on port 9525
    2019-01-18 11:43:44 IST [ISS.0025.0013I] Cache Sweeper started
    2019-01-18 11:43:44 IST [ISS.0035.0003I] Log rotation interval set to 1440 minutes.
    2019-01-18 11:43:44 IST [ISS.0025.0057I] Reading system level information
    2019-01-18 11:43:44 IST [ISS.0159.0001I] Digital Event Services Initialized.
    2019-01-18 11:43:44 IST [ISS.0014.0002I] Initialization completed in 446 seconds.
    2019-01-18 11:43:44 IST [ISS.0025.0016I] Config File Directory Saved
    2019-01-18 11:43:45 IST [ISS.0012.0022C] Access Denied. Authentication resolved to user “GatewayInternalTechnicalUser”. User is not defined in any of the available user stores.
    2019-01-18 11:43:45 IST [ISS.0053.0002C] Access denied for user GatewayInternalTechnicalUser on port 9525 → ‘invoke/apigateway.ui:getSolutionDetails’ from 127.0.0.1.
    2019-01-18 11:43:59 IST [ISS.0012.0022C] Access Denied. Authentication resolved to user “GatewayInternalTechnicalUser”. User is not defined in any of the available user stores.
    2019-01-18 11:43:59 IST [ISS.0053.0002C] Access denied for user GatewayInternalTechnicalUser on port 9525 → ‘invoke/apigateway.ui:getSolutionDetails’ from 127.0.0.1.
    2019-01-18 11:44:12 IST [ISS.0053.0002C] Access denied for user Administrator on port 9525 → ‘wm-message’ from 127.0.0.1.
    2019-01-18 11:44:14 IST [ISS.0012.0022C] Access Denied. Authentication resolved to user “GatewayInternalTechnicalUser”. User is not defined in any of the available user stores.
    2019-01-18 11:44:14 IST [ISS.0053.0002C] Access denied for user GatewayInternalTechnicalUser on port 9525 → ‘invoke/apigateway.ui:getSolutionDetails’ from 127.0.0.1.
    2019-01-18 11:44:29 IST [ISS.0012.0022C] Access Denied. Authentication resolved to user “GatewayInternalTechnicalUser”. User is not defined in any of the available user stores.
    2019-01-18 11:44:29 IST [ISS.0053.0002C] Access denied for user GatewayInternalTechnicalUser on port 9525 → ‘invoke/apigateway.ui:getSolutionDetails’ from 127.0.0.1.
    2019-01-18 11:44:44 IST [ISS.0012.0022C] Access Denied. Authentication resolved to user “GatewayInternalTechnicalUser”. User is not defined in any of the available user stores.
    2019-01-18 11:44:44 IST [ISS.0053.0002C] Access denied for user GatewayInternalTechnicalUser on port 9525 → ‘invoke/apigateway.ui:getSolutionDetails’ from 127.0.0.1.
    2019-01-18 11:44:59 IST [ISS.0012.0022C] Access Denied. Authentication resolved to user “GatewayInternalTechnicalUser”. User is not defined in any of the available user stores.
    2019-01-18 11:44:59 IST [ISS.0053.0002C] Access denied for user GatewayInternalTechnicalUser on port 9525 → ‘invoke/apigateway.ui:getSolutionDetails’ from 127.0.0.1.
    2019-01-18 11:45:14 IST [ISS.0012.0022C] Access Denied. Authentication resolved to user “GatewayInternalTechnicalUser”. User is not defined in any of the available user stores.
    2019-01-18 11:45:14 IST [ISS.0053.0002C] Access denied for user GatewayInternalTechnicalUser on port 9525 → ‘invoke/apigateway.ui:getSolutionDetails’ from 127.0.0.1.
    2019-01-18 11:45:29 IST [ISS.0012.0022C] Access Denied. Authentication resolved to user “GatewayInternalTechnicalUser”. User is not defined in any of the available user stores.
    2019-01-18 11:45:29 IST [ISS.0053.0002C] Access denied for user GatewayInternalTechnicalUser on port 9525 → ‘invoke/apigateway.ui:getSolutionDetails’ from 127.0.0.1.
    2019-01-18 11:45:44 IST [ISS.0012.0022C] Access Denied. Authentication resolved to user “GatewayInternalTechnicalUser”. User is not defined in any of the available user stores.
    2019-01-18 11:45:44 IST [ISS.0053.0002C] Access denied for user GatewayInternalTechnicalUser on port 9525 → ‘invoke/apigateway.ui:getSolutionDetails’ from 127.0.0.1.
    2019-01-18 11:45:59 IST [ISS.0012.0022C] Access Denied. Authentication resolved to user “GatewayInternalTechnicalUser”. User is not defined in any of the available user stores.
    2019-01-18 11:45:59 IST [ISS.0053.0002C] Access denied for user GatewayInternalTechnicalUser on port 9525 → ‘invoke/apigateway.ui:getSolutionDetails’ from 127.0.0.1.
    2019-01-18 11:46:14 IST [ISS.0012.0022C] Access Denied. Authentication resolved to user “GatewayInternalTechnicalUser”. User is not defined in any of the available user stores.
    2019-01-18 11:46:14 IST [ISS.0053.0002C] Access denied for user GatewayInternalTechnicalUser on port 9525 → ‘invoke/apigateway.ui:getSolutionDetails’ from 127.0.0.1.
    2019-01-18 11:46:29 IST [ISS.0012.0022C] Access Denied. Authentication resolved to user “GatewayInternalTechnicalUser”. User is not defined in any of the available user stores.


    #API-Management
    #API-Gateway
    #webMethods


  • 9.  RE: Login issue with the API gateway page

    Posted Fri January 18, 2019 02:22 AM

    Can you guys suggest how to access elastic search i mean any sort of path where i can access it to start it?


    #API-Gateway
    #API-Management
    #webMethods


  • 10.  RE: Login issue with the API gateway page

    Posted Fri January 18, 2019 02:29 AM

    Its available at:

    /Event Data Store(Internal Data Store)/bin

    Thanks,
    Shiv


    #API-Gateway
    #webMethods
    #API-Management


  • 11.  RE: Login issue with the API gateway page

    Posted Fri January 18, 2019 02:34 AM

    …\CONFIG\CEL-INSTANCES.PROPERTIES
    install.service=true
    Access is denied.
    Failed stopping ‘sagcel103_1’ service
    → Downloading file:///C:\SoftwareAG\InternalDataStore\repo\search-guard-5.zip
    [=================================================] 100%
    @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
    @ WARNING: plugin requires additional permissions @
    @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@

    • java.io.FilePermission /proc/sys/net/core/somaxconn read
    • java.lang.RuntimePermission accessClassInPackage.sun.misc
    • java.lang.RuntimePermission accessClassInPackage.sun.nio.ch
    • java.lang.RuntimePermission accessClassInPackage.sun.security.x509
    • java.lang.RuntimePermission accessDeclaredMembers
    • java.lang.RuntimePermission getClassLoader
    • java.lang.RuntimePermission loadLibrary.*
    • java.lang.RuntimePermission setContextClassLoader
    • java.lang.RuntimePermission shutdownHooks
    • java.lang.reflect.ReflectPermission suppressAccessChecks
    • java.security.SecurityPermission getProperty.ssl.KeyManagerFactory.algorithm
    • java.security.SecurityPermission setProperty.ocsp.enable
    • java.util.PropertyPermission com.sun.security.enableCRLDP write
    • java.util.PropertyPermission es.set.netty.runtime.available.processors write
    • java.util.PropertyPermission java.security.debug write
    • java.util.PropertyPermission java.security.krb5.conf write
    • java.util.PropertyPermission javax.security.auth.useSubjectCredsOnly write
    • java.util.PropertyPermission sun.nio.ch.bugLevel write
    • java.util.PropertyPermission sun.security.krb5.debug write
    • java.util.PropertyPermission sun.security.spnego.debug write
    • javax.security.auth.AuthPermission doAs
    • javax.security.auth.AuthPermission modifyPrivateCredentials
    • javax.security.auth.kerberos.ServicePermission * accept
      See Permissions in the JDK
      for descriptions of what these permissions allow and the associated risks.
      → Installed search-guard-5

    ---------- …\CONFIG\CEL-INSTANCES.PROPERTIES
    install.service=true
    Failed starting ‘sagcel103_1’ service


    #webMethods
    #API-Gateway
    #API-Management


  • 12.  RE: Login issue with the API gateway page

    Posted Fri March 01, 2019 05:01 AM

    hello, I have the same issue after installing API Gateway 10.3 on a windows server as a service:

    \InternalDataStore\logs\startup.log file:

    ---------- …\CONFIG\CEL-INSTANCES.PROPERTIES
    install.service=true
    Failed starting ‘sagcel103_1’ service

    Does anyone has an answer ?


    #webMethods
    #API-Gateway
    #API-Management


  • 13.  RE: Login issue with the API gateway page

    Posted Fri March 01, 2019 05:14 AM

    If you are able to see the below in ElasticSearch Logs, then work with you Client to get the below configurations added on the OS Server.

    [1]: max file descriptors [4096] for elasticsearch process is too low, increase to at least [65536]
    [2]: max virtual memory areas vm.max_map_count [65530] is too low, increase to at least [262144]

    cat /proc/sys/fs/file-max this command will give the current max file descriptor limit.

    A. To change the number of file descriptors in Linux, do the following as the root user:

    1. Edit the following line in the /etc/sysctl.conf file:
      fs.file-max = 65536
      (value is the new file descriptor limit that you want to set )
    2. Apply the change by running the following command:
      # /sbin/sysctl –p
    3. Check the new value:
      cat /proc/sys/fs/file-max

    B. B. To increase the max_map_count parameter:

    1. Add the following line to /etc/sysctl.conf:
      vm.max_map_count=262144

      where map_count should be around 1 per 128 KB of system memory. 
      For example: vm.max_map_count=2097152 on a 256 GB system.
      
    2. Reload the config as root:
      sysctl –p

    3. Check the new value:
      cat /proc/sys/vm/max_map_count

    4. Restart Vector.

    Not sure if it will help but, give it a try as it worked for a friend :slight_smile:


    #webMethods
    #API-Gateway
    #API-Management


  • 14.  RE: Login issue with the API gateway page

    Posted Sun November 10, 2019 09:36 AM

    Dear all,

    I am a newbie on APIGateway and I’d like to get your help on the issue that I’m dealing with.When I try to login my local APIGateway with Administrator/manage; I get the “Data store is down” message.To sort out this;I manually created “GatewayInternalTechnicalUser” user however I still face with the same error.Below you may find the log details.I’d be grateful if you could give me a help for this.

    APIGateway.log:

    2019-11-10 16:30:08 INFO [apigatewayui] [com.softwareag.apigateway.ui.service.RequestHandler] - Login request for User: Administrator invoked.
    2019-11-10 16:30:08 INFO [apigatewayui] [com.softwareag.apigateway.ui.service.ServerConnection] - Get ACL calls returns unexpected status code : 500
    2019-11-10 16:30:08 ERROR [apigatewayui] [com.softwareag.apigateway.ui.service.RequestHandler] - Data store is down - com.softwareag.apigateway.ui.exception.DataStoreConnectionException: Data store is down

    server.log:
    2019-11-10 16:29:41 EET [YAI.0300.8889E] [default][SAG-1LTD1Z2] Exception while searching index. Search request cannot be completed due IOException java.net.ConnectException: Timeout connecting to [/192.168.0.35:9240]
    at org.elasticsearch.client.RestClient.extractAndWrapCause(RestClient.java:804) ~[?:?]
    at org.elasticsearch.client.RestClient.performRequest(RestClient.java:225) ~[?:?]
    at org.elasticsearch.client.RestClient.performRequest(RestClient.java:212) ~[?:?]
    at com.softwareag.apigateway.core.datastore.ElasticsearchClientImpl.performRequest(ElasticsearchClientImpl.java:170) ~[?:?]
    at com.softwareag.apigateway.core.datastore.ElasticsearchClientImpl.searchDoc(ElasticsearchClientImpl.java:1613) ~[?:?]
    at com.softwareag.apigateway.core.datastore.ElasticsearchClientImpl.searchDocuments(ElasticsearchClientImpl.java:1122) [?:?]
    at com.softwareag.apigateway.core.datastore.ElasticsearchClientImpl.searchDocuments(ElasticsearchClientImpl.java:1175) [?:?]
    at com.softwareag.apigateway.core.datastore.ElasticSearchQueryExecutor.fetchDocuments(ElasticSearchQueryExecutor.java:147) [?:?]
    at com.softwareag.apigateway.core.datastore.ElasticSearchQueryExecutor.getResponse(ElasticSearchQueryExecutor.java:57) [?:?]
    at com.softwareag.apigateway.core.datastore.ElasticSearchQueryExecutor.execute(ElasticSearchQueryExecutor.java:29) [?:?]
    at com.softwareag.apigateway.core.datastore.GatewayElasticsearchRepository.findRecords(GatewayElasticsearchRepository.java:235) [?:?]
    at com.softwareag.apigateway.core.datastore.GatewayElasticsearchRepository.findAll(GatewayElasticsearchRepository.java:223) [?:?]
    at com.softwareag.apigateway.core.persistence.handlers.PackagePersistanceHandler.getAll(PackagePersistanceHandler.java:30) [?:?]
    at com.softwareag.apigateway.core.manager.PackageManager.getAll(PackageManager.java:155) [?:?]
    at com.softwareag.pg.pgmen.processors.QuotaSurvivalProcessor.exec(QuotaSurvivalProcessor.java:41) [?:?]
    at com.softwareag.pg.pgmen.processors.DCProcessor.run(DCProcessor.java:38) [?:?]
    at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) [?:1.8.0_222]
    at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308) [?:1.8.0_222]
    at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180) [?:1.8.0_222]
    at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294) [?:1.8.0_222]
    at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) [?:1.8.0_222]
    at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) [?:1.8.0_222]
    at java.lang.Thread.run(Thread.java:748) [?:1.8.0_222]
    Caused by: java.net.ConnectException: Timeout connecting to [/192.168.0.35:9240]
    at org.apache.http.nio.pool.RouteSpecificPool.timeout(RouteSpecificPool.java:169) ~[?:?]
    at org.apache.http.nio.pool.AbstractNIOConnPool.requestTimeout(AbstractNIOConnPool.java:628) ~[?:?]
    at org.apache.http.nio.pool.AbstractNIOConnPool$InternalSessionRequestCallback.timeout(AbstractNIOConnPool.java:894) ~[?:?]
    at org.apache.http.impl.nio.reactor.SessionRequestImpl.timeout(SessionRequestImpl.java:183) ~[?:?]
    at org.apache.http.impl.nio.reactor.DefaultConnectingIOReactor.processTimeouts(DefaultConnectingIOReactor.java:210) ~[?:?]
    at org.apache.http.impl.nio.reactor.DefaultConnectingIOReactor.processEvents(DefaultConnectingIOReactor.java:155) ~[?:?]
    at org.apache.http.impl.nio.reactor.AbstractMultiworkerIOReactor.execute(AbstractMultiworkerIOReactor.java:351) ~[?:?]
    at org.apache.http.impl.nio.conn.PoolingNHttpClientConnectionManager.execute(PoolingNHttpClientConnectionManager.java:221) ~[?:?]
    at org.apache.http.impl.nio.client.CloseableHttpAsyncClientBase$1.run(CloseableHttpAsyncClientBase.java:64) ~[?:?]
    … 1 more

    2019-11-10 16:29:41 EET [YAI.0103.0014I] [default][SAG-1LTD1Z2] Error while retrieving Documents for Index gateway_default, Type packages. Cause: Search request cannot be completed
    2019-11-10 16:30:18 EET [YAI.0103.0012I] [default][SAG-1LTD1Z2] Error while creating/updating Document for Index gateway_default_audit, Type auditlogs, Id d4b01016-cee8-4560-999e-be0b9e717253. Cause: Timeout connecting to [/192.168.0.35:9240]
    2019-11-10 16:30:18 EET [YAI.0205.0032E] [default][SAG-1LTD1Z2] Error sending pgmen event. Cause: com.softwareag.apigateway.core.exceptions.DataStoreException java.net.ConnectException: Timeout connecting to [/192.168.0.35:9240] com.softwareag.apigateway.core.exceptions.DataStoreException: java.net.ConnectException: Timeout connecting to [/192.168.0.35:9240]
    at com.softwareag.apigateway.core.datastore.GatewayElasticsearchRepository.index(GatewayElasticsearchRepository.java:180) ~[?:?]
    at com.softwareag.apigateway.core.datastore.GatewayElasticsearchRepository.index(GatewayElasticsearchRepository.java:162) ~[?:?]
    at com.softwareag.apigateway.core.persistence.handlers.GatewayAuditlogPersistenceHandler.saveGatewayAuditlogData(GatewayAuditlogPersistenceHandler.java:33) ~[?:?]
    at com.softwareag.pg.pgmen.events.gateway.GatewayAuditlogEventSender.onSend(GatewayAuditlogEventSender.java:61) ~[?:?]
    at com.softwareag.pg.pgmen.events.EventSender.send(EventSender.java:168) ~[?:?]
    at com.softwareag.pg.pgmen.events.BaseEventPublisher.sendHere(BaseEventPublisher.java:276) ~[?:?]
    at com.softwareag.pg.pgmen.events.BaseEventPublisher.publish(BaseEventPublisher.java:249) ~[?:?]
    at com.softwareag.pg.pgmen.events.BaseEventPublisher.lambda$publishEventAsync$2(BaseEventPublisher.java:216) ~[?:?]
    at java.util.concurrent.CompletableFuture$AsyncSupply.run(CompletableFuture.java:1590) [?:1.8.0_222]
    at java.util.concurrent.CompletableFuture$AsyncSupply.exec(CompletableFuture.java:1582) [?:1.8.0_222]
    at java.util.concurrent.ForkJoinTask.doExec(ForkJoinTask.java:289) [?:1.8.0_222]
    at java.util.concurrent.ForkJoinPool$WorkQueue.runTask(ForkJoinPool.java:1056) [?:1.8.0_222]
    at java.util.concurrent.ForkJoinPool.runWorker(ForkJoinPool.java:1692) [?:1.8.0_222]
    at java.util.concurrent.ForkJoinWorkerThread.run(ForkJoinWorkerThread.java:157) [?:1.8.0_222]
    Caused by: java.net.ConnectException: Timeout connecting to [/192.168.0.35:9240]
    at org.elasticsearch.client.RestClient.extractAndWrapCause(RestClient.java:804) ~[?:?]
    at org.elasticsearch.client.RestClient.performRequest(RestClient.java:225) ~[?:?]
    at org.elasticsearch.client.RestClient.performRequest(RestClient.java:212) ~[?:?]
    at com.softwareag.apigateway.core.datastore.ElasticsearchClientImpl.performRequest(ElasticsearchClientImpl.java:170) ~[?:?]
    at com.softwareag.apigateway.core.datastore.ElasticsearchClientImpl.createOrUpdate(ElasticsearchClientImpl.java:1478) ~[?:?]
    at com.softwareag.apigateway.core.datastore.ElasticsearchClientImpl.createDocument(ElasticsearchClientImpl.java:333) ~[?:?]
    at com.softwareag.apigateway.core.datastore.GatewayElasticsearchRepository.index(GatewayElasticsearchRepository.java:174) ~[?:?]
    … 13 more
    Caused by: java.net.ConnectException: Timeout connecting to [/192.168.0.35:9240]
    at org.apache.http.nio.pool.RouteSpecificPool.timeout(RouteSpecificPool.java:169) ~[?:?]
    at org.apache.http.nio.pool.AbstractNIOConnPool.requestTimeout(AbstractNIOConnPool.java:628) ~[?:?]
    at org.apache.http.nio.pool.AbstractNIOConnPool$InternalSessionRequestCallback.timeout(AbstractNIOConnPool.java:894) ~[?:?]
    at org.apache.http.impl.nio.reactor.SessionRequestImpl.timeout(SessionRequestImpl.java:183) ~[?:?]
    at org.apache.http.impl.nio.reactor.DefaultConnectingIOReactor.processTimeouts(DefaultConnectingIOReactor.java:210) ~[?:?]
    at org.apache.http.impl.nio.reactor.DefaultConnectingIOReactor.processEvents(DefaultConnectingIOReactor.java:155) ~[?:?]
    at org.apache.http.impl.nio.reactor.AbstractMultiworkerIOReactor.execute(AbstractMultiworkerIOReactor.java:351) ~[?:?]
    at org.apache.http.impl.nio.conn.PoolingNHttpClientConnectionManager.execute(PoolingNHttpClientConnectionManager.java:221) ~[?:?]
    at org.apache.http.impl.nio.client.CloseableHttpAsyncClientBase$1.run(CloseableHttpAsyncClientBase.java:64) ~[?:?]
    at java.lang.Thread.run(Thread.java:748) ~[?:1.8.0_222]

    2019-11-10 16:30:41 EET [YAI.0300.8889E] [default][SAG-1LTD1Z2] Exception while searching index. Search request cannot be completed due IOException java.net.ConnectException: Timeout connecting to [/192.168.0.35:9240]
    at org.elasticsearch.client.RestClient.extractAndWrapCause(RestClient.java:804) ~[?:?]
    at org.elasticsearch.client.RestClient.performRequest(RestClient.java:225) ~[?:?]
    at org.elasticsearch.client.RestClient.performRequest(RestClient.java:212) ~[?:?]
    at com.softwareag.apigateway.core.datastore.ElasticsearchClientImpl.performRequest(ElasticsearchClientImpl.java:170) ~[?:?]
    at com.softwareag.apigateway.core.datastore.ElasticsearchClientImpl.searchDoc(ElasticsearchClientImpl.java:1613) ~[?:?]
    at com.softwareag.apigateway.core.datastore.ElasticsearchClientImpl.searchDocuments(ElasticsearchClientImpl.java:1122) [?:?]
    at com.softwareag.apigateway.core.datastore.ElasticsearchClientImpl.searchDocuments(ElasticsearchClientImpl.java:1175) [?:?]
    at com.softwareag.apigateway.core.datastore.ElasticSearchQueryExecutor.fetchDocuments(ElasticSearchQueryExecutor.java:147) [?:?]
    at com.softwareag.apigateway.core.datastore.ElasticSearchQueryExecutor.getResponse(ElasticSearchQueryExecutor.java:57) [?:?]
    at com.softwareag.apigateway.core.datastore.ElasticSearchQueryExecutor.execute(ElasticSearchQueryExecutor.java:29) [?:?]
    at com.softwareag.apigateway.core.datastore.GatewayElasticsearchRepository.findRecords(GatewayElasticsearchRepository.java:235) [?:?]
    at com.softwareag.apigateway.core.datastore.GatewayElasticsearchRepository.findAll(GatewayElasticsearchRepository.java:223) [?:?]
    at com.softwareag.apigateway.core.persistence.handlers.PackagePersistanceHandler.getAll(PackagePersistanceHandler.java:30) [?:?]
    at com.softwareag.apigateway.core.manager.PackageManager.getAll(PackageManager.java:155) [?:?]
    at com.softwareag.pg.pgmen.processors.QuotaSurvivalProcessor.exec(QuotaSurvivalProcessor.java:41) [?:?]
    at com.softwareag.pg.pgmen.processors.DCProcessor.run(DCProcessor.java:38) [?:?]
    at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) [?:1.8.0_222]
    at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308) [?:1.8.0_222]
    at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180) [?:1.8.0_222]
    at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294) [?:1.8.0_222]
    at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) [?:1.8.0_222]
    at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) [?:1.8.0_222]
    at java.lang.Thread.run(Thread.java:748) [?:1.8.0_222]
    Caused by: java.net.ConnectException: Timeout connecting to [/192.168.0.35:9240]
    at org.apache.http.nio.pool.RouteSpecificPool.timeout(RouteSpecificPool.java:169) ~[?:?]
    at org.apache.http.nio.pool.AbstractNIOConnPool.requestTimeout(AbstractNIOConnPool.java:628) ~[?:?]
    at org.apache.http.nio.pool.AbstractNIOConnPool$InternalSessionRequestCallback.timeout(AbstractNIOConnPool.java:894) ~[?:?]
    at org.apache.http.impl.nio.reactor.SessionRequestImpl.timeout(SessionRequestImpl.java:183) ~[?:?]
    at org.apache.http.impl.nio.reactor.DefaultConnectingIOReactor.processTimeouts(DefaultConnectingIOReactor.java:210) ~[?:?]
    at org.apache.http.impl.nio.reactor.DefaultConnectingIOReactor.processEvents(DefaultConnectingIOReactor.java:155) ~[?:?]
    at org.apache.http.impl.nio.reactor.AbstractMultiworkerIOReactor.execute(AbstractMultiworkerIOReactor.java:351) ~[?:?]
    at org.apache.http.impl.nio.conn.PoolingNHttpClientConnectionManager.execute(PoolingNHttpClientConnectionManager.java:221) ~[?:?]
    at org.apache.http.impl.nio.client.CloseableHttpAsyncClientBase$1.run(CloseableHttpAsyncClientBase.java:64) ~[?:?]
    … 1 more

    2019-11-10 16:30:41 EET [YAI.0103.0014I] [default][SAG-1LTD1Z2] Error while retrieving Documents for Index gateway_default, Type packages. Cause: Search request cannot be completed


    #webMethods
    #API-Management
    #API-Gateway


  • 15.  RE: Login issue with the API gateway page

    Posted Fri December 20, 2019 10:24 PM

    @Deniz,

    About the user creation “GatewayInternalTechnicalUser”.
    Faced this issue and found the license provided was not of API gateway.

    Can you please confirm if the license provided is of API gateway and not Integration server.
    Under API gateway license you will have most of the IS features disabled. Screen shoot from the licenses page from IS admin screen would help.


    #webMethods
    #API-Gateway
    #API-Management