JBossDeveloper

The instructions says:
6) Eliminate all mbeans groups from the jboss-service.xml file EXCEPT the following sections:
a.) Log4j Initialization
b.) JNDI
c.) Security
d.) Deployment Scanning

I eliminated the following mbean group as well:


jboss.system:service=MainDeployer
jboss.system:service=ServiceDeployer
jboss.j2ee:service=EARDeployer
jboss.ejb:service=EJBDeployer
jboss.jca:service=RARDeployer
jboss.jca:service=ConnectionFactoryDeployer
jboss.web:service=WebServer
jboss:service=Mail
jboss.mq:service=DestinationManager
jboss:service=Naming
jboss:service=TransactionManager
jboss:service=ClientUserTransaction
jboss:service=CorbaORB


Which includes the Transaction manager.

The instruction also says:

5) Delete all files and directories from the jboss\server\default\deploy directory EXCEPT:
a) jbossweb.sar/
b) jmx-console.war/
c) cache-invalidation-service.xml
d) hsqldb-ds.xml
e) jboss-jca.sar
f) jboss-local-jdbc.rar
g) jbossmq-destinations-service.xml
h) jbossmq-service.xml
i) transaction-service.xml

So, I kept cache-invalidation service.

Also, the instruction says:

I actually left the following files in the deploy dir

jmx-ejb-connector-server.sar
jmx-invoker-adaptor-server.sar/
jmx-rmi-adaptor.sar/

and I was able to shut down the jbossMQ server gracefully.

So, I kept both adaptor services.

Was anything wrong?

It's a service start ordering problem, try adding the contents of the transaction-service.xml before the JRMP Invoker in jboss-service.xml

or try removing the InvokerAdaptorService and JRMP Invoker and see if you can get along without JRMP invoker (if InvokerAdaptorService is the only one using it -- if it is using it)

or

create a separate invoker-service.xml in your deploy dir where you include JRMP Invoker (still needs to add a dependency to tx manager service or use prefix deployment scanner to order tx manager before JRMP invoker).


-- Juha

I was actually able to deploy it.
What I did was I reinstalled back in the Transactions Section of jboss-service.xml XidFactory mbean and TransactionManager mbean.
I was also able to remove cache-invalidation-service.xml, jmx-rmi-adaptor.sar, jmx-invoker-adaptor-server.sar, http-invoker.sar from deploy directory.

