关于weblogic11g中wlst工具连接AdminServer失败的问题

[deepsea2011]

我在weblogic10.3.6上通过config.sh创建了一个base_domain，只配置了一个AdminServer,通过base_domain/bin/startWebLogic.sh启动AdminiServer,可以启动成功，并且通过http://192.168.137.23:7001/console 输入用户名密码后正常可以访问console。

但是如果通过wlst工具启动AdminiServer后，通过http://192.168.137.23:7001/console 输入用户名密码后无法访问console。

操作系统为centos6.8 64位，JDK版本：jdk1.7.0_80

1、wlst.sh启动server的记录：
`wls:/offline> startServer('AdminServer','base_domain','t3://192.168.137.23:7001')
Starting weblogic server ...
WLST-WLS-1560346833567: <Jun 12, 2019 9:40:35 PM CST> <Info> <Security> <BEA-090905> <Disabling CryptoJ JCE Provider self-integrity check for better startup performance. To enable this check, specify -Dweblogic.security.allowCryptoJDefaultJCEVerification=true>
WLST-WLS-1560346833567: <Jun 12, 2019 9:40:35 PM CST> <Info> <Security> <BEA-090906> <Changing the default Random Number Generator in RSA CryptoJ from ECDRBG to FIPS186PRNG. To disable this change, specify -Dweblogic.security.allowCryptoJDefaultPRNG=true>
WLST-WLS-1560346833567: <Jun 12, 2019 9:40:39 PM CST> <Info> <WebLogicServer> <BEA-000377> <Starting WebLogic Server with Java HotSpot(TM) 64-Bit Server VM Version 24.80-b11 from Oracle Corporation>
.WLST-WLS-1560346833567: <Jun 12, 2019 9:40:40 PM CST> <Info> <Management> <BEA-141107> <Version: WebLogic Server 10.3.6.0 Tue Nov 15 08:52:36 PST 2011 1441050 >
.WLST-WLS-1560346833567: <Jun 12, 2019 9:40:41 PM CST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STARTING>
WLST-WLS-1560346833567: <Jun 12, 2019 9:40:42 PM CST> <Info> <WorkManager> <BEA-002900> <Initializing self-tuning thread pool>
WLST-WLS-1560346833567: <Jun 12, 2019 9:40:42 PM CST> <Notice> <LoggingService> <BEA-320400> <The log file /u02/weblogic/weblogic/wlserver_10.3/common/bin/servers/AdminServer/logs/AdminServer.log will be rotated. Reopen the log file if tailing has stopped. This can happen on some platforms like Windows.>
WLST-WLS-1560346833567: <Jun 12, 2019 9:40:42 PM CST> <Notice> <LoggingService> <BEA-320401> <The log file has been rotated to /u02/weblogic/weblogic/wlserver_10.3/common/bin/servers/AdminServer/logs/AdminServer.log00009. Log messages will continue to be logged in /u02/weblogic/weblogic/wlserver_10.3/common/bin/servers/AdminServer/logs/AdminServer.log.>
WLST-WLS-1560346833567: <Jun 12, 2019 9:40:42 PM CST> <Notice> <Log Management> <BEA-170019> <The server log file /u02/weblogic/weblogic/wlserver_10.3/common/bin/servers/AdminServer/logs/AdminServer.log is opened. All server side log events will be written to this file.>
.WLST-WLS-1560346833567: <Jun 12, 2019 9:40:45 PM CST> <Notice> <Security> <BEA-090082> <Security initializing using security realm myrealm.>
..WLST-WLS-1560346833567: <Jun 12, 2019 9:40:49 PM CST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STANDBY>
WLST-WLS-1560346833567: <Jun 12, 2019 9:40:49 PM CST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STARTING>
WLST-WLS-1560346833567: <Jun 12, 2019 9:40:49 PM CST> <Notice> <LoggingService> <BEA-320400> <The log file /u02/weblogic/weblogic/wlserver_10.3/common/bin/servers/AdminServer/logs/base_domain.log will be rotated. Reopen the log file if tailing has stopped. This can happen on some platforms like Windows.>
WLST-WLS-1560346833567: <Jun 12, 2019 9:40:49 PM CST> <Notice> <LoggingService> <BEA-320401> <The log file has been rotated to /u02/weblogic/weblogic/wlserver_10.3/common/bin/servers/AdminServer/logs/base_domain.log00009. Log messages will continue to be logged in /u02/weblogic/weblogic/wlserver_10.3/common/bin/servers/AdminServer/logs/base_domain.log.>
WLST-WLS-1560346833567: <Jun 12, 2019 9:40:49 PM CST> <Notice> <Log Management> <BEA-170027> <The Server has established connection with the Domain level Diagnostic Service successfully.>
WLST-WLS-1560346833567: <Jun 12, 2019 9:40:50 PM CST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to ADMIN>
WLST-WLS-1560346833567: <Jun 12, 2019 9:40:50 PM CST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to RESUMING>
WLST-WLS-1560346833567: <Jun 12, 2019 9:40:50 PM CST> <Notice> <Server> <BEA-002613> <Channel "Default" is now listening on 192.168.137.23:7001 for protocols iiop, t3, ldap, snmp, http.>
WLST-WLS-1560346833567: <Jun 12, 2019 9:40:50 PM CST> <Notice> <WebLogicServer> <BEA-000331> <Started WebLogic Admin Server "AdminServer" for domain "base_domain" running in Development Mode>
WLST-WLS-1560346833567: <Jun 12, 2019 9:40:50 PM CST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to RUNNING>
WLST-WLS-1560346833567: <Jun 12, 2019 9:40:50 PM CST> <Notice> <WebLogicServer> <BEA-000360> <Server started in RUNNING mode>
Server started successfully.
'WLST-WLS-1560346833567'

2、console控制台报错：
WebLogic Server 已拒绝此用户名或口令。请重试
3、通过connect()命令连接Adminserver同样报错

wls:/offline> connect('weblogic','weblogic123','t3://192.168.137.23:7001')
Connecting to t3://192.168.137.23:7001 with userid weblogic ...
Traceback (innermost last):
File "<console>", line 1, in ?
File "<iostream>", line 22, in connect
File "<iostream>", line 648, in raiseWLSTException
WLSTException: Error occured while performing connect : User: weblogic, failed to be authenticated.
Use dumpStack() to view the full stacktrace
wls:/offline> dumpStack()
This Exception occurred at Wed Jun 12 22:04:24 CST 2019.
javax.naming.AuthenticationException [Root exception is java.lang.SecurityException: User: weblogic, failed to be authenticated.]
javax.naming.AuthenticationException [Root exception is java.lang.SecurityException: User: weblogic, failed to be authenticated.]