JBoss启动异常——常见错误

转自：https://jingyan.baidu.com/article/db55b609e596654ba20a2f58.html

初学习jboss，遇到一些问题，转载一些好东西收藏着。

工具/原料

• jboss应用服务器
• window操作系统

第一类报错：java.rmi.server.ExportException

• 报错：“java.rmi.server.ExportException: Port already in use: 1098; nested exception is:  java.net.BindException: Address already in use: JVM_Bind“

• 此错误常在4.2版本中出现。

  需要修改的文件的路径：jboss-4.2.2.GA\server\default\conf\jboss-service.xml   把1098改为其它端口号，直到它成功为止。

  1099

  1098

  END

第二类报错：java.net.BindException

• 报错：“java.net.BindException: Address already in use: JVM_Bind:8080

  需要修改的文件的路径：jboss-4.2.2.GA\server\default\deploy\jboss-web.deployer\server.xml”

• 此错误在各个版本都常见。

  把8080改为其它端口号，直到它成功为止，修改后一定记得要保存.如安装eclipse插件可以打开服务直接修改Port即可。

  END

第三类报错：Deployment "AttachmentStore" is in error due to

• 报错："Deployment "AttachmentStore" is in error due to: java.lang.IllegalArgumentException: Wrong arguments. new for target java.lang.reflect.Constructor expected=[java.net.URI] actual=[java.io.File]"

  具体：

  ...

  16:15:28,605 ERROR [AbstractKernelController] Error installing to Instantiated: name=AttachmentStore state=Described  

  java.lang.IllegalArgumentException: Wrong arguments. new for target java.lang.reflect.Constructor expected=[java.net.URI] actual=[java.io.File]   

      at org.jboss.reflect.plugins.introspection.ReflectionUtils.handleErrors(ReflectionUtils.java:395)   

      at org.jboss.reflect.plugins.introspection.ReflectionUtils.newInstance(ReflectionUtils.java:153)   

      at org.jboss.reflect.plugins.introspection.ReflectConstructorInfoImpl.newInstance(ReflectConstructorInfoImpl.java:106)   

      at org.jboss.joinpoint.plugins.BasicConstructorJoinPoint.dispatch(BasicConstructorJoinPoint.java:80)   

      at org.jboss.aop.microcontainer.integration.AOPConstructorJoinpoint.createTarget(AOPConstructorJoinpoint.java:282)   

      at org.jboss.aop.microcontainer.integration.AOPConstructorJoinpoint.dispatch(AOPConstructorJoinpoint.java:103)   

      at org.jboss.kernel.plugins.dependency.KernelControllerContextAction$JoinpointDispatchWrapper.execute(KernelControllerContextAction.java:241)   

      at org.jboss.kernel.plugins.dependency.ExecutionWrapper.execute(ExecutionWrapper.java:47)   

      at org.jboss.kernel.plugins.dependency.KernelControllerContextAction.dispatchExecutionWrapper(KernelControllerContextAction.java:109)   

      at org.jboss.kernel.plugins.dependency.KernelControllerContextAction.dispatchJoinPoint(KernelControllerContextAction.java:70)   

      at org.jboss.kernel.plugins.dependency.InstantiateAction.installActionInternal(InstantiateAction.java:66)   

      at org.jboss.kernel.plugins.dependency.InstallsAwareAction.installAction(InstallsAwareAction.java:54)   

      at org.jboss.kernel.plugins.dependency.InstallsAwareAction.installAction(InstallsAwareAction.java:42)   

      at org.jboss.dependency.plugins.action.SimpleControllerContextAction.simpleInstallAction(SimpleControllerContextAction.java:62)   

      at org.jboss.dependency.plugins.action.AccessControllerContextAction.install(AccessControllerContextAction.java:71)   

      at org.jboss.dependency.plugins.AbstractControllerContextActions.install(AbstractControllerContextActions.java:51)   

      at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:348)   

      at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:1631)   

      at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:934)   

      at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1082)   

      at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:984)   

      at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:774)   

      at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:540)   

      at org.jboss.kernel.plugins.deployment.AbstractKernelDeployer.deployBean(AbstractKernelDeployer.java:319)   

      at org.jboss.kernel.plugins.deployment.AbstractKernelDeployer.deployBeans(AbstractKernelDeployer.java:297)   

      at org.jboss.kernel.plugins.deployment.AbstractKernelDeployer.deploy(AbstractKernelDeployer.java:130)   

      at org.jboss.kernel.plugins.deployment.BasicKernelDeployer.deploy(BasicKernelDeployer.java:76)   

      at org.jboss.bootstrap.microcontainer.TempBasicXMLDeployer.deploy(TempBasicXMLDeployer.java:91)   

      at org.jboss.bootstrap.microcontainer.TempBasicXMLDeployer.deploy(TempBasicXMLDeployer.java:161)   

      at org.jboss.bootstrap.microcontainer.ServerImpl.doStart(ServerImpl.java:138)   

      at org.jboss.bootstrap.AbstractServerImpl.start(AbstractServerImpl.java:450)   

      at org.jboss.Main.boot(Main.java:221)   

      at org.jboss.Main$1.run(Main.java:556)   

      at java.lang.Thread.run(Thread.java:619)   

  Failed to boot JBoss:   

  java.lang.IllegalStateException: Incompletely deployed:   

    

  DEPLOYMENTS IN ERROR:   

    Deployment "AttachmentStore" is in error due to: java.lang.IllegalArgumentException: Wrong arguments. new for target java.lang.reflect.Constructor expected=[java.net.URI] actual=[java.io.File]   

    

  DEPLOYMENTS MISSING DEPENDENCIES:   

    Deployment "ProfileServicePersistenceDeployer" is missing the following dependencies:   

      Dependency "AttachmentStore" (should be in state "Installed", but is actually in state "**ERROR**")   

    Deployment "ProfileServiceDeployer" is missing the following dependencies:   

      Dependency "AttachmentStore" (should be in state "Installed", but is actually in state "**ERROR**")   

    Deployment "ProfileService" is missing the following dependencies:   

      Dependency "ProfileServiceDeployer" (should be in state "Installed", but is actually in state "Instantiated")   

      Dependency "jboss.kernel:service=KernelController" (should be in state "Installed", but is actually in state "**ERROR**")   

    Deployment "ProfileServiceBootstrap" is missing the following dependencies:   

      Dependency "ProfileService" (should be in state "Installed", but is actually in state "Instantiated")   

      Dependency "jboss.kernel:service=Kernel" (should be in state "Installed", but is actually in state "**ERROR**")   

    

      at org.jboss.kernel.plugins.deployment.AbstractKernelDeployer.internalValidate(AbstractKernelDeployer.java:278)   

      at org.jboss.kernel.plugins.deployment.AbstractKernelDeployer.validate(AbstractKernelDeployer.java:174)   

      at org.jboss.bootstrap.microcontainer.ServerImpl.doStart(ServerImpl.java:142)   

      at org.jboss.bootstrap.AbstractServerImpl.start(AbstractServerImpl.java:450)   

      at org.jboss.Main.boot(Main.java:221)   

      at org.jboss.Main$1.run(Main.java:556)   

      at java.lang.Thread.run(Thread.java:619)   

  16:15:29,515 INFO  [ServerImpl] Runtime shutdown hook called, forceHalt: true  

  16:15:29,523 INFO  [ServerImpl] Shutdown complete   

  Shutdown complete   

  Halting VM  

• 此错误常在5.1版本中出现。

  这个错误是配置文件profile.xml内的一个bug，文件路径为：$JBOSS_HOME/server//conf/bootstrap/profile.xml

  把其中的节点：

   

  修改为：

   

  END

第四类报错：ERROR [org.jboss.kernel.plugins.dependency.AbstractKernelController] (main) Error installing to Start

• 报错："ERROR [org.jboss.kernel.plugins.dependency.AbstractKernelController] (main) Error installing to Start: name=jboss:service=NamingProviderURLWriter state=Create mode=Manual requiredState=Installed

  java.io.IOException: Access is denied"

• 解决办法：停止windows的Indexing Service服务。

  END

第五类报错：启动正常在但是使用JBoss Tool3.1的插件JBossAS Tool发布无效(JBoss5.1 Runtime Server发布无效)

• 在默认Runtime路径“workspace\.metadata\.plugins\org.jboss.ide.eclipse.as.core\JBoss_5.1_Runtime_ServerXXX”内可以看到发布的项目，启动JBoss却无法访问发布信息。

• 出现原因：创建JBoss的项目的时候项目物理路径内不能存在空格，比如路径“Ejb Project”等带有空格目录的项目发布后将无法被JBoss正确加载

  解决办法：在开发JBoss的项目时候项目路径一定不要带空格或者其它比较少用的特殊字符，JBoss对路径特别敏感。

  END

查看端口方法

1. 第一，二说明端口被其他进程占用了，查看占用进程的方法为：

   以1098端口为例：

   1）命令行cmd -> netstat -ano | findstr "1098"，得到占用端口1098的pID

   2）ctrl+alt+del，进入任务管理器，点击“查看‘，选择pid后，查看是那个进程占用的，结束即可

   
   END

注意事项

直接查看占用端口进程，并结束进程有一定风险，建议修改端口号（高手请忽略）。