My Oracle Support Banner

Managed Server Will Not Shut Down via WLST When Using t3s Protocol (Doc ID 942728.1)

Last updated on DECEMBER 11, 2017

Applies to:

Oracle Weblogic Server - Version 9.2 to 10.3
Information in this document applies to any platform.

Symptoms

We are unable to shutdown a managed server when we use the t3s protocol in the WLST scripts. The same script using the t3 protocol is working fine. The admin server is shutting down fine with either protocol.

We get the following error:

Shutting down the server managed1 with force=false while connected to adminserver ...
This Exception occurred at Tue Mar 17 12:10:41 PDT 2009.
weblogic.server.ServerLifecycleException: Can not get to the relevant ServerRuntimeMBean for server managed1.
at weblogic.server.ServerLifeCycleRuntime$ShutdownRequest.run(ServerLifeCycleRuntime.java:489)


Here is a sample WLST script to reproduce the issue:

connect(url='t3s://localhost:7002',adminServerName='adminserver')
shutdown('managed1','Server')
exit()

Steps to reproduce: 

  1. Create a domain for WLS 10.3 with one admin and one managed server.
  2. Enable SSL and configure the Demo Identity and Demo trust for the keystores on both the admin and managed servers.
  3. Edit the stopWeblogic.cmd script
    set ADMIN_URL=t3s://localhost:7002
    And add the -Dweblogic.security.TrustKeyStore=DemoTrust
  4. Start the admin server.
  5. Start the managed server.
  6. Stop the managed server.

Cause

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
Symptoms
Cause
Solution
References

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