2,633
社区成员
发帖
与我相关
我的任务
分享不能访问was5的管理控制台？？如何解决
我在windows上安装了WAS5 ND版产品。由于在安装deployment manager是我选择了重新设置端口，所以不存在端口冲突问题。我已经把server1加到deployment manager中，如果我不先启动nodeagent，server1就不能正常启动，如果我先启动nodeagent，在再服务中启动server1就能正常启动，但是访问http://localhost:9090/admin时报错时该页无法显示。如果访问http://localhost:9091/admin时却能正常访问DM的管理控制台，不知道问题出在那里。
前几天是可以同时访问was的console和dm的console的，但是现在不行了，我不想每次出现这种问题的时候都卸了重装，不知道那位大侠可以给了解决方法。
以下是admin.traceout的内容
×××××××××××××××××××××××××××××××××××××
************* End Display Current Environment *************
[04-3-28 15:34:57:529 CST] 649c2806 ManagerAdmin I TRAS0017I: 启动跟踪状态是 *=all=disabled。
[04-3-28 15:34:57:539 CST] 649c2806 AbstractShell A WASX7357I: 根据请求，脚本编制客户机未连接到任何服务器进程。特定的配置和应用程序操作以本地方式可用。
[04-3-28 15:34:57:619 CST] 649c2806 AbstractShell A WASX7326I: 已装入属性文件“/D:/travelsky/WebSphere/AppServer/properties/wsadmin.properties”
[04-3-28 15:34:57:659 CST] 649c2806 AdminControlC W WASX7072E: 控制服务不可用。
[04-3-28 15:35:01:124 CST] 649c2806 AdminConfigCl A WASX7208I: 现在有效的验证设置：级别=HIGHEST，交叉验证=true，输出文件=D:\travelsky\WebSphere\AppServer\logs\wsadmin.valout
[04-3-28 15:35:01:164 CST] 649c2806 AdminAppClien W WASX7072E: 控制服务不可用。
[04-3-28 15:35:01:595 CST] 649c2806 AbstractShell A WASX7303I: 下列未识别的选项传递到脚本编制环境并作为 argv 可用：“[wangyb, wangyb]”
[04-3-28 15:35:03:057 CST] 649c2806 AbstractShell A WASX7091I: 执行脚本：“G:\nt\util\petstoreConfig.jacl”
×××××××××××××××××××××××××××××××××××××
以下是admin.properties的内容
#-------------------------------------------------------------------------
# Properties file for scripting client
# Base App Server version
#-------------------------------------------------------------------------
#
#-------------------------------------------------------------------------
# The connectionType determines what connector is used.
# It can be SOAP or RMI.
# The default is SOAP.
#-------------------------------------------------------------------------
com.ibm.ws.scripting.connectionType=SOAP
#com.ibm.ws.scripting.connectionType=RMI
#-------------------------------------------------------------------------
# The port property determines what port is used when attempting
# a connection.
# The default SOAP port for a single-server installation is 8880
#-------------------------------------------------------------------------
#com.ibm.ws.scripting.port=8880
com.ibm.ws.scripting.port=8889
#com.ibm.ws.scripting.port=2809
#-------------------------------------------------------------------------
# The host property determines what host is used when attempting
# a connection.
# The default value is localhost.
#-------------------------------------------------------------------------
com.ibm.ws.scripting.host=localhost
#-------------------------------------------------------------------------
# The defaultLang property determines what scripting language to use.
# Jacl is the sole supported language
#-------------------------------------------------------------------------
com.ibm.ws.scripting.defaultLang=jacl
#-------------------------------------------------------------------------
# The traceFile property determines where trace and logging
# output are directed. If more than one user will be using
# wsadmin simultaneously, different traceFile properties should
# be set in user properties files.
# The default is that all tracing and logging go to the console;
# it is recommended that a value be specified here.
# If the file name contains DBCS characters, use unicode format such as \uxxxx, where xxxx is a number
#-------------------------------------------------------------------------
com.ibm.ws.scripting.traceFile=D:/WebSphere/AppServer/logs/wsadmin.traceout
#-------------------------------------------------------------------------
# The validationOutput property determines where validation
# reports are directed. If more than one user will be using
# wsadmin simultaneously, different validationOutput properties should
# be set in user properties files.
# The default is wsadmin.valout in the current directory.
# If the file name contains DBCS characters, use unicode format such as \uxxxx, where xxxx is a number
#-------------------------------------------------------------------------
#com.ibm.ws.scripting.validationOutput=
#-------------------------------------------------------------------------
# The traceString property governs the trace in effect for
# the scripting client process.
# The default is no tracing.
#-------------------------------------------------------------------------
#com.ibm.ws.scripting.traceString=com.ibm.*=all=enabled
#-------------------------------------------------------------------------
# The profiles property is a list of profiles to be run before
# running user commands, scripts, or an interactive shell.
# securityProcs is included here by default to make security
# configuration easier.
#-------------------------------------------------------------------------
com.ibm.ws.scripting.profiles=D:/WebSphere/AppServer/bin/securityProcs.jacl;D:/WebSphere/AppServer/bin/LTPA_LDAPSecurityProcs.jacl
#-------------------------------------------------------------------------
# The emitWarningForCustomSecurityPolicy property controls whether
# message WASX7207W is emitted when custom permissions are found.
# Possible values are: true, false
# The default is "true"
#-------------------------------------------------------------------------
# com.ibm.ws.scripting.emitWarningForCustomSecurityPolicy=true
#-------------------------------------------------------------------------
# The tempdir property determines what directory to use for temporary
# files when installing applications.
# The default is that the JVM decides -- this is java.io.tmpdir
#-------------------------------------------------------------------------
#com.ibm.ws.scripting.tempdir=
#-------------------------------------------------------------------------
# The validationLevel property determines what level of validation to
# use when configuration changes are made from the scripting interface.
# Possible values are: NONE, LOW, MEDIUM, HIGH, HIGHEST
# The default is HIGHEST
#-------------------------------------------------------------------------
#com.ibm.ws.scripting.validationLevel=
#-------------------------------------------------------------------------
# The crossDocumentValidationEnabled property determines whether the validation
# mechanism examines other documents when changes are made to one document.
# Possible values are: true, false
# The default is true
#-------------------------------------------------------------------------
#com.ibm.ws.scripting.crossDocumentValidationEnabled=
#-------------------------------------------------------------------------
# The classpath property is appended to the list of paths to search for
# classes and resources.
# There is no default value.
#-------------------------------------------------------------------------
#com.ibm.ws.scripting.classpath=
前几天是可以同时访问was的console和dm的console的，但是现在不行了，我不想每次出现这种问题的时候都卸了重装，不知道那位大侠可以给了解决方法。
以下是admin.traceout的内容
×××××××××××××××××××××××××××××××××××××
************* End Display Current Environment *************
[04-3-28 15:34:57:529 CST] 649c2806 ManagerAdmin I TRAS0017I: 启动跟踪状态是 *=all=disabled。
[04-3-28 15:34:57:539 CST] 649c2806 AbstractShell A WASX7357I: 根据请求，脚本编制客户机未连接到任何服务器进程。特定的配置和应用程序操作以本地方式可用。
[04-3-28 15:34:57:619 CST] 649c2806 AbstractShell A WASX7326I: 已装入属性文件“/D:/travelsky/WebSphere/AppServer/properties/wsadmin.properties”
[04-3-28 15:34:57:659 CST] 649c2806 AdminControlC W WASX7072E: 控制服务不可用。
[04-3-28 15:35:01:124 CST] 649c2806 AdminConfigCl A WASX7208I: 现在有效的验证设置：级别=HIGHEST，交叉验证=true，输出文件=D:\travelsky\WebSphere\AppServer\logs\wsadmin.valout
[04-3-28 15:35:01:164 CST] 649c2806 AdminAppClien W WASX7072E: 控制服务不可用。
[04-3-28 15:35:01:595 CST] 649c2806 AbstractShell A WASX7303I: 下列未识别的选项传递到脚本编制环境并作为 argv 可用：“[wangyb, wangyb]”
[04-3-28 15:35:03:057 CST] 649c2806 AbstractShell A WASX7091I: 执行脚本：“G:\nt\util\petstoreConfig.jacl”
×××××××××××××××××××××××××××××××××××××
以下是admin.properties的内容
#-------------------------------------------------------------------------
# Properties file for scripting client
# Base App Server version
#-------------------------------------------------------------------------
#
#-------------------------------------------------------------------------
# The connectionType determines what connector is used.
# It can be SOAP or RMI.
# The default is SOAP.
#-------------------------------------------------------------------------
com.ibm.ws.scripting.connectionType=SOAP
#com.ibm.ws.scripting.connectionType=RMI
#-------------------------------------------------------------------------
# The port property determines what port is used when attempting
# a connection.
# The default SOAP port for a single-server installation is 8880
#-------------------------------------------------------------------------
#com.ibm.ws.scripting.port=8880
com.ibm.ws.scripting.port=8889
#com.ibm.ws.scripting.port=2809
#-------------------------------------------------------------------------
# The host property determines what host is used when attempting
# a connection.
# The default value is localhost.
#-------------------------------------------------------------------------
com.ibm.ws.scripting.host=localhost
#-------------------------------------------------------------------------
# The defaultLang property determines what scripting language to use.
# Jacl is the sole supported language
#-------------------------------------------------------------------------
com.ibm.ws.scripting.defaultLang=jacl
#-------------------------------------------------------------------------
# The traceFile property determines where trace and logging
# output are directed. If more than one user will be using
# wsadmin simultaneously, different traceFile properties should
# be set in user properties files.
# The default is that all tracing and logging go to the console;
# it is recommended that a value be specified here.
# If the file name contains DBCS characters, use unicode format such as \uxxxx, where xxxx is a number
#-------------------------------------------------------------------------
com.ibm.ws.scripting.traceFile=D:/WebSphere/AppServer/logs/wsadmin.traceout
#-------------------------------------------------------------------------
# The validationOutput property determines where validation
# reports are directed. If more than one user will be using
# wsadmin simultaneously, different validationOutput properties should
# be set in user properties files.
# The default is wsadmin.valout in the current directory.
# If the file name contains DBCS characters, use unicode format such as \uxxxx, where xxxx is a number
#-------------------------------------------------------------------------
#com.ibm.ws.scripting.validationOutput=
#-------------------------------------------------------------------------
# The traceString property governs the trace in effect for
# the scripting client process.
# The default is no tracing.
#-------------------------------------------------------------------------
#com.ibm.ws.scripting.traceString=com.ibm.*=all=enabled
#-------------------------------------------------------------------------
# The profiles property is a list of profiles to be run before
# running user commands, scripts, or an interactive shell.
# securityProcs is included here by default to make security
# configuration easier.
#-------------------------------------------------------------------------
com.ibm.ws.scripting.profiles=D:/WebSphere/AppServer/bin/securityProcs.jacl;D:/WebSphere/AppServer/bin/LTPA_LDAPSecurityProcs.jacl
#-------------------------------------------------------------------------
# The emitWarningForCustomSecurityPolicy property controls whether
# message WASX7207W is emitted when custom permissions are found.
# Possible values are: true, false
# The default is "true"
#-------------------------------------------------------------------------
# com.ibm.ws.scripting.emitWarningForCustomSecurityPolicy=true
#-------------------------------------------------------------------------
# The tempdir property determines what directory to use for temporary
# files when installing applications.
# The default is that the JVM decides -- this is java.io.tmpdir
#-------------------------------------------------------------------------
#com.ibm.ws.scripting.tempdir=
#-------------------------------------------------------------------------
# The validationLevel property determines what level of validation to
# use when configuration changes are made from the scripting interface.
# Possible values are: NONE, LOW, MEDIUM, HIGH, HIGHEST
# The default is HIGHEST
#-------------------------------------------------------------------------
#com.ibm.ws.scripting.validationLevel=
#-------------------------------------------------------------------------
# The crossDocumentValidationEnabled property determines whether the validation
# mechanism examines other documents when changes are made to one document.
# Possible values are: true, false
# The default is true
#-------------------------------------------------------------------------
#com.ibm.ws.scripting.crossDocumentValidationEnabled=
#-------------------------------------------------------------------------
# The classpath property is appended to the list of paths to search for
# classes and resources.
# There is no default value.
#-------------------------------------------------------------------------
#com.ibm.ws.scripting.classpath=
...全文
请发表友善的回复…
发表回复
prettyqiqi 2004-04-05
- 打赏
- 举报
难道把接点加到DM中以后，即使端口不冲突也不能访问单独访问was5 的console吗？
iceleighton 2004-04-01
- 打赏
- 举报
很简单，当你把Server1加到ND环境中后，Server本身的管理控制台就上移到ND节点上，
而且,原来隐藏在Server1中的Node Agent就独立了出来，这样在启动Server1之前就
必须先启动Node Agent。由于你在安装的时候选择了无冲突的端口，所以ND的控制台
访问的端口就是9091。也就是说当你把Server1加入ND后，Server1本身就失去了管理
自身的功能，而ND则担负起管理所有节点和应用服务器的工作。
简单一句话，你所碰到的是正常的情况，根本没问题！
而且,原来隐藏在Server1中的Node Agent就独立了出来，这样在启动Server1之前就
必须先启动Node Agent。由于你在安装的时候选择了无冲突的端口，所以ND的控制台
访问的端口就是9091。也就是说当你把Server1加入ND后，Server1本身就失去了管理
自身的功能，而ND则担负起管理所有节点和应用服务器的工作。
简单一句话，你所碰到的是正常的情况，根本没问题！
iceleighton 2004-04-01
- 打赏
- 举报
如果你在Addnode的时候没有选择把Server1的应用移植到
ND环境，那么就没法访问了。如果选择了移植，
那么关键就看你的端口是不是被修改过，如果是请访问：
http://localhost:9085/snoop
ND环境，那么就没法访问了。如果选择了移植，
那么关键就看你的端口是不是被修改过，如果是请访问：
http://localhost:9085/snoop
delubo 2004-04-01
- 打赏
- 举报
接着上面的这位仁兄，我再问一个问题，安装完成后，我怎样在访问原来的例子，比如说snoop和petstore等？？
prettyqiqi 2004-03-31
- 打赏
- 举报
×××××××××××××××××××××××××××××××××××××
以下是server1的SystemOut的内容
************ Start Display Current Environment ************
WebSphere Platform 5.0 [BASE 5.0.0 s0245.03] [ND 5.0.0 s0245.03] running with process name wangybNetwork\wangyb\server1 and process id 4328
Host Operating System is Windows 2000, version 5.0
Java version = J2RE 1.3.1 IBM Windows 32 build cn131-20021107 (JIT enabled: jitc), Java Compiler = jitc, Java VM name = Classic VM
was.install.root = D:\WebSphere\AppServer
user.install.root = D:\WebSphere\AppServer
Java Home = D:\WebSphere\AppServer\java\jre
ws.ext.dirs = D:\WebSphere\AppServer\java/lib;D:\WebSphere\AppServer/classes;D:\WebSphere\AppServer/classes;D:\WebSphere\AppServer/lib;D:\WebSphere\AppServer/lib/ext;D:\WebSphere\AppServer/web/help;D:\WebSphere\AppServer/deploytool/itp/plugins/com.ibm.etools.ejbdeploy/runtime
Classpath = D:\WebSphere\AppServer/properties;D:\WebSphere\AppServer/properties;D:\WebSphere\AppServer/lib/bootstrap.jar;D:\WebSphere\AppServer/lib/j2ee.jar;D:\WebSphere\AppServer/lib/lmproxy.jar;D:\WebSphere\AppServer\lib\msbase.jar;D:\WebSphere\AppServer\lib\mssqlserver.jar;D:\WebSphere\AppServer\lib\msutil.jar;D:\WebSphere\AppServer\lib\WriteXML.jar
Java Library path = D:\WebSphere\AppServer\java\bin;.;C:\WINNT\System32;C:\WINNT;D:\WebSphere\AppServer\bin;D:\WebSphere\AppServer\java\bin;D:\WebSphere\AppServer\java\jre\bin;D:\IBM\WebSphereMQ\Java\lib;C:\WINNT\system32;C:\WINNT;C:\WINNT\System32\Wbem;C:\WINNT\System32\wbem\;C:\Program Files\Microsoft BizTalk Server\;C:\Program Files\Common Files\Microsoft Shared\Enterprise Servers\Commerce\;C:\PROGRA~1\ULTRAE~1;d:\Program Files\Starbase\StarGate SDK\Lib;d:\Program Files\Starbase\StarGate SDK\Bin;C:\Program Files\Microsoft SQL Server\80\Tools\Binn\;%CORBA_PATH%;C:\Program Files\Symantec\pcAnywhere\;c:\WebSphere\AppServer\bin;C:\WebSphere\AppServer\bin;D:\IBM\WebSphereMQ\bin;D:\IBM\WebSphereMQ\WEMPS\bin
************* End Display Current Environment *************
[04-3-31 16:45:23:850 CST] 249e2a80 ManagerAdmin I TRAS0017I: 启动跟踪状态是 *=all=enabled。
[04-3-31 16:45:25:422 CST] 249e2a80 AdminInitiali A ADMN0015I: AdminService 初始化
[04-3-31 16:45:27:395 CST] 249e2a80 Configuration A SECJ0215I: 成功地将 JAAS 登录提供程序配置类设置为 com.ibm.ws.security.auth.login.Configuration。
[04-3-31 16:45:27:565 CST] 249e2a80 SecurityDM I SECJ0231I: 成功注册了安全性组件的 FFDC 诊断模块 com.ibm.ws.security.core.SecurityDM：true。
[04-3-31 16:45:27:816 CST] 249e2a80 SecurityCompo I SECJ0309I: 禁用 Java 2 安全性。
[04-3-31 16:45:27:856 CST] 249e2a80 SecurityCompo I SECJ0212I: WCCM JAAS 配置信息已成功推送到登录提供程序类。
[04-3-31 16:45:27:906 CST] 249e2a80 SecurityCompo I SECJ0240I: 成功完成安全性服务初始化
[04-3-31 16:45:31:802 CST] 249e2a80 PmiRmArmWrapp I PMRM0001I: ARM 实现为：none
[04-3-31 16:45:42:857 CST] 249e2a80 ContainerImpl E WSVR0102E: 停止 null [class com.ibm.ws.runtime.component.ORBImpl] 时发生错误
java.lang.NullPointerException
at com.ibm.ejs.oa.EJSORB.terminate(EJSORB.java:383)
at com.ibm.ws.runtime.component.ORBImpl.stop(ORBImpl.java:271)
at com.ibm.ws.runtime.component.ContainerImpl.stopComponents(ContainerImpl.java:367)
at com.ibm.ws.runtime.component.ContainerImpl.stop(ContainerImpl.java:238)
at com.ibm.ws.runtime.component.ServerImpl.stop(ServerImpl.java:204)
at com.ibm.ws.runtime.WsServer.start(WsServer.java:139)
at com.ibm.ws.runtime.WsServer.main(WsServer.java:232)
at java.lang.reflect.Method.invoke(Native Method)
at com.ibm.ws.bootstrap.WSLauncher.main(WSLauncher.java:94)
[04-3-31 16:45:42:877 CST] 249e2a80 ContainerImpl E WSVR0102E: 停止 [class com.ibm.ws.management.component.JMXConnectors] 时发生错误
java.lang.NullPointerException
at com.ibm.ws.management.component.JMXConnectors.stop(JMXConnectors.java:226)
at com.ibm.ws.runtime.component.ContainerImpl.stopComponents(ContainerImpl.java:367)
at com.ibm.ws.management.component.AdminImpl.stop(AdminImpl.java:415)
at com.ibm.ws.runtime.component.ContainerImpl.stopComponents(ContainerImpl.java:367)
at com.ibm.ws.runtime.component.ContainerImpl.stop(ContainerImpl.java:238)
at com.ibm.ws.runtime.component.ServerImpl.stop(ServerImpl.java:204)
at com.ibm.ws.runtime.WsServer.start(WsServer.java:139)
at com.ibm.ws.runtime.WsServer.main(WsServer.java:232)
at java.lang.reflect.Method.invoke(Native Method)
at com.ibm.ws.bootstrap.WSLauncher.main(WSLauncher.java:94)
[04-3-31 16:45:42:938 CST] 249e2a80 WsServer E WSVR0003E: 服务器 server1 无法启动
com.ibm.ws.exception.RuntimeError
at com.ibm.ws.runtime.component.ORBImpl.start(ORBImpl.java:259)
at com.ibm.ws.runtime.component.ContainerImpl.startComponents(ContainerImpl.java:343)
at com.ibm.ws.runtime.component.ContainerImpl.start(ContainerImpl.java:234)
at com.ibm.ws.runtime.component.ServerImpl.start(ServerImpl.java:182)
at com.ibm.ws.runtime.WsServer.start(WsServer.java:135)
at com.ibm.ws.runtime.WsServer.main(WsServer.java:232)
at java.lang.reflect.Method.invoke(Native Method)
at com.ibm.ws.bootstrap.WSLauncher.main(WSLauncher.java:94)
---- Begin backtrace for nested exception
com.ibm.ejs.EJSException: Could not register with Location Service Daemon, which could only reside in the NodeAgent. Make sure the NodeAgent for this node is up an running.; nested exception is:
org.omg.CORBA.TRANSIENT: Connection refused: connect:host=wangyb,port=9900 minor code: 4942F301 completed: No
org.omg.CORBA.TRANSIENT: Connection refused: connect:host=wangyb,port=9900 minor code: 4942F301 completed: No
at com.ibm.CORBA.transport.TransportConnectionBase.connect(TransportConnectionBase.java:353)
at com.ibm.ws.orbimpl.transport.WSTransport.getConnection(WSTransport.java:414)
at com.ibm.rmi.iiop.TransportManager.get(TransportManager.java:84)
at com.ibm.rmi.iiop.GIOPImpl.locate(GIOPImpl.java:177)
at com.ibm.rmi.corba.Corbaloc.locateUsingINS(Corbaloc.java:301)
at com.ibm.rmi.corba.Corbaloc.resolve(Corbaloc.java:363)
at com.ibm.rmi.corba.InitialReferenceClient.resolve_initial_references(InitialReferenceClient.java:151)
at com.ibm.rmi.corba.ORB.resolve_initial_references(ORB.java:3162)
at com.ibm.rmi.iiop.ORB.resolve_initial_references(ORB.java:531)
at com.ibm.CORBA.iiop.ORB.resolve_initial_references(ORB.java:2810)
at com.ibm.ejs.oa.LocationService.register(LocationService.java:160)
at com.ibm.ejs.oa.EJSServerORBImpl.<init>(EJSServerORBImpl.java:140)
at com.ibm.ejs.oa.EJSORB.init(EJSORB.java:337)
at com.ibm.ws.runtime.component.ORBImpl.start(ORBImpl.java:255)
at com.ibm.ws.runtime.component.ContainerImpl.startComponents(ContainerImpl.java:343)
at com.ibm.ws.runtime.component.ContainerImpl.start(ContainerImpl.java:234)
at com.ibm.ws.runtime.component.ServerImpl.start(ServerImpl.java:182)
at com.ibm.ws.runtime.WsServer.start(WsServer.java:135)
at com.ibm.ws.runtime.WsServer.main(WsServer.java:232)
at java.lang.reflect.Method.invoke(Native Method)
at com.ibm.ws.bootstrap.WSLauncher.main(WSLauncher.java:94)
[04-3-31 16:45:42:948 CST] 249e2a80 WsServer E WSVR0009E: 启动期间发生错误
