Integration Server Responding very slow

server.log (90.4 KB)

I am using 10.5 (IS) in my local machine (Virtual Machine fedora 36) it taking , lots of time to boot the server.

what are the setup required to overcome this issue?

Hi @sazhad ,
I see a few issues from the server log attached.

  • 2022-06-28 02:21:15 PDT [ISS.0025.0049I] The JCE Unlimited Strength Jurisdiction Policy File was found
    2022-06-28 02:34:13 PDT [ISS.0025.0041I] FIPS mode not initialized
    and
    2022-06-28 21:42:59 PDT [ISS.0025.0049I] The JCE Unlimited Strength Jurisdiction Policy File was found
    2022-06-28 21:56:03 PDT [ISS.0025.0041I] FIPS mode not initialized

There is almost 14 minutes difference between these two steps , you can set logging facility 25 - Initialization to trace and get more details.

  • 2022-06-28 21:56:33 PDT [com.webmethods.fabric.agent.FabricAgent.null.load.errorI] [agent.load.error] Error processing registry config file /webMethods/wm105/IntegrationServer/instances/default/config/fabric-agent.xml java.io.FileNotFoundException: /webMethods/wm105/IntegrationServer/instances/default/config/fabric-agent.xml (No such file or directory) - Looks like there is a file missing
  • There are some UM related errors as well. - topic/dca_event_response does not exist in Universal Messaging Realm.
    at com.webmethods.optimize.jndiUtil.NirvanaJMSConfig.initTopics(NirvanaJMSConfig.java:195)
  • You can also confirm if the memory requirements are met in the VM for running IS and the OS is supported.

-NP

Thank you @ Nagendra Prasad

