[eugenejsn]

MyEclipse Blue 2014. Linux OS.

Create Jboss 7.x Server
Enable
JBoss home directory: /jbossas71
Server Name:
Option program arguments:
Option shutdown arguments: –connect command=:shutdown
Use auto-deploy mode

Now, from the Server panel, right mouse click on the JBoss AS 7 –> Run server –> server get launched.

Next, stop the server from the IDE; then switch to the jboss as 7 home on linux cmd line console, type

/jboss_as_7_home/bin/standalone.sh

RESULTS:

JBoss Bootstrap Environment

JBOSS_HOME: /jbossas711

JAVA: /usr/lib64/jvm/jre/bin/java be wrong?

JAVA_OPTS: -server -XX:+UseCompressedOops -XX:+TieredCompilation -Xms64m -Xmx512m -XX:MaxPermSize=256m -Djava.net.preferIPv4Stack=true -Dorg.jboss.resolver.warning=true -Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000 -Djboss.modules.system.pkgs=org.jboss.byteman -Djava.awt.headless=true -Djboss.server.default.config=standalone.xml

=========================================================================

16:44:37,996 INFO [org.jboss.modules] JBoss Modules version 1.1.1.GA
16:44:38,079 INFO [org.jboss.msc] JBoss MSC version 1.0.2.GA
16:44:38,113 INFO [org.jboss.as] JBAS015899: JBoss AS 7.1.1.Final “Brontes” starting
16:44:38,519 INFO [org.xnio] XNIO Version 3.0.3.GA
16:44:38,520 INFO [org.jboss.as.server] JBAS015888: Creating http management service using socket-binding (management-http)
16:44:38,524 INFO [org.xnio.nio] XNIO NIO Implementation Version 3.0.3.GA
16:44:38,528 INFO [org.jboss.remoting] JBoss Remoting version 3.2.3.GA
16:44:38,543 INFO [org.jboss.as.logging] JBAS011502: Removing bootstrap log handlers
16:44:38,545 INFO [org.jboss.as.configadmin] (ServerService Thread Pool — 26) JBAS016200: Activating ConfigAdmin Subsystem
16:44:38,550 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool — 31) JBAS010280: Activating Infinispan subsystem.
16:44:38,561 INFO [org.jboss.as.naming] (ServerService Thread Pool — 38) JBAS011800: Activating Naming Subsystem
16:44:38,561 INFO [org.jboss.as.osgi] (ServerService Thread Pool — 39) JBAS011940: Activating OSGi Subsystem
16:44:38,565 INFO [org.jboss.as.security] (ServerService Thread Pool — 44) JBAS013101: Activating Security Subsystem
16:44:38,576 INFO [org.jboss.as.connector] (MSC –> ERROR: service thread 1-16) JBAS010408: Starting JCA Subsystem (JBoss IronJacamar 1.0.9.Final) be wrong?
16:44:38,581 INFO [org.jboss.as.webservices] (ServerService Thread Pool — 48) JBAS015537: Activating WebServices Extension
16:44:38,584 INFO [org.jboss.as.security] (MSC service thread 1-4) JBAS013100: Current PicketBox version=4.0.7.Final
16:44:38,608 INFO [org.jboss.as.naming] (MSC service thread 1-3) JBAS011802: Starting Naming Service
16:44:38,621 INFO [org.jboss.as.mail.extension] (MSC service thread 1-12) JBAS015400: Bound mail session [java:jboss/mail/Default]
16:44:38,625 INFO [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool — 27) JBAS010403: Deploying JDBC-compliant driver class org.h2.Driver (version 1.3)
16:44:38,647 INFO [org.jboss.ws.common.management.AbstractServerConfig] (MSC service thread 1-3) JBoss Web Services – Stack CXF Server 4.0.2.GA
16:44:38,695 INFO [org.apache.coyote.http11.Http11Protocol] (MSC service thread 1-2) Starting Coyote HTTP/1.1 on http–127.0.0.1-8080
16:44:38,842 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-16) JBAS010400: Bound data source [java:jboss/datasources/ExampleDS]
16:44:38,872 WARN [org.jboss.as.server.deployment.scanner] (MSC service thread 1-14) JBAS015005: Reliable deployment behaviour is not possible when auto-deployment of exploded content is enabled (i.e. deployment without use of “.dodeploy”‘ marker files). Configuration of auto-deployment of exploded content is not recommended in any situation where reliability is desired. Configuring the deployment scanner’s auto-deploy-exploded setting to “false” is recommended.
16:44:38,873 INFO [org.jboss.as.server.deployment.scanner] (MSC service thread 1-14) JBAS015012: Started FileSystemDeploymentService for directory /jbossas711/standalone/deployments
16:44:38,874 INFO [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads – 1) JBAS015014: Re-attempting failed deployment DeepyWebEAR.ear
16:44:38,875 INFO [org.jboss.as.remoting] (MSC service thread 1-12) JBAS017100: Listening on /127.0.0.1:9999
16:44:38,875 INFO [org.jboss.as.remoting] (MSC service thread 1-15) JBAS017100: Listening on /127.0.0.1:4447
16:44:38,924 INFO [org.jboss.as.server.deployment] (MSC service thread 1-7) JBAS015876: Starting deployment of “DeepyWebEAR.ear”
16:44:38,993 INFO [org.jboss.as.server.deployment] (MSC service thread 1-5) JBAS015876: Starting deployment of “DeepyWeb.war”
16:44:39,670 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-2) MSC00001: Failed to start service jboss.deployment.subunit.”DeepyWebEAR.ear”.”DeepyWeb.war”.PARSE: org.jboss.msc.service.StartException in service jboss.deployment.subunit.”DeepyWebEAR.ear”.”DeepyWeb.war”.PARSE: Failed to process phase PARSE of subdeployment “DeepyWeb.war” of deployment “DeepyWebEAR.ear”
at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:119) [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:1110) [rt.jar:1.6.0_24]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) [rt.jar:1.6.0_24]
at java.lang.Thread.run(Thread.java:679) [rt.jar:1.6.0_24]
Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: JBAS018014: Failed to parse XML descriptor “/jbossas711/standalone/deployments/DeepyWebEAR.ear/DeepyWeb.war/WEB-INF/dropdown.tld” at [13,17]
at org.jboss.as.web.deployment.TldParsingDeploymentProcessor.parseTLD(TldParsingDeploymentProcessor.java:128)
at org.jboss.as.web.deployment.TldParsingDeploymentProcessor.deploy(TldParsingDeploymentProcessor.java:91)
at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:113) [jboss-as-server-7.1.1.Final.jar:7.1.1.Final]
… 5 more

