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

Analytic Engine Failed - could not bind to path : monitor.ws

webMethods Community Member

webMethods Community MemberTue May 06, 2008 04:38 PM

  • 1.  Analytic Engine Failed - could not bind to path : monitor.ws

    Posted Thu January 10, 2008 08:45 AM

    Hi,

    *** Product :
    Optimize 7.1.1

    *** Problem :
    After the startup of Analytic, Prediction, Data Collector and My webMethods Server, I connect me to MWS to configure Analytic Engine (Administration > My webMethods > System Setting).

    When I check the server status, this is failed.

    In MWS log, I have the error :

    MET (webservice : WARN) [RID:42] - could not bind to path: http://xxx:xxxx/services/monitor.wsdl
    org.xml.sax.SAXParseException: Premature end of file.
    MET (wsclient : FATAL) [RID:42] - com.webMethods.caf.wsclient.proxy.impl.WSClientDynamicProxy: Failed to bind to endPoint: http://xxxx:xxxx/services/monitor.wsdl and interface: interface com.webMethods.bpo.service.IBaseWebService: could not bind to path: http://xxxx:xxxx/services/monitor.wsdl
    com.webMethods.caf.wsclient.WSClientException: Failed to bind to endPoint: http://xxxx:xxxx/services/monitor.wsdl and interface: interface com.webMethods.bpo.service.IBaseWebService: could not bind to path: http://xxxx:xxxx/services/monitor.wsdl

    So I can’t acces to Administration > Analytics. I have the message :

    Error executing search. Have a System Administrator verify the Analytic Engine settings at Administration → My webMethods → System Settings.

    The parameter is correct (I think).
    The Analytic Engine, Data Collection Services, Prediction Engine are on-line (Administration > System-Wide > System Information).

    Regards,
    Isabelle


    #webMethods
    #webMethods-BPMS
    #BPM


  • 2.  RE: Analytic Engine Failed - could not bind to path : monitor.ws

    Posted Fri January 11, 2008 02:32 AM

    Note :
    After a periode of time of 2 hours, the Analytic Engine Server connexion is OK.

    How it’s possible to


    #webMethods
    #webMethods-BPMS
    #BPM


  • 3.  RE: Analytic Engine Failed - could not bind to path : monitor.ws

    Posted Tue April 15, 2008 07:03 AM

    The fix OPTPROC_7-1_Fix3.zip resolves this problem


    #webMethods
    #webMethods-BPMS
    #BPM


  • 4.  RE: Analytic Engine Failed - could not bind to path : monitor.ws

    Posted Wed April 16, 2008 07:20 AM

    hi,

    I faced the same problem.

    I tried the OPTPROC_7-1_Fix4.zip which supercedes OPTPROC_7-1_Fix3.zip.
    However the problem still remains.

    Something am I missing.

    Regards,
    Sumit


    #BPM
    #webMethods
    #webMethods-BPMS


  • 5.  RE: Analytic Engine Failed - could not bind to path : monitor.ws

    Posted Wed April 16, 2008 07:23 AM

    Hi,

    I missed one part, restarted all servers and it worked fine.

    Sorry for the confusion.

    Regards,
    Sumit


    #webMethods
    #webMethods-BPMS
    #BPM


  • 6.  RE: Analytic Engine Failed - could not bind to path : monitor.ws

    Posted Thu April 17, 2008 09:59 AM

    Hi Sumit

    we are facing the same issue,I couldn’t find the fixes in advantage.

    Are they downloadable or we need to request wM

    Thanks

    Bhanu


    #webMethods
    #webMethods-BPMS
    #BPM


  • 7.  RE: Analytic Engine Failed - could not bind to path : monitor.ws

    Posted Thu April 17, 2008 10:28 AM

    Are you running multiple AE? If so, make sure they are using the unique cluster port under Configure servers tab (System-wide > Environments > Define Environments) even if they are not setup as a cluster.


    #webMethods
    #webMethods-BPMS
    #BPM


  • 8.  RE: Analytic Engine Failed - could not bind to path : monitor.ws

    Posted Tue May 06, 2008 04:38 PM


  • 9.  RE: Analytic Engine Failed - could not bind to path : monitor.ws

    Posted Tue May 13, 2008 02:23 AM

    It is downlodable from advantage.
    Link : Download Fixes → webMethods Optimize for Process


    #webMethods-BPMS
    #BPM
    #webMethods


  • 10.  RE: Analytic Engine Failed - could not bind to path : monitor.ws

    Posted Wed December 24, 2014 01:03 PM

    Hello,

    Has anyone found any solution on this ? Even we are facing similar issue.

    Here we have MWS in clusture ( say server machine A and B) and Analytic Engine is installed on one of them ( only on server machine A and not on machine B ).

    I am able to see connectivity to Analytical Engine Host from MWS A properly (System Setting > Servers). But unable to se connectivity from MWS B.

    I also tried hitting url : http://serverA:12503/services/monitor.wsdl from both machines. ( Analytical Engine is on machine A only)

    I am able to see wsdl from machine A, but nothing is fetched when the same url is hit from machine B.

    Any solutions to this issue ?

    Thanks in advance !


    #BPM
    #webMethods
    #webMethods-BPMS


  • 11.  RE: Analytic Engine Failed - could not bind to path : monitor.ws

    Posted Wed December 24, 2014 01:06 PM

    Hello,

    Has anyone found any solution on this ? Even we are facing similar issue.

    Here we have MWS running in clusture ( say server machine A and B) and Analytic Engine is installed on one of them ( only on server machine A and not on machine B ).

    I am able to see connectivity to Analytical Engine Host from MWS A properly (System Setting > Servers). But unable to se connectivity from MWS B.

    I also tried hitting url : http://serverA:12503/services/monitor.wsdl from both machines. ( Analytical Engine is on machine A only)

    I am able to see wsdl from machine A, but nothing is fetched when the same url is hit from machine B.

    Any solutions to this issue ?

    Product: 8.2

    Thanks in advance !


    #webMethods-BPMS
    #BPM
    #webMethods


  • 12.  RE: Analytic Engine Failed - could not bind to path : monitor.ws

    Posted Thu December 25, 2014 04:58 AM

    Hi Hitesh,

    If you are getting unable to bind path to xx.wsdl, probably you didn’t add required server components as part of environment settings, like I stated in other post, kindly shared the needed snapshots to suggest you to overcome this issue.

    Thanks,


    #webMethods
    #webMethods-BPMS
    #BPM


  • 13.  RE: Analytic Engine Failed - could not bind to path : monitor.ws

    Posted Mon December 29, 2014 03:15 AM

    Please find below environment configuration:

    SERVER - A:

    1. MWS
    2. Optimize Engine

    SERVER - B:

    1. MWS

    Let me know if you need more information.

    Thanks for the help.

    Regards,
    Hitesh



    #webMethods-BPMS
    #webMethods
    #BPM


  • 14.  RE: Analytic Engine Failed - could not bind to path : monitor.ws

    Posted Mon January 05, 2015 01:05 PM

    Can you share a screenshot from your environment config (TAB “Define Hosts” & TAB “Map Servers”)?

    Are the 2 MWS clustered (sharing the same mws-database schema)?
    Can you try a telnet from second MWS to the specified port?

    Maybe this will help us to find the cause.

    Regards,
    Holger


    #webMethods
    #webMethods-BPMS
    #BPM