BPEL issue cannot resolve address

[jbarranza]

Hi all,
i face an issue with a Bpel process. I call a servlet edit by OTM and i put the full address of OTM server in Bpel link partner as follow

service name="GLogService">
<port name="HTTPPost" binding="tns:HTTPPost">
<http:address location="http://xxxxxx.com/GC3/glog.integration.servlet.WMServlet"/>
<!--<http:address location="http://otm-connor-gc3-55-wl.us.oracle.com/GC3/glog.integration.servlet.WMServlet"/>-->
</port>
</service>


when the process start it cannots get an answer with OTM and give back the following dns error

http://xxxxxxx.comhttp//xxxxxxx.com/GC3/glog.integration.servlet.WMServlet

the server name is substitute with the name it self in a strange way.
Someone could help me?

[chrisplough]

Re: BPEL issue cannot resolve address

Hello,

This is indeed a strange error, as the FQDN (fully-qualified domain name) appears to be duplicating itself. Is this partner link being defined directly in the BPEL flow or via the GLog WSDL file?

More detail would definitely help, as I don't see an issue with the configuration that you posted.

Thanks,
Chris

[jbarranza]

Re: BPEL issue cannot resolve address

Hi Chris,
thanks for your answer. To help you better understand the issue i can say you that the lines that i show you, are in GLogXML.wsdl file.
Please keep in mind that the system is configured to avoid forward the http request to proxy for internal domain like in this case.

Let me know if you need of any further infos.

Regards,
Matteo

[chrisplough]

Re: BPEL issue cannot resolve address

Matteo,

Thanks for the information. Unfortunately, this doesn't give me enough to offer any great suggestions.

Your configuration looks correct and I'm not aware of any other configuration issues with BPEL that could cause this.

Some additional thoughts:

• Are any other BPEL processes configured -- meaning does this happen for every BPEL process or just a singular one (helps to rule out server-wide configuration issues.
• Can you ensure that the encoding of the GLogXML.wsdl file is correct and that there aren't any hidden or control characters causing an issue.
• Is there any more information present in the BPEL log files to help troubleshoot?

Thanks,
Chris