[英]Glassfish admin console faile
I use glassfish 3.0.1 on windows 2003 with JDK 6u24. 我在带有JDK 6u24的Windows 2003上使用glassfish 3.0.1。 When I start the server and try to login to the admin console (4848) I will receive this error message:
当我启动服务器并尝试登录到管理控制台(4848)时,我将收到此错误消息:
[#|2011-02-24T12:59:37.578+0330|INFO|glassfish3.0.1|javax.enterprise.system.std.
com.sun.enterprise.v3.services.impl|_ThreadID=25;_ThreadName=http-thread-pool-48
48-(2);|Cannot refresh Catalog : Connection timed out: connect|#]
Update 更新资料
[#|2011-02-24T12:58:51.343+0330|INFO|glassfish3.0.1|null|_ThreadID=24;_ThreadNam
e=Thread-23;|The Admin Console is already installed, but not yet loaded.|#]
[#|2011-02-24T12:58:51.343+0330|INFO|glassfish3.0.1|null|_ThreadID=24;_ThreadNam
e=Thread-23;|The Admin Console is loading...|#]
[#|2011-02-24T12:58:52.296+0330|INFO|glassfish3.0.1|javax.enterprise.system.cont
ainer.web.com.sun.enterprise.web|_ThreadID=24;_ThreadName=Thread-23;|Created HTT
P listener http-listener-1 on port 80|#]
[#|2011-02-24T12:58:52.296+0330|INFO|glassfish3.0.1|javax.enterprise.system.cont
ainer.web.com.sun.enterprise.web|_ThreadID=24;_ThreadName=Thread-23;|Created HTT
P listener http-listener-2 on port 8181|#]
[#|2011-02-24T12:58:52.296+0330|INFO|glassfish3.0.1|javax.enterprise.system.cont
ainer.web.com.sun.enterprise.web|_ThreadID=24;_ThreadName=Thread-23;|Created HTT
P listener admin-listener on port 4848|#]
[#|2011-02-24T12:58:52.343+0330|INFO|glassfish3.0.1|javax.enterprise.system.cont
ainer.web.com.sun.enterprise.web|_ThreadID=24;_ThreadName=Thread-23;|Created vir
tual server server|#]
[#|2011-02-24T12:58:52.343+0330|INFO|glassfish3.0.1|javax.enterprise.system.cont
ainer.web.com.sun.enterprise.web|_ThreadID=24;_ThreadName=Thread-23;|Created vir
tual server __asadmin|#]
[#|2011-02-24T12:58:53.531+0330|INFO|glassfish3.0.1|javax.enterprise.system.cont
ainer.web.com.sun.enterprise.web|_ThreadID=24;_ThreadName=Thread-23;|Virtual ser
ver server loaded system default web module|#]
[#|2011-02-24T12:58:54.671+0330|INFO|glassfish3.0.1|javax.enterprise.system.core
.security.com.sun.enterprise.security|_ThreadID=24;_ThreadName=Thread-23;|SEC100
2: Security Manager is OFF.|#]
[#|2011-02-24T12:58:54.937+0330|INFO|glassfish3.0.1|javax.enterprise.system.core
.security.com.sun.enterprise.security|_ThreadID=24;_ThreadName=Thread-23;|Securi
ty startup service called|#]
[#|2011-02-24T12:58:54.953+0330|INFO|glassfish3.0.1|javax.enterprise.system.core
.security.com.sun.enterprise.security|_ThreadID=24;_ThreadName=Thread-23;|SEC114
3: Loading policy provider com.sun.enterprise.security.provider.PolicyWrapper.|#
]
[#|2011-02-24T12:58:55.062+0330|INFO|glassfish3.0.1|javax.enterprise.system.core
.security.com.sun.enterprise.security.auth.realm|_ThreadID=24;_ThreadName=Thread
-23;|Realm admin-realm of classtype com.sun.enterprise.security.auth.realm.file.
FileRealm successfully created.|#]
[#|2011-02-24T12:58:55.062+0330|INFO|glassfish3.0.1|javax.enterprise.system.core
.security.com.sun.enterprise.security.auth.realm|_ThreadID=24;_ThreadName=Thread
-23;|Realm file of classtype com.sun.enterprise.security.auth.realm.file.FileRea
lm successfully created.|#]
[#|2011-02-24T12:58:55.062+0330|INFO|glassfish3.0.1|javax.enterprise.system.core
.security.com.sun.enterprise.security.auth.realm|_ThreadID=24;_ThreadName=Thread
-23;|Realm certificate of classtype com.sun.enterprise.security.auth.realm.certi
ficate.CertificateRealm successfully created.|#]
[#|2011-02-24T12:58:55.078+0330|INFO|glassfish3.0.1|javax.enterprise.system.core
.security.com.sun.enterprise.security|_ThreadID=24;_ThreadName=Thread-23;|Securi
ty service(s) started successfully....|#]
[#|2011-02-24T12:58:56.687+0330|INFO|glassfish3.0.1|javax.enterprise.resource.we
bcontainer.jsf.config|_ThreadID=24;_ThreadName=Thread-23;|Initializing Mojarra 2
.0.2 (FCS b10) for context ''|#]
[#|2011-02-24T12:58:58.546+0330|INFO|glassfish3.0.1|javax.enterprise.system.cont
ainer.web.com.sun.enterprise.web|_ThreadID=24;_ThreadName=Thread-23;|Loading app
lication __admingui at /|#]
[#|2011-02-24T12:58:58.546+0330|INFO|glassfish3.0.1|null|_ThreadID=24;_ThreadNam
e=Thread-23;|Loading __admingui Application done is 7203 ms|#]
[#|2011-02-24T12:58:58.546+0330|INFO|glassfish3.0.1|null|_ThreadID=24;_ThreadNam
e=Thread-23;|The Admin Console application is loaded.|#]
[#|2011-02-24T12:59:02.515+0330|INFO|glassfish3.0.1|javax.enterprise.system.tool
s.admin.org.glassfish.server|_ThreadID=25;_ThreadName=http-thread-pool-4848-(2);
|AMX ComplianceMonitor: ValidationLevel = full, UnregisterNonCompliant = false,
LogInaccessibleAttributes = true|#]
[#|2011-02-24T12:59:02.828+0330|INFO|glassfish3.0.1|javax.enterprise.system.tool
s.admin.org.glassfish.server|_ThreadID=26;_ThreadName=Thread-24;|AMX config read
, domain config registered as amx:pp=/,type=domain|#]
[#|2011-02-24T12:59:03.046+0330|INFO|glassfish3.0.1|javax.enterprise.system.tool
s.admin.org.glassfish.server|_ThreadID=27;_ThreadName=Thread-27;|J2EEDomain regi
stered at amx:pp=/,type=J2EEDomain,j2eeType=J2EEDomain,name=amx|#]
[#|2011-02-24T12:59:03.046+0330|INFO|glassfish3.0.1|javax.enterprise.system.tool
s.admin.org.glassfish.server|_ThreadID=25;_ThreadName=http-thread-pool-4848-(2);
|AMXStartupServiceNew: AMX ready for use, DomainRoot = amx:pp=,type=domain-root|
#]
[#|2011-02-24T12:59:10.843+0330|WARNING|glassfish3.0.1|javax.enterprise.system.c
ontainer.web.com.sun.web.security|_ThreadID=25;_ThreadName=http-thread-pool-4848
-(2);|Web login failed: Login failed: javax.security.auth.login.LoginException:
Failed file login for admin.|#]
[#|2011-02-24T12:59:10.843+0330|WARNING|glassfish3.0.1|org.apache.catalina.conne
ctor.Request|_ThreadID=25;_ThreadName=http-thread-pool-4848-(2);|PWC4011: Unable
to set request character encoding to UTF-8 from context , because request param
eters have already been read, or ServletRequest.getReader() has already been cal
led|#]
[#|2011-02-24T12:59:16.093+0330|INFO|glassfish3.0.1|org.glassfish.admingui|_Thre
adID=25;_ThreadName=http-thread-pool-4848-(2);|admin console: initSessionAttribu
tes()|#]
[#|2011-02-24T12:59:37.578+0330|INFO|glassfish3.0.1|javax.enterprise.system.std.
com.sun.enterprise.v3.services.impl|_ThreadID=25;_ThreadName=http-thread-pool-48
48-(2);|Cannot refresh Catalog : Connection timed out: connect|#]
[#|2011-02-24T13:08:09.015+0330|INFO|glassfish3.0.1|org.glassfish.admingui|_Thre
adID=28;_ThreadName=http-thread-pool-4848-(1);|admin console: initSessionAttribu
tes()|#]
[#|2011-02-24T13:08:30.125+0330|INFO|glassfish3.0.1|javax.enterprise.system.std.
com.sun.enterprise.v3.services.impl|_ThreadID=28;_ThreadName=http-thread-pool-48
48-(1);|Cannot refresh Catalog : Connection timed out: connect|#]
[#|2011-02-24T13:14:16.546+0330|WARNING|glassfish3.0.1|com.sun.grizzly.config.Gr
izzlyServiceListener|_ThreadID=17;_ThreadName=Thread-13;|Interrupting idle Threa
d: http-thread-pool-4848-(2)|#]
It seems that Glassfish has a lot of trouble recently caused by the new version 3.1. 似乎Glassfish最近因新版本3.1引起了很多麻烦。 The admin console tries to look for new updates at start-up.
管理控制台会在启动时尝试查找新的更新。 If the update server will not respond in a certain time, the update count fails or take a long time.
如果更新服务器在一定时间内不响应,则更新计数失败或花费很长时间。
You could first try to choose a different update server with glassfishs update tool. 您可以先尝试使用glassfishs更新工具选择其他更新服务器。 You will find it in
glassfish/bin
folder. 您将在
glassfish/bin
文件夹中找到它。
If this doesn't work, you could disable the update module of the glassfish admin console by renaming the file console-updatecenter-plugin.jar
in the folder glassfish/glassfish/modules
. 如果这不起作用,则可以通过重命名文件夹
glassfish/glassfish/modules
中的console-updatecenter-plugin.jar
文件来禁用glassfish管理控制台的更新glassfish/glassfish/modules
。
You could also disable network access from the admin console by adding the following to the JVM-Options of your domain.xml: 您还可以通过将以下内容添加到domain.xml的JVM-Options中来从管理控制台禁用网络访问:
-Dcom.sun.enterprise.tools.admingui.NO_NETWORK=true
-Dcom.sun.enterprise.tools.admingui.NO_NETWORK = true
声明:本站的技术帖子网页,遵循CC BY-SA 4.0协议,如果您需要转载,请注明本站网址或者原文地址。任何问题请咨询:yoyou2525@163.com.