]
David Lloyd commented on AS7-300:
---------------------------------
Can we verify that this issue still is happening? It should be fixed.
Server startup message on console goes missing if a deployment fails
during server startup
------------------------------------------------------------------------------------------
Key: AS7-300
URL:
https://issues.jboss.org/browse/AS7-300
Project: Application Server 7
Issue Type: Bug
Environment: AS7 upstream dated April 19 2011
Reporter: jaikiran pai
Fix For: 7.1.0.Beta1
I placed a failing deployment (picked the .ear from JBAS-9261) in the
standalone/deployments folder and started the standalone server. The server picked up the
deployment during startup and threw a service missing dependency error but *did not* show
the usual server started in xxx ms message. Here's the entire log:
{code}
14:02:49,540 INFO [org.jboss.as.deployment] (MSC service thread 1-4) Started
FileSystemDeploymentService for directory
/NotBackedUp/jpai/business/jboss/wc/jbossas/as7/jboss-as/build/target/jboss-7.0.0.Beta3-SNAPSHOT/standalone/deployments
14:02:49,592 INFO [org.jboss.as.jmx.JMXConnectorService] (MSC service thread 1-1)
Starting remote JMX connector
14:02:49,633 INFO [org.jboss.as.server.deployment] (DeploymentScanner-threads - 1)
Content added at location
/NotBackedUp/jpai/business/jboss/wc/jbossas/as7/jboss-as/build/target/jboss-7.0.0.Beta3-SNAPSHOT/standalone/data/content/43/79aa12f1960aa376bf9cb259576498616f5a7c/content
14:02:49,636 INFO [org.jboss.remoting] (MSC service thread 1-4) JBoss Remoting version
3.1.0.Beta2
14:02:49,712 INFO [org.apache.catalina.core.AprLifecycleListener] (MSC service thread
1-2) The Apache Tomcat Native library which allows optimal performance in production
environments was not found on the java.library.path:
/opt/Java/SunJava-6/jdk1.6.0_21/jre/lib/i386/server:/opt/Java/SunJava-6/jdk1.6.0_21/jre/lib/i386:/opt/Java/SunJava-6/jdk1.6.0_21/jre/../lib/i386:/usr/java/packages/lib/i386:/lib:/usr/lib
14:02:49,879 INFO [org.jboss.as.server.deployment] (MSC service thread 1-2) Starting
deployment of "Stateless.ear"
14:02:49,883 INFO [org.hornetq.core.server.impl.HornetQServerImpl] (MSC service thread
1-3) live server is starting..
14:02:49,980 WARN [org.jboss.vfs] (MSC service thread 1-1) VFS was unable to set the
URLStreamHandlerFactory. This will have unpredictable results
14:02:50,022 INFO [org.apache.coyote.http11.Http11Protocol] (MSC service thread 1-2)
Starting Coyote HTTP/1.1 on http-localhost-127.0.0.1-8080
14:02:50,114 INFO [org.jboss.as.connector] (MSC service thread 1-4) Starting JCA
Subsystem (JBoss IronJacamar 1.0.0.Beta5)
14:02:50,123 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) Starting
deployment of "StatelessWeb.war"
14:02:50,132 INFO [org.jboss.as.server.deployment] (MSC service thread 1-4) Starting
deployment of "StatelessEJB.jar"
14:02:50,134 INFO [org.jboss.as.server.deployment] (MSC service thread 1-4) Starting
deployment of "StatelessClient.jar"
14:02:50,145 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) Class Path
entry StatelessEJB.jar in "/content/Stateless.ear/StatelessClient.jar" does not
point to a valid jar for a Class-Path reference.
14:02:50,221 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread
1-1) Bound JDBC Data-source [java:/H2DS]
14:02:50,435 INFO [org.hornetq.core.remoting.impl.netty.NettyAcceptor] (MSC service
thread 1-3) Started Netty Acceptor version 3.2.1.Final-r2319 localhost:5455 for CORE
protocol
14:02:50,436 INFO [org.hornetq.core.remoting.impl.netty.NettyAcceptor] (MSC service
thread 1-3) Started Netty Acceptor version 3.2.1.Final-r2319 localhost:5445 for CORE
protocol
14:02:50,438 INFO [org.hornetq.core.server.impl.HornetQServerImpl] (MSC service thread
1-3) HornetQ Server version 2.1.2.Final (Colmeia, 120) started
14:02:50,480 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-3) MSC00001: Failed
to start service
jboss.deployment.subunit."Stateless.ear"."StatelessWeb.war".INSTALL:
org.jboss.msc.service.StartException in service
jboss.deployment.subunit."Stateless.ear"."StatelessWeb.war".INSTALL:
Failed to process phase INSTALL of subdeployment "StatelessWeb.war" of
deployment "Stateless.ear"
at
org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:108)
at
org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1675)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
[:1.6.0_21]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
[:1.6.0_21]
at java.lang.Thread.run(Thread.java:619) [:1.6.0_21]
Caused by: java.lang.IllegalArgumentException: Cannot find source service for lookup
name: KeksLocal
at
org.jboss.as.ee.component.LookupBindingSourceDescription.<init>(LookupBindingSourceDescription.java:73)
at
org.jboss.as.ejb3.deployment.processors.EjbRefProcessor.processDescriptorEntries(EjbRefProcessor.java:99)
at
org.jboss.as.ee.component.AbstractDeploymentDescriptorBindingsProcessor.deploy(AbstractDeploymentDescriptorBindingsProcessor.java:57)
at
org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:102)
... 4 more
14:02:50,661 INFO [org.jboss.as.server] (MSC service thread 1-1) Service status report
New missing/unsatisfied dependencies:
service jboss.naming.context.java.module.Stateless.StatelessWeb (missing)
Services which failed to start:
service
jboss.deployment.subunit."Stateless.ear"."StatelessWeb.war".INSTALL:
org.jboss.msc.service.StartException in service
jboss.deployment.subunit."Stateless.ear"."StatelessWeb.war".INSTALL:
Failed to process phase INSTALL of subdeployment "StatelessWeb.war" of
deployment "Stateless.ear"
{code}
Removing the failing deployment and restarting the server shows the server startup
message:
{code}
14:08:33,603 INFO [org.jboss.as] (MSC service thread 1-2) JBoss AS 7.0.0.Beta3-SNAPSHOT
"TBD" started in 3328ms - Started 99 of 123 services (24 services are passive or
on-demand)
{code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: