Are you writing scripts to start & stop the admin server?
Are you getting below error when trying to start the Admin Server using scripts?
<Error> <Configuration Management> <xxxxx.na.lzb.hq> <AdminServer> <[STANDBY] ExecuteThread: '2' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1541099907869> <BEA-150000> <An error occurred while establishing a connection back to the Adminstration Server t3://10.1.2.79:7001 during startup. Since bootstrap succeeded, check that t3://1xx.yy.zz.rr:7001 uniquely identifies the Administration Server.
Are you getting below error when trying to start the Admin Server using scripts?
<Error> <Configuration Management> <xxxxx.na.lzb.hq> <AdminServer> <[STANDBY] ExecuteThread: '2' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1541099907869> <BEA-150000> <An error occurred while establishing a connection back to the Adminstration Server t3://10.1.2.79:7001 during startup. Since bootstrap succeeded, check that t3://1xx.yy.zz.rr:7001 uniquely identifies the Administration Server.
Here the catch:
If you have set this variable any where in your scripts or property file, you are bound to get the error.
ADMIN_URL=<HOST>:<PORT>
Resolution: ==> Do not set the variable ADMIN_URL anywhere in you startup script or property file.
Repeat the above statement 4 more times again.
No comments:
Post a Comment