Skip to content

Why it's never starting? #288

@ericrf

Description

@ericrf

I'm trying to start a websphere traditional for testing/debugging purposes
For that i've created a docker compose file to start my WAS but it never get started

here is my docker compose file

version: "3.9"
services:
  was:
    image: ibmcom/websphere-traditional:8.5.5.21
    environment:
      - ENABLE_BASIC_LOGGING=true
    ports:
      - 9043:9043
      - 9443:9443
    volumes:
      - ./PASSWORD:/tmp/PASSWORD
    deploy:
      resources:
        limits:
          cpus: "8"
          memory: 8000M
        reservations:
          cpus: "8"
          memory: 4000M

here is the log

#  docker-compose --compatibility up
[+] Running 1/0
 ⠿ Container was-was-1  Recreated                                                                                                                                                                       0.0s
Attaching to was-was-1
was-was-1  | Configure logging mode
was-was-1  | WASX7357I: By request, this scripting client is not connected to any server process. Certain configuration and application operations will be available in local mode.
was-was-1  | WASX7357I: By request, this scripting client is not connected to any server process. Certain configuration and application operations will be available in local mode.
was-was-1  | WASX7303I: The following options are passed to the scripting environment and are available as arguments that are stored in the argv variable: "[/work/config-ibm/webContainer.props]"
was-was-1  | HPEL is enabled
was-was-1  | Starting logViewer ................
was-was-1  | Starting server ...................
was-was-1  | ADMU0116I: Tool information is being logged in file
was-was-1  |            /opt/IBM/WebSphere/AppServer/profiles/AppSrv01/logs/server1/startServer.log
was-was-1  | ADMU0128I: Starting tool with the AppSrv01 profile
was-was-1  | ADMU3100I: Reading configuration for server: server1
was-was-1  | Time: [0x64248b31], Process: [248], Thread: [0x5f2a6700]: Error during WaitForExecOutcome. result=[0] errno=[2]
was-was-1  | Time: [0x64248b31], Process: [248], Thread: [0x5f2a6700]: Error during WaitForExecOutcome. result=[0] errno=[2]
was-was-1  | Time: [0x64248b31], Process: [248], Thread: [0x5f2a6700]: Creation failure, spawn was unsuccessful.  Therefore deallocating process structure at: [0x5957e7e0]
was-was-1  | Time: [0x64248b31], Process: [248], Thread: [0x5f2a6700]: Creation failure, spawn was unsuccessful.  Therefore deallocating process structure at: [0x5957e7e0]
was-was-1  | ADMU0111E: Program exiting with error:
was-was-1  |            com.ibm.ws.process.exception.CreateProcessTimeoutException:
was-was-1  |            PROC0031E: The process creation failed.  The process creation for
was-was-1  |            program [/opt/IBM/WebSphere/AppServer/java/8.0/bin/java] with
was-was-1  |            priority [20] timed out.  This can occur if the system activity is
was-was-1  |            too high for a process to be created within a specific time limit of
was-was-1  |            two minutes.
was-was-1  | ADMU1211I: To obtain a full trace of the failure, use the -trace option.
was-was-1  | ADMU0211I: Error details may be seen in the file:
was-was-1  |            /opt/IBM/WebSphere/AppServer/profiles/AppSrv01/logs/server1/startServer.log
was-was-1 exited with code 255
# tail -f /opt/IBM/WebSphere/AppServer/profiles/AppSrv01/logs/server1/startServer.log
Classpath = /opt/IBM/WebSphere/AppServer/profiles/AppSrv01/properties:/opt/IBM/WebSphere/AppServer/properties:/opt/IBM/WebSphere/AppServer/lib/startup.jar:/opt/IBM/WebSphere/AppServer/lib/bootstrap.jar:/opt/IBM/WebSphere/AppServer/lib/lmproxy.jar:/opt/IBM/WebSphere/AppServer/lib/urlprotocols.jar:/opt/IBM/WebSphere/AppServer/java/lib/tools.jar
Java Library path = /opt/IBM/WebSphere/AppServer/java/jre/lib/amd64/compressedrefs:/opt/IBM/WebSphere/AppServer/java/jre/lib/amd64:/opt/IBM/WebSphere/AppServer/lib/native/linux/x86_64/:/opt/IBM/WebSphere/AppServer/bin:/opt/IBM/WebSphere/AppServer/nulldllsdir:/usr/lib64:/usr/lib
Orb Version = IBM Java ORB build orbdev-userlvl-20200106.1711
Max file descriptor count = 1073741816
Current trace specification = *=info
************* End Display Current Environment *************
[3/30/23 14:30:09:423 UTC] 00000001 ManagerAdmin  I   TRAS0017I: The startup trace state is *=info.
[3/30/23 14:30:09:490 UTC] 00000001 AdminTool     A   ADMU0128I: Starting tool with the AppSrv01 profile
[3/30/23 14:30:09:492 UTC] 00000001 AdminTool     A   ADMU3100I: Reading configuration for server: server1
[3/30/23 14:30:09:502 UTC] 00000001 ImplFactory   W   WSVR0072W: Ignoring undeclared override of interface, com.ibm.websphere.cluster.topography.DescriptionManager, with implementation, com.ibm.ws.cluster.propagation.bulletinboard.BBDescriptionManager
[3/30/23 14:30:09:670 UTC] 00000001 ModelMgr      I   WSVR0801I: Initializing all server configuration models
[3/30/23 14:30:11:727 UTC] 00000001 WorkSpaceMana A   WKSP0500I: Workspace configuration consistency check is disabled.

Is there any minimum requirement to start it? Or am i doing something wrong?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions