Jboss related errors and solutions,

Jboss related errors and solutions,
Question 1

Error message:

MSC00001: Failed to start service jboss.web.deployment.default-host./: Caused by: java.lang.IllegalArgumentException: Child container with name  already exists        at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:804)        at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:792)        at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:356)        at org.jboss.as.web.deployment.WebContextInjector.inject(WebContextInjector.java:62)        at org.jboss.as.web.deployment.WebContextInjector.inject(WebContextInjector.java:38)        at org.jboss.msc.inject.CastingInjector.inject(CastingInjector.java:55) 

Solution:
Find % JBOSS_HOME %/configuration/standalone. xml and modify enable-welcome-root = "false" to prevent the default context of jboss from conflict with your application.

Question 2:

Error message:

14:01:59,555 WARN  [org.jboss.as.ee] (MSC service thread 1-14) JBAS011006: Not installing optional component org.springframework.web.context.request.async.StandardServletAsyncWebRequest due to exception: org.jboss.as.server.deployment.DeploymentUnitProcessingException: JBAS011054: Could not find default constructor for class org.springframework.web.context.request.async.StandardServletAsyncWebRequest    at org.jboss.as.ee.component.ComponentDescription$DefaultComponentConfigurator.configure(ComponentDescription.java:606)    at org.jboss.as.ee.component.deployers.EEModuleConfigurationProcessor.deploy(EEModuleConfigurationProcessor.java:81)    at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:113) [jboss-as-server-7.1.1.Final.jar:7.1.1.Final]    at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]    at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]    at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_65]    at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_65]    at java.lang.Thread.run(Thread.java:745) [rt.jar:1.7.0_65]

Solution:
Find % JBOSS_HOME %/configuration/standalone. xml, and add the following content in console-handler name = "CONSOLE">.

  <filter>     <not>            <match pattern="JBAS011006"/>     </not>  </filter>

Question 3:

Error message:
Jboss7.1.1 Final is used in the company's website system. Because some data and service test environments are not available, it is inevitable to debug some jsp pages in the test environment, the jboss application downloaded from the jboss community has a problem. The newly added jsp page is deployed in real time, and the modified jsp page cannot be deployed normally.
Solution:

• In the jboss7 \ standalone \ configuration \ standalone. xml file, find

<subsystem xmlns="urn:jboss:domain:web:1.0" default-virtual-server="default-host">                 <configuration>                     <jsp-configuration development="true"/>                 </configuration>                 <connector name="http" protocol="HTTP/1.1" socket-binding="http" scheme="http"/>                 <virtual-server name="default-host" enable-welcome-root="true">                     <alias name="localhost"/>                     <alias name="example.com"/>                 </virtual-server>             </subsystem>   

• Paste the jboss-as-7.1.1.Final in the jboss-as-web-7.1.1.Final-RECOMPILE.jar/modules/org/jboss/as/web/main directory.

  Open module. xml (jboss-as-7.1.1.Final/modules/org/jboss/as/web/main) and comment out the following code

<!--resource-root path="jboss-as-web-7.1.1.Final.jar"/-->

Add the following lines under the line commented above

<resource-root path="jboss-as-web-7.1.1.Final-RECOMPILE.jar"/>

References
Https://community.jboss.org/message/723945#723945#723945
Updating ..., You are welcome to provide solutions to related problems.

Copyright Disclaimer: This article is an original article by the blogger and cannot be reproduced without the permission of the blogger.