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

isabelle.janin.24129 · January 10, 2008, 1:45pm

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

isabelle.janin.24129 · January 11, 2008, 7:32am

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

How it’s possible to

isabelle.janin.24129 · April 15, 2008, 11:03am

The fix OPTPROC_7-1_Fix3.zip resolves this problem

smk · April 16, 2008, 11:20am

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

smk · April 16, 2008, 11:23am

Hi,

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

Sorry for the confusion.

Regards,
Sumit

c-bvallakv.760874 · April 17, 2008, 1:59pm

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

c-nasir.naqvi.252223 · April 17, 2008, 2:28pm

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.

sjain.497510 · May 6, 2008, 8:38pm

1

smk · May 13, 2008, 6:23am

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

HItesh_Tambe2 · December 24, 2014, 6:03pm

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 !

HItesh_Tambe2 · December 24, 2014, 6:06pm

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 !

MR_as173d · December 25, 2014, 9:58am

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,

HItesh_Tambe2 · December 29, 2014, 8:15am

Please find below environment configuration:

SERVER - A:

MWS
Optimize Engine

SERVER - B:

MWS

Let me know if you need more information.

Thanks for the help.

Regards,
Hitesh

Holger_von_Thomsen · January 5, 2015, 6:04pm

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