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.


#TechXchangePresenter
 View Only
Expand all | Collapse all

Unable to startup MWS 9.6

  • 1.  Unable to startup MWS 9.6

    Posted Thu July 17, 2014 04:01 PM

    Hi
    I’m was doing a fresh install on windows 2012 server but had to uninstall MWS as we were not going to use enbedded database. I cleaned the MWS from services and all reference to it. Now when I try to start it up the following messages are in the wrapper log but the MWS says it has started:
    2014/07/17 17:50:08 | Launching a JVM…
    INFO | jvm 1 | 2014/07/17 17:50:08 | WrapperManager: Initializing…
    INFO | jvm 1 | 2014/07/17 17:50:09 | Debug options:
    INFO | jvm 1 | 2014/07/17 17:50:09 | file:/E:/SoftwareAG/common/bin/.options loaded
    INFO | jvm 1 | 2014/07/17 17:50:09 | Registering Software AG Platform Hooks …
    INFO | jvm 1 | 2014/07/17 17:50:10 | Jul 17, 2014 5:50:10 PM com.softwareag.platform.console.internal.LocalConsoleManager open
    INFO | jvm 1 | 2014/07/17 17:50:10 | INFO: Local JLine console disabled: JVM not attached to a text terminal.
    INFO | jvm 1 | 2014/07/17 17:50:10 | Jul 17, 2014 5:50:10 PM com.softwareag.platform.shutdown.internal.Activator start
    INFO | jvm 1 | 2014/07/17 17:50:10 | INFO: Shutdown port listener disabled: Required property “com.softwareag.platform.shutdown.port” is not set or empty.
    INFO | jvm 1 | 2014/07/17 17:50:10 | Jul 17, 2014 5:50:10 PM com.softwareag.platform.startup.internal.Activator$1 addingService
    INFO | jvm 1 | 2014/07/17 17:50:10 | INFO: Discovered location: osgi.user.area=file:/C:/user/
    INFO | jvm 1 | 2014/07/17 17:50:10 | Jul 17, 2014 5:50:10 PM com.softwareag.platform.startup.internal.Activator$1 addingService
    INFO | jvm 1 | 2014/07/17 17:50:10 | INFO: Discovered location: osgi.instance.area=file:/E:/SoftwareAG/profiles/MWS_default/workspace/
    INFO | jvm 1 | 2014/07/17 17:50:10 | Jul 17, 2014 5:50:10 PM com.softwareag.platform.startup.internal.Activator$1 addingService
    INFO | jvm 1 | 2014/07/17 17:50:10 | INFO: Discovered location: osgi.configuration.area=file:/E:/SoftwareAG/profiles/MWS_default/configuration/
    INFO | jvm 1 | 2014/07/17 17:50:10 | Jul 17, 2014 5:50:10 PM com.softwareag.platform.startup.internal.Activator$1 addingService
    INFO | jvm 1 | 2014/07/17 17:50:10 | INFO: Discovered location: osgi.install.area=file:/E:/SoftwareAG/profiles/MWS_default/
    INFO | jvm 1 | 2014/07/17 17:50:10 | Jul 17, 2014 5:50:10 PM com.softwareag.platform.startup.internal.Activator$1 addingService
    INFO | jvm 1 | 2014/07/17 17:50:10 | INFO: Discovered location: eclipse.home.location=file:/E:/SoftwareAG/profiles/MWS_default/
    INFO | jvm 1 | 2014/07/17 17:50:10 | Jul 17, 2014 5:50:10 PM com.softwareag.platform.startup.internal.Activator replaceSystemPropertyLocations
    INFO | jvm 1 | 2014/07/17 17:50:10 | INFO: Replacing system property @url.java.security.auth.login.config->@osgi.configuration.area:jaas.config with java.security.auth.login.config->file:/E:/SoftwareAG/profiles/MWS_default/configuration/jaas.config
    INFO | jvm 1 | 2014/07/17 17:50:10 | Jul 17, 2014 5:50:10 PM com.softwareag.platform.startup.internal.Activator replaceSystemPropertyLocations
    INFO | jvm 1 | 2014/07/17 17:50:10 | INFO: Replacing system property @url.sag.install.area->@osgi.install.area:…/… with sag.install.area->file:/E:/SoftwareAG/
    INFO | jvm 1 | 2014/07/17 17:50:10 | Jul 17, 2014 5:50:10 PM com.softwareag.platform.startup.internal.Activator$1 addingService
    INFO | jvm 1 | 2014/07/17 17:50:10 | INFO: Discovered location: sag.install.area=file:/E:/SoftwareAG/
    INFO | jvm 1 | 2014/07/17 17:50:10 | Jul 17, 2014 5:50:10 PM com.softwareag.platform.startup.internal.LocationRegistry open
    INFO | jvm 1 | 2014/07/17 17:50:10 | INFO: Registered location sag.install.area=file:/E:/SoftwareAG/
    INFO | jvm 1 | 2014/07/17 17:50:11 | Jul 17, 2014 5:50:11 PM com.softwareag.platform.logging.init.internal.Activator start
    INFO | jvm 1 | 2014/07/17 17:50:11 | INFO: Setting configuration directory to E:\SoftwareAG\profiles\MWS_default/configuration
    INFO | jvm 1 | 2014/07/17 17:50:11 | Jul 17, 2014 5:50:11 PM com.webMethods.sc.config.ConfigurationLogger log
    INFO | jvm 1 | 2014/07/17 17:50:11 | INFO: Out-of-band file changes will be monitored every ‘60000’ milliseconds
    INFO | jvm 1 | 2014/07/17 17:50:11 | log4j:WARN Unrecognized element threshold
    INFO | jvm 1 | 2014/07/17 17:50:11 | Jul 17, 2014 5:50:11 PM com.webMethods.sc.config.ConfigurationLogger log
    INFO | jvm 1 | 2014/07/17 17:50:11 | INFO: Out-of-band file changes will be monitored every ‘60000’ milliseconds
    INFO | jvm 1 | 2014/07/17 17:50:18 | [p2] Thu Jul 17 17:50:17 GMT 2014 - [Start Level Event Dispatcher] [reconciler] User requested forced reconciliation via “osgi.checkConfiguration=true” System property.
    INFO | jvm 1 | 2014/07/17 17:50:18 | [p2] Thu Jul 17 17:50:17 GMT 2014 - [Start Level Event Dispatcher] [reconciler] Performing reconciliation.
    INFO | jvm 1 | 2014/07/17 17:50:19 | [p2] Thu Jul 17 17:50:19 GMT 2014 - [Start Level Event Dispatcher] [reconciler] User requested forced reconciliation via “osgi.checkConfiguration=true” System property.
    INFO | jvm 1 | 2014/07/17 17:50:19 | [p2] Thu Jul 17 17:50:19 GMT 2014 - [Start Level Event Dispatcher] [reconciler] Performing reconciliation.
    INFO | jvm 1 | 2014/07/17 17:50:20 | [p2] Thu Jul 17 17:50:19 GMT 2014 - [Start Level Event Dispatcher] [reconciler] Nothing to do.
    INFO | jvm 1 | 2014/07/17 17:50:20 | [p2] Thu Jul 17 17:50:19 GMT 2014 - [Start Level Event Dispatcher] [reconciler] Writing out timestamps to file : E:\SoftwareAG\profiles\MWS_default\configuration\org.eclipse.osgi\bundles\132\data\cache.timestamps
    INFO | jvm 1 | 2014/07/17 17:50:20 | [p2] Thu Jul 17 17:50:19 GMT 2014 - [Start Level Event Dispatcher] [reconciler] E:\SoftwareAG\profiles\MWS_default\dropins=1405613251513
    INFO | jvm 1 | 2014/07/17 17:50:20 | [p2] Thu Jul 17 17:50:19 GMT 2014 - [Start Level Event Dispatcher] [reconciler] E:\SoftwareAG\profiles\MWS_default\links=0
    INFO | jvm 1 | 2014/07/17 17:50:20 | [p2] Thu Jul 17 17:50:19 GMT 2014 - [Start Level Event Dispatcher] [reconciler] E:\SoftwareAG\profiles\MWS_default\configuration\org.eclipse.update\platform.xml=0
    INFO | jvm 1 | 2014/07/17 17:50:20 | [p2] Thu Jul 17 17:50:19 GMT 2014 - [Start Level Event Dispatcher] [reconciler] E:\SoftwareAG\profiles\MWS_default\plugins=0
    INFO | jvm 1 | 2014/07/17 17:50:20 | [p2] Thu Jul 17 17:50:19 GMT 2014 - [Start Level Event Dispatcher] [reconciler] E:\SoftwareAG\profiles\MWS_default\features=0
    INFO | jvm 1 | 2014/07/17 17:51:12 | Jul 17, 2014 5:51:12 PM com.webMethods.sc.config.ConfigurationLogger log
    INFO | jvm 1 | 2014/07/17 17:51:12 | WARNING: Failed to process OOB file-change event on file ‘E:\SoftwareAG\profiles\MWS_default\configuration\org.eclipse.core.runtime.manager.tmp1007087602713076760.instance’
    INFO | jvm 1 | 2014/07/17 17:51:12 | Jul 17, 2014 5:51:12 PM com.webMethods.sc.config.ConfigurationLogger log
    INFO | jvm 1 | 2014/07/17 17:51:12 | WARNING: Failed to process OOB file-change event on file ‘E:\SoftwareAG\profiles\MWS_default\configuration\org.eclipse.equinox.app.manager.tmp352680381487535818.instance’
    Any ides out there?


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


  • 2.  RE: Unable to startup MWS 9.6

    Posted Fri July 18, 2014 07:31 AM

    not the best of approaches, but you can try uninstalling again and delete all MWS related folders before installing again.


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


  • 3.  RE: Unable to startup MWS 9.6

    Posted Fri July 18, 2014 07:37 AM

    I decided to uninstall all the webMethosd 9.6 products and then install them again. See how that goes.
    Thanks


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


  • 4.  RE: Unable to startup MWS 9.6

    Posted Fri July 18, 2014 08:43 AM

    Hi Maria ,

    You were able to install MWS and start successfully?


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


  • 5.  RE: Unable to startup MWS 9.6

    Posted Fri July 18, 2014 09:04 AM

    No now I get these errors in the MWS log
    2014-07-18 10:55:04 GMT (Framework:FATAL) - [POP.004.0201] Cannot initialize MWS, invalid database schema is specified
    java.sql.SQLSyntaxErrorException: [SoftwareAG][Oracle JDBC Driver][Oracle]ORA-00942: table or view does not exist

    at com.wm.dd.jdbc.oraclebase.ddcr.b(Unknown Source)
    at com.wm.dd.jdbc.oraclebase.ddcr.a(Unknown Source)
    at com.wm.dd.jdbc.oraclebase.ddcq.b(Unknown Source)
    at com.wm.dd.jdbc.oraclebase.ddcq.a(Unknown Source)
    at com.wm.dd.jdbc.oracle.ddal.a(Unknown Source)
    at com.wm.dd.jdbc.oracle.ddal.a(Unknown Source)
    at com.wm.dd.jdbc.oracle.ddam.r(Unknown Source)
    at com.wm.dd.jdbc.oraclebase.dde3.w(Unknown Source)
    at com.wm.dd.jdbc.oraclebase.dde3.v(Unknown Source)
    at com.wm.dd.jdbc.oraclebase.dde3.executeQuery(Unknown Source)
    at com.webmethods.portal.service.sql.core.BaseSqlWorker.executeQuery(BaseSqlWorker.java:536)
    at com.webmethods.portal.service.sql.core.ConnectionManager.validateDatasource(ConnectionManager.java:713)
    at com.webmethods.portal.service.sql.core.ConnectionManager.init(ConnectionManager.java:291)
    at com.webmethods.portal.service.sql.core.ConnectionManager.init(ConnectionManager.java:214)
    at com.webmethods.portal.system.init.impl.ClusterPhaseProvider.initializeDatabaseConfigLocator(ClusterPhaseProvider.java:98)
    at com.webmethods.portal.system.init.impl.PartitionPhaseProvider.initializePhases(PartitionPhaseProvider.java:30)
    at com.webmethods.portal.system.PortalSystem.init(PortalSystem.java:920)
    at com.webmethods.portal.system.PortalSystem.main(PortalSystem.java:856)
    at com.webmethods.portal.system.PortalSystemActivator$1.call(PortalSystemActivator.java:56)
    at com.webmethods.portal.system.PortalSystemActivator$1.call(PortalSystemActivator.java:53)
    at java.util.concurrent.FutureTask.run(FutureTask.java:262)
    at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
    at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
    at java.lang.Thread.run(Thread.java:744)
    

    2014-07-18 10:55:09 GMT (org.eclipse.gemini.blueprint.service.importer.support.AbstractOsgiServiceImportFactoryBean:WARN) - OSGi importer [consumers] definition contains no interfaces: all invocations will be executed on the proxy and not on the backing service
    2014-07-18 10:55:16 GMT (com.softwareag.security.idp.saml.SamlManagedService:ERROR) - osgi.configuration.area was not set/found.
    2014-07-18 10:55:19 GMT (Osgi.Platform.Logger:ERROR) - [com.softwareag.wsstack.osgi.axis2:9.6.0.0000-0237 (144)] FrameworkEvent ERROR
    2014-07-18 10:55:22 GMT (Osgi.Platform.Logger:ERROR) - [com.softwareag.wsstack.osgi.axis2:9.6.0.0000-0237 (144)] FrameworkEvent ERROR
    2014-07-18 10:55:22 GMT (Osgi.Platform.Logger:ERROR) - [org.eclipse.equinox.cm:1.0.400.v20130327-1442 (269)] Failed to create bean jmxConnector
    2014-07-18 10:55:23 GMT (Osgi.Platform.Logger:ERROR) - [com.webMethods.caf.server:9.6.0.0000-0164 (183)] FrameworkEvent ERROR


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


  • 6.  RE: Unable to startup MWS 9.6

    Posted Fri July 18, 2014 09:27 AM

    During your installation steps what is the JDBC driver url you provided? Kindly share the screen shot…

    Check if MWS database schema was correctly created by dbConfigurator tool. You might need to drop and re-create MWS schema.


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


  • 7.  RE: Unable to startup MWS 9.6

    Posted Tue January 13, 2015 05:38 AM

    Hi Maria,

    Did the installation of the MWS 9.6 work in the end?

    We are doing a fresh install of MWS 9.7 on windows server 2012, 64 bits (similar setup as the one you mentioned above) and we are facing the same issues with the MWS wrapper.

    On top of that we have seen the following error in the sag-osgi.log file:
    " [com.softwareag.security.idp.saml.SamlManagedService] 2015-01-13 09:28:51,300 ERROR: osgi.configuration.area was not set/found."

    Thanks!
    Ana


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


  • 8.  RE: Unable to startup MWS 9.6

    Posted Tue January 13, 2015 05:50 AM

    Can you share your MWS logs or errors. Lets see what is the issue here.


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


  • 9.  RE: Unable to startup MWS 9.6

    Posted Tue January 13, 2015 07:59 AM

    Hi Ana & Maria,

    After installing the MWS properly, did you install/create MWS DB tables with help of DB component configurator tool. If you have done, then kindly check any issue in the provided DB URL in configuration.

    Thanks,


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


  • 10.  RE: Unable to startup MWS 9.6

    Posted Wed January 14, 2015 05:25 AM

    Hi All,

    Thank you for your quick replies.

    We have solved the issue, the root cause is unclear though, but we do suspect that some things made a difference:

    1. when first installing MWS - due to insufficient rights the execution failed, however, we continued with installation on top of the initial one which ran partially
    2. afterwards I uninstalled MWS and re-tried installing, however, the same errors popped up. Based on the logs, I suspected that uninstall of MWS, did not remove all the files, but some " traces" were left: probably in the /common folder.
    3. with these in mind: I uninstalled the complete webMethods 9.7 installation and tried the install from scratch. This time, as per the recommendation from Software AG (from the ticket raised with them), I followed a different approach on the MWS migration:

    1.- Create a new DB for MWS 9.7 (this will be later not used or deleted)
    2.- Install MWS 9.7 with default instance.
    3.- Start MWS 97 default instance and check if it runs correctly
    3.- Stop the MWS 9.7
    4.- Delete the MWS default instance with

    mws.bat -s default delete
    5.- Check that there is nothing left in profiles/MWS…
    6.- Upgrade MWS 9.5 DB to MWS 9.7
    7.- Migrate default instance.

    NOTE:

    • Keep in mind that we had a dedicated MWS database for the MWS Server.
    • When running the DB Migration, I used the command line tool instead of the GUI as the first time (in the Upgrade guide, it is mentioned to you the command line, however, there’s nowhere written that using the GUI instead of the command line will lead to issues, but… better safe than sorry.)

    Lessons learned: MWS installation can be quite tedious in case some errors pop up during the initial install. If something goes wrong, you pretty much have to uninstall everything and not MWS component only or make sure you check that the uninstall removed all the files related to MWS old installation and not traces were left (I checked profiles and the default instance folder but it seems it was not enough), otherwise, you will get even more errors.

    Thanks,
    Ana


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


  • 11.  RE: Unable to startup MWS 9.6

    Posted Wed January 14, 2015 06:22 AM

    Good to hear your issue is been resolved and thanks for sharing the points which you observed.

    Thanks,


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


  • 12.  RE: Unable to startup MWS 9.6

    Posted Wed January 14, 2015 06:38 AM

    Please unistall the server , delete the foljavascript:void(0);der manuaaly after uninstall and then ReInstall


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


  • 13.  RE: Unable to startup MWS 9.6

    Posted Wed January 14, 2015 01:34 PM

    @Sankalp,

    What did you mean by delete the foljavascript:void(0); can you please provide more details on this.


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


  • 14.  RE: Unable to startup MWS 9.6

    Posted Thu January 15, 2015 01:55 PM

    I think that “delete the foljavascript:void(0);der” should have been “delete the folder”.


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


  • 15.  RE: Unable to startup MWS 9.6

    Posted Fri January 16, 2015 01:21 AM

    Ya it is :lol: I am not sure it might be a typo error.


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


  • 16.  RE: Unable to startup MWS 9.6

    Posted Mon January 19, 2015 10:30 AM

    Can you please be more specific regarding the folder you are referring to?

    Removing the visible traces of the MWS installation did not help (the MWS folder from SoftwareAG installation folder and the MWS_default folder from profiles).

    The problem I had when posting here was solved as I mentioned above, but your reply might be useful for someone else.

    Thanks,
    Ana


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