Now my configuration from xml console is the following:
JMImplementation
name=Default,service=LoaderRepository
type=MBeanRegistry
type=MBeanServerDelegate
jboss
service=Hypersonic
service=JNDIView
service=Naming
service=TransactionManager
service=XidFactory
service=invoker,type=jrmp
jboss.deployment
flavor=URL,type=DeploymentScanner
jboss.jca
name=DefaultDS,service=LocalTxCM
name=DefaultDS,service=ManagedConnectionFactory
name=DefaultDS,service=ManagedConnectionPool
name=JBoss LocalTransaction JDBC Wrapper,service=RARDeployment
name=JMS Adapter,service=RARDeployment
name=JmsXA,service=ManagedConnectionFactory
name=JmsXA,service=ManagedConnectionPool
name=JmsXA,service=TxCM
service=CachedConnectionManager
service=ConnectionFactoryDeployer
service=RARDeployer
jboss.mq
name=JBossMQProvider,service=JMSProviderLoader
name=StdJMSPool,service=ServerSessionPoolMBean
service=DestinationManager
service=InvocationLayer,type=HTTP
service=InvocationLayer,type=JVM
service=InvocationLayer,type=OIL
service=InvocationLayer,type=OIL2
service=InvocationLayer,type=RMI
service=InvocationLayer,type=UIL
service=InvocationLayer,type=UIL2
service=Invoker
service=MessageCache
service=PersistenceManager
service=SecurityManager
service=StateManager
service=TracingInterceptor
jboss.mq.destination
name=A,service=Queue
name=B,service=Queue
name=C,service=Queue
name=D,service=Queue
name=DLQ,service=Queue
name=ex,service=Queue
name=securedTopic,service=Topic
name=testDurableTopic,service=Topic
name=testQueue,service=Queue
name=testTopic,service=Topic
jboss.security
service=JaasSecurityManager
service=SecurityConfig
service=XMLLoginConfig
jboss.system
service=JARDeployer
service=Logging,type=Log4jService
service=MainDeployer
service=ServiceController
service=ServiceDeployer
type=Server
type=ServerConfig
type=ServerInfo
jboss.web
AJP13Listener=0,Jetty=0
Code=0
HashSessionManager=0,JBossWebApplicationContext=0,Jetty=0,context=/jbossmq-httpil
HashSessionManager=0,JBossWebApplicationContext=1,Jetty=0,context=/jmx-console
JBossLogSink=0,Log=0
JBossWebApplicationContext=0,Jetty=0,context=/jbossmq-httpil
JBossWebApplicationContext=0,Jetty=0,context=/jbossmq-httpil,name=HTTPServerILServlet
JBossWebApplicationContext=0,Jetty=0,context=/jbossmq-httpil,name=default
JBossWebApplicationContext=0,Jetty=0,context=/jbossmq-httpil,name=invoker
JBossWebApplicationContext=0,Jetty=0,context=/jbossmq-httpil,name=jsp
JBossWebApplicationContext=1,Jetty=0,context=/jmx-console
JBossWebApplicationContext=1,Jetty=0,context=/jmx-console,name=ClusterView
JBossWebApplicationContext=1,Jetty=0,context=/jmx-console,name=ClusteredConsoleServlet
JBossWebApplicationContext=1,Jetty=0,context=/jmx-console,name=DisplayMBeans
JBossWebApplicationContext=1,Jetty=0,context=/jmx-console,name=DisplayOpResult
JBossWebApplicationContext=1,Jetty=0,context=/jmx-console,name=HtmlAdaptor
JBossWebApplicationContext=1,Jetty=0,context=/jmx-console,name=InspectMBean
JBossWebApplicationContext=1,Jetty=0,context=/jmx-console,name=default
JBossWebApplicationContext=1,Jetty=0,context=/jmx-console,name=invoker
JBossWebApplicationContext=1,Jetty=0,context=/jmx-console,name=jsp
Jetty=0
Jetty=0,NCSARequestLog=0
Jetty=0,SocketListener=0
Log=0
service=WebServer
jmx.loading
UCL=128edf2
UCL=135b1f3
UCL=16dfa45
UCL=16eb6bc
UCL=185572a
UCL=1fc3c84
UCL=3a6e5c
UCL=5e176f
UCL=682406
UCL=6833f2
UCL=7736bd
UCL=7b4703
UCL=8b567c
UCL=d6b059
UCL=e7f6eb
UCL=ecb67f


Does it look good? I just need JMX and JMS.

Looks ok,

you won't need all the different invocation layers in JMS so you can remove those that you don't use from the JMS config (also all the test destinations).

-- Juha

OK. Now I have this in JMX Console:

JMImplementation
name=Default,service=LoaderRepository
type=MBeanRegistry
type=MBeanServerDelegate
jboss
service=Hypersonic
service=JNDIView
service=Naming
service=TransactionManager
service=XidFactory
service=invoker,type=jrmp
jboss.deployment
flavor=URL,type=DeploymentScanner
jboss.jca
name=DefaultDS,service=LocalTxCM
name=DefaultDS,service=ManagedConnectionFactory
name=DefaultDS,service=ManagedConnectionPool
name=JBoss LocalTransaction JDBC Wrapper,service=RARDeployment
service=CachedConnectionManager
service=ConnectionFactoryDeployer
service=RARDeployer
jboss.mq
service=DestinationManager
service=Invoker
service=MessageCache
service=PersistenceManager
service=SecurityManager
service=StateManager
service=TracingInterceptor
jboss.mq.destination
name=A,service=Queue
name=B,service=Queue
name=C,service=Queue
name=D,service=Queue
name=DLQ,service=Queue
name=ex,service=Queue
name=securedTopic,service=Topic
jboss.security
service=JaasSecurityManager
service=SecurityConfig
service=XMLLoginConfig
jboss.system
service=JARDeployer
service=Logging,type=Log4jService
service=MainDeployer
service=ServiceController
service=ServiceDeployer
type=Server
type=ServerConfig
type=ServerInfo
jboss.web
AJP13Listener=0,Jetty=0
Code=0
HashSessionManager=0,JBossWebApplicationContext=0,Jetty=0,context=/jmx-console
JBossLogSink=0,Log=0
JBossWebApplicationContext=0,Jetty=0,context=/jmx-console
JBossWebApplicationContext=0,Jetty=0,context=/jmx-console,name=ClusterView
JBossWebApplicationContext=0,Jetty=0,context=/jmx-console,name=ClusteredConsoleServlet
JBossWebApplicationContext=0,Jetty=0,context=/jmx-console,name=DisplayMBeans
JBossWebApplicationContext=0,Jetty=0,context=/jmx-console,name=DisplayOpResult
JBossWebApplicationContext=0,Jetty=0,context=/jmx-console,name=HtmlAdaptor
JBossWebApplicationContext=0,Jetty=0,context=/jmx-console,name=InspectMBean
JBossWebApplicationContext=0,Jetty=0,context=/jmx-console,name=default
JBossWebApplicationContext=0,Jetty=0,context=/jmx-console,name=invoker
JBossWebApplicationContext=0,Jetty=0,context=/jmx-console,name=jsp
Jetty=0
Jetty=0,NCSARequestLog=0
Jetty=0,SocketListener=0
Log=0
service=WebServer
jmx.loading
UCL=167e3a5
UCL=16dfa45
UCL=190ef12
UCL=19a37a
UCL=5dc994
UCL=5e176f
UCL=7736bd
UCL=f0b4a3

