jboss启动常见的错误，希望对你有所帮助！
工具/原料
jboss应用服务器
window操作系统
第一类报错：java.rmi.server.ExportException
1、报错：“java.rmi.server.ExportException:Portalreadyinuse:1098;nestedexceptionis:java.net.BindException:Addressalreadyinuse:JVM_Bind“
2、此错误常在4.2版本中出现。需要修改的文件的路径：jboss-4.2.2.GA\server\default\conf\jboss-service.xml把1098改为其它端口号，直到它成功为止。<attributename="Port">1099</attribute><attributename="RmiPort">1098</attribute>
第二类报错：java.net.BindException
1、报错：“java.net.BindException:Addressalreadyinuse:JVM_Bind:8080需要修改的文件的路径：jboss-4.2.2.GA\server\default\deploy\jboss-web.deployer\server.xml”
2、此错误在各个版本都常见。把8080改为其它端口号，直到它成功为止，修改后一定记得要保存.如安装eclipse插件可以打开服务直接修改Port即可。
第三类报错：Deployment"AttachmentStore"isinerrordueto
1、报错：&qu艺皱麾酪ot;Deployment"AttachmentStore"isinerrordue墉掠载牿to:java.lang.IllegalArgumentException:Wrongarguments.newfortargetjava.lang.reflect.Constructorexpected=[java.net.URI]actual=[java.io.File]"具体：...16:15:28,605ERROR[AbstractKernelController]ErrorinstallingtoInstantiated:name=AttachmentStorestate=Describedjava.lang.IllegalArgumentException:Wrongarguments.newfortargetjava.lang.reflect.Constructorexpected=[java.net.URI]actual=[java.io.File]atorg.jboss.reflect.plugins.introspection.ReflectionUtils.handleErrors(ReflectionUtils.java:395)atorg.jboss.reflect.plugins.introspection.ReflectionUtils.newInstance(ReflectionUtils.java:153)atorg.jboss.reflect.plugins.introspection.ReflectConstructorInfoImpl.newInstance(ReflectConstructorInfoImpl.java:106)atorg.jboss.joinpoint.plugins.BasicConstructorJoinPoint.dispatch(BasicConstructorJoinPoint.java:80)atorg.jboss.aop.microcontainer.integration.AOPConstructorJoinpoint.createTarget(AOPConstructorJoinpoint.java:282)atorg.jboss.aop.microcontainer.integration.AOPConstructorJoinpoint.dispatch(AOPConstructorJoinpoint.java:103)atorg.jboss.kernel.plugins.dependency.KernelControllerContextAction$JoinpointDispatchWrapper.execute(KernelControllerContextAction.java:241)atorg.jboss.kernel.plugins.dependency.ExecutionWrapper.execute(ExecutionWrapper.java:47)atorg.jboss.kernel.plugins.dependency.KernelControllerContextAction.dispatchExecutionWrapper(KernelControllerContextAction.java:109)atorg.jboss.kernel.plugins.dependency.KernelControllerContextAction.dispatchJoinPoint(KernelControllerContextAction.java:70)atorg.jboss.kernel.plugins.dependency.InstantiateAction.installActionInternal(InstantiateAction.java:66)atorg.jboss.kernel.plugins.dependency.InstallsAwareAction.installAction(InstallsAwareAction.java:54)atorg.jboss.kernel.plugins.dependency.InstallsAwareAction.installAction(InstallsAwareAction.java:42)atorg.jboss.dependency.plugins.action.SimpleControllerContextAction.simpleInstallAction(SimpleControllerContextAction.java:62)atorg.jboss.dependency.plugins.action.AccessControllerContextAction.install(AccessControllerContextAction.java:71)atorg.jboss.dependency.plugins.AbstractControllerContextActions.install(AbstractControllerContextActions.java:51)atorg.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:348)atorg.jboss.dependency.plugins.AbstractController.install(AbstractController.java:1631)atorg.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:934)atorg.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1082)atorg.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:984)atorg.jboss.dependency.plugins.AbstractController.install(AbstractController.java:774)atorg.jboss.dependency.plugins.AbstractController.install(AbstractController.java:540)atorg.jboss.kernel.plugins.deployment.AbstractKernelDeployer.deployBean(AbstractKernelDeployer.java:319)atorg.jboss.kernel.plugins.deployment.AbstractKernelDeployer.deployBeans(AbstractKernelDeployer.java:297)atorg.jboss.kernel.plugins.deployment.AbstractKernelDeployer.deploy(AbstractKernelDeployer.java:130)atorg.jboss.kernel.plugins.deployment.BasicKernelDeployer.deploy(BasicKernelDeployer.java:76)atorg.jboss.bootstrap.microcontainer.TempBasicXMLDeployer.deploy(TempBasicXMLDeployer.java:91)atorg.jboss.bootstrap.microcontainer.TempBasicXMLDeployer.deploy(TempBasicXMLDeployer.java:161)atorg.jboss.bootstrap.microcontainer.ServerImpl.doStart(ServerImpl.java:138)atorg.jboss.bootstrap.AbstractServerImpl.start(AbstractServerImpl.java:450)atorg.jboss.Main.boot(Main.java:221)atorg.jboss.Main$1.run(Main.java:556)atjava.lang.Thread.run(Thread.java:619)FailedtobootJBoss:java.lang.IllegalStateException:Incompletelydeployed:DEPLOYMENTSINERROR:Deployment"AttachmentStore"isinerrordueto:java.lang.IllegalArgumentException:Wrongarguments.newfortargetjava.lang.reflect.Constructorexpected=[java.net.URI]actual=[java.io.File]DEPLOYMENTSMISSINGDEPENDENCIES:Deployment"ProfileServicePersistenceDeployer"ismissingthefollowingdependencies:Dependency"AttachmentStore"(shouldbeinstate"Installed",butisactuallyinstate"**ERROR**")Deployment"ProfileServiceDeployer"ismissingthefollowingdependencies:Dependency"AttachmentStore"(shouldbeinstate"Installed",butisactuallyinstate"**ERROR**")Deployment"ProfileService"ismissingthefollowingdependencies:Dependency"ProfileServiceDeployer"(shouldbeinstate"Installed",butisactuallyinstate"Instantiated")Dependency"jboss.kernel:service=KernelController"(shouldbeinstate"Installed",butisactuallyinstate"**ERROR**")Deployment"ProfileServiceBootstrap"ismissingthefollowingdependencies:Dependency"ProfileService"(shouldbeinstate"Installed",butisactuallyinstate"Instantiated")Dependency"jboss.kernel:service=Kernel"(shouldbeinstate"Installed",butisactuallyinstate"**ERROR**")atorg.jboss.kernel.plugins.deployment.AbstractKernelDeployer.internalValidate(AbstractKernelDeployer.java:278)atorg.jboss.kernel.plugins.deployment.AbstractKernelDeployer.validate(AbstractKernelDeployer.java:174)atorg.jboss.bootstrap.microcontainer.ServerImpl.doStart(ServerImpl.java:142)atorg.jboss.bootstrap.AbstractServerImpl.start(AbstractServerImpl.java:450)atorg.jboss.Main.boot(Main.java:221)atorg.jboss.Main$1.run(Main.java:556)atjava.lang.Thread.run(Thread.java:619)16:15:29,515INFO[ServerImpl]Runtimeshutdownhookcalled,forceHalt:true16:15:29,523INFO[ServerImpl]ShutdowncompleteShutdowncompleteHaltingVM
2、此错误常在5.1版本中出现。这个错误是配置文件profile.xml内的一稍僚敉视个bug，文件路径为：$JBOSS_HOME/server/<serverName>/conf/芟鲠阻缒bootstrap/profile.xml把其中的节点：<beanname="AttachmentStore"class="org.jboss.system.server.profileservice.repository.AbstractAttachmentStore"><constructor><parameter><injectbean="BootstrapProfileFactory"property="attachmentStoreRoot"/></parameter></constructor>修改为：<beanname="AttachmentStore"class="org.jboss.system.server.profileservice.repository.AbstractAttachmentStore"><constructor><parameterclass="java.io.File"><injectbean="BootstrapProfileFactory"property="attachmentStoreRoot"/></parameter></constructor>
第四类报错：ERROR[org.jboss.kernel.plugins.dependency.AbstractKernelController](main)ErrorinstallingtoStart
1、报错：&qu艺皱麾酪ot;ERROR[org.jboss.kernel.plugins.dependency.AbstractKern髫潋啜缅elController](main)ErrorinstallingtoStart:name=jboss:service=NamingProviderURLWriterstate=Createmode=ManualrequiredState=Installedjava.io.IOException:Accessisdenied"
2、解决办法：停止windows的IndexingService服务。
第五类报错：启动正常在但是使用JBossTool3.1的插件JBossASTool发布无效(JBoss5.1RuntimeServer发布无效)
1、在默认Runtime路径“workspace\.metadata\.plugins\org.jboss.ide.eclipse.as.core\JBoss_5.1_Runtime_ServerXXX”内可以看到发布的项目，启动JBoss却无法访问发布信息。
2、出现原因：创建JBoss的项目的时候项目物理路径内不能存在空格，比如路径“EjbProject”等带有空格目录的项目发布后将无法被JBoss正确加载解决办法：在开发JBoss的项目时候项目路径一定不要带空格或者其它比较少用的特殊字符，JBoss对路径特别敏感。
查看端口方法
1、第一，二说明端口被其他进程占用了，查看占用进程的方法为：以1098端口为例：1）命令行cmd->netstat-ano|findstr"1098"，得到占用端口1098的pID2）ctrl+alt+del，进入任务管理器，点击“查看‘，选择pid后，查看是那个进程占用的，结束即可
