This content has been marked as final. Show 4 replies
Did you find the resolution for this issue?
if not you need to configure a frontend host (this is used for httpclusterserrvlet) which act as loadbalancer among you managed servers.
I'm receiving the same error while trying to invoke a web service, running on a separate website, via a web service control created in BEA workshop.
Do I still need configure a frontEndHost ? Thanks
created wlw-runtime-config-xml with host name and port # for managed server.
This "front end host" -problem can occur not only if the server cluster is lacking the front end parameters, but also if the client side is lacking them, if the web service client is deployed in a WebLogic cluster and created as a ServiceControl by using BEA's framework. This should be quite common - say, you have a WebLogic cluster containing SOA-like services, and other WebLogic clusters which use those services.
The reason is that web service client control components seem to always have SOAP callbacks enabled by default, even if the conversation is not asynchronous. When the service control (that is, the web service client) is calling the web service, the control framework writes the client's callback address to the SOAP header. If the framework can't find the client's callback address, the "front end host" -exception is thrown.
The front end host address and port should be defined in the client side in the similar way than in the server side, by following BEA's support pattern "Resolving RuntimeExceptions Generated while Deploying a Workshop Application to a Cluster" - e.g. by defining the cluster's front end host parameters.
Edited by jspaalan at 05/27/2008 3:06 AM
Edited by jspaalan at 05/27/2008 3:08 AM