gpt4 book ai didi

java - Jboss 4.2 无法在 win 7 64 位上启动

转载 作者:行者123 更新时间:2023-12-02 07:27:09 25 4
gpt4 key购买 nike

我有 JBoss-4.2.3.GA,即使我将启动时间和停止时间增加到 500 秒,也无法在给定时间内启动。

我后来尝试了其他版本的 JBOSS 4.2,但它也无法启动。

很久以前(在其他一些系统中)我在 Windows 7 64 位中遇到了类似的问题,为此我更改了 XX:MaxPermSize 解决了该问题。但这在这里没有帮助。

我正在使用 eclipse indigo版本:Indigo 服务版本 2内部版本号:20120216-1857启动服务器。

启动服务器后控制台显示:

13:05:08,325 INFO  [Server] Starting JBoss (MX MicroKernel)...
13:05:08,325 INFO [Server] Release ID: JBoss [Trinity] 4.2.3.GA (build: SVNTag=JBoss_4_2_3_GA date=200807181439)
13:05:08,327 INFO [Server] Home Dir: C:\jboss-4.2.3.GA
13:05:08,327 INFO [Server] Home URL: file:/C:/jboss-4.2.3.GA/
13:05:08,327 INFO [Server] Patch URL: null
13:05:08,327 INFO [Server] Server Name: default
13:05:08,328 INFO [Server] Server Home Dir: C:\jboss-4.2.3.GA\server\default
13:05:08,328 INFO [Server] Server Home URL: file:/C:/jboss-4.2.3.GA/server/default/
13:05:08,328 INFO [Server] Server Log Dir: C:\jboss-4.2.3.GA\server\default\log
13:05:08,328 INFO [Server] Server Temp Dir: C:\jboss-4.2.3.GA\server\default\tmp
13:05:08,328 INFO [Server] Root Deployment Filename: jboss-service.xml
13:05:08,492 INFO [ServerInfo] Java version: 1.6.0_35,Sun Microsystems Inc.
13:05:08,492 INFO [ServerInfo] Java VM: Java HotSpot(TM) 64-Bit Server VM 20.10-b01,Sun Microsystems Inc.
13:05:08,493 INFO [ServerInfo] OS-System: Windows 7 6.1,amd64
13:05:08,728 INFO [Server] Core system initialized
13:05:09,745 INFO [WebService] Using RMI server codebase: http://127.0.0.1:8083/
13:05:09,746 INFO [Log4jService$URLWatchTimerTask] Configuring from URL: resource:jboss-log4j.xml
13:05:09,969 INFO [TransactionManagerService] JBossTS Transaction Service (JTA version) - JBoss Inc.
13:05:09,969 INFO [TransactionManagerService] Setting up property manager MBean and JMX layer
13:05:10,077 INFO [TransactionManagerService] Starting recovery manager
13:05:10,117 INFO [TransactionManagerService] Recovery manager started
13:05:10,117 INFO [TransactionManagerService] Binding TransactionManager JNDI Reference
13:05:11,387 INFO [EJB3Deployer] Starting java:comp multiplexer
13:05:12,542 INFO [NativeServerConfig] JBoss Web Services - Native
13:05:12,542 INFO [NativeServerConfig] jbossws-3.0.1-native-2.0.4.GA (build=200803312044)
13:05:13,070 INFO [Embedded] Catalina naming disabled
13:05:13,149 INFO [AprLifecycleListener] The Apache Tomcat Native library which allows optimal performance in production environments was not found on the java.library.path: C:\Program Files\Java\jre6\bin;C:\Windows\Sun\Java\bin;C:\Windows\system32;C:\Windows;C:\Program Files\Common Files\Microsoft Shared\Windows Live;C:\Program Files (x86)\Common Files\Microsoft Shared\Windows Live;c:\Program Files (x86)\Intel\iCLS Client\;c:\Program Files\Intel\iCLS Client\;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Program Files\Intel\Intel(R) Management Engine Components\DAL;C:\Program Files\Intel\Intel(R) Management Engine Components\IPT;C:\Program Files (x86)\Intel\Intel(R) Management Engine Components\DAL;C:\Program Files (x86)\Intel\Intel(R) Management Engine Components\IPT;C:\Program Files (x86)\Windows Live\Shared.;C:\Program Files\Java\jdk1.6.0_35\bin;C:\Program Files\TortoiseSVN\bin;.
13:05:13,182 INFO [Http11Protocol] Initializing Coyote HTTP/1.1 on http-127.0.0.1-8080
13:05:13,183 INFO [AjpProtocol] Initializing Coyote AJP/1.3 on ajp-127.0.0.1-8009
13:05:13,183 INFO [Catalina] Initialization processed in 113 ms
13:05:13,183 INFO [StandardService] Starting service jboss.web
13:05:13,185 INFO [StandardEngine] Starting Servlet Engine: JBossWeb/2.0.1.GA
13:05:13,215 INFO [Catalina] Server startup in 31 ms
13:05:13,280 INFO [TomcatDeployer] deploy, ctxPath=/, warUrl=.../deploy/jboss-web.deployer/ROOT.war/
13:05:13,602 INFO [TomcatDeployer] deploy, ctxPath=/invoker, warUrl=.../deploy/http-invoker.sar/invoker.war/
13:05:13,714 INFO [TomcatDeployer] deploy, ctxPath=/jbossws, warUrl=.../deploy/jbossws.sar/jbossws-context.war/
13:05:13,819 INFO [TomcatDeployer] deploy, ctxPath=/jbossmq-httpil, warUrl=.../deploy/jms/jbossmq-httpil.sar/jbossmq-httpil.war/
13:05:14,231 INFO [TomcatDeployer] deploy, ctxPath=/web-console, warUrl=.../deploy/management/console-mgr.sar/web-console.war/
13:05:14,510 INFO [MailService] Mail Service bound to java:/Mail
13:05:14,589 INFO [RARDeployment] Required license terms exist, view META-INF/ra.xml in .../deploy/jboss-ha-local-jdbc.rar
13:05:14,607 INFO [RARDeployment] Required license terms exist, view META-INF/ra.xml in .../deploy/jboss-ha-xa-jdbc.rar
13:05:14,625 INFO [RARDeployment] Required license terms exist, view META-INF/ra.xml in .../deploy/jboss-local-jdbc.rar
13:05:14,642 INFO [RARDeployment] Required license terms exist, view META-INF/ra.xml in .../deploy/jboss-xa-jdbc.rar
13:05:14,673 INFO [RARDeployment] Required license terms exist, view META-INF/ra.xml in .../deploy/jms/jms-ra.rar
13:05:14,692 INFO [RARDeployment] Required license terms exist, view META-INF/ra.xml in .../deploy/mail-ra.rar
13:05:14,722 INFO [RARDeployment] Required license terms exist, view META-INF/ra.xml in .../deploy/quartz-ra.rar
13:05:14,730 INFO [QuartzResourceAdapter] start quartz!!!
13:05:14,768 INFO [SimpleThreadPool] Job execution threads will use class loader of thread: main
13:05:14,784 INFO [QuartzScheduler] Quartz Scheduler v.1.5.2 created.
13:05:14,785 INFO [RAMJobStore] RAMJobStore initialized.
13:05:14,785 INFO [StdSchedulerFactory] Quartz scheduler 'DefaultQuartzScheduler' initialized from default resource file in Quartz package: 'quartz.properties'
13:05:14,785 INFO [StdSchedulerFactory] Quartz scheduler version: 1.5.2
13:05:14,785 INFO [QuartzScheduler] Scheduler DefaultQuartzScheduler_$_NON_CLUSTERED started.
13:05:15,309 INFO [ConnectionFactoryBindingService] Bound ConnectionManager 'jboss.jca:service=DataSourceBinding,name=DefaultDS' to JNDI name 'java:DefaultDS'
13:05:15,444 INFO [A] Bound to JNDI name: queue/A
13:05:15,445 INFO [B] Bound to JNDI name: queue/B
13:05:15,446 INFO [C] Bound to JNDI name: queue/C
13:05:15,447 INFO [D] Bound to JNDI name: queue/D
13:05:15,448 INFO [ex] Bound to JNDI name: queue/ex
13:05:15,457 INFO [testTopic] Bound to JNDI name: topic/testTopic
13:05:15,458 INFO [securedTopic] Bound to JNDI name: topic/securedTopic
13:05:15,459 INFO [testDurableTopic] Bound to JNDI name: topic/testDurableTopic
13:05:15,461 INFO [testQueue] Bound to JNDI name: queue/testQueue
13:05:15,479 INFO [UILServerILService] JBossMQ UIL service available at : /127.0.0.1:8093
13:05:15,494 INFO [DLQ] Bound to JNDI name: queue/DLQ
13:05:15,549 INFO [ConnectionFactoryBindingService] Bound ConnectionManager 'jboss.jca:service=ConnectionFactoryBinding,name=JmsXA' to JNDI name 'java:JmsXA'
13:05:15,567 INFO [TomcatDeployer] deploy, ctxPath=/jmx-console, warUrl=.../deploy/jmx-console.war/
13:05:15,688 INFO [Http11Protocol] Starting Coyote HTTP/1.1 on http-127.0.0.1-8080
13:05:15,706 INFO [AjpProtocol] Starting Coyote AJP/1.3 on ajp-127.0.0.1-8009
13:05:15,717 INFO [Server] JBoss (MX MicroKernel) [4.2.3.GA (build: SVNTag=JBoss_4_2_3_GA date=200807181439)] Started in 7s:388ms

它说已开始,但尚未完全开始。

我的服务器概览如下:

Server Configurations

我在 500 秒内遇到与下面相同的错误,但我附加了 10 秒的快照。

Eclipse Message

我将 run.bat、run.conf 文件的内容附加到 Jboss 的 bin 文件夹中:

run.bat

@echo off
rem -------------------------------------------------------------------------
rem JBoss Bootstrap Script for Win32
rem -------------------------------------------------------------------------

rem $Id: run.bat 73584 2008-05-22 12:09:26Z dimitris@jboss.org $

@if not "%ECHO%" == "" echo %ECHO%
@if "%OS%" == "Windows_NT" setlocal

set DIRNAME=.\
if "%OS%" == "Windows_NT" set DIRNAME=%~dp0%
set PROGNAME=run.bat
if "%OS%" == "Windows_NT" set PROGNAME=%~nx0%

pushd %DIRNAME%..
set JBOSS_HOME=%CD%
popd

REM Add bin/native to the PATH if present
if exist "%JBOSS_HOME%\bin\native" set PATH=%JBOSS_HOME%\bin\native;%PATH%
if exist "%JBOSS_HOME%\bin\native" set JAVA_OPTS=%JAVA_OPTS% -Djava.library.path="%PATH%"

rem Find run.jar, or we can't continue