Will I be able to have message driven beans?

> OK. Now I have this in JMX Console:

Did you remove *all* JMS invocation layers? You're going to want at least one :-)

You can remove all the default destinations (queues A, B, C, etc).

> Will I be able to have message driven beans?

No.

-- Juha

> OK. Now I have this in JMX Console:

Did you remove *all* JMS invocation layers? You're going to want at least one :-)

Does it matter which one? Any one?

You can remove all the default destinations (queues A, B, C, etc).

> Will I be able to have message driven beans?

No.

What do I need to have in order to have message driven beans?

Is RMI Invocation layer OK?

> Does it matter which one? Any one?

You will want the JVM IL if you're using in-VM messaging for fast by-reference messaging.

OIL2 is pure socket implementation, it should be fairly performant. UIL2 if your client environment doesn't allow server sockets to be created.

> What do I need to have in order to have message
> driven beans?

An EJB container and the required services.

-- Juha

Ok. I followed the steps prescribed here and am still getting an MBean exception with cause 'Incomplete Deployment listing'. Any ideas would be greatly appreciated:

12:28:55,797 INFO [Server] Starting JBoss (MX MicroKernel)...
12:28:55,797 INFO [Server] Release ID: JBoss [WonderLand] 3.2.2RC4 (build: CVST
ag=JBoss_3_2_2_RC4 date=200309172341)
12:28:55,797 INFO [Server] Home Dir: C:\programs\jboss-3.2.2RC4
12:28:55,797 INFO [Server] Home URL: file:/C:/programs/jboss-3.2.2RC4/
12:28:55,797 INFO [Server] Library URL: file:/C:/programs/jboss-3.2.2RC4/lib/
12:28:55,807 INFO [Server] Patch URL: null
12:28:55,807 INFO [Server] Server Name: minimal-jms
12:28:55,807 INFO [Server] Server Home Dir: C:\programs\jboss-3.2.2RC4\server\m
inimal-jms
12:28:55,807 INFO [Server] Server Home URL: file:/C:/programs/jboss-3.2.2RC4/se
rver/minimal-jms/
12:28:55,817 INFO [Server] Server Data Dir: C:\programs\jboss-3.2.2RC4\server\m
inimal-jms\data
12:28:55,847 INFO [Server] Server Temp Dir: C:\programs\jboss-3.2.2RC4\server\m
inimal-jms\tmp
12:28:55,867 INFO [Server] Server Config URL: file:/C:/programs/jboss-3.2.2RC4/
server/minimal-jms/conf/
12:28:55,867 INFO [Server] Server Library URL: file:/C:/programs/jboss-3.2.2RC4
/server/minimal-jms/lib/
12:28:55,867 INFO [Server] Root Deployemnt Filename: jboss-service.xml
12:28:55,877 INFO [Server] Starting General Purpose Architecture (GPA)...
12:28:56,498 INFO [ServerInfo] Java version: 1.4.1_03,Sun Microsystems Inc.
12:28:56,498 INFO [ServerInfo] Java VM: Java HotSpot(TM) Client VM 1.4.1_03-b02
,Sun Microsystems Inc.
12:28:56,498 INFO [ServerInfo] OS-System: Windows XP 5.1,x86
12:28:56,598 INFO [ServiceController] Controller MBean online
12:28:56,738 INFO [MainDeployer] Creating
12:28:56,818 INFO [MainDeployer] Created
12:28:56,818 INFO [MainDeployer] Starting
12:28:56,818 INFO [MainDeployer] Started
12:28:56,988 INFO [JARDeployer] Creating
12:28:57,028 INFO [JARDeployer] Created
12:28:57,028 INFO [JARDeployer] Starting
12:28:57,028 INFO [MainDeployer] Adding deployer: org.jboss.deployment.JARDeplo
yer@4e79f1
12:28:57,028 INFO [JARDeployer] Started
12:28:57,059 INFO [SARDeployer] Creating
12:28:57,109 INFO [SARDeployer] Created
12:28:57,119 INFO [SARDeployer] Starting
12:28:57,119 INFO [MainDeployer] Adding deployer: org.jboss.deployment.SARDeplo
yer@134a7d8
12:28:57,149 INFO [SARDeployer] Started
12:28:57,159 INFO [Server] Core system initialized
12:28:57,199 INFO [MainDeployer] Starting deployment of package: file:/C:/progr
ams/jboss-3.2.2RC4/server/minimal-jms/conf/jboss-service.xml
12:29:00,163 INFO [Log4jService] Creating
12:29:00,363 INFO [Log4jService$URLWatchTimerTask] Configuring from URL: resour
ce:log4j.xml
12:29:00,854 INFO [Log4jService] Created
12:29:00,864 INFO [NamingService] Creating
12:29:00,864 INFO [NamingService] Created
12:29:00,874 INFO [JNDIView] Creating
12:29:00,874 INFO [JNDIView] Created
12:29:00,874 INFO [SecurityConfig] Creating
12:29:00,874 INFO [SecurityConfig] Created
12:29:00,874 INFO [XMLLoginConfig] Creating
12:29:00,884 INFO [XMLLoginConfig] Created
12:29:00,884 INFO [JaasSecurityManagerService] Creating
12:29:00,884 INFO [JaasSecurityManagerService] Created
12:29:00,884 INFO [TransactionManagerService] Creating
12:29:00,884 INFO [TransactionManagerService] Created
12:29:00,884 INFO [JRMPInvoker] Creating
12:29:00,884 INFO [JRMPInvoker] Created
12:29:00,884 INFO [LocalInvoker] Creating
12:29:00,904 INFO [LocalInvoker] Created
12:29:00,904 INFO [PooledInvoker] Creating
12:29:00,904 INFO [PooledInvoker] Created
12:29:00,914 INFO [URLDeploymentScanner] Creating
12:29:00,924 INFO [URLDeploymentScanner] Created
12:29:00,924 INFO [Log4jService] Starting
12:29:00,924 INFO [AbstractDeploymentScanner$ScannerThread] Running
12:29:00,934 INFO [Log4jService] Started
12:29:00,944 INFO [NamingService] Starting
12:29:00,964 INFO [NamingService] Starting jnp server
12:29:01,225 INFO [NamingService] Started jnpPort=1099, rmiPort=0, backlog=50,
bindAddress=null, Client SocketFactory=null, Server SocketFactory=null
12:29:01,275 INFO [NamingService] Listening on port 1099
12:29:01,325 INFO [NamingService] Started
12:29:01,325 INFO [JNDIView] Starting
12:29:01,335 INFO [JNDIView] Started
12:29:01,335 INFO [SecurityConfig] Starting
12:29:01,345 INFO [SecurityConfig] Started
12:29:01,345 INFO [XMLLoginConfig] Starting
12:29:01,495 INFO [XMLLoginConfig] Started
12:29:01,495 INFO [JaasSecurityManagerService] Starting
12:29:01,535 INFO [JaasSecurityManagerService] Started
12:29:01,535 INFO [TransactionManagerService] Starting
12:29:01,625 INFO [TransactionManagerService] Started
12:29:01,625 INFO [JRMPInvoker] Starting
12:29:01,705 INFO [JRMPInvoker] Started
12:29:01,705 INFO [LocalInvoker] Starting
12:29:01,705 INFO [LocalInvoker] Started
12:29:01,715 INFO [PooledInvoker] Starting
12:29:01,795 INFO [PooledInvoker] Started
12:29:01,795 INFO [URLDeploymentScanner] Starting
12:29:01,815 INFO [MainDeployer] Starting deployment of package: file:/C:/progr
ams/jboss-3.2.2RC4/server/minimal-jms/deploy/jbossweb-tomcat41.sar/
12:29:01,855 INFO [SARDeployer] nested deployment: file:/C:/programs/jboss-3.2.
2RC4/server/minimal-jms/deploy/jbossweb-tomcat41.sar/ant.jar
12:29:01,855 INFO [SARDeployer] nested deployment: file:/C:/programs/jboss-3.2.
2RC4/server/minimal-jms/deploy/jbossweb-tomcat41.sar/bootstrap.jar
12:29:01,855 INFO [SARDeployer] nested deployment: file:/C:/programs/jboss-3.2.
2RC4/server/minimal-jms/deploy/jbossweb-tomcat41.sar/catalina.jar
12:29:01,865 INFO [SARDeployer] nested deployment: file:/C:/programs/jboss-3.2.
2RC4/server/minimal-jms/deploy/jbossweb-tomcat41.sar/commons-beanutils.jar
12:29:01,875 INFO [SARDeployer] nested deployment: file:/C:/programs/jboss-3.2.
2RC4/server/minimal-jms/deploy/jbossweb-tomcat41.sar/commons-collections.jar
12:29:01,875 INFO [SARDeployer] nested deployment: file:/C:/programs/jboss-3.2.
2RC4/server/minimal-jms/deploy/jbossweb-tomcat41.sar/commons-digester.jar
12:29:01,875 INFO [SARDeployer] nested deployment: file:/C:/programs/jboss-3.2.
2RC4/server/minimal-jms/deploy/jbossweb-tomcat41.sar/commons-logging.jar
12:29:01,875 INFO [SARDeployer] nested deployment: file:/C:/programs/jboss-3.2.
2RC4/server/minimal-jms/deploy/jbossweb-tomcat41.sar/jakarta-regexp-1.2.jar
12:29:01,885 INFO [SARDeployer] nested deployment: file:/C:/programs/jboss-3.2.
2RC4/server/minimal-jms/deploy/jbossweb-tomcat41.sar/jasper-compiler.jar
12:29:01,885 INFO [SARDeployer] nested deployment: file:/C:/programs/jboss-3.2.
2RC4/server/minimal-jms/deploy/jbossweb-tomcat41.sar/jasper-runtime.jar
12:29:01,885 INFO [SARDeployer] nested deployment: file:/C:/programs/jboss-3.2.
2RC4/server/minimal-jms/deploy/jbossweb-tomcat41.sar/naming-common.jar
12:29:01,905 INFO [SARDeployer] nested deployment: file:/C:/programs/jboss-3.2.
2RC4/server/minimal-jms/deploy/jbossweb-tomcat41.sar/naming-resources.jar
12:29:01,915 INFO [SARDeployer] nested deployment: file:/C:/programs/jboss-3.2.
2RC4/server/minimal-jms/deploy/jbossweb-tomcat41.sar/servlets-common.jar
12:29:01,915 INFO [SARDeployer] nested deployment: file:/C:/programs/jboss-3.2.
2RC4/server/minimal-jms/deploy/jbossweb-tomcat41.sar/servlets-default.jar
12:29:01,926 INFO [SARDeployer] nested deployment: file:/C:/programs/jboss-3.2.
2RC4/server/minimal-jms/deploy/jbossweb-tomcat41.sar/servlets-invoker.jar
12:29:01,926 INFO [SARDeployer] nested deployment: file:/C:/programs/jboss-3.2.
2RC4/server/minimal-jms/deploy/jbossweb-tomcat41.sar/servlets-webdav.jar
12:29:01,926 INFO [SARDeployer] nested deployment: file:/C:/programs/jboss-3.2.
2RC4/server/minimal-jms/deploy/jbossweb-tomcat41.sar/tomcat-coyote.jar
12:29:01,926 INFO [SARDeployer] nested deployment: file:/C:/programs/jboss-3.2.
2RC4/server/minimal-jms/deploy/jbossweb-tomcat41.sar/tomcat-http11.jar
12:29:01,936 INFO [SARDeployer] nested deployment: file:/C:/programs/jboss-3.2.
2RC4/server/minimal-jms/deploy/jbossweb-tomcat41.sar/tomcat-jk2.jar
12:29:01,936 INFO [SARDeployer] nested deployment: file:/C:/programs/jboss-3.2.
2RC4/server/minimal-jms/deploy/jbossweb-tomcat41.sar/tomcat-util.jar
12:29:01,936 INFO [SARDeployer] nested deployment: file:/C:/programs/jboss-3.2.
2RC4/server/minimal-jms/deploy/jbossweb-tomcat41.sar/tomcat41-service.jar
12:29:02,316 WARN [MainDeployer] The manifest entry in file:/C:/programs/jboss-
3.2.2RC4/server/minimal-jms/deploy/jbossweb-tomcat41.sar/tomcat-util.jar referen
ces URL file:/C:/programs/jboss-3.2.2RC4/server/minimal-jms/deploy/jbossweb-tomc
at41.sar/log4j.jar which could not be opened, entry ignored
12:29:02,326 WARN [MainDeployer] The manifest entry in file:/C:/programs/jboss-
3.2.2RC4/server/minimal-jms/deploy/jbossweb-tomcat41.sar/tomcat-util.jar referen
ces URL file:/C:/programs/jboss-3.2.2RC4/server/minimal-jms/deploy/jbossweb-tomc
at41.sar/log4j-core.jar which could not be opened, entry ignored
12:29:02,326 WARN [MainDeployer] The manifest entry in file:/C:/programs/jboss-
3.2.2RC4/server/minimal-jms/deploy/jbossweb-tomcat41.sar/tomcat-util.jar referen
ces URL file:/C:/programs/jboss-3.2.2RC4/server/minimal-jms/deploy/jbossweb-tomc
at41.sar/mx4j.jar which could not be opened, entry ignored
12:29:03,007 WARN [MainDeployer] The manifest entry in file:/C:/programs/jboss-
3.2.2RC4/server/minimal-jms/deploy/jbossweb-tomcat41.sar/tomcat-jk2.jar referenc
es URL file:/C:/programs/jboss-3.2.2RC4/server/minimal-jms/deploy/jbossweb-tomca
t41.sar/workers.jar which could not be opened, entry ignored
12:29:03,017 WARN [MainDeployer] The manifest entry in file:/C:/programs/jboss-
3.2.2RC4/server/minimal-jms/deploy/jbossweb-tomcat41.sar/tomcat-jk2.jar referenc
es URL file:/C:/programs/jboss-3.2.2RC4/server/minimal-jms/deploy/classes/ which
could not be opened, entry ignored
12:29:03,087 WARN [MainDeployer] The manifest entry in file:/C:/programs/jboss-
3.2.2RC4/server/minimal-jms/deploy/jbossweb-tomcat41.sar/tomcat-jk2.jar referenc
es URL file:/C:/programs/jboss-3.2.2RC4/server/minimal-jms/deploy/jbossweb-tomca
t41.sar/log4j.jar which could not be opened, entry ignored
12:29:03,428 WARN [MainDeployer] The manifest entry in file:/C:/programs/jboss-
3.2.2RC4/server/minimal-jms/deploy/jbossweb-tomcat41.sar/bootstrap.jar reference
s URL file:/C:/programs/jboss-3.2.2RC4/server/minimal-jms/deploy/jbossweb-tomcat
41.sar/commons-daemon.jar which could not be opened, entry ignored
12:29:03,958 WARN [MainDeployer] The manifest entry in file:/C:/programs/jboss-
3.2.2RC4/server/minimal-jms/deploy/jbossweb-tomcat41.sar/commons-logging.jar ref
erences URL file:/C:/programs/jboss-3.2.2RC4/server/minimal-jms/deploy/jbossweb-
tomcat41.sar/log4j.jar which could not be opened, entry ignored
12:29:03,958 WARN [MainDeployer] The manifest entry in file:/C:/programs/jboss-
3.2.2RC4/server/minimal-jms/deploy/jbossweb-tomcat41.sar/commons-logging.jar ref
erences URL file:/C:/programs/jboss-3.2.2RC4/server/minimal-jms/deploy/jbossweb-
tomcat41.sar/log4j-core.jar which could not be opened, entry ignored
12:29:04,319 WARN [MainDeployer] The manifest entry in file:/C:/programs/jboss-
3.2.2RC4/server/minimal-jms/deploy/jbossweb-tomcat41.sar/ant.jar references URL
file:/C:/programs/jboss-3.2.2RC4/server/minimal-jms/deploy/jbossweb-tomcat41.sar
/xml-apis.jar which could not be opened, entry ignored
12:29:04,329 WARN [MainDeployer] The manifest entry in file:/C:/programs/jboss-
3.2.2RC4/server/minimal-jms/deploy/jbossweb-tomcat41.sar/ant.jar references URL
file:/C:/programs/jboss-3.2.2RC4/server/minimal-jms/deploy/jbossweb-tomcat41.sar
/xercesImpl.jar which could not be opened, entry ignored
12:29:04,329 WARN [MainDeployer] The manifest entry in file:/C:/programs/jboss-
3.2.2RC4/server/minimal-jms/deploy/jbossweb-tomcat41.sar/ant.jar references URL
file:/C:/programs/jboss-3.2.2RC4/server/minimal-jms/deploy/jbossweb-tomcat41.sar
/optional.jar which could not be opened, entry ignored
12:29:04,329 WARN [MainDeployer] The manifest entry in file:/C:/programs/jboss-
3.2.2RC4/server/minimal-jms/deploy/jbossweb-tomcat41.sar/ant.jar references URL
file:/C:/programs/jboss-3.2.2RC4/server/minimal-jms/deploy/jbossweb-tomcat41.sar
/xalan.jar which could not be opened, entry ignored
12:29:04,639 INFO [EmbeddedTomcatService] Creating
12:29:04,669 INFO [EmbeddedTomcatService] Created
12:29:04,679 INFO [EmbeddedTomcatService] Starting
12:29:06,292 INFO [STDOUT] Apache Tomcat/4.1.27-LE-jdk14
12:29:06,532 INFO [Http11Protocol] Initializing Coyote HTTP/1.1 on port 8080
12:29:06,572 INFO [Http11Protocol] Starting Coyote HTTP/1.1 on port 8080
12:29:06,752 WARN [JkMain] No properties file found C:\programs\jboss-3.2.2RC4\
server\minimal-jms\conf\jk2.properties
12:29:06,853 INFO [ChannelSocket] JK2: ajp13 listening on /0.0.0.0:8009
12:29:06,913 INFO [JkMain] Jk running ID=0 time=0/161 config=null
12:29:06,913 INFO [EmbeddedTomcatService] OK
12:29:06,913 INFO [MainDeployer] Adding deployer: org.jboss.web.tomcat.tc4.Embe
ddedTomcatService@3a5794
12:29:06,913 INFO [EmbeddedTomcatService] Started
12:29:06,913 INFO [MainDeployer] Deployed package: file:/C:/programs/jboss-3.2.
2RC4/server/minimal-jms/deploy/jbossweb-tomcat41.sar/
12:29:06,923 INFO [MainDeployer] Starting deployment of package: file:/C:/progr
ams/jboss-3.2.2RC4/server/minimal-jms/deploy/jms/jbossmq-destinations-service.xm
l
12:29:07,273 INFO [MainDeployer] Deployed package: file:/C:/programs/jboss-3.2.
2RC4/server/minimal-jms/deploy/jms/jbossmq-destinations-service.xml
12:29:07,293 INFO [MainDeployer] Starting deployment of package: file:/C:/progr
ams/jboss-3.2.2RC4/server/minimal-jms/deploy/jms/jbossmq-service.xml
12:29:07,624 INFO [DynamicStateManager] Creating
12:29:07,624 INFO [DynamicStateManager] Created
12:29:07,624 INFO [DynamicStateManager] Starting
12:29:07,704 INFO [DynamicStateManager] Started
12:29:07,714 INFO [MainDeployer] Deployed package: file:/C:/programs/jboss-3.2.
2RC4/server/minimal-jms/deploy/jms/jbossmq-service.xml
12:29:07,714 INFO [MainDeployer] Starting deployment of package: file:/C:/progr
ams/jboss-3.2.2RC4/server/minimal-jms/deploy/jmx-console.war/
12:29:08,034 INFO [EmbeddedTomcatService] deploy, ctxPath=/jmx-console, warUrl=
file:/C:/programs/jboss-3.2.2RC4/server/minimal-jms/deploy/jmx-console.war/
12:29:09,827 INFO [Engine] ContextConfig[/jmx-console]: Added certificates -> r
equest attribute Valve
12:29:09,917 WARN [EmbeddedTomcatService] Unable to invoke setDelegate on class
loader:org.jboss.web.tomcat.tc4.WebCtxLoader$ENCLoader@e183e9
12:29:09,917 INFO [Engine] StandardManager[/jmx-console]: Seeding random number
generator class java.security.SecureRandom
12:29:10,348 INFO [Engine] StandardManager[/jmx-console]: Seeding of random num
ber generator has been completed
12:29:10,408 INFO [Engine] StandardWrapper[/jmx-console:default]: Loading conta
iner servlet default
12:29:10,548 INFO [Engine] StandardWrapper[/jmx-console:invoker]: Loading conta
iner servlet invoker
12:29:12,851 INFO [MainDeployer] Deployed package: file:/C:/programs/jboss-3.2.
2RC4/server/minimal-jms/deploy/jmx-console.war/
12:29:12,861 ERROR [URLDeploymentScanner] MBeanException: Exception in MBean ope
ration 'checkIncompleteDeployments()'
Cause: Incomplete Deployment listing:
Packages waiting for a deployer:

