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
  • 1.  After host migration, MWS is not coming up

    Posted Thu October 26, 2023 06:34 AM

    Hi Experts,

    Consider migration is happened from platinum host to palladium host.
    I have created a tar and placed in the palladium, generated a cert and placed, updated in all the necessary configs.
    But the MWS is not coming up.
    Attached the logs, can someone please assist.

    wrapper | Base configuration file is /ngs/app/b2bhrp/apps/wm1015_b2bhr_mws/profiles/MWS_default/configuration/wrapper.conf
    wrapper | Found #include file in /ngs/app/b2bhrp/apps/wm1015_b2bhr_mws/profiles/MWS_default/configuration/wrapper.conf: /ngs/app/b2bhrp/apps/wm1015_b2bhr_mws/MWS/bin/wrapper-license.conf
    wrapper | Reading included configuration file, /ngs/app/b2bhrp/apps/wm1015_b2bhr_mws/MWS/bin/wrapper-license.conf
    wrapper | Found #include file in /ngs/app/b2bhrp/apps/wm1015_b2bhr_mws/profiles/MWS_default/configuration/wrapper.conf: %OSGI_INSTALL_AREA%/configuration/custom_wrapper.conf
    wrapper | After environment variable replacements: /ngs/app/b2bhrp/apps/wm1015_b2bhr_mws/profiles/MWS_default/configuration/custom_wrapper.conf
    wrapper | Reading included configuration file, /ngs/app/b2bhrp/apps/wm1015_b2bhr_mws/profiles/MWS_default/configuration/custom_wrapper.conf
    wrapper | The ‘SHUTDOWN_TIMEOUT’ environment variable was referenced but has not been defined.
    wrapper | Encountered an invalid numerical value for configuration property wrapper.shutdown.timeout=%SHUTDOWN_TIMEOUT%. Resolving to 30.
    wrapper | → Wrapper Started as Console
    wrapper | Java Service Wrapper Standard Edition 64-bit 3.5.50
    wrapper | Copyright (C) 1999-2022 Tanuki Software, Ltd. All Rights Reserved.
    wrapper | http://wrapper.tanukisoftware.com
    wrapper | Licensed to Software AG for Software AG My webMethods Server
    wrapper |
    wrapper | Launching a JVM…
    jvm 1 | Listening for transport dt_socket at address: 10033
    wrapper | Startup failed: Timed out waiting for a signal from the JVM.
    wrapper | JVM did not exit on request, termination requested.
    wrapper | JVM received a signal SIGKILL (9).
    wrapper | JVM process is gone.
    wrapper | JVM exited after being requested to terminate.
    wrapper | Launching a JVM…
    jvm 2 | Listening for transport dt_socket at address: 10033
    wrapper | Startup failed: Timed out waiting for a signal from the JVM.
    wrapper | JVM did not exit on request, termination requested.
    wrapper | JVM received a signal SIGKILL (9).
    wrapper | JVM process is gone.
    wrapper | JVM exited after being requested to terminate.
    wrapper | Launching a JVM…
    jvm 3 | Listening for transport dt_socket at address: 10033
    wrapper | Startup failed: Timed out waiting for a signal from the JVM.
    wrapper | JVM did not exit on request, termination requested.
    wrapper | JVM received a signal SIGKILL (9).
    wrapper | JVM process is gone.
    wrapper | JVM exited after being requested to terminate.
    wrapper | Launching a JVM…
    jvm 4 | Listening for transport dt_socket at address: 10033
    ^Cwrapper | INT trapped. Shutting down.
    ^Cwrapper | INT trapped. Forcing immediate shutdown.
    wrapper | JVM did not exit on request, termination requested.
    wrapper | JVM received a signal SIGKILL (9).
    wrapper | JVM process is gone.
    wrapper | JVM exited after being requested to terminate.
    wrapper | ← Wrapper Stopped

    error_log.txt (170.5 KB)
    full_log.txt (163.5 KB)
    problem_log.txt (53.3 KB)


    #MWS-CAF-Task-Engine
    #webMethods-cloud
    #Integration-Server-and-ESB
    #webMethods
    #webMethods-io-Integration
    #Adapters-and-E-Standards


  • 2.  RE: After host migration, MWS is not coming up



  • 3.  RE: After host migration, MWS is not coming up

    Posted Thu October 26, 2023 08:28 AM

    I can see in the logs:
    2023-10-26 03:02:00 PDT (c.w.p.s.c.i.ClusterProvider:ERROR) [Start Level: Equinox Container: 8d201942-cffe-4f9e-a4b7-26fe470fc046] - Address already in use (Bind failed)
    com.webMethods.portal.system.init.InitializationException: Address already in use (Bind failed)
    at com.webMethods.portal.system.cluster.impl.ClusterProvider.isPortAvailable(ClusterProvider.java:543) ~[com.webMethods.caf.server_10.15.0.0001-0218.jar:10.15.0.0001-0218]
    at com.webMethods.portal.system.cluster.impl.ClusterProvider.init(ClusterProvider.java:439) ~[com.webMethods.caf.server_10.15.0.0001-0218.jar:10.15.0.0001-0218]
    at com.webMethods.portal.system.impl.BaseProvider.activate(BaseProvider.java:144) [com.webMethods.caf.server_10.15.0.0001-0218.jar:10.15.0.0001-0218]
    at com.webMethods.portal.system.cluster.impl.ClusterProvider.activate(ClusterProvider.java:220) [com.webMethods.caf.server_10.15.0.0001-0218.jar:10.15.0.0001-0218]
    at jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[?:?]
    at jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) ~[?:?]
    at jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[?:?]
    at java.lang.reflect.Method.invoke(Method.java:566) ~[?:?]


    #Integration-Server-and-ESB
    #MWS-CAF-Task-Engine
    #webMethods-cloud
    #webMethods
    #webMethods-io-Integration
    #Adapters-and-E-Standards


  • 4.  RE: After host migration, MWS is not coming up

    Posted Wed November 01, 2023 12:26 AM