Common JBoss startup errors

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.
Path of the file 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 8080 to another number until it is successfully modified. Remember to save it after modification. If you install the Eclipse plug-in, you can open the service and directly modify the port.
This error is common in all versions.

In JBoss, this exception indicates that port 1098 is occupied by other processes. The method for viewing the occupied processes is as follows:

1) Run cmd-> netstat-ano | findstr "1098" to obtain the PID occupying port 1098.
2) CTRL + ALT + DEL, enter the task manager, click "View", select the PID, and check that the process is occupied.

3. 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]
Details:
...
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.exe cute (kernelcontrollercontextaction. Java: 241)
At org.jboss.kernel.plugins.dependency.executionwrapper.exe cute (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" (shocould be in state "installed", but is actually in state "** error **")
Deployment "profileservicedeployer" is missing the following dependencies:
Dependency "attachmentstore" (shocould be in state "installed", but is actually in state "** error **")
Deployment "profileservice" is missing the following dependencies:
Dependency "profileservicedeployer" (shocould be in state "installed", but is actually in state "instantiated ")
Dependency "JBoss. kernel: service = kernelcontroller" (shocould be in state "installed", but is actually in state "** error **")
Deployment "profileservicebootstrap" is missing the following dependencies:
Dependency "profileservice" (shocould be in state "installed", but is actually in state "instantiated ")
Dependency "JBoss. kernel: service = kernel" (shocould 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

This error often occurs in version 5.1.
This error is a bug in profile. xml. The file path is $ jboss_home/Server/<servername>/CONF/Bootstrap/profile. xml.
Put the following nodes:
<Bean name = "attachmentstore" class = "org. JBoss. system. server. profileservice. repository. abstractattachmentstore">
<Constructor> <parameter> <inject bean = "bootstrapprofilefactory" property = "attachmentstoreroot"/> </parameter> </constructor>
To:
<Bean name = "attachmentstore" class = "org. JBoss. system. server. profileservice. repository. abstractattachmentstore">
<Constructor> <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

Solution: Stop the Windows indexing service. The cause of the error is as follows:
It seemed that a file was being locked for some reason, and that file was 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 wowould fail on the locked file ), it turns out that file was 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.exe (aka the Windows indexing service) was 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 cocould 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 you can see, I was using the JBoss Tools Integration with Eclipse, so I tried just exporting the war file and copying it manually to the JBoss deploy directory, but still no luck. with nightmares of "pouring through source code to see what JBoss is doing when it throws this exception" dancing in my head, luckily Google gave a bunch of pieces to the puzzle to what might be causing this. it turns out that JBoss requires all servlets and such to be inside a package. this was not the case when I was 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 have to unlock the puzzle of JAX-WS, jaxb, and how everything lives in harmony to create a viable SOA solution ....

5. the jbossas tool, which runs normally but uses JBoss tool3.1, cannot be released (the jboss5.1 Runtime Server Release is invalid), but the default runtime path "workspace \. metadata \. plugins \ Org. JBoss. IDE. eclipse. as. in core \ jboss_5.20.runtime_serverxxx, you can view the released project and start JBoss but cannot access the publishing information. This problem has been depressing for two days and I finally found a speechless problem, there cannot be spaces in the physical path of the project when a JBoss project is created, for example, projects with spaces such as the path "ejb3 project" cannot be correctly loaded by JBoss after being released.ProgramMember ).

Solution: when developing a JBoss project, the project path must not contain spaces or other less-used special characters. JBoss is particularly sensitive to paths.

OK. It can be started normally.