Incompletely deployed packages:

MBeans waiting for classes:

MBeans waiting for other MBeans:
[ObjectName: jboss.mq.destination:service=Topic,name=testTopic
state: CONFIGURED
I Depend On: jboss.mq:service=DestinationManager
jboss.mq:service=SecurityManager

Depends On Me: , ObjectName: jboss.mq.destination:service=Topic,name=securedTop
ic
state: CONFIGURED
I Depend On: jboss.mq:service=DestinationManager
jboss.mq:service=SecurityManager

Depends On Me: , ObjectName: jboss.mq.destination:service=Topic,name=testDurabl
eTopic
state: CONFIGURED
I Depend On: jboss.mq:service=DestinationManager
jboss.mq:service=SecurityManager

Depends On Me: , ObjectName: jboss.mq.destination:service=Queue,name=testQueue
state: CONFIGURED
I Depend On: jboss.mq:service=DestinationManager
jboss.mq:service=SecurityManager

Depends On Me: , ObjectName: jboss.mq.destination:service=Queue,name=A
state: CONFIGURED
I Depend On: jboss.mq:service=DestinationManager

Depends On Me: , ObjectName: jboss.mq.destination:service=Queue,name=B
state: CONFIGURED
I Depend On: jboss.mq:service=DestinationManager

Depends On Me: , ObjectName: jboss.mq.destination:service=Queue,name=C
state: CONFIGURED
I Depend On: jboss.mq:service=DestinationManager

Depends On Me: , ObjectName: jboss.mq.destination:service=Queue,name=D
state: CONFIGURED
I Depend On: jboss.mq:service=DestinationManager

Depends On Me: , ObjectName: jboss.mq.destination:service=Queue,name=ex
state: CONFIGURED
I Depend On: jboss.mq:service=DestinationManager

Depends On Me: , ObjectName: jboss.mq:service=Invoker
state: CONFIGURED
I Depend On: jboss.mq:service=TracingInterceptor

Depends On Me: , ObjectName: jboss.mq:service=TracingInterceptor
state: CONFIGURED
I Depend On: jboss.mq:service=SecurityManager

Depends On Me: jboss.mq:service=Invoker
, ObjectName: jboss.mq:service=SecurityManager
state: CONFIGURED
I Depend On: jboss.mq:service=DestinationManager

Depends On Me: jboss.mq.destination:service=Topic,name=testTopic
jboss.mq.destination:service=Topic,name=securedTopic
jboss.mq.destination:service=Topic,name=testDurableTopic
jboss.mq.destination:service=Queue,name=testQueue
jboss.mq:service=TracingInterceptor
jboss.mq.destination:service=Queue,name=DLQ
, ObjectName: jboss.mq.destination:service=Queue,name=DLQ
state: CONFIGURED
I Depend On: jboss.mq:service=DestinationManager
jboss.mq:service=SecurityManager

Depends On Me: ]
12:29:12,881 INFO [URLDeploymentScanner] Started
12:29:12,881 INFO [MainDeployer] Deployed package: file:/C:/programs/jboss-3.2.
2RC4/server/minimal-jms/conf/jboss-service.xml
12:29:12,891 INFO [Server] JBoss (MX MicroKernel) [3.2.2RC4 (build: CVSTag=JBos
s_3_2_2_RC4 date=200309172341)] Started in 17s:14ms