Request Can Not Reach the Restarted Server When Using WebLogic T3 Client

(Doc ID 2116561.1)

Last updated on MARCH 28, 2016

Applies to:

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


When using WebLogic T3 Client,  if the environment are not set correctly, the requests will just going to one managed server, and not round-robin when one server is restarted again.

The issue was reproduced as below:

A. Create a domain with 2 managed server (MS1(localhost:7003), MS2(localhost:7005)) in it. Note that this is a non-clustered environment

B.  Deploy the attachment file ejb.jar to MS1 and MS2

   Note that there is one jndi name(jndi_ejb)in two MS1 and MS2 now

C. Prepare the client src

   1) Put the attachment file ejb.jar and in one folder

   2) Start the weblogic server (admin server, two managed servers)

   3) Start a new cmd and enter domain\bin\setDomainEnv.cmd to set the class path environment

   4) Run the command below to create client class

       javac -cp .;ejb.jar;%classpath%

   5) Run the command below to execute client class

       java -cp .;ejb.jar;%classpath% exec_ejb

       ※let this client keep running

   6) There are requests can be found in weblogic console/ deployment/ejb/Monitoring

       in two of the servers

   7) Stop MS1 in Weblogic console using force shut down

   8) As above 6), you will see the requests just going in to MS2 only

   9) Start MS1 again

  10) The requests will never come to MS1




Sign In with your My Oracle Support account

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

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms