4:28 p.m.
One thing that might be a problem is having too much information to dump. We may need to
abbreviate it and tell them to use a tool (console) to visualize the graph
Sent from my iPhone
On Mar 20, 2011, at 2:48 PM, "David M. Lloyd" <david.lloyd(a)redhat.com>
wrote:
This is https://issues.jboss.org/browse/JBAS-9010 - for now the only
way
is to open up jconsole and use the MSC MBean and figure out what is
missing. I'm hoping to a comprehensive solution by Beta3.
On 03/20/2011 02:17 PM, Scott Stark wrote:
> I'm working on starting up the current as7 trunk code under makara, and
> it is using various jboss.server.* properties to control various
> locations. An example of the startup arguments is:
>
> /opt/vostok/cartridges/jboss-7.0.0/bundle/bin/standalone.sh
> -Dvostok.app.home=/srv/web-apps/817468314962368366457975751090375370
> -Dvostok.app.base=/srv/web-apps/817468314962368366457975751090375370/app
> -Dvostok.node.id=
>
-Djboss.server.data.dir=/srv/web-apps/817468314962368366457975751090375370/app/data/jboss
>
-Djboss.server.log.dir=/srv/web-apps/817468314962368366457975751090375370/app/data/logs/jboss
>
-Djboss.server.temp.dir=/srv/web-apps/817468314962368366457975751090375370/app/data/tmp/jboss
> -Djboss.patch.url=file:/opt/vostok/cartridges/jboss-7.0.0/bundle/classes
>
-Djboss.server.config.dir=/srv/web-apps/817468314962368366457975751090375370/app/info/setup/jboss-7.0.0/configuration/
>
> Now, the server is starting, but it shows 6 services with failed
> dependencies. However, the logs do not show any errors, even at trace
> level logging. How do I get more information on what the dependency
> problem is?
>
> 10:59:08,865 INFO [org.jboss.as.deployment] (MSC service thread 1-4)
> Started FileSystemDeploymentService for directory
> /home/git/JBossAS/jboss-as/build/target/jboss-7.0.0.Alpha2/standalone/deployments
> 10:59:08,880 INFO
> [org.jboss.wsf.common.management.AbstractServerConfig] (MSC service
> thread 1-2) JBoss Web Services - Stack CXF Server 4.0.0.Alpha2
> 10:59:08,887 INFO [org.jboss.as.jmx.JMXConnectorService] (MSC service
> thread 1-2) Starting remote JMX connector
> 10:59:08,929 INFO [org.jboss.remoting] (MSC service thread 1-3) JBoss
> Remoting version 3.1.0.Beta2
> 10:59:08,997 INFO [org.hornetq.core.server.impl.HornetQServerImpl] (MSC
> service thread 1-1) live server is starting..
> 10:59:09,198 INFO [org.apache.coyote.http11.Http11Protocol] (MSC
> service thread 1-3) Starting Coyote HTTP/1.1 on http-8080
> 10:59:09,312 INFO [org.hornetq.core.remoting.impl.netty.NettyAcceptor]
> (MSC service thread 1-1) Started Netty Acceptor version
> 3.2.1.Final-r2319 localhost:5445 for CORE protocol
> 10:59:09,313 INFO [org.hornetq.core.remoting.impl.netty.NettyAcceptor]
> (MSC service thread 1-1) Started Netty Acceptor version
> 3.2.1.Final-r2319 localhost:5455 for CORE protocol
> 10:59:09,314 INFO [org.hornetq.core.server.impl.HornetQServerImpl] (MSC
> service thread 1-1) HornetQ Server version 2.1.2.Final (Colmeia, 120)
> started
> 10:59:09,390 ERROR [org.jboss.as] (MSC service thread 1-2) JBoss AS
> 7.0.0.Alpha2 "Halloween" started (with errors) in 3115ms - Started 79 of
> 108 services (6 services failed or missing dependencies, 23 services are
> passive or on-demand)
> Services missing dependencies:
> service jboss.connector.config
> service jboss.connector.defaultbootstrapcontext
> service jboss.txn.ArjunaTransactionManager
> service jboss.txn.TransactionManager
> service jboss.txn.TransactionSynchronizationRegistry
> service jboss.txn.UserTransaction
> 10:59:11,460 INFO [org.apache.coyote.http11.Http11Protocol] (MSC
> service thread 1-3) Stopping Coyote HTTP/1.1 on http-8080
>
> _______________________________________________
> jboss-as7-dev mailing list
> jboss-as7-dev(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
--
- DML
_______________________________________________
jboss-as7-dev mailing list
jboss-as7-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-as7-dev