set RUNJAR=%JBOSS_HOME%\bin\run.jar
if exist "%RUNJAR%" goto FOUND_RUN_JAR
echo Could not locate %RUNJAR%. Please check that you are in the
echo bin directory when running this script.
goto END

:FOUND_RUN_JAR

if not "%JAVA_HOME%" == "" goto ADD_TOOLS

set JAVA=java

echo JAVA_HOME is not set. Unexpected results may occur.
echo Set JAVA_HOME to the directory of your local JDK to avoid this message.
goto SKIP_TOOLS

:ADD_TOOLS

set JAVA=%JAVA_HOME%\bin\java

rem A full JDK with toos.jar is not required anymore since jboss web packages
rem the eclipse jdt compiler and javassist has its own internal compiler.
if not exist "%JAVA_HOME%\lib\tools.jar" goto SKIP_TOOLS

rem If exists, point to the JDK javac compiler in case the user wants to
rem later override the eclipse jdt compiler for compiling JSP pages.
set JAVAC_JAR=%JAVA_HOME%\lib\tools.jar

:SKIP_TOOLS

rem If JBOSS_CLASSPATH or JAVAC_JAR is empty, don't include it, as this will
rem result in including the local directory in the classpath, which makes
rem error tracking harder.
if not "%JAVAC_JAR%" == "" set RUNJAR=%JAVAC_JAR%;%RUNJAR%
if "%JBOSS_CLASSPATH%" == "" set RUN_CLASSPATH=%RUNJAR%
if "%RUN_CLASSPATH%" == "" set RUN_CLASSPATH=%JBOSS_CLASSPATH%;%RUNJAR%

set JBOSS_CLASSPATH=%RUN_CLASSPATH%

rem Setup JBoss specific properties
set JAVA_OPTS=%JAVA_OPTS% -Dprogram.name=%PROGNAME%

rem Add -server to the JVM options, if supported
"%JAVA%" -server -version 2>&1 | findstr /I hotspot > nul
if not errorlevel == 1 (set JAVA_OPTS=%JAVA_OPTS% -server)

rem JVM memory allocation pool parameters. Modify as appropriate.
set JAVA_OPTS=%JAVA_OPTS% -Xms128m -Xmx512m -XX:PermSize=256m -XX:MaxPermSize=512m

rem With Sun JVMs reduce the RMI GCs to once per hour
set JAVA_OPTS=%JAVA_OPTS% -Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000

rem JPDA options. Uncomment and modify as appropriate to enable remote debugging.
rem set JAVA_OPTS=-Xdebug -Xrunjdwp:transport=dt_socket,address=8787,server=y,suspend=y %JAVA_OPTS%

rem Setup the java endorsed dirs
set JBOSS_ENDORSED_DIRS=%JBOSS_HOME%\lib\endorsed

echo ===============================================================================
echo.
echo JBoss Bootstrap Environment
echo.
echo JBOSS_HOME: %JBOSS_HOME%
echo.
echo JAVA: %JAVA%
echo.
echo JAVA_OPTS: %JAVA_OPTS%
echo.
echo CLASSPATH: %JBOSS_CLASSPATH%
echo.
echo ===============================================================================
echo.

:RESTART
"%JAVA%" %JAVA_OPTS% ^
-Djava.endorsed.dirs="%JBOSS_ENDORSED_DIRS%" ^
-classpath "%JBOSS_CLASSPATH%" ^
org.jboss.Main %*

if ERRORLEVEL 10 goto RESTART

:END
if "%NOPAUSE%" == "" pause

:END_NO_PAUSE

run.conf

## -*- shell-script -*- ######################################################
## ##
## JBoss Bootstrap Script Configuration ##
## ##
##############################################################################

### $Id: run.conf 62747 2007-05-02 17:43:36Z dimitris@jboss.org $

#
# This file is optional; it may be removed if not needed.
#

#
# Specify the maximum file descriptor limit, use "max" or "maximum" to use
# the default, as queried by the system.
#
# Defaults to "maximum"
#
#MAX_FD="maximum"

#
# Specify the profiler configuration file to load.
#
# Default is to not load profiler configuration file.
#
#PROFILER=""

#
# Specify the location of the Java home directory. If set then $JAVA will
# be defined to $JAVA_HOME/bin/java, else $JAVA will be "java".
#
#JAVA_HOME="/opt/java/jdk"

#
# Specify the exact Java VM executable to use.
#
#JAVA=""

#
# Specify options to pass to the Java VM.
#
if [ "x$JAVA_OPTS" = "x" ]; then
JAVA_OPTS="-Xms128m -Xmx512m -XX:PermSize=256m -XX:MaxPermSize=512m -Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000"
fi

# Sample JPDA settings for remote socket debuging
#JAVA_OPTS="$JAVA_OPTS -Xrunjdwp:transport=dt_socket,address=8787,server=y,suspend=n"

# Sample JPDA settings for shared memory debugging
#JAVA_OPTS="$JAVA_OPTS -Xrunjdwp:transport=dt_shmem,server=y,suspend=n,address=jboss"

请帮助我解决此问题,以便我可以开始在我的服务器上工作。

最佳答案

查看日志中的行:

13:05:13,182 INFO [Http11Protocol] 在 http-127.0.0.1-8080 上初始化 Coyote HTTP/1.1。

它表明http监听端口8080(而不是端口8090),所以你应该通过地址localhost:8080访问。

你在哪里配置了http端口?您不应该直接更改服务的端口,而应使用 JBoss 服务绑定(bind)集,请记住 JBoss 打开多个端口,因此为了避免端口冲突,您应该全部更改。

检查:https://community.jboss.org/wiki/ConfiguringMultipleJBossInstancesOnOneMachine

更新:您发布的 Eclipse 屏幕不会更改 JBoss 的端口,Elcipse 使用它来了解 Jboss http 正在监听的位置,因此您并没有真正更改 JBoss 中的端口。

另一方面,由于端口问题,如果您从 Eclipse 启动 JBoss 服务器,则必须增加 Eclipse 等待 JBoss 启动的时间(如果 JBoss 花费的时间比“Server timeout delay”更长) Eclipse 中服务器的属性,它将返回错误)。

关于java - Jboss 4.2 无法在 win 7 64 位上启动,我们在Stack Overflow上找到一个类似的问题: https://stackoverflow.com/questions/13393410/

25 4 0
Copyright 2021 - 2024 cfsdn All Rights Reserved 蜀ICP备2022000587号
广告合作:1813099741@qq.com 6ren.com