Could you please tell me what setup I need to do, for now?

  • 2022-06-28 21:56:33 PDT [com.webmethods.fabric.agent.FabricAgent.null.load.errorI] [agent.load.error] Error processing registry config file /webMethods/wm105/IntegrationServer/instances/default/config/fabric-agent.xml java.io.FileNotFoundException: /webMethods/wm105/IntegrationServer/instances/default/config/fabric-agent.xml (No such file or directory) - Looks like there is a file missing
    #-rw-r–r–. 1 azhad azhad 860 Jul 11 2019 modules.cnf
    -rw-r–r–. 1 azhad azhad 2498 Jul 11 2019 is_jaas.cnf
    -rw-r–r–. 1 azhad azhad 962 Jul 11 2019 configPassman.cnf
    drwxr-xr-x. 4 azhad azhad 32 Jun 27 03:23 TCDB
    drwxr-xr-x. 5 azhad azhad 88 Jun 27 03:23 wss
    drwxr-xr-x. 2 azhad azhad 23 Jun 27 03:23 dsp
    drwxr-xr-x. 2 azhad azhad 34 Jun 27 03:23 healthindicators
    drwxr-xr-x. 2 azhad azhad 30 Jun 27 03:23 locking
    drwxr-xr-x. 3 azhad azhad 24 Jun 27 03:23 dynamicvariables
    drwxr-xr-x. 2 azhad azhad 4096 Jun 27 03:23 policy
    drwxr-xr-x. 2 azhad azhad 26 Jun 27 03:23 feature
    drwxr-xr-x. 2 azhad azhad 187 Jun 27 03:24 Caching
    -rw-r–r–. 1 azhad azhad 73 Jun 27 04:43 ISMSvcExcptFilter.cnf
    -rw-r–r–. 1 azhad azhad 8852 Jun 27 04:43 ISMJournalLogFilter.cnf
    -rw-r–r–. 1 azhad azhad 1739 Jun 27 04:57 passman.cnf
    -rw-r–r–. 1 azhad azhad 2587 Jun 27 04:57 empw.dat
    drwxr-xr-x. 7 azhad azhad 81 Jun 27 04:57 jdbc
    drwxr-xr-x. 2 azhad azhad 26 Jun 27 04:57 microservices
    -rw-r–r–. 1 azhad azhad 1788 Jun 27 04:57 repository4.cnf
    -rw-r–r–. 1 azhad azhad 0 Jun 27 04:57 globalVariables.cnf
    drwxr-xr-x. 2 azhad azhad 21 Jun 27 04:57 jwt
    -rw-r–r–. 1 azhad azhad 221 Jun 27 04:57 cluster.node.properties.bak
    drwxr-xr-x. 2 azhad azhad 168 Jun 27 04:57 lwq
    -rw-r–r–. 1 azhad azhad 3086 Jun 27 05:00 messaging.cnf
    -rw-r–r–. 1 azhad azhad 3085 Jun 27 05:01 XARecoveryStore.cnf
    -rw-r–r–. 1 azhad azhad 0 Jun 27 05:01 passwordExpirationSettings.cnf
    -rw-r–r–. 1 azhad azhad 0 Jun 27 05:01 reliableMessaging.cnf
    drwxr-xr-x. 2 azhad azhad 4096 Jun 27 05:01 endpoints
    -rw-r–r–. 1 azhad azhad 566 Jun 27 05:02 remote.cnf
    -rw-r–r–. 1 azhad azhad 73 Jun 27 05:02 registry.cnf
    -rw-r–r–. 1 azhad azhad 73 Jun 27 05:02 proxy.cnf
    drwxr-xr-x. 2 azhad azhad 81 Jun 27 05:02 auditing
    drwxr-xr-x. 2 azhad azhad 29 Jun 27 05:02 integrationlive
    drwxr-xr-x. 10 azhad azhad 175 Jun 27 05:02 security
    drwxr-xr-x. 22 azhad azhad 4096 Jun 27 05:02 backup
    -rw-r–r–. 1 azhad azhad 5604 Jun 27 09:21 jms.cnf
    -rw-r–r–. 1 azhad azhad 1830 Jun 27 22:16 licenseKey.xml
    drwxr-xr-x. 4 azhad azhad 92 Jun 28 21:56 sftp
    -rw-r–r–. 1 azhad azhad 8222 Jun 28 21:56 users.cnf
    -rw-r–r–. 1 azhad azhad 218 Jun 28 21:56 invokemanager.cnf
    -rw-r–r–. 1 azhad azhad 441 Jun 28 21:56 parsing.cnf
    -rw-r–r–. 1 azhad azhad 8658 Jun 28 21:56 dispatch.cnf
    -rw-r–r–. 1 azhad azhad 3282 Jun 28 21:56 eventcfg.bin
    -rw-r–r–. 1 azhad azhad 1344 Jun 28 21:57 WORK-txnPassStore.dat
    -rw-r–r–. 1 azhad azhad 1344 Jun 28 21:57 txnPassStore.dat
    -rw-r–r–. 1 azhad azhad 26281 Jun 28 21:57 server.cnf
    drwxr-xr-x. 2 azhad azhad 54 Jun 28 22:28 jndi
    -rw-r–r–. 1 azhad azhad 6570 Jun 28 22:48 acls.cnf
    -rw-r–r–. 1 azhad azhad 15886 Jun 28 22:48 aclmap_sm.cnf
    -rw-r–r–. 1 azhad azhad 7311 Jun 28 22:48 acllist.cnf
    -rw-r–r–. 1 azhad azhad 5237 Jun 28 22:48 aclread.cnf
    -rw-r–r–. 1 azhad azhad 4451 Jun 28 22:48 aclwrite.cnf
    drwxr-xr-x. 2 azhad azhad 6 Jun 28 22:48 work

  • There are some UM related errors as well. - topic/dca_event_response does not exist in Universal Messaging Realm. #—> may I create a topic “dca_event_response” with this name…?
    at com.webmethods.optimize.jndiUtil.NirvanaJMSConfig.initTopics(NirvanaJMSConfig.java:195)
  • You can also confirm if the memory requirements are met in the VM for running IS and the OS is supported. #memoray configurations—> 6GB/RAM and 80 GB Storage with 2 dual core

On taking a second look, While you may have a installation with some missing files, the major delay seems to be between the JCE and the FIPS steps -14 minutes , point 1 from earlier post. It would be helpful to check if there are trace logs in the Initialization facility 25 mentioned earlier.
Also I noticed that Fedora is not on the standard Operating Systems that the product is certified against.
10.5 Requirements , while it may work very well, it is not certified.
I would suggest you to try with another OS if you have

For the fabric agent xml you can check if the installation logs for any errors. <install_dir>/install/logs/ installLog.txt, although this is not majorly delaying the startup .
I do not have much idea about the UM related error , will wait for any other responses.

-NP

Hi,

in addition to Nagendras answers:

when you do not require connectivity from IS to Optimize you can disable the WmOptimize package, this would avoid the optimize related messages about missing UM artifacts.

Usually there is no need to create the Optimize-related artifcats in UM manually, this should be done when the starting the Optimize AnalyticsEngine and WS-DataCollector for the first time after they were configured & deployed via Environment Definition in MWS.

Regards,
Holger

1 Like