16:44:39,674 INFO [org.jboss.as] (MSC service thread 1-15) JBAS015951: Admin console listening on http://127.0.0.1:9990
16:44:39,674 ERROR [org.jboss.as] (MSC service thread 1-15) JBAS015875: JBoss AS 7.1.1.Final “Brontes” started (with errors) in 1805ms – Started 140 of 217 services (2 services failed or missing dependencies, 74 services are passive or on-demand)
16:44:39,875 INFO [org.jboss.as.server] (DeploymentScanner-threads – 2) JBAS015870: Deploy of deployment “DeepyWebEAR.ear” was rolled back with failure message {“JBAS014671: Failed services” => {“jboss.deployment.subunit.”DeepyWebEAR.ear”.”DeepyWeb.war”.PARSE” => “org.jboss.msc.service.StartException in service jboss.deployment.subunit.”DeepyWebEAR.ear”.”DeepyWeb.war”.PARSE: Failed to process phase PARSE of subdeployment “DeepyWeb.war” of deployment “DeepyWebEAR.ear””}}
16:44:39,892 INFO [org.jboss.as.server.deployment] (MSC service thread 1-13) JBAS015877: Stopped deployment DeepyWeb.war in 16ms
16:44:39,893 INFO [org.jboss.as.server.deployment] (MSC service thread 1-11) JBAS015877: Stopped deployment DeepyWebEAR.ear in 17ms
16:44:39,893 INFO [org.jboss.as.controller] (DeploymentScanner-threads – 2) JBAS014774: Service status report
JBAS014777: Services which failed to start: service jboss.deployment.subunit.”DeepyWebEAR.ear”.”DeepyWeb.war”.PARSE: org.jboss.msc.service.StartException in service jboss.deployment.subunit.”DeepyWebEAR.ear”.”DeepyWeb.war”.PARSE: Failed to process phase PARSE of subdeployment “DeepyWeb.war” of deployment “DeepyWebEAR.ear”

16:44:39,894 ERROR [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads – 1) {“JBAS014653: Composite operation failed and was rolled back. Steps that failed:” => {“Operation step-2” => {“JBAS014671: Failed services” => {“jboss.deployment.subunit.”DeepyWebEAR.ear”.”DeepyWeb.war”.PARSE” => “org.jboss.msc.service.StartException in service jboss.deployment.subunit.\”DeepyWebEAR.ear\”.\”DeepyWeb.war\”.PARSE: Failed to process phase PARSE of subdeployment \”DeepyWeb.war\” of deployment \”DeepyWebEAR.ear\””}}}}

Go to browser: http://127.0.0.1:9990/console/App.html#server-overview

DOES display the admin page. Why doesn’t it give me a clean message: server is open for business. Obviously, something is wrong. What settings were not properly set?

Thanks

Eugene

[support-pradeep]

Eugene,

When the JBoss server is started without any issues it shows the following message :

[org.jboss.as] (Controller Boot Thread) JBAS015874: JBoss AS 7.1.1.Final “Brontes” started in 17888ms – Started 133 of 208 services (74 services are passive or on-demand)

Now, from the Server panel, right mouse click on the JBoss AS 7 –> Run server –> server get launched

Looks like JBoss server has started without any issues in MyEclipse at your end. As you are seeing issues outside of MyEclipse, I suggest you to cross post on Jboss forums for better support on this.

Let us know If you see any issues in MyEclipse.

[Author]

Posts