Somebody really screwed up jboss-head.  Can the butt-head who did fix it?
This is ridiculous

MBeans waiting for other MBeans:
[org.jboss.system.ServiceContext@17342155 {
  objectName: jboss.ejb:service=EJBDeployer
  state: CONFIGURED
  dependencies: [jboss.tm:service=TransactionManagerService,
jboss:service=WebService]
}, org.jboss.system.ServiceContext@3e0fd571 {
  objectName: jboss:service=invoker,type=jrmp
  state: CONFIGURED
  dependencies: [jboss.tm:service=TransactionManagerService]
}, org.jboss.system.ServiceContext@383f0c1 {
  objectName: jboss:service=invoker,type=pooled
  state: CONFIGURED
  dependencies: [jboss.tm:service=TransactionManagerService]
}, org.jboss.system.ServiceContext@840583a5 {
  objectName: jboss:service=invoker,type=local
  state: CONFIGURED
  dependencies: [jboss.tm:service=TransactionManagerService]
}, org.jboss.system.ServiceContext@1d93f68e {
  objectName: jboss:service=WorkManager,type=TrunkInvoker
  state: CONFIGURED
  dependencies: [jboss.tm:service=TransactionManagerService]
  dependants: [jboss:service=invoker,type=trunk]
}, org.jboss.system.ServiceContext@8477e1ee {
  objectName: jboss:service=invoker,type=trunk
  state: CONFIGURED
  dependencies: [jboss.tm:service=TransactionManagerService,
jboss:service=WorkManager,type=TrunkInvoker]
  dependants: [jboss.mq:service=InvocationLayer,type=Trunk]
}, org.jboss.system.ServiceContext@b6ffee76 {
  objectName: jboss.tm:service=ClientUserTransaction
  state: CONFIGURED
  dependencies: [jboss.tm:service=TransactionManagerService,
jboss.jca:service=CachedConnectionManager]
}, org.jboss.system.ServiceContext@458d04ba {
  objectName: jboss.jca:service=BaseWorkManager
  state: CONFIGURED
  dependencies: [jboss.tm:service=TransactionManagerService]
  dependants: [jboss.jca:service=BaseBootstrapContext]
}, org.jboss.system.ServiceContext@1b5fa8c3 {
  objectName: jboss.jca:service=BaseBootstrapContext
  state: CONFIGURED
  dependencies: [jboss.jca:service=BaseWorkManager]
}, org.jboss.system.ServiceContext@f7fa85cc {
  objectName: jboss.jca:service=LocalTxCM,name=DefaultDS
  state: CONFIGURED
  dependencies: [jboss.tm:service=TransactionManagerService,
jboss.jca:service=CachedConnectionManager, jboss.jca:servic
e=ManagedConnectionPool,name=DefaultDS,
jboss.jca:service=ManagedConnectionFactory,name=DefaultDS,
jboss:service=Hyperso
nic]
  dependants: [jboss.mq:service=PersistenceManager]
}, org.jboss.system.ServiceContext@ddeabeb0 {
  objectName:
jboss.deployment:name=file%3a/C%3a/jboss/jboss-head/build/output/jboss-4.0.0
alpha/server/default/deploy/jm
s-ds.xml,service=DeploymentInfo
  state: CONFIGURED
  dependencies: [jboss.deployment:name=JMS Adapter,service=DeploymentInfo,
jboss.tm:service=XidFactory]
}, org.jboss.system.ServiceContext@5aec6f45 {
  objectName: jboss.mq.destination:service=Topic,name=testTopic
  state: CONFIGURED
  dependencies: [jboss.mq:service=SecurityManager,
jboss.mq:service=DestinationManager]
}, org.jboss.system.ServiceContext@8236d6f0 {
  objectName: jboss.mq.destination:service=Topic,name=securedTopic
  state: CONFIGURED
  dependencies: [jboss.mq:service=SecurityManager,
jboss.mq:service=DestinationManager]
}, org.jboss.system.ServiceContext@6ece5dd4 {
  objectName: jboss.mq.destination:service=Topic,name=testDurableTopic
  state: CONFIGURED
  dependencies: [jboss.mq:service=SecurityManager,
jboss.mq:service=DestinationManager]
}, org.jboss.system.ServiceContext@5c719389 {
  objectName: jboss.mq.destination:service=Queue,name=testQueue
  state: CONFIGURED
  dependencies: [jboss.mq:service=SecurityManager,
jboss.mq:service=DestinationManager]
}, org.jboss.system.ServiceContext@a18d4300 {
  objectName: jboss.mq.destination:service=Queue,name=testObjectMessage
  state: CONFIGURED
  dependencies: [jboss.mq:service=DestinationManager]
}, org.jboss.system.ServiceContext@efdb3dab {
  objectName: jboss.mq.destination:service=Queue,name=A
  state: CONFIGURED
  dependencies: [jboss.mq:service=DestinationManager]
}, org.jboss.system.ServiceContext@49b6a7ec {
  objectName: jboss.mq.destination:service=Queue,name=B
  state: CONFIGURED
  dependencies: [jboss.mq:service=DestinationManager]
}, org.jboss.system.ServiceContext@a392122d {
  objectName: jboss.mq.destination:service=Queue,name=C
  state: CONFIGURED
  dependencies: [jboss.mq:service=DestinationManager]
}, org.jboss.system.ServiceContext@fd6d7c6e {
  objectName: jboss.mq.destination:service=Queue,name=D
  state: CONFIGURED
  dependencies: [jboss.mq:service=DestinationManager]
}, org.jboss.system.ServiceContext@51b98823 {
  objectName: jboss.mq.destination:service=Queue,name=ex
  state: CONFIGURED



-------------------------------------------------------
This SF.NET email is sponsored by: Thawte.com - A 128-bit supercerts will
allow you to extend the highest allowed 128 bit encryption to all your 
clients even if they use browsers that are limited to 40 bit encryption. 
Get a guide here:http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0030en
_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development

Reply via email to