19:31:27,953 INFO [ServerImpl] Starting JBoss (Microcontainer)...
19:31:27,953 INFO [ServerImpl] Release ID: JBoss [Morpheus] 5.0.1.GA (build: SVNTag=JBoss_5_0_1_GA date=200902231221)
19:31:27,953 INFO [ServerImpl] Bootstrap URL: null
19:31:27,953 INFO [ServerImpl] Home Dir: E:\jboss-5.0.1.GA
19:31:27,953 INFO [ServerImpl] Home URL: file:/E:/jboss-5.0.1.GA/
19:31:27,953 INFO [ServerImpl] Library URL: file:/E:/jboss-5.0.1.GA/lib/
19:31:27,953 INFO [ServerImpl] Patch URL: null
19:31:27,953 INFO [ServerImpl] Common Base URL: file:/E:/jboss-5.0.1.GA/common/
19:31:27,968 INFO [ServerImpl] Common Library URL: file:/E:/jboss-5.0.1.GA/common/lib/
19:31:27,968 INFO [ServerImpl] Server Name: default
19:31:27,968 INFO [ServerImpl] Server Base Dir: E:\jboss-5.0.1.GA\server
19:31:27,968 INFO [ServerImpl] Server Base URL: file:/E:/jboss-5.0.1.GA/server/
19:31:27,968 INFO [ServerImpl] Server Config URL: file:/E:/jboss-5.0.1.GA/server/default/conf/
19:31:27,968 INFO [ServerImpl] Server Home Dir: E:\jboss-5.0.1.GA\server\default
19:31:27,968 INFO [ServerImpl] Server Home URL: file:/E:/jboss-5.0.1.GA/server/default/
19:31:27,984 INFO [ServerImpl] Server Data Dir: E:\jboss-5.0.1.GA\server\default\data
19:31:27,984 INFO [ServerImpl] Server Library URL: file:/E:/jboss-5.0.1.GA/server/default/lib/
19:31:27,984 INFO [ServerImpl] Server Log Dir: E:\jboss-5.0.1.GA\server\default\log
19:31:27,984 INFO [ServerImpl] Server Native Dir: E:\jboss-5.0.1.GA\server\default\tmp\native
19:31:27,984 INFO [ServerImpl] Server Temp Dir: E:\jboss-5.0.1.GA\server\default\tmp
19:31:27,984 INFO [ServerImpl] Server Temp Deploy Dir: E:\jboss-5.0.1.GA\server\default\tmp\deploy
19:31:29,140 INFO [ServerImpl] Starting Microcontainer, bootstrapURL=file:/E:/jboss-5.0.1.GA/server/default/conf/bootstrap.xml
19:31:30,078 INFO [VFSCacheFactory] Initializing VFSCache [org.jboss.virtual.plugins.cache.CombinedVFSCache]
19:31:30,078 INFO [VFSCacheFactory] Using VFSCache [CombinedVFSCache[real-cache: null]]
19:31:30,515 INFO [CopyMechanism] VFS temp dir: E:\jboss-5.0.1.GA\server\default\tmp
19:31:30,640 INFO [ZipEntryContext] VFS force nested jars copy-mode is enabled.
19:31:32,265 INFO [ServerInfo] Java version: 1.5.0_09,Sun Microsystems Inc.
19:31:32,265 INFO [ServerInfo] Java Runtime: Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_09-b01)
19:31:32,265 INFO [ServerInfo] Java VM: Java HotSpot(TM) Client VM 1.5.0_09-b01,Sun Microsystems Inc.
19:31:32,265 INFO [ServerInfo] OS-System: Windows XP 5.1,x86
19:31:32,312 INFO [JMXKernel] Legacy JMX core initialized
19:31:35,125 INFO [ProfileServiceImpl] Loading profile: default from: org.jboss.system.server.profileservice.repository.SerializableDeploymentRepository@61a414(root=E:\jboss-5.0.1.GA\server, key=org.jboss.profileservice.spi.ProfileKey@143b82c3[domain=default,server=default,name=default])
19:31:35,125 INFO [ProfileImpl] Using repository:org.jboss.system.server.profileservice.repository.SerializableDeploymentRepository@61a414(root=E:\jboss-5.0.1.GA\server, key=org.jboss.profileservice.spi.ProfileKey@143b82c3[domain=default,server=default,name=default])
19:31:35,125 INFO [ProfileServiceImpl] Loaded profile: ProfileImpl@7a3a30{key=org.jboss.profileservice.spi.ProfileKey@143b82c3[domain=default,server=default,name=default]}
19:31:37,203 INFO [WebService] Using RMI server codebase: http://127.0.0.1:8083/
19:31:48,625 INFO [NativeServerConfig] JBoss Web Services - Stack Native Core
19:31:48,625 INFO [NativeServerConfig] 3.0.5.GA
19:32:13,765 ERROR [AbstractKernelController] Error installing to Parse: name=vfszip:/E:/jboss-5.0.1.GA/server/default/deploy/agentsystem.war/ state=Not Installed mode=Manual requiredState=Parse
org.jboss.deployers.spi.DeploymentException: Error creating managed object for vfszip:/E:/jboss-5.0.1.GA/server/default/deploy/agentsystem.war/
at org.jboss.deployers.spi.DeploymentException.rethrowAsDeploymentException(DeploymentException.java:49)
at org.jboss.deployers.spi.deployer.helpers.AbstractParsingDeployerWithOutput.createMetaData(AbstractParsingDeployerWithOutput.java:337)
at org.jboss.deployers.spi.deployer.helpers.AbstractParsingDeployerWithOutput.createMetaData(AbstractParsingDeployerWithOutput.java:297)
at org.jboss.deployers.spi.deployer.helpers.AbstractParsingDeployerWithOutput.createMetaData(AbstractParsingDeployerWithOutput.java:269)
at org.jboss.deployers.spi.deployer.helpers.AbstractParsingDeployerWithOutput.deploy(AbstractParsingDeployerWithOutput.java:230)
at org.jboss.deployers.plugins.deployers.DeployerWrapper.deploy(DeployerWrapper.java:171)
at org.jboss.deployers.plugins.deployers.DeployersImpl.doDeploy(DeployersImpl.java:1439)
at org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersImpl.java:1157)
at org.jboss.deployers.plugins.deployers.DeployersImpl.install(DeployersImpl.java:1098)
at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:348)
at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:1598)
at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:934)
at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1062)
at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:984)
at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:822)
at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:553)
at org.jboss.deployers.plugins.deployers.DeployersImpl.process(DeployersImpl.java:781)
at org.jboss.deployers.plugins.main.MainDeployerImpl.process(MainDeployerImpl.java:698)
at org.jboss.system.server.profileservice.ProfileServiceBootstrap.loadProfile(ProfileServiceBootstrap.java:304)
at org.jboss.system.server.profileservice.ProfileServiceBootstrap.start(ProfileServiceBootstrap.java:205)
at org.jboss.bootstrap.AbstractServerImpl.start(AbstractServerImpl.java:405)
at org.jboss.Main.boot(Main.java:209)
at org.jboss.Main$1.run(Main.java:547)
at java.lang.Thread.run(Thread.java:595)
Caused by: java.net.ConnectException: Connection refused: connect
at java.net.PlainSocketImpl.socketConnect(Native Method)
at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:333)
at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:195)
at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:182)
at java.net.Socket.connect(Socket.java:516)
at java.net.Socket.connect(Socket.java:466)
at sun.net.NetworkClient.doConnect(NetworkClient.java:157)
at sun.net.www.http.HttpClient.openServer(HttpClient.java:365)
at sun.net.www.http.HttpClient.openServer(HttpClient.java:477)
at sun.net.www.http.HttpClient.<init>(HttpClient.java:214)
at sun.net.www.http.HttpClient.New(HttpClient.java:287)
at sun.net.www.http.HttpClient.New(HttpClient.java:299)
at sun.net.www.protocol.http.HttpURLConnection.getNewHttpClient(HttpURLConnection.java:796)
at sun.net.www.protocol.http.HttpURLConnection.plainConnect(HttpURLConnection.java:748)
at sun.net.www.protocol.http.HttpURLConnection.connect(HttpURLConnection.java:673)
at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:917)
at org.apache.xerces.impl.XMLEntityManager.setupCurrentEntity(Unknown Source)
at org.apache.xerces.impl.XMLEntityManager.startEntity(Unknown Source)
at org.apache.xerces.impl.XMLEntityManager.startDTDEntity(Unknown Source)
at org.apache.xerces.impl.XMLDTDScannerImpl.setInputSource(Unknown Source)
at org.apache.xerces.impl.XMLDocumentScannerImpl$DTDDispatcher.dispatch(Unknown Source)
at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source)
at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
at org.apache.xerces.parsers.DOMParser.parse(Unknown Source)
at org.apache.xerces.jaxp.DocumentBuilderImpl.parse(Unknown Source)
at org.jboss.deployers.vfs.spi.deployer.JAXPDeployer.doParse(JAXPDeployer.java:196)
at org.jboss.deployers.vfs.spi.deployer.JAXPDeployer.parse(JAXPDeployer.java:167)
at org.jboss.deployers.vfs.spi.deployer.AbstractVFSParsingDeployer.handleMultipleFiles(AbstractVFSParsingDeployer.java:328)
at org.jboss.deployers.vfs.spi.deployer.AbstractVFSParsingDeployer.parse(AbstractVFSParsingDeployer.java:241)
at org.jboss.deployers.spi.deployer.helpers.AbstractParsingDeployerWithOutput.createMetaData(AbstractParsingDeployerWithOutput.java:330)
... 22 more
19:32:25,781 INFO [JMXConnectorServerService] JMX Connector server: service:jmx:rmi://127.0.0.1/jndi/rmi://127.0.0.1:1090/jmxconnector
19:32:27,109 INFO [MailService] Mail Service bound to java:/Mail
19:32:30,312 WARN [JBossASSecurityMetadataStore] WARNING! POTENTIAL SECURITY RISK. It has been detected that the MessageSucker component which sucks messages from one node to another has not had its password changed from the installation default. Please see the JBoss Messaging user guide for instructions on how to do this.
19:32:30,343 WARN [AnnotationCreator] No ClassLoader provided, using TCCL: org.jboss.managed.api.annotation.ManagementComponent
19:32:30,562 INFO [TransactionManagerService] JBossTS Transaction Service (JTA version) - JBoss Inc.
19:32:30,562 INFO [TransactionManagerService] Setting up property manager MBean and JMX layer
19:32:30,890 INFO [TransactionManagerService] Initializing recovery manager
19:32:31,078 INFO [TransactionManagerService] Recovery manager configured
19:32:31,078 INFO [TransactionManagerService] Binding TransactionManager JNDI Reference
19:32:31,140 INFO [TransactionManagerService] Starting transaction recovery manager
19:32:32,046 INFO [Http11Protocol] Initializing Coyote HTTP/1.1 on http-127.0.0.1-8080
19:32:32,062 INFO [AjpProtocol] Initializing Coyote AJP/1.3 on ajp-127.0.0.1-8009
19:32:32,062 INFO [StandardService] Starting service jboss.web
19:32:32,062 INFO [StandardEngine] Starting Servlet Engine: JBoss Web/2.1.2.GA
19:32:32,187 INFO [Catalina] Server startup in 261 ms
19:32:32,218 INFO [TomcatDeployment] deploy, ctxPath=/invoker
19:32:34,031 INFO [TomcatDeployment] deploy, ctxPath=/web-console
19:32:34,500 INFO [TomcatDeployment] deploy, ctxPath=/jbossws
19:32:34,718 INFO [RARDeployment] Required license terms exist, view vfszip:/E:/jboss-5.0.1.GA/server/default/deploy/jboss-local-jdbc.rar/META-INF/ra.xml
19:32:34,765 INFO [RARDeployment] Required license terms exist, view vfszip:/E:/jboss-5.0.1.GA/server/default/deploy/jboss-xa-jdbc.rar/META-INF/ra.xml
19:32:34,828 INFO [RARDeployment] Required license terms exist, view vfszip:/E:/jboss-5.0.1.GA/server/default/deploy/jms-ra.rar/META-INF/ra.xml
19:32:34,875 INFO [RARDeployment] Required license terms exist, view vfszip:/E:/jboss-5.0.1.GA/server/default/deploy/mail-ra.rar/META-INF/ra.xml
19:32:34,937 INFO [RARDeployment] Required license terms exist, view vfszip:/E:/jboss-5.0.1.GA/server/default/deploy/quartz-ra.rar/META-INF/ra.xml
19:32:35,109 INFO [SimpleThreadPool] Job execution threads will use class loader of thread: main
19:32:35,156 INFO [QuartzScheduler] Quartz Scheduler v.1.5.2 created.
19:32:35,156 INFO [RAMJobStore] RAMJobStore initialized.
19:32:35,156 INFO [StdSchedulerFactory] Quartz scheduler 'DefaultQuartzScheduler' initialized from default resource file in Quartz package: 'quartz.properties'
19:32:35,156 INFO [StdSchedulerFactory] Quartz scheduler version: 1.5.2
19:32:35,156 INFO [QuartzScheduler] Scheduler DefaultQuartzScheduler_$_NON_CLUSTERED started.
19:32:36,015 INFO [ConnectionFactoryBindingService] Bound ConnectionManager 'jboss.jca:service=DataSourceBinding,name=DefaultDS' to JNDI name 'java:DefaultDS'
19:32:36,656 INFO [ServerPeer] JBoss Messaging 1.4.1.GA server [0] started
19:32:36,812 INFO [QueueService] Queue[/queue/DLQ] started, fullSize=200000, pageSize=2000, downCacheSize=2000
19:32:36,906 INFO [ConnectionFactory] Connector bisocket://127.0.0.1:4457 has leasing enabled, lease period 10000 milliseconds
19:32:36,906 INFO [ConnectionFactory] org.jboss.jms.server.connectionfactory.ConnectionFactory@400552 started
19:32:36,906 INFO [ConnectionFactory] Connector bisocket://127.0.0.1:4457 has leasing enabled, lease period 10000 milliseconds
19:32:36,906 INFO [ConnectionFactory] org.jboss.jms.server.connectionfactory.ConnectionFactory@113a03d started
19:32:36,921 INFO [QueueService] Queue[/queue/ExpiryQueue] started, fullSize=200000, pageSize=2000, downCacheSize=2000
19:32:36,921 WARN [ConnectionFactoryJNDIMapper] supportsFailover attribute is true on connection factory: jboss.messaging.connectionfactory:service=ClusteredConnectionFactory but post office is non clustered. So connection factory will *not* support failover
19:32:36,921 WARN [ConnectionFactoryJNDIMapper] supportsLoadBalancing attribute is true on connection factory: jboss.messaging.connectionfactory:service=ClusteredConnectionFactory but post office is non clustered. So connection factory will *not* support load balancing
19:32:36,921 INFO [ConnectionFactory] Connector bisocket://127.0.0.1:4457 has leasing enabled, lease period 10000 milliseconds
19:32:36,921 INFO [ConnectionFactory] org.jboss.jms.server.connectionfactory.ConnectionFactory@4fc8a7 started
19:32:37,953 INFO [ConnectionFactoryBindingService] Bound ConnectionManager 'jboss.jca:service=ConnectionFactoryBinding,name=JmsXA' to JNDI name 'java:JmsXA'
19:32:38,000 INFO [TomcatDeployment] deploy, ctxPath=/
19:32:38,140 INFO [TomcatDeployment] deploy, ctxPath=/jmx-console
19:32:38,265 ERROR [ProfileServiceBootstrap] Failed to load profile: Summary of incomplete deployments (SEE PREVIOUS ERRORS FOR DETAILS):
DEPLOYMENTS IN ERROR:
Deployment "vfszip:/E:/jboss-5.0.1.GA/server/default/deploy/agentsystem.war/" is in error due to the following reason(s): java.net.ConnectException: Connection refused: connect
19:32:38,281 INFO [Http11Protocol] Starting Coyote HTTP/1.1 on http-127.0.0.1-8080
19:32:38,312 INFO [AjpProtocol] Starting Coyote AJP/1.3 on ajp-127.0.0.1-8009
19:32:38,328 INFO [ServerImpl] JBoss (Microcontainer) [5.0.1.GA (build: SVNTag=JBoss_5_0_1_GA date=200902231221)] Started in 1m:10s:344ms
</init>
相关推荐
NULL 博文链接:https://zhangxing119.iteye.com/blog/691383
在JBoss中部署应用程序相当直观,只需要将部署单元复制到对应的部署目录(例如server/default/deploy)。JBoss会持续监控该目录,一旦发现新文件,就会自动进行部署。部署的文件可以是EJB JARs、Web应用WARs、企业...
在部署 Jboss 项目时,需要启动 Jboss 服务器,以便 Jboss 服务器可以正确地运行项目。 九、测试 在部署 Jboss 项目时,需要测试项目,以便确保项目可以正确地运行。在测试时,需要输入项目的 URL,以便访问项目的...
JBossTools实践系列:JBossESB服务开发入门
赠送jar包:jboss-logging-3.4.1.Final.jar; 赠送原API文档:jboss-logging-3.4.1.Final-javadoc.jar; 赠送源代码:jboss-logging-3.4.1.Final-sources.jar; 赠送Maven依赖信息文件:jboss-logging-3.4.1.Final....
Linux下JBOSS部署手册
赠送jar包:jboss-logging-3.4.3.Final.jar; 赠送原API文档:jboss-logging-3.4.3.Final-javadoc.jar; 赠送源代码:jboss-logging-3.4.3.Final-sources.jar; 赠送Maven依赖信息文件:jboss-logging-3.4.3.Final....
3. **启用自动启动**:如果jar包没有自动启动,可以在部署目录下创建一个与其同名的`.deployment`文件,使JBOSS在启动时识别并加载该应用,例如: ``` echo. > %JBOSS_HOME%\standalone\deployments\myapp.jar....
jboss热部署,jboss热部署,jboss热部署,jboss热部署,jboss热部署,jboss热部署,jboss热部署,jboss热部署,jboss热部署,jboss热部署,jboss热部署,jboss热部署
这意味着在JBoss部署时,会先启动这个EJB耳朵文件中的所有服务,然后再启动包含`jboss-web.xml`的Web应用,确保了正确的启动顺序。 除了`<depends>`元素,JBoss还提供了`<depends-on>`元素,两者略有不同。`...
可以尝试在`jboss-app.xml`文件中将`loader-repository`设置为`jboss.web.deployment:loader-repository-class=org.jboss.web.tomcat.service.loader.HotDeployClassLoaderRepository`,以使用JBoss的热部署类加载器...
在本文中,我们将深入探讨JBoss的启动过程及其相关知识点。 1. **JBoss目录结构**: JBoss的安装目录包含多个子目录,如`bin`、`server`、`deploy`等。`bin`目录下有启动和停止服务器的脚本,`server`目录则包含了...
【JBOSS,JBoss安装部署】 JBoss是Red Hat公司开发的一款开源的应用服务器,它基于Java EE(Enterprise Edition)规范,提供了全面的企业级应用程序部署和管理解决方案。本篇文章将详细讲解JBoss的安装和部署过程,...
jboss7开发部署详细文档 jboss7是一个基于Java EE的应用服务器,提供了一个强大且灵活的平台来开发和部署企业级应用程序。本文档旨在指导开发者如何在jboss7上进行开发和部署, 并且介绍了如何将jboss4.2版本平滑地...
1. 安装JBoss:首先,你需要下载并安装适合版本的JBoss应用服务器,确保其运行正常。 2. EJB项目准备:创建一个包含EJB组件的Maven或Gradle项目,遵循Java EE规范,编写EJB接口、实现类以及相应的部署描述符(ejb-...
3. **重新部署**:有时,简单地停止和重新启动服务器,或者重新部署整个项目是解决问题的有效方法。 4. **检查部署配置**:确保Eclipse的部署配置与实际的项目结构匹配,且部署路径正确无误。 5. **更新JBoss版本*...
在Jboss应用服务器中,启动报错Failed to parse WEB-INF/web.xml; - nested throwable是一种常见的错误,本文将对此错误进行深入分析,并提供解决方案。 错误原因 Jboss应用服务器在启动时,会对WEB-INF目录下的...
2. **连接数据库**:使用`Class.forName()`方法注册驱动,然后通过`DriverManager.getConnection()`方法建立与数据库的连接。 ```java Class.forName("oracle.jdbc.driver.OracleDriver"); Connection conn = ...
描述了apache jboss3.2.6做负载均衡(load balance)的部署细节以及一些常见错误说明;描述了部署jboss3.2.3/3.2.6时一些心得、常用配置项。 目 录 1 .Apache2.0及连接器jk1.2的编译部署 4 1.1下载相关软件包 ...
"在IntelliJ IDEA 8中部署Jboss服务器图解" IntelliJ IDEA 8是 JetBrains 公司开发的一款功能强大且灵活的集成开发环境(IDE),它支持多种programming语言,包括Java、Python、Ruby、PHP等。Jboss则是一款流行的...