IS URL not working (10.7)

, ,
1

Unable to access the IS URL in browser, it was working fine but all of sudden getting below error. Appreciate if someone could take a look and advise.

2021-09-14 05:57:09 PDT [ISS.0028.0012I] (tid=74) WmISExtDC: Startup service (com.wm.isextdc.PkgInit:init)
2021-09-14 05:57:09 PDT [ISS.0028.0012I] (tid=74) WmAgileAppsDeployer: Startup service (com.softwareag.agileapps.deployer.Util:startup)
2021-09-14 05:57:09 PDT [ISS.0028.0012I] (tid=74) WmCDS: Startup service (wm.cds.services_java:init)
2021-09-14 05:57:09 PDT [ISS.0030.0012E] (tid=746) ERROR: The Admin API routing file contains a duplicate. Both wm.cds.rest.services.PrincipalUpdateRest.generateUserSharedSecret and wm.cds.rest.services.PrincipalLookupRest.searchUserDirectoryPageless have a method of POST and logically identical URLs.
2021-09-14 05:57:09 PDT [ISS.0028.0012I] (tid=74) WmOptimize: Startup service (wm.optimize.admin:startup)
2021-09-14 05:57:09 PDT [OPT.0001.0001I] (tid=746) Initialising Mapi interface
2021-09-14 05:57:10 PDT [OPT.0001.0001E] (tid=746) Error while creating connection.
Root cause: java.lang.RuntimeException: java.lang.RuntimeException: java.lang.RuntimeException: JMS Provider admin objects initialization error!
at com.webMethods.common.mapi.jms.ConnectionUtil.(ConnectionUtil.java:49)
at com.webMethods.common.mapi.jms.MapiCommunicator.(MapiCommunicator.java:98)
at com.webMethods.optimize.management.Mapi.init(Mapi.java:222)
at com.webMethods.optimize.management.Mapi.(Mapi.java:87)
at pub.optimize.monitoring.createNewConnection(monitoring.java:667)
at pub.optimize.monitoring.createDefaultBrokerConnection(monitoring.java:1396)
at wm.optimize.admin.createDefaultBrokerConnection(admin.java:198)
at wm.optimize.admin.startup(admin.java:217)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at com.wm.app.b2b.server.JavaService.baseInvoke(JavaService.java:404)
at com.wm.app.b2b.server.invoke.InvokeManager.process(InvokeManager.java:759)
at com.wm.app.b2b.server.util.tspace.ReservationProcessor.process(ReservationProcessor.java:39)
at com.wm.app.b2b.server.invoke.StatisticsProcessor.process(StatisticsProcessor.java:53)
at com.wm.app.b2b.server.invoke.ServiceCompletionImpl.process(ServiceCompletionImpl.java:243)
at com.wm.app.b2b.server.invoke.ValidateProcessor.process(ValidateProcessor.java:49)
at com.wm.app.b2b.server.invoke.PipelineProcessor.process(PipelineProcessor.java:171)
at com.wm.app.b2b.server.ACLManager.process(ACLManager.java:339)
at com.wm.app.b2b.server.invoke.DispatchProcessor.process(DispatchProcessor.java:33)
at com.wm.app.b2b.server.AuditLogManager.process(AuditLogManager.java:394)
at com.wm.app.b2b.server.invoke.InvokeManager.invoke(InvokeManager.java:629)
at com.wm.app.b2b.server.invoke.InvokeManager.invoke(InvokeManager.java:434)
at com.wm.app.b2b.server.invoke.InvokeManager.invoke(InvokeManager.java:392)
at com.wm.app.b2b.server.ServiceManager.invoke(ServiceManager.java:260)
at com.wm.app.b2b.server.ServiceManager.invoke(ServiceManager.java:116)
at com.wm.app.b2b.server.ServiceManager.invoke(ServiceManager.java:75)
at com.wm.app.b2b.server.SessionInvoke.run(SessionInvoke.java:30)
at com.wm.util.pool.PooledThread.run(PooledThread.java:127)
at java.lang.Thread.run(Thread.java:748)
Caused by: java.lang.RuntimeException: java.lang.RuntimeException: JMS Provider admin objects initialization error!
at com.webMethods.optimize.jndiUtil.JMSJNDIUtil.initializeForClient(JMSJNDIUtil.java:127)
at com.webMethods.common.mapi.jms.ConnectionUtil.(ConnectionUtil.java:45)
… 30 more
Caused by: java.lang.RuntimeException: JMS Provider admin objects initialization error!
at com.webMethods.optimize.jndiUtil.NirvanaJMSConfig.refresh(NirvanaJMSConfig.java:441)
at com.webMethods.optimize.jndiUtil.JMSConfigFactory.refresh(JMSConfigFactory.java:63)
at com.webMethods.optimize.jndiUtil.JMSJNDIUtil.initializeForClient(JMSJNDIUtil.java:124)
… 31 more
Caused by: java.lang.RuntimeException: topic/dca_event_response does not exist in Universal Messaging Realm.
at com.webMethods.optimize.jndiUtil.NirvanaJMSConfig.initTopics(NirvanaJMSConfig.java:197)
at com.webMethods.optimize.jndiUtil.NirvanaJMSConfig.refresh(NirvanaJMSConfig.java:437)
… 33 more

