IBM webMethods Hybrid Integration

IBM webMethods Hybrid Integration

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

“Realm is currently not reachable” repeats in log after upgrading

  • 1.  “Realm is currently not reachable” repeats in log after upgrading

    Posted Fri January 13, 2017 10:49 AM

    Hi experts,
    I’m facing a problem, when I start up IS or MWS, “Realm is currently not reachable” always repeats in log screen, I have installed all fix of 9.8 version.

    IS log:
    jvm 1 | [Fri Jan 13 21:39:01 CST 2017],Failed to connect to Realm on attempt
    1 - nSessionAttributes:conns=1/[nsp://localhost:9000/] - com.pcbsys.nirvana.clie
    nt.nRealmUnreachableException: Realm is currently not reachable:com.pcbsys.found
    ation.base.fException: Retry count=1 exceeded attempting to connect to host - [n
    sp://localhost:9000/]

    MWS log:
    jvm 2 | [Fri Jan 13 22:44:48 CST 2017],Session 162 has been created with URL
    list: nSessionAttributes:conns=1/[nsp://localhost:9000/]
    jvm 2 | [Fri Jan 13 22:44:50 CST 2017],Failed to connect to Realm on attempt
    1 - nSessionAttributes:conns=1/[nsp://localhost:9000/] - com.pcbsys.nirvana.clie
    nt.nRealmUnreachableException: Realm is currently not reachable:com.pcbsys.found
    ation.base.fException: Retry count=1 exceeded attempting to connect to host - [n
    sp://localhost:9000/]

    the version of webMethods is 9.8, and I have installed all fix of this version.
    thanks in advance.


    #webMethods-Upgrade
    #Integration-Server-and-ESB
    #webMethods-General
    #webMethods


  • 2.  RE: “Realm is currently not reachable” repeats in log after upgrading

    Posted Sat January 14, 2017 04:57 AM

    When you start IS it tries to connect to UM server, check if you UM server running on nsp://localhost:9000/] is up and running.

    If it is running on a different IP and port you must change it on IS>> Messaging.


    #webMethods-General
    #Integration-Server-and-ESB
    #webMethods-Upgrade
    #webMethods


  • 3.  RE: “Realm is currently not reachable” repeats in log after upgrading

    Posted Sat January 14, 2017 09:38 AM

    hi,
    how to check the UM server is running?or how to start the UM server?does it start up automatically with windows?


    #webMethods
    #webMethods-General
    #Integration-Server-and-ESB
    #webMethods-Upgrade


  • 4.  RE: “Realm is currently not reachable” repeats in log after upgrading

    Posted Sat January 14, 2017 10:23 AM

    Hi,

    You can check entries in run => services.msc.
    If it is running you will see it with that status.

    Try running nserver manually that will prompt UM startup log. And you will see when it is up and running.


    #webMethods-General
    #Integration-Server-and-ESB
    #webMethods
    #webMethods-Upgrade


  • 5.  RE: “Realm is currently not reachable” repeats in log after upgrading

    Posted Sat January 14, 2017 10:38 AM

    Hi Bari,
    these are all services about Software AG, are they OK?
    they are all running.
    QQ20170114223554.jpg


    #Integration-Server-and-ESB
    #webMethods
    #webMethods-Upgrade
    #webMethods-General


  • 6.  RE: “Realm is currently not reachable” repeats in log after upgrading

    Posted Sat January 14, 2017 10:44 AM

    Hi

    Yes these are SAG services but non states UM.
    You can try running the service manually from file system.


    #webMethods-Upgrade
    #webMethods-General
    #webMethods
    #Integration-Server-and-ESB


  • 7.  RE: “Realm is currently not reachable” repeats in log after upgrading

    Posted Sat January 14, 2017 10:52 AM

    hi bari,
    thanks for your reply, I am a newbie for webMethods, and could you tell me how to run the um server, or how to stop IS to connect the um server, actually, I dont use um.
    thanks a lot.


    #webMethods
    #webMethods-General
    #Integration-Server-and-ESB
    #webMethods-Upgrade


  • 8.  RE: “Realm is currently not reachable” repeats in log after upgrading

    Posted Sat January 14, 2017 03:41 PM

    If you are not using you may disable the UM connection on IS so that the error does not show up on IS repeatedly.


    #Integration-Server-and-ESB
    #webMethods-Upgrade
    #webMethods-General
    #webMethods


  • 9.  RE: “Realm is currently not reachable” repeats in log after upgrading

    Posted Sun January 15, 2017 09:32 AM

    Hi M@he$h,
    I’m sorry for my late response, in Settings > Messaging > webMethods Messaging Settings, the UM server ‘Enabled’ is ‘No’ by default. I never changed it, It’s weird. the um server is inactive, but IS and MWS always try to connect to umserver.
    MWS20170115213158.jpg
    IS20170115213210.png


    #webMethods-General
    #Integration-Server-and-ESB
    #webMethods
    #webMethods-Upgrade


  • 10.  RE: “Realm is currently not reachable” repeats in log after upgrading

    Posted Sun January 15, 2017 09:51 AM

    Hi,
    even though I delete the config of UM in Message Config, IS and MWS still try connecting to the um server.

    jvm 1 | [Sun Jan 15 21:47:42 CST 2017],Session 8 has been created with URL li
    st: nSessionAttributes:conns=1/[nsp://localhost:9000/]
    jvm 1 | [Sun Jan 15 21:47:42 CST 2017],Failed to connect to Realm on attempt
    1 - nSessionAttributes:conns=1/[nsp://localhost:9000/] - com.pcbsys.nirvana.clie
    nt.nRealmUnreachableException: Realm is currently not reachable:com.pcbsys.found
    ation.base.fException: Retry count=1 exceeded attempting to connect to host - [n
    sp://localhost:9000/]


    #webMethods-General
    #webMethods
    #webMethods-Upgrade
    #Integration-Server-and-ESB


  • 11.  RE: “Realm is currently not reachable” repeats in log after upgrading

    Posted Sun January 15, 2017 10:03 AM

    [327]2017-01-15 21:48:23 CST [ISS.0028.0013E] Startup service exited with the following error: com.wm.app.b2b.server.ServiceException: java.lang.RuntimeException: java.lang.RuntimeException: javax.naming.CommunicationException: JNDI setup failed on RNAME=nsp://localhost:9000 [Root exception is com.pcbsys.nirvana.client.nRealmUnreachableException: Realm is currently not reachable:Realm was still unreachable after max retry count - nSessionAttributes:conns=1/[nsp://localhost:9000/]]
    [326]
    [325] … 42 more
    [324] at com.pcbsys.nirvana.client.nSession.actualInit(nSession.java:6221)
    [323] at com.pcbsys.nirvana.client.nSession.connect(nSession.java:7338)
    [322] at com.pcbsys.nirvana.client.nSession.establishConnection(nSession.java:7504)
    [321]Caused by: com.pcbsys.nirvana.client.nRealmUnreachableException: Realm is currently not reachable:com.pcbsys.foundation.base.fException: Retry count=1 exceeded attempting to connect to host - [nsp://localhost:9000/]
    [320] … 38 more
    [319] at com.pcbsys.nirvana.nSpace.NirvanaContext.(NirvanaContext.java:127)
    [318] at com.pcbsys.nirvana.client.nSession.init(nSession.java:6121)
    [317] at com.pcbsys.nirvana.client.nSession.init(nSession.java:6137)
    [316] at com.pcbsys.nirvana.client.nSession.init(nSession.java:6190)
    [315] at com.pcbsys.nirvana.client.nSession.actualInit(nSession.java:6242)
    [314]Caused by: com.pcbsys.nirvana.client.nRealmUnreachableException: Realm is currently not reachable:Realm was still unreachable after max retry count - nSessionAttributes:conns=1/[nsp://localhost:9000/]
    [313] … 30 more
    [312] at com.webMethods.optimize.jndiUtil.JMSJNDIUtil.(JMSJNDIUtil.java:61)
    [311] at javax.naming.InitialContext.(InitialContext.java:216)
    [310] at javax.naming.InitialContext.init(InitialContext.java:244)
    [309] at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:313)
    [308] at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:684)
    [307] at com.pcbsys.nirvana.nSpace.NirvanaContextFactory.getInitialContext(NirvanaContextFactory.java:35)
    [306] at com.pcbsys.nirvana.nSpace.NirvanaContextFactory.getContext(NirvanaContextFactory.java:53)
    [305] at com.pcbsys.nirvana.nSpace.NirvanaContext.(NirvanaContext.java:74)
    [304] at com.pcbsys.nirvana.nSpace.NirvanaContext.(NirvanaContext.java:144)
    [303]Caused by: javax.naming.CommunicationException: JNDI setup failed on RNAME=nsp://localhost:9000 [Root exception is com.pcbsys.nirvana.client.nRealmUnreachableException: Realm is currently not reachable:Realm was still unreachable after max retry count - nSessionAttributes:conns=1/[nsp://localhost:9000/]]
    [302] … 29 more
    [301] at com.webMethods.common.mapi.jms.ConnectionUtil.(ConnectionUtil.java:44)
    [300] at com.webMethods.optimize.jndiUtil.JMSJNDIUtil.(JMSJNDIUtil.java:64)
    [299]Caused by: java.lang.RuntimeException: javax.naming.CommunicationException: JNDI setup failed on RNAME=nsp://localhost:9000 [Root exception is com.pcbsys.nirvana.client.nRealmUnreachableException: Realm is currently not reachable:Realm was still unreachable after max retry count - nSessionAttributes:conns=1/[nsp://localhost:9000/]]
    [298] at java.lang.Thread.run(Thread.java:745)
    [297] at com.wm.util.pool.PooledThread.run(PooledThread.java:127)
    [296] at com.wm.app.b2b.server.SessionInvoke.run(SessionInvoke.java:33)
    [295] at com.wm.app.b2b.server.ServiceManager.invoke(ServiceManager.java:79)
    [294] at com.wm.app.b2b.server.ServiceManager.invoke(ServiceManager.java:107)
    [293] at com.wm.app.b2b.server.ServiceManager.invoke(ServiceManager.java:238)
    [292] at com.wm.app.b2b.server.invoke.InvokeManager.invoke(InvokeManager.java:386)
    [291] at com.wm.app.b2b.server.invoke.InvokeManager.invoke(InvokeManager.java:549)
    [290] at com.wm.app.b2b.server.AuditLogManager.process(AuditLogManager.java:370)
    [289] at com.wm.app.b2b.server.invoke.DispatchProcessor.process(DispatchProcessor.java:34)
    [288] at com.wm.app.b2b.server.ACLManager.process(ACLManager.java:303)
    [287] at com.wm.app.b2b.server.invoke.PipelineProcessor.process(PipelineProcessor.java:171)
    [286] at com.wm.app.b2b.server.invoke.ValidateProcessor.process(ValidateProcessor.java:49)
    [285] at com.wm.app.b2b.server.invoke.ServiceCompletionImpl.process(ServiceCompletionImpl.java:243)
    [284] at com.wm.app.b2b.server.invoke.StatisticsProcessor.process(StatisticsProcessor.java:49)
    [283] at com.wm.app.b2b.server.util.tspace.ReservationProcessor.process(ReservationProcessor.java:39)
    [282] at com.wm.app.b2b.server.invoke.InvokeManager.process(InvokeManager.java:650)
    [281] at com.wm.app.b2b.server.JavaService.baseInvoke(JavaService.java:441)
    [280] at java.lang.reflect.Method.invoke(Method.java:498)
    [279] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
    [278] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
    [277] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    [276] at wm.optimize.admin.startup(admin.java:218)
    [275] at wm.optimize.admin.createDefaultBrokerConnection(admin.java:200)
    [274] at pub.optimize.monitoring.createDefaultBrokerConnection(monitoring.java:1480)
    [273] at pub.optimize.monitoring.createNewConnection(monitoring.java:715)
    [272] at com.webMethods.optimize.management.Mapi.(Mapi.java:73)
    [271] at com.webMethods.optimize.management.Mapi.init(Mapi.java:159)
    [270] at com.webMethods.common.mapi.jms.MapiCommunicator.(MapiCommunicator.java:99)
    [269] at com.webMethods.common.mapi.jms.ConnectionUtil.(ConnectionUtil.java:49)
    [268]Root cause: java.lang.RuntimeException: java.lang.RuntimeException: javax.naming.CommunicationException: JNDI setup failed on RNAME=nsp://localhost:9000 [Root exception is com.pcbsys.nirvana.client.nRealmUnreachableException: Realm is currently not reachable:Realm was still unreachable after max retry count - nSessionAttributes:conns=1/[nsp://localhost:9000/]]
    [267]2017-01-15 21:48:23 CST [OPT.0001.0001E] Error while creating connection.
    [266]2017-01-15 21:48:20 CST [ISS.0028.0012I] WmOptimize: Startup service (wm.optimize.admin:startup)
    [265]2017-01-15 21:48:20 CST [ISS.0028.0012I] WmNUMDeployer: Startup service (com.softwareag.deployer.num.java.Util:startup)
    [264]2017-01-15 21:48:20 CST [RUL.0010.0100I] RESFacade initialized with basePath: [C:\SoftwareAG\IntegrationServer\instances\default\packages\WmBusinessRules\projects]
    [263]2017-01-15 21:48:20 CST [RUL.0005.1033I] wM Business Rules Auditing into Universal Messaging feature is turned off.
    [262]2017-01-15 21:48:20 CST [RUL.0005.1031I] wM Business Rules Auditing into Database feature is turned off.
    [261]2017-01-15 21:48:20 CST [RUL.0050.0300I] Successfully registered server with id: 172.18.8.35:5555
    [260]2017-01-15 21:48:20 CST [RUL.0050.0203I] Checking license expiration unlimited …
    [259]2017-01-15 21:48:20 CST [RUL.0050.0205I] Checking license product version …
    [258]2017-01-15 21:48:20 CST [RUL.0050.0204I] Checking license product code …
    [257]2017-01-15 21:48:20 CST [RUL.0050.0202I] Checking license signature …
    [256]2017-01-15 21:48:20 CST [RUL.0050.0201I] Starting to validate license file…
    [255]2017-01-15 21:48:20 CST [RUL.0050.0200I] License file is expected at: C:\SoftwareAG\IntegrationServer\instances\default\packages\WmBusinessRules\config\licenseKey.xml
    [254]2017-01-15 21:48:20 CST [ISS.0028.0012I] WmBusinessRules: Startup service (wm.businessrules.admin:startup)
    [253]2017-01-15 21:48:19 CST [BPM.0101.1600W] Unable to get Optimize process data collector. Tracking enabled models will not be logged to Optimize.
    [252]2017-01-15 21:48:19 CST [ISS.0028.0012I] WmPRT: Startup service (wm.prt.admin:startup)
    [251]2017-01-15 21:48:18 CST [MON.0119.0707I] addMwUsertoMonitorACL: MonitorAdministrators
    [250]2017-01-15 21:48:18 CST [MON.0119.0707I] addMwUsertoMonitorACL: MonitorUsers
    [249]2017-01-15 21:48:18 CST [MON.0119.0707I] addMwUsertoMonitorACL: MonitorUsers
    [248]2017-01-15 21:48:18 CST [MON.0119.0706I] Setting ACLs with CDS roles
    [247]2017-01-15 21:48:18 CST [MON.0119.0704I] CDS User Manager running
    [246]2017-01-15 21:48:18 CST [MON.0119.0707I] addMwUsertoMonitorACL: true
    [245]2017-01-15 21:48:18 CST [ISS.0028.0012I] WmMonitor: Startup service (wm.monitor.admin:startup)
    [244]2017-01-15 21:48:18 CST [ISS.0028.0012I] WmLogUtil: Startup service (wm.loggingUtility:start)
    [243]2017-01-15 21:48:18 CST [ISS.0028.0012I] WmXSLT: Startup service (wm.xslt.Admin:startup)
    [242]2017-01-15 21:48:18 CST [ISS.0028.0012I] WmPublic: Startup service (pub.storage:startup)
    [241]2017-01-15 21:48:18 CST [ISS.0028.0012I] WmRoot: Startup service (wm.server.sftpclient:updateKexList)
    [240]2017-01-15 21:48:18 CST [ISS.0028.0012I] WmRoot: Startup service (wm.server.kerberossettings:init)
    [239]2017-01-15 21:48:18 CST [ISS.0028.0012I] WmRoot: Startup service (wm.server.ntlmclient:init)
    [238]2017-01-15 21:48:18 CST [ISS.0028.0012I] WmRoot: Startup service (wm.server.security.keystore:createDefaultKeyStoreTrustStoreAliases)
    [237]2017-01-15 21:48:18 CST [ISS.0028.0012I] WmRoot: Startup service (wm.server.oauth:init)
    [236]2017-01-15 21:48:18 CST [ISS.0028.0012I] WmRoot: Startup service (wm.server.ws:init)
    [235]2017-01-15 21:48:18 CST [ISS.0028.0012I] WmRoot: Startup service (wm.server.tspace:init)
    [234]2017-01-15 21:48:18 CST [ISS.0028.0012I] WmRoot: Startup service (wm.server.soap:init)
    [233]2017-01-15 21:48:17 CST [ISC.0063.0011I] Start


    #webMethods-General
    #Integration-Server-and-ESB
    #webMethods-Upgrade
    #webMethods


  • 12.  RE: “Realm is currently not reachable” repeats in log after upgrading

    Posted Mon January 16, 2017 02:54 AM

    Hi Felix,

    It seems you have installed Command Central on your machine.

    Please start up Command central service from the list of services and open the link.
    https://Host IP:8091/

    Configure the server to which you want to monitor.

    From here you can start and stop the UM instance.

    Regards,
    Syed Faraz Ahmed


    #webMethods-Upgrade
    #webMethods
    #Integration-Server-and-ESB
    #webMethods-General


  • 13.  RE: “Realm is currently not reachable” repeats in log after upgrading

    Posted Mon January 16, 2017 07:52 AM

    Hi Felix,

    Have u installed both IS and UM are in separate machine/same machine?

    Thanks,
    Krish


    #webMethods-Upgrade
    #webMethods
    #Integration-Server-and-ESB
    #webMethods-General


  • 14.  RE: “Realm is currently not reachable” repeats in log after upgrading

    Posted Tue January 17, 2017 08:36 PM

    Hi Krishna,
    I didn’t install UM, and I don’t use UM, I use Broker insted of UM.
    thanks for your reply.


    #webMethods-General
    #webMethods-Upgrade
    #webMethods
    #Integration-Server-and-ESB


  • 15.  RE: “Realm is currently not reachable” repeats in log after upgrading



  • 16.  RE: “Realm is currently not reachable” repeats in log after upgrading

    Posted Tue January 17, 2017 09:02 PM

    Hello All,
    I have download universalmessaging_9.9.77666_windows_vm from http://terracotta.org/products/universal-messaging, however, It is Free Trial version with 88 days, I want to know how to import terracotta-license.key, Our company have this license.
    thanks.


    #webMethods-Upgrade
    #webMethods-General
    #Integration-Server-and-ESB
    #webMethods


  • 17.  RE: “Realm is currently not reachable” repeats in log after upgrading

    Posted Fri March 10, 2017 07:12 AM