oracle/docker-images

weblogic uses the external mapped port inside the container when 7201:7001 docker port mapping is used

Open

#1,860 创建于 2021年2月12日

在 GitHub 查看
 (10 评论) (0 反应) (1 负责人)Shell (6,139 star) (5,379 fork)batch import
help wantedweblogic

描述

Hello, I am starting two WebLogic 12.2.1.4 domains in docker from my docker-compose.yml file. So I am starting 4 containers:

  • admin-server-A + managed-server-A1
  • admin-server-B + managed-server-B1

The following Docker port mapping is used:

  • admin-server-A: 7101:7001
  • managed-server-A1: 8101:8001
  • admin-server-B: 7201:7001
  • managed-server-B1: 8201:8001

Everything works fine, except this:

<Feb 12, 2021 5:11:21,002 PM UTC> <Notice> <JMX> <BEA-149535> <JMX Resiliency Activity Server=All Servers : Resolving connection list DomainRuntimeServiceMBean> 
javax.ws.rs.ProcessingException: java.net.ConnectException: Tried all: '1' addresses, but could not connect over HTTP to server: 'localhost', port: '7201'
failed reasons:
 [0] address:'localhost/127.0.0.1',port:'7201' : java.net.ConnectException: Connection refused

The 2nd WL admin server tries to use port 7201 in the container but actually, it is listening on the default 7001 port inside the container. Port 7201 is used from the host machine, and of course, WL is not listening on 7201 inside the container.

Why WL sees and wanna use the host port, instead of use the default 7001?

贡献者指南

技术栈
dockerjava
领域
infrastructuredevops
议题类型
bug
难度面向新贡献者的预计实现难度，1 表示很小改动，5 表示专家级工作。
4
预计时间有经验贡献者完成调查、实现、测试并准备 pull request 的粗略时间范围。
half day
活动状态议题当前的可参与程度：新鲜、活跃、陈旧、阻塞或等待维护者输入。
stale
清晰度议题是否清楚说明期望改动、验收标准和下一步。
needs investigation
前置要求
Docker networking basicsWebLogic domain configuration
新手友好度1-100 的估计分数，表示该议题对首次贡献者的友好程度。
25
研究方向
Investigate how WebLogic determines its listen address within the container. Check the Dockerfiles and domain creation scripts in the oracle/docker images repository to see if the listen address is hardcoded or derived from environment variables. Look for any existing environment variables like ADMIN PORT or HOSTNAME that might be used. Also review the JMX resolution logic that causes the admin server to use the external mapped port instead of the container's internal port. The issue likely requires modifying the Dockerfile or startup script to ensure the server binds to the correct internal port.