2021-09-14 05:57:10 PDT [ISS.0028.0013E] (tid=74) Startup service exited with the following error: com.wm.app.b2b.server.ServiceException: java.lang.RuntimeException: java.lang.RuntimeException: java.lang.RuntimeException: JMS Provider admin objects initialization error!
2021-09-14 05:57:10 PDT [ISS.0028.0012I] (tid=74) WmDeployer: Startup service (wm.deployer.Util:startup)
2021-09-14 05:57:10 PDT [ISS.0028.0012I] (tid=74) WmDeployer: Startup service (wm.deployer.Util:verifyPlugins)
2021-09-14 05:57:10 PDT [ISS.0028.0012I] (tid=74) WmFlatFile: Startup service (wm.server.ff:init)
2021-09-14 05:57:10 PDT [ISS.0028.0012I] (tid=74) WmFlatFile: Startup service (wm.server.ff:setACLs)
2021-09-14 05:57:10 PDT [ISS.0028.0012I] (tid=74) WmART: Startup service (wm.art.admin:startup)
2021-09-14 05:57:10 PDT [ISS.0028.0012I] (tid=74) WmAdmin: Startup service (wm.admin.controller:init)
2021-09-14 05:57:10 PDT [ISS.0028.0012I] (tid=74) WmDB: Startup service (wm.server.db:startup)
2021-09-14 05:57:10 PDT [ISS.0028.0012I] (tid=74) WmCloud: Startup service (wm.client.integrationlive.admin:createDefaultILiveTrustStoreAlias)
2021-09-14 05:57:10 PDT [ISS.0028.0012I] (tid=74) WmCloud: Startup service (wm.client.integrationlive.admin:loadTenantAccountInfo)
2021-09-14 05:57:10 PDT [ISS.0021.6005I] (tid=746) webMethods Cloud information was not loaded because the settings are not specified.
2021-09-14 05:57:10 PDT [ISS.0028.0012I] (tid=74) WmCloud: Startup service (wm.client.integrationlive.connector:initConnectors)
2021-09-14 05:57:10 PDT [ISS.0028.0012I] (tid=74) WmDocumentumAdapter: Startup service (wm.wmDocumentumAdapter.admin:startUp)
2021-09-14 05:57:10 PDT [ART.0114.1100I] (tid=746) Adapter Runtime: Facility 7070 - WmDocumentumAdapter registered with bundle com.wm.adapter.wmDocumentumAdapter.WmDocumentumAdapterResourceBundle.
2021-09-14 05:57:10 PDT [ADA.7070.0100I] (tid=746) Documentum Adapter initialized
2021-09-14 05:57:10 PDT [ADA.7070.0100I] (tid=746) Documentum Adapter initialized
2021-09-14 05:57:10 PDT [ISS.0028.0012I] (tid=74) WmSharePointAdapter: Startup service (wm.wmSharePointAdapter.admin:startUp)
2021-09-14 05:57:10 PDT [ART.0114.1100I] (tid=746) Adapter Runtime: Facility 7072 - WmSharePointAdapter registered with bundle com.wm.adapter.wmSharePointAdapter.WmSharePointAdapterResourceBundle.
2021-09-14 05:57:10 PDT [ISS.0028.0012I] (tid=74) WmARTExtDC: Startup service (com.wm.artextdc.pkginit:init)
2021-09-14 05:57:10 PDT [ISS.0028.0012I] (tid=74) WmJDBCAdapter: Startup service (wm.adapter.wmjdbc.admin:registerAdapter)

2

Take a look at Holger’s response here (link) and see if it applies to you.
Do you use Optimize? And if yes, have you set it up to communicate to the messaging layer?

KM

1 Like
3

Hi Mugada,

Could you please guide on how to set it up? for someone reason IS service shows running but unable to access the IS URL in browser.

4

The nitty-gritties depend on the Optimize license you have (i.e., Optimize for Infrastructure, B2B, etc.). Take at look at this documentation which provides you detailed steps (link) on setting it up.

KM

5

Could you please elaborate on what you mean by IS service shows running, do you mean that IS is up and is available at the primary port and you have issues accessing it from the browser? In that case you can try an alternative client like designer/ postman to connect and see if that works. The port that IS is up on should be mentioned in the server log.

-NP

1 Like
6

Hi Ishwar,

can you check the mentioned file (most likely under WmCDS/config folder or under central config folder of IS):

This sounds more related to me for IS not completing the startup sequence than the incorrect messaging configuration for Optimize.

Last line in the server log after IS has finished starting up should read “Config directory saved.”

Regards,
Holger

1 Like
7

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.