Common errors with JBoss startup

1. Error: Java.rmi.server.ExportException:Port already in use:1098; Nested exception is:
Java.net.BindException:Address already in Use:jvm_bind
This error often occurs in version 4.2.
The path of the file that needs to be modified: Jboss-4.2.2.ga\server\default\conf\jboss-service.xml change 1098 to another number until it succeeds

<attribute name= "Port" >1099</attribute>

<attribute name= "Rmiport" >1098</attribute>

2. Error: Java.net.BindException:Address already in use:jvm_bind:8080
Path of the file to be modified: Jboss-4.2.2.ga\server\default\deploy\jboss-web.deployer\server.xml
Change the 8080 to another number, until it succeeds, and make sure you remember to save it. If you install the Eclipse plugin, you can change the port directly by opening the service.
This error is common across versions.

In JBoss, this exception indicates that port 1098 is occupied by other processes, and the way to view the occupation process is:

1) command-line cmd-Netstat-ano | Findstr "1098", get PID that occupies port 1098
2) Ctrl+alt+del, go to Task Manager, click "View", select PID, view is the process occupied, the end can

3. Error: Deployment "Attachmentstore" is in the error due to:java.lang.IllegalArgumentException:Wrong arguments. New for Tar Get Java.lang.reflect.Constructor Expected=[java.net.uri] Actual=[java.io.file]
Specific:
...
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 being in the state "installed", but was actually in the state "**error**")
Deployment "Profileservicedeployer" is missing the following dependencies:
Dependency "Attachmentstore" (should being in the state "installed", but was actually in the state "**error**")
Deployment "ProfileService" is missing the following dependencies:
Dependency "Profileservicedeployer" (should being in the state "installed", but was actually in the state "instantiated")
Dependency "Jboss.kernel:service=kernelcontroller" (should being in the state "installed", but was actually in the state "**error**")
Deployment "Profileservicebootstrap" is missing the following dependencies:
Dependency "ProfileService" (should being in the state "installed", but was actually in the state "instantiated")
Dependency "Jboss.kernel:service=kernel" (should being in the state "installed", but was actually in the 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 VMS

To place the node:
<bean name= "Attachmentstore" class= " Org.jboss.system.server.profileservice.repository.AbstractAttachmentStore ";
 <constructor>< Span style= "color: #ff0000;" ><parameter> <inject bean= "bootstrapprofilefactory" property= "Attachmentstoreroot"/></ Parameter></constructor>
modified to:
<bean name= "Attachmentstore" class= " Org.jboss.system.server.profileservice.repository.AbstractAttachmentStore ";
 <constructor>< Span style= "color: #ff0000;" ><parameter class= "Java.io.File"; <inject bean= "bootstrapprofilefactory" property= " Attachmentstoreroot "/></PARAMETER></CONSTRUCTOR>

4. Error message:
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

Workaround: Stop Windows Indexing Service services. The error occurred for the following reasons:
It seemed that a file is being locked for some reason, and that file is obviously necessary for JBoss to start. Some further investigation (OK, I admit, I just tried to delete all of JBoss with the faith that it would fail on the lock Ed file), it turns out this file is some file called Jnp-service.url in the data directory of the default server. After downloading and installing the handy Unlocker tool (http://ccollomb.free.fr/unlocker/), it turns out that CIDAEMON.E Xe (aka the Windows indexing Service) is locking the file for some reason. Turning off the indexing Service solved that problem.

The second issue came when I attempted to deploy my WAR file with my JAX-ws service into my new JBoss server. Again, I could not get it to deploy, and a review of the log files showed
"Vfsfile:/c:/dev/workspaces/beliefnet/.metadata/.plugins/org.jboss.ide.eclipse.as.core/jboss_5.1_server/deploy /raftsoa.war/"is in error due to the following reason (s): Java.lang.StringIndexOutOfBoundsException:String index out of Range: 1
A strange and cryptic error indeed. As can see, I am using the JBoss tools integration with Eclipse, so I tried just exporting the WAR file and copying I T manually to the JBoss deploy directory, but still no luck. With nightmares of ' pouring through source code to see what JBoss was doing when it throws this exception ' Dancing in my he AD, luckily Google gave a bunch of pieces to the puzzle to what might is causing this. It turns out this JBoss requires all servlets and such to being inside a package. This is a case when I am just deploying in Tomcat alone, but luckily this is among the easiest problems to fix.
Happy to say, after those issues were resolved, my sample JAX-ws application is up and running. Now I just has to unlock the puzzle of Jax-WS, JAXB, and how everything lives on harmony to create a viable SOA solution. ...

5. Start normal on but use JBoss Tool3.1 plug-in Jbossas tool Publishing is invalid (JBoss5.1 runtime server publication is invalid), but in the default runtime path "Workspace\.metadata\. Plugins\org.jboss.ide.eclipse.as.core\jboss_5.1_runtime_serverxxx "Can see the published project, start JBoss but unable to access the release information, this problem depressed me for two days, Finally, there is a non-language problem, that is, when creating JBoss project, there can be no space in the physical path of the project, such as the path "EJB3 project", such as the project with a blank directory will not be properly loaded by JBoss (really admire the programmers).

WORKAROUND: When developing JBoss projects, the project path must not take spaces or other less special characters, and JBoss is particularly sensitive to paths.

OK, it can start normally.

From:http://www.cnblogs.com/zhmore/archive/2010/09/25/1834700.html

Common errors with JBoss startup