My Oracle Support Banner

Port Issue With A Domain Created Using A Template (Doc ID 2259941.1)

Last updated on NOVEMBER 03, 2017

Applies to:

Oracle WebLogic Server - Version 10.3.6 and later
Information in this document applies to any platform.


Customer built an OSB domain using a template. Changed all the port numbers since the new domain is built on the same hardware.  The source domain managed server's port# is 8011 and new domain's port number was changed to 8015. This new domain has been running fine without any issues for almost a year.

A simple Java POC was deployed to this new environment and the URL validated. Surprisingly it the source domain port# 8011 instead of 8015.
After that WSDL on all applications running on new domain showed the same incorrect entry.

<port name="insertRecordPort" binding="tns:insertRecordPortBinding"><soap:address location="http://<hostname>:8011/javaApplications-testLoadBalancer-context-root/insertRecordPort"/></port>

But the application is running successfully.  Somewhere within the new instance, it contains the 8011 as a hard-coded value.

How to find the location where this is hard coded to correct this error?




To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!

In this Document

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.