How can I get a stand-alone distribution of JBossMQ?

[nphelps]

Q: I want to use JBossMQ as a stand-alone JMS server. Is this possible? What about the stand-alone distribution on the SourceForge download page? Is it up-to-date?

A: The stand-alone distribution of JBossMQ available on SourceForge is old, and therefore should be used only if your happy with older code. However, it is easy to remove all the non-JBossMQ services from a standard JBossMQ binary distribution. The following instructions explain how to do this. The finished configuration contains JBossMQ, Security/JBoss, and the JMX-Console. NOTE: To support the JMX-Console Web/JBoss (Jetty) is required.

1.) Download the standard JBoss 3.0.x distribution and unzip it.

2.) Delete the following directories:
a.) jboss\server\all
b.) jboss\server\minimal

3) Delete all files from the jboss\client directory EXCEPT:
a.) auth.conf
b.) cacerts
c.) concurrent.jar
d.) jboss-client.jar
e.) jboss-common-client.jar
f.) jboss-j2ee.jar
g.) jbossmq-client.jar
h.) jnet.jar
i.) jnp-client.jar
j.) log4j.jar

4.) Delete the following files from jboss\server\default\conf directory
a.) jboss-minimal.xml
b.) standardjaws.xml
c.) standardjboss.xml
d.) standardjbosscmp-jdbc.xml

5) Delete all files and directories from the jboss\server\default\deploy directory EXCEPT:
a.) jbossweb.sar directory
b.) jmx-console.war directory
c.) jbossmq-destinations-service.xml
d.) jbossmq-service.xml

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

[cjsceats]

I have a very similar problem to those described above, attempting this using JBoss 3.2.2 purely as a JMS provider.

It appears that there is some sort of dependency here that is unfulfilled when using the recommended configuration.

Can anyone help?



10:17:56,500 INFO [Server] Starting JBoss (MX MicroKernel)...
10:17:56,500 INFO [Server] Release ID: JBoss [WonderLand] 3.2.2 (build: CVSTag=
JBoss_3_2_2 date=200310182216)
10:17:56,500 INFO [Server] Home Dir: C:\jboss-3.2.2
10:17:56,500 INFO [Server] Home URL: file:/C:/jboss-3.2.2/
10:17:56,500 INFO [Server] Library URL: file:/C:/jboss-3.2.2/lib/
10:17:56,500 INFO [Server] Patch URL: null
10:17:56,500 INFO [Server] Server Name: jms_default
10:17:56,500 INFO [Server] Server Home Dir: C:\jboss-3.2.2\server\jms_default
10:17:56,500 INFO [Server] Server Home URL: file:/C:/jboss-3.2.2/server/jms_def
ault/
10:17:56,500 INFO [Server] Server Data Dir: C:\jboss-3.2.2\server\jms_default\d
ata
10:17:56,515 INFO [Server] Server Temp Dir: C:\jboss-3.2.2\server\jms_default\t
mp
10:17:56,515 INFO [Server] Server Config URL: file:/C:/jboss-3.2.2/server/jms_d
efault/conf/
10:17:56,515 INFO [Server] Server Library URL: file:/C:/jboss-3.2.2/server/jms_
default/lib/
10:17:56,515 INFO [Server] Root Deployemnt Filename: jboss-service.xml
10:17:56,515 INFO [Server] Starting General Purpose Architecture (GPA)...
10:17:56,718 INFO [ServerInfo] Java version: 1.4.1_02,Sun Microsystems Inc.
10:17:56,718 INFO [ServerInfo] Java VM: Java HotSpot(TM) Client VM 1.4.1_02-b06
,Sun Microsystems Inc.
10:17:56,718 INFO [ServerInfo] OS-System: Windows XP 5.1,x86
10:17:56,750 INFO [ServiceController] Controller MBean online
10:17:56,828 INFO [MainDeployer] Started jboss.system:service=MainDeployer
10:17:56,890 INFO [MainDeployer] Adding deployer: org.jboss.deployment.JARDeplo
yer@12a0f6c
10:17:56,890 INFO [JARDeployer] Started jboss.system:service=JARDeployer
10:17:56,921 INFO [MainDeployer] Adding deployer: org.jboss.deployment.SARDeplo
yer@12b3d53
10:17:56,921 INFO [SARDeployer] Started jboss.system:service=ServiceDeployer
10:17:56,921 INFO [Server] Core system initialized
10:17:56,937 INFO [MainDeployer] Starting deployment of package: file:/C:/jboss
-3.2.2/server/jms_default/conf/jboss-service.xml
10:17:58,000 INFO [Log4jService$URLWatchTimerTask] Configuring from URL: resour
ce:log4j.xml
10:17:58,218 INFO [Log4jService] Started jboss.system:type=Log4jService,service
=Logging
10:17:58,234 INFO [NamingService] Starting jnp server
10:17:58,234 INFO [AbstractDeploymentScanner$ScannerThread] Running
10:17:58,296 INFO [NamingService] Started jnpPort=1099, rmiPort=1098, backlog=5
0, bindAddress=/0.0.0.0, Client SocketFactory=null, Server SocketFactory=org.jbo
ss.net.sockets.DefaultSocketFactory@ad093076
10:17:58,312 INFO [NamingService] Listening on port 1099
10:17:58,328 INFO [NamingService] Started jboss:service=Naming
10:17:58,328 INFO [JNDIView] Started jboss:service=JNDIView
10:17:58,328 INFO [SecurityConfig] Started jboss.security:service=SecurityConfi
g
10:17:58,390 INFO [XMLLoginConfig] Started jboss.security:service=XMLLoginConfi
g
10:17:58,406 INFO [JaasSecurityManagerService] Started jboss.security:service=J
aasSecurityManager
10:17:58,406 INFO [MainDeployer] Starting deployment of package: file:/C:/jboss
-3.2.2/server/jms_default/deploy/jboss-jca.sar
10:17:58,671 INFO [XSLSubDeployer] Created templates: org.apache.xalan.template
s.StylesheetRoot@b2c6a6
10:17:58,671 INFO [MainDeployer] Adding deployer: org.jboss.resource.RARDeploye
r@10ffb38
10:17:58,671 INFO [RARDeployer] Started jboss.jca:service=RARDeployer
10:17:58,671 INFO [MainDeployer] Adding deployer: org.jboss.deployment.XSLSubDe
ployer@36527f
10:17:58,671 INFO [XSLSubDeployer] Started jboss.jca:service=ConnectionFactoryD
eployer
10:17:58,671 INFO [MainDeployer] Deployed package: file:/C:/jboss-3.2.2/server/
jms_default/deploy/jboss-jca.sar
10:17:58,671 INFO [MainDeployer] Starting deployment of package: file:/C:/jboss
-3.2.2/server/jms_default/deploy/jbossweb-tomcat41.sar/
10:17:58,687 INFO [SARDeployer] nested deployment: file:/C:/jboss-3.2.2/server/
jms_default/deploy/jbossweb-tomcat41.sar/ant.jar
10:17:58,687 INFO [SARDeployer] nested deployment: file:/C:/jboss-3.2.2/server/
jms_default/deploy/jbossweb-tomcat41.sar/bootstrap.jar
10:17:58,687 INFO [SARDeployer] nested deployment: file:/C:/jboss-3.2.2/server/
jms_default/deploy/jbossweb-tomcat41.sar/catalina.jar
10:17:58,687 INFO [SARDeployer] nested deployment: file:/C:/jboss-3.2.2/server/
jms_default/deploy/jbossweb-tomcat41.sar/commons-beanutils.jar
10:17:58,687 INFO [SARDeployer] nested deployment: file:/C:/jboss-3.2.2/server/
jms_default/deploy/jbossweb-tomcat41.sar/commons-collections.jar
10:17:58,687 INFO [SARDeployer] nested deployment: file:/C:/jboss-3.2.2/server/
jms_default/deploy/jbossweb-tomcat41.sar/commons-digester.jar
10:17:58,687 INFO [SARDeployer] nested deployment: file:/C:/jboss-3.2.2/server/
jms_default/deploy/jbossweb-tomcat41.sar/commons-logging.jar
10:17:58,687 INFO [SARDeployer] nested deployment: file:/C:/jboss-3.2.2/server/
jms_default/deploy/jbossweb-tomcat41.sar/jakarta-regexp-1.2.jar
10:17:58,687 INFO [SARDeployer] nested deployment: file:/C:/jboss-3.2.2/server/
jms_default/deploy/jbossweb-tomcat41.sar/jasper-compiler.jar
10:17:58,687 INFO [SARDeployer] nested deployment: file:/C:/jboss-3.2.2/server/
jms_default/deploy/jbossweb-tomcat41.sar/jasper-runtime.jar
10:17:58,687 INFO [SARDeployer] nested deployment: file:/C:/jboss-3.2.2/server/
jms_default/deploy/jbossweb-tomcat41.sar/naming-common.jar
10:17:58,687 INFO [SARDeployer] nested deployment: file:/C:/jboss-3.2.2/server/
jms_default/deploy/jbossweb-tomcat41.sar/naming-resources.jar
10:17:58,687 INFO [SARDeployer] nested deployment: file:/C:/jboss-3.2.2/server/
jms_default/deploy/jbossweb-tomcat41.sar/servlets-common.jar
10:17:58,687 INFO [SARDeployer] nested deployment: file:/C:/jboss-3.2.2/server/
jms_default/deploy/jbossweb-tomcat41.sar/servlets-default.jar
10:17:58,687 INFO [SARDeployer] nested deployment: file:/C:/jboss-3.2.2/server/
jms_default/deploy/jbossweb-tomcat41.sar/servlets-invoker.jar
10:17:58,687 INFO [SARDeployer] nested deployment: file:/C:/jboss-3.2.2/server/
jms_default/deploy/jbossweb-tomcat41.sar/servlets-webdav.jar
10:17:58,687 INFO [SARDeployer] nested deployment: file:/C:/jboss-3.2.2/server/
jms_default/deploy/jbossweb-tomcat41.sar/tomcat-coyote.jar
10:17:58,687 INFO [SARDeployer] nested deployment: file:/C:/jboss-3.2.2/server/
jms_default/deploy/jbossweb-tomcat41.sar/tomcat-http11.jar
10:17:58,687 INFO [SARDeployer] nested deployment: file:/C:/jboss-3.2.2/server/
jms_default/deploy/jbossweb-tomcat41.sar/tomcat-jk2.jar
10:17:58,687 INFO [SARDeployer] nested deployment: file:/C:/jboss-3.2.2/server/
jms_default/deploy/jbossweb-tomcat41.sar/tomcat-util.jar
10:17:58,687 INFO [SARDeployer] nested deployment: file:/C:/jboss-3.2.2/server/
jms_default/deploy/jbossweb-tomcat41.sar/tomcat41-service.jar
10:17:59,328 INFO [MainDeployer] Deployed package: file:/C:/jboss-3.2.2/server/
jms_default/deploy/jbossweb-tomcat41.sar/
10:17:59,328 INFO [MainDeployer] Starting deployment of package: file:/C:/jboss
-3.2.2/server/jms_default/deploy/jmx-invoker-adaptor-server.sar/
10:17:59,406 INFO [NamingAlias] Bound link jmx/rmi/RMIAdaptor to jmx/invoker/RM
IAdaptor
10:17:59,406 INFO [NamingAlias] Started jboss.jmx:alias=jmx/rmi/RMIAdaptor
10:17:59,406 INFO [InvokerAdaptorService] Started jboss.jmx:type=adaptor,name=I
nvoker
10:17:59,406 INFO [MainDeployer] Deployed package: file:/C:/jboss-3.2.2/server/
jms_default/deploy/jmx-invoker-adaptor-server.sar/
10:17:59,406 INFO [MainDeployer] Starting deployment of package: file:/C:/jboss
-3.2.2/server/jms_default/deploy/jboss-local-jdbc.rar
10:17:59,500 INFO [RARDeployer] nested deployment: file:/C:/jboss-3.2.2/server/
jms_default/tmp/deploy/tmp45536jboss-local-jdbc.rar-contents/jboss-local-jdbc.ja
r
10:17:59,515 INFO [MainDeployer] Deployed package: file:/C:/jboss-3.2.2/server/
jms_default/deploy/jboss-local-jdbc.rar
10:17:59,515 INFO [MainDeployer] Starting deployment of package: file:/C:/jboss
-3.2.2/server/jms_default/deploy/hsqldb-ds.xml
10:17:59,671 INFO [RARDeployment] Started jboss.jca:service=ManagedConnectionFa
ctory,name=DefaultDS
10:17:59,687 INFO [JBossManagedConnectionPool] Started jboss.jca:service=Manage
dConnectionPool,name=DefaultDS
10:17:59,687 INFO [MainDeployer] Deployed package: file:/C:/jboss-3.2.2/server/
jms_default/deploy/hsqldb-ds.xml
10:17:59,687 INFO [MainDeployer] Starting deployment of package: file:/C:/jboss
-3.2.2/server/jms_default/deploy/cache-invalidation-service.xml
10:17:59,718 INFO [InvalidationManager] Starting Invalidation Manager jboss.cac
he:service=InvalidationManager
10:17:59,718 INFO [InvalidationManager] Started jboss.cache:service=Invalidatio
nManager
10:17:59,718 INFO [MainDeployer] Deployed package: file:/C:/jboss-3.2.2/server/
jms_default/deploy/cache-invalidation-service.xml
10:17:59,718 INFO [MainDeployer] Starting deployment of package: file:/C:/jboss
-3.2.2/server/jms_default/deploy/jbossmq-destinations-service.xml
10:17:59,812 INFO [MainDeployer] Deployed package: file:/C:/jboss-3.2.2/server/
jms_default/deploy/jbossmq-destinations-service.xml
10:17:59,812 INFO [MainDeployer] Starting deployment of package: file:/C:/jboss
-3.2.2/server/jms_default/deploy/jbossmq-service.xml
10:17:59,968 INFO [DynamicStateManager] Started jboss.mq:service=StateManager
10:17:59,968 INFO [MainDeployer] Deployed package: file:/C:/jboss-3.2.2/server/
jms_default/deploy/jbossmq-service.xml
10:17:59,984 INFO [MainDeployer] Starting deployment of package: file:/C:/jboss
-3.2.2/server/jms_default/deploy/transaction-service.xml
10:18:00,000 INFO [MainDeployer] Deployed package: file:/C:/jboss-3.2.2/server/
jms_default/deploy/transaction-service.xml
10:18:00,000 INFO [MainDeployer] Starting deployment of package: file:/C:/jboss
-3.2.2/server/jms_default/deploy/jmx-console.war/
10:18:00,000 INFO [MainDeployer] deployment waiting for deployer: file:/C:/jbos
s-3.2.2/server/jms_default/deploy/jmx-console.war/
10:18:00,000 INFO [MainDeployer] Deployment of package: file:/C:/jboss-3.2.2/se
rver/jms_default/deploy/jmx-console.war/ is waiting for an appropriate deployer.

10:18:00,000 ERROR [URLDeploymentScanner] MBeanException: Exception in MBean ope
ration 'checkIncompleteDeployments()'
Cause: Incomplete Deployment listing:
Packages waiting for a deployer:
[org.jboss.deployment.DeploymentInfo@6d49d703 { url=file:/C:/jboss-3.2.2/server/
jms_default/deploy/jmx-console.war/ }
deployer: null
status: null
state: INIT_WAITING_DEPLOYER
watch: file:/C:/jboss-3.2.2/server/jms_default/deploy/jmx-console.war/
lastDeployed: 1068373080000
lastModified: 1068368510343
mbeans:
]Incompletely deployed packages:
[org.jboss.deployment.DeploymentInfo@6d49d703 { url=file:/C:/jboss-3.2.2/server/
jms_default/deploy/jmx-console.war/ }
deployer: null
status: null
state: INIT_WAITING_DEPLOYER
watch: file:/C:/jboss-3.2.2/server/jms_default/deploy/jmx-console.war/
lastDeployed: 1068373080000
lastModified: 1068368510343
mbeans:
]MBeans waiting for classes:

MBeans waiting for other MBeans:
[ObjectName: jboss.web:service=WebServer
state: CONFIGURED
I Depend On: jboss:service=TransactionManager

Depends On Me: , ObjectName: jboss.jmx:type=adaptor,name=Invoker,protocol=jrmp,
service=proxyFactory
state: CONFIGURED
I Depend On: jboss:service=invoker,type=jrmp

Depends On Me: , ObjectName: jboss.jca:service=LocalTxCM,name=DefaultDS
state: CONFIGURED
I Depend On: jboss.jca:service=ManagedConnectionPool,name=DefaultDS
jboss.jca:service=CachedConnectionManager
jboss.security:service=JaasSecurityManager
jboss:service=TransactionManager

Depends On Me: , 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: , ObjectName: jboss.jca:service=CachedConnectionManager
state: CONFIGURED
I Depend On: jboss:service=TransactionManager

Depends On Me: jboss.jca:service=LocalTxCM,name=DefaultDS
]
10:18:00,000 INFO [URLDeploymentScanner] Started jboss.deployment:type=Deployme
ntScanner,flavor=URL
10:18:00,000 INFO [MainDeployer] Deployed package: file:/C:/jboss-3.2.2/server/
jms_default/conf/jboss-service.xml
10:18:00,000 INFO [Server] JBoss (MX MicroKernel) [3.2.2 (build: CVSTag=JBoss_3
_2_2 date=200310182216)] Started in 3s:485ms

[paveu]

Hi!

Little modifiaction of point 5 above for JBoss 3.2.0 RC4

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

Only then it works correctly. Unless there's something missing in description above my "Add:" which I don't know, and point 5 was OK.

Greetings
Pawel

[jj]

I can start JMS with 3.2.0 using this approach. However, I get the following when trying to stop jboss.

I'd appreciate any suggestions. Thanks in advance,
jj

bash-2.05# ./jboss_init stop
CMD_STOP = java -classpath /private/app/jboss/jboss-3.2.0/bin/shutdown.jar:/private/app/jboss/jboss-3.2.0/client/jnet.jar org.jboss.Shutdown --shutdown
Exception in thread "main" javax.naming.NameNotFoundException: jmx not bound
at org.jnp.server.NamingServer.getBinding(NamingServer.java:495)
at org.jnp.server.NamingServer.getBinding(NamingServer.java:503)
at org.jnp.server.NamingServer.getObject(NamingServer.java:509)
at org.jnp.server.NamingServer.lookup(NamingServer.java:253)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:261)
at sun.rmi.transport.Transport$1.run(Transport.java:148)
at java.security.AccessController.doPrivileged(Native Method)
at sun.rmi.transport.Transport.serviceCall(Transport.java:144)
at sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:460)
at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:701)
at java.lang.Thread.run(Thread.java:536)
at sun.rmi.transport.StreamRemoteCall.exceptionReceivedFromServer(StreamRemoteCall.java:247)
at sun.rmi.transport.StreamRemoteCall.executeCall(StreamRemoteCall.java:223)
at sun.rmi.server.UnicastRef.invoke(UnicastRef.java:133)
at org.jnp.server.NamingServer_Stub.lookup(Unknown Source)
at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:492)
at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:471)
at javax.naming.InitialContext.lookup(InitialContext.java:347)
at org.jboss.Shutdown.main(Shutdown.java:180)

[avenet]

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.

[arabin]

I am going to install this minimal configuration for JBoss 3.2.2RC3.
Do I need to have Tomcat JBossWeb HTTP server or do I need to have integrated Jetty 4.2.11 instead of Tomcat or does it matter at all?
Is the advice to have Jetty above actually an advice to have any Web/JBoss or should it be necessarily Jetty?
And another question. Will I be able to deploy MBeans and invoke methods on them with this type of installation? Or is JMX-Console not enough for that?

[arabin]

Basicly, I am asking about MBeans that are prepared by user from cratch and deployed, not only standard predefined MBeans, provided by JBoss.

[arabin]

I was trying to use that approach for JBoss 3.2.2RC3 (which came from installation for JBoss with
Tomcat JBossWeb HTTP server jboss-3.2.2RC3.zip)

I copied contents jboss\server\default directory to jboss\server\jms_minimal and fulfilled
the instructions for this local folder (I kept the initial folders all, minimal and default) and for jboss\client folder. So, when I start the server, I start it "run -c jms_minimal"

I have the following problems with it.
1. There is not file cacerts in jboss\client directory. So, I could not keep it.
2. There is no directory jbossweb.sar in jboss\server\jms_minimal\deploy, so I could not not keep it.
3. The files jbossmq-destinations-service.xml and jbossmq-service.xml are not directly under
jboss\server\jms_minimal\deploy but rather in jboss\server\jms_minimal\deploy\jms
So, I kept them in jboss\server\jms_minimal\deploy\jms directory and removed anything else from
jboss\server\jms_minimal\deploy\jms directory

I fullfilled the rest of the instructions successfully.
However, when I try to start jboss using "run -c jms_minimal" command, I have the following output.
This output shows that there are some errors.
Also, JMX_Console http://localhost:8080/jmx-console/ says "the page cannot be displayed".
Is there any solution to the problem in 3.2.2RC3



C:\jboss-3.2.2RC3\bin>run -c jms_minimal
===============================================================================
.
JBoss Bootstrap Environment
.
JBOSS_HOME: C:\jboss-3.2.2RC3\bin\\..
.
JAVA: C:\Sun\j2eesdk1.4_beta2\jdk\bin\java
.
JAVA_OPTS: -Dprogram.name=run.bat
.
CLASSPATH: ;C:\Sun\j2eesdk1.4_beta2\jdk\lib\tools.jar;C:\jboss-3.2.2RC3\bin\\r
un.jar
.
===============================================================================
.
13:13:47,515 INFO [Server] Starting JBoss (MX MicroKernel)...
13:13:47,515 INFO [Server] Release ID: JBoss [WonderLand] 3.2.2RC3 (build: CVST
ag=JBoss_3_2_2_RC3 date=200308241317)
13:13:47,515 INFO [Server] Home Dir: C:\jboss-3.2.2RC3
13:13:47,515 INFO [Server] Home URL: file:/C:/jboss-3.2.2RC3/
13:13:47,531 INFO [Server] Library URL: file:/C:/jboss-3.2.2RC3/lib/
13:13:47,531 INFO [Server] Patch URL: null
13:13:47,531 INFO [Server] Server Name: jms_minimal
13:13:47,531 INFO [Server] Server Home Dir: C:\jboss-3.2.2RC3\server\jms_minima
l
13:13:47,531 INFO [Server] Server Home URL: file:/C:/jboss-3.2.2RC3/server/jms_
minimal/
13:13:47,531 INFO [Server] Server Data Dir: C:\jboss-3.2.2RC3\server\jms_minima
l\data
13:13:47,531 INFO [Server] Server Temp Dir: C:\jboss-3.2.2RC3\server\jms_minima
l\tmp
13:13:47,546 INFO [Server] Server Config URL: file:/C:/jboss-3.2.2RC3/server/jm
s_minimal/conf/
13:13:47,546 INFO [Server] Server Library URL: file:/C:/jboss-3.2.2RC3/server/j
ms_minimal/lib/
13:13:47,546 INFO [Server] Root Deployemnt Filename: jboss-service.xml
13:13:47,546 INFO [Server] Starting General Purpose Architecture (GPA)...
13:13:47,718 INFO [ServerInfo] Java version: 1.4.1_02,Sun Microsystems Inc.
13:13:47,718 INFO [ServerInfo] Java VM: Java HotSpot(TM) Client VM 1.4.1_02-b06
,Sun Microsystems Inc.
13:13:47,718 INFO [ServerInfo] OS-System: Windows XP 5.1,x86
13:13:47,765 INFO [ServiceController] Controller MBean online
13:13:47,796 INFO [MainDeployer] Creating
13:13:47,828 INFO [MainDeployer] Created
13:13:47,828 INFO [MainDeployer] Starting
13:13:47,828 INFO [MainDeployer] Started
13:13:47,875 INFO [JARDeployer] Creating
13:13:47,890 INFO [JARDeployer] Created
13:13:47,890 INFO [JARDeployer] Starting
13:13:47,890 INFO [MainDeployer] Adding deployer: org.jboss.deployment.JARDeplo
yer@4e79f1
13:13:47,890 INFO [JARDeployer] Started
13:13:47,906 INFO [SARDeployer] Creating
13:13:47,921 INFO [SARDeployer] Created
13:13:47,921 INFO [SARDeployer] Starting
13:13:47,921 INFO [MainDeployer] Adding deployer: org.jboss.deployment.SARDeplo
yer@134a7d8
13:13:47,937 INFO [SARDeployer] Started
13:13:47,937 INFO [Server] Core system initialized
13:13:47,953 INFO [MainDeployer] Starting deployment of package: file:/C:/jboss
-3.2.2RC3/server/jms_minimal/conf/jboss-service.xml
13:13:49,046 INFO [Log4jService] Creating
13:13:49,046 INFO [Log4jService$URLWatchTimerTask] Configuring from URL: resour
ce:log4j.xml
13:13:49,234 INFO [Log4jService] Created
13:13:49,234 INFO [NamingService] Creating
13:13:49,234 INFO [NamingService] Created
13:13:49,234 INFO [JNDIView] Creating
13:13:49,234 INFO [JNDIView] Created
13:13:49,234 INFO [SecurityConfig] Creating
13:13:49,234 INFO [SecurityConfig] Created
13:13:49,234 INFO [XMLLoginConfig] Creating
13:13:49,234 INFO [XMLLoginConfig] Created
13:13:49,234 INFO [JaasSecurityManagerService] Creating
13:13:49,250 INFO [JaasSecurityManagerService] Created
13:13:49,250 INFO [URLDeploymentScanner] Creating
13:13:49,250 INFO [AbstractDeploymentScanner$ScannerThread] Running
13:13:49,250 INFO [URLDeploymentScanner] Created
13:13:49,250 INFO [Log4jService] Starting
13:13:49,250 INFO [Log4jService] Started
13:13:49,250 INFO [NamingService] Starting
13:13:49,250 INFO [NamingService] Starting jnp server
13:13:49,312 INFO [NamingService] Started jnpPort=1099, rmiPort=0, backlog=50,
bindAddress=null, Client SocketFactory=null, Server SocketFactory=null
13:13:49,328 INFO [NamingService] Listening on port 1099
13:13:49,343 INFO [NamingService] Started
13:13:49,343 INFO [JNDIView] Starting
13:13:49,343 INFO [JNDIView] Started
13:13:49,343 INFO [SecurityConfig] Starting
13:13:49,343 INFO [SecurityConfig] Started
13:13:49,343 INFO [XMLLoginConfig] Starting
13:13:49,390 INFO [XMLLoginConfig] Started
13:13:49,390 INFO [JaasSecurityManagerService] Starting
13:13:49,406 INFO [JaasSecurityManagerService] Started
13:13:49,406 INFO [URLDeploymentScanner] Starting
13:13:49,406 INFO [MainDeployer] Starting deployment of package: file:/C:/jboss
-3.2.2RC3/server/jms_minimal/deploy/jboss-jca.sar
13:13:49,484 INFO [RARDeployer] Creating
13:13:49,500 INFO [RARDeployer] Created
13:13:49,500 INFO [XSLSubDeployer] Creating
13:13:49,671 INFO [XSLSubDeployer] Created templates: org.apache.xalan.template
s.StylesheetRoot@364641
13:13:49,671 INFO [XSLSubDeployer] Created
13:13:49,671 INFO [RARDeployer] Starting
13:13:49,671 INFO [MainDeployer] Adding deployer: org.jboss.resource.RARDeploye
r@13e754f
13:13:49,671 INFO [RARDeployer] Started
13:13:49,671 INFO [XSLSubDeployer] Starting
13:13:49,671 INFO [MainDeployer] Adding deployer: org.jboss.deployment.XSLSubDe
ployer@187c55c
13:13:49,671 INFO [XSLSubDeployer] Started
13:13:49,671 INFO [MainDeployer] Deployed package: file:/C:/jboss-3.2.2RC3/serv
er/jms_minimal/deploy/jboss-jca.sar
13:13:49,671 INFO [MainDeployer] Starting deployment of package: file:/C:/jboss
-3.2.2RC3/server/jms_minimal/deploy/jmx-ejb-connector-server.sar
13:13:49,687 INFO [MainDeployer] Deployed package: file:/C:/jboss-3.2.2RC3/serv
er/jms_minimal/deploy/jmx-ejb-connector-server.sar
13:13:49,687 INFO [MainDeployer] Starting deployment of package: file:/C:/jboss
-3.2.2RC3/server/jms_minimal/deploy/jmx-invoker-adaptor-server.sar/
13:13:49,750 INFO [InvokerAdaptorService] Creating
13:13:49,750 INFO [InvokerAdaptorService] Created
13:13:49,750 INFO [InvokerAdaptorService] Starting
13:13:49,765 INFO [InvokerAdaptorService] Started
13:13:49,765 INFO [MainDeployer] Deployed package: file:/C:/jboss-3.2.2RC3/serv
er/jms_minimal/deploy/jmx-invoker-adaptor-server.sar/
13:13:49,765 INFO [MainDeployer] Starting deployment of package: file:/C:/jboss
-3.2.2RC3/server/jms_minimal/deploy/jmx-rmi-adaptor.sar/
13:13:49,781 INFO [RMIAdaptorService] Creating
13:13:49,781 INFO [RMIAdaptorService] Created
13:13:49,781 INFO [RMIAdaptorService] Starting
13:13:49,812 INFO [RMIAdaptorService] Started
13:13:49,812 INFO [MainDeployer] Deployed package: file:/C:/jboss-3.2.2RC3/serv
er/jms_minimal/deploy/jmx-rmi-adaptor.sar/
13:13:49,812 INFO [MainDeployer] Starting deployment of package: file:/C:/jboss
-3.2.2RC3/server/jms_minimal/deploy/jboss-local-jdbc.rar
13:13:49,968 INFO [RARDeployer] nested deployment: file:/C:/jboss-3.2.2RC3/serv
er/jms_minimal/tmp/deploy/tmp48603jboss-local-jdbc.rar-contents/jboss-local-jdbc
.jar
13:13:49,984 INFO [MainDeployer] Deployed package: file:/C:/jboss-3.2.2RC3/serv
er/jms_minimal/deploy/jboss-local-jdbc.rar
13:13:49,984 INFO [MainDeployer] Starting deployment of package: file:/C:/jboss
-3.2.2RC3/server/jms_minimal/deploy/hsqldb-ds.xml
13:13:50,046 INFO [XSLSubDeployer] transformed into doc: [#document: null]
13:13:50,125 INFO [HypersonicDatabase] Creating
13:13:50,125 INFO [HypersonicDatabase] Created
13:13:50,125 INFO [RARDeployment] Creating
13:13:50,125 INFO [RARDeployment] Created
13:13:50,125 INFO [JBossManagedConnectionPool] Creating
13:13:50,125 INFO [JBossManagedConnectionPool] Created
13:13:50,125 INFO [HypersonicDatabase] Starting
13:13:50,125 INFO [HypersonicDatabase] Started
13:13:50,140 INFO [RARDeployment] Starting
13:13:50,156 INFO [STDOUT] server.properties not found, using command line or d
efault properties
13:13:50,156 INFO [STDOUT] Opening database: C:\jboss-3.2.2RC3\server\jms_minim
al\data\hypersonic\default
13:13:50,156 INFO [STDOUT] HSQLDB server 1.7.1 is running
13:13:50,156 INFO [STDOUT] Use SHUTDOWN to close normally. Use [Ctrl]+[C] to ab
ort abruptly
13:13:50,171 INFO [RARDeployment] Started
13:13:50,171 INFO [JBossManagedConnectionPool] Starting
13:13:50,171 INFO [JBossManagedConnectionPool] Started
13:13:50,187 INFO [MainDeployer] Deployed package: file:/C:/jboss-3.2.2RC3/serv
er/jms_minimal/deploy/hsqldb-ds.xml
13:13:50,187 INFO [MainDeployer] Starting deployment of package: file:/C:/jboss
-3.2.2RC3/server/jms_minimal/deploy/cache-invalidation-service.xml
13:13:50,234 INFO [InvalidationManager] Creating
13:13:50,234 INFO [InvalidationManager] Created
13:13:50,234 INFO [InvalidationManager] Starting
13:13:50,234 INFO [InvalidationManager] Starting Invalidation Manager jboss.cac
he:service=InvalidationManager
13:13:50,234 INFO [InvalidationManager] Started
13:13:50,234 INFO [MainDeployer] Deployed package: file:/C:/jboss-3.2.2RC3/serv
er/jms_minimal/deploy/cache-invalidation-service.xml
13:13:50,234 INFO [MainDeployer] Starting deployment of package: file:/C:/jboss
-3.2.2RC3/server/jms_minimal/deploy/jms/jbossmq-destinations-service.xml
13:13:50,375 INFO [MainDeployer] Deployed package: file:/C:/jboss-3.2.2RC3/serv
er/jms_minimal/deploy/jms/jbossmq-destinations-service.xml
13:13:50,375 INFO [MainDeployer] Starting deployment of package: file:/C:/jboss
-3.2.2RC3/server/jms_minimal/deploy/jms/jbossmq-service.xml
13:13:50,453 INFO [STDOUT] Mon Sep 08 13:13:50 GMT-05:00 2003 Listening for con
nections ...
13:13:50,531 INFO [DynamicStateManager] Creating
13:13:50,531 INFO [DynamicStateManager] Created
13:13:50,531 INFO [DynamicStateManager] Starting
13:13:50,546 INFO [DynamicStateManager] Started
13:13:50,546 INFO [MainDeployer] Deployed package: file:/C:/jboss-3.2.2RC3/serv
er/jms_minimal/deploy/jms/jbossmq-service.xml
13:13:50,546 INFO [MainDeployer] Starting deployment of package: file:/C:/jboss
-3.2.2RC3/server/jms_minimal/deploy/transaction-service.xml
13:13:50,562 INFO [CachedConnectionManager] Creating
13:13:50,562 INFO [CachedConnectionManager] Created
13:13:50,562 INFO [CachedConnectionManager] Starting
13:13:50,640 INFO [CachedConnectionManager] Started
13:13:50,640 INFO [MainDeployer] Deployed package: file:/C:/jboss-3.2.2RC3/serv
er/jms_minimal/deploy/transaction-service.xml
13:13:50,640 INFO [MainDeployer] Starting deployment of package: file:/C:/jboss
-3.2.2RC3/server/jms_minimal/deploy/jmx-console.war/
13:13:50,640 INFO [MainDeployer] deployment waiting for deployer: file:/C:/jbos
s-3.2.2RC3/server/jms_minimal/deploy/jmx-console.war/
13:13:50,640 INFO [MainDeployer] Deployment of package: file:/C:/jboss-3.2.2RC3
/server/jms_minimal/deploy/jmx-console.war/ is waiting for an appropriate deploy
er.
13:13:50,640 ERROR [URLDeploymentScanner] MBeanException: Exception in MBean ope
ration 'checkIncompleteDeployments()'
Cause: Incomplete Deployment listing:
Packages waiting for a deployer:
[org.jboss.deployment.DeploymentInfo@9bede379 { url=file:/C:/jboss-3.2.2RC3/serv
er/jms_minimal/deploy/jmx-console.war/ }
deployer: null
status: null
state: INIT_WAITING_DEPLOYER
watch: file:/C:/jboss-3.2.2RC3/server/jms_minimal/deploy/jmx-console.war/
lastDeployed: 1063044830640
lastModified: 1063037026734
mbeans:
]Incompletely deployed packages:
[org.jboss.deployment.DeploymentInfo@9bede379 { url=file:/C:/jboss-3.2.2RC3/serv
er/jms_minimal/deploy/jmx-console.war/ }
deployer: null
status: null
state: INIT_WAITING_DEPLOYER
watch: file:/C:/jboss-3.2.2RC3/server/jms_minimal/deploy/jmx-console.war/
lastDeployed: 1063044830640
lastModified: 1063037026734
mbeans:
]MBeans waiting for classes:

MBeans waiting for other MBeans:
[ObjectName: jboss.jmx:type=adaptor,name=Invoker,protocol=jrmp,service=proxyFact
ory
state: CONFIGURED
I Depend On: jboss:service=invoker,type=jrmp

Depends On Me: , ObjectName: jboss.jca:service=LocalTxCM,name=DefaultDS
state: CONFIGURED
I Depend On: jboss.jca:service=ManagedConnectionPool,name=DefaultDS
jboss.jca:service=CachedConnectionManager
jboss.security:service=JaasSecurityManager
jboss:service=TransactionManager

Depends On Me: , 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: ]
13:13:50,703 INFO [URLDeploymentScanner] Started
13:13:50,703 INFO [MainDeployer] Deployed package: file:/C:/jboss-3.2.2RC3/serv
er/jms_minimal/conf/jboss-service.xml
13:13:50,703 INFO [Server] JBoss (MX MicroKernel) [3.2.2RC3 (build: CVSTag=JBos
s_3_2_2_RC3 date=200308241317)] Started in 3s:157ms

[arabin]

I actually fulfilled the same stape based on 3.2.2RC3 installation for JBoss with Jetty (instead of Tomcat). Then it is more clear to me what is jbossweb-jetty.sar directory - that is probably what is an equivalent of jbossweb.sar in 3.2.1.
I was able to start jmx console. However, the server did not start correctly - I still see an error

I would prefer the DestinationManager to start as well, if possible.

16:22:13,156 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.jmx:type=adaptor,name=Invoker,protocol=jrmp,service=proxyFact
ory
state: CONFIGURED
I Depend On: jboss:service=invoker,type=jrmp

Depends On Me: , ObjectName: jboss.jca:service=LocalTxCM,name=DefaultDS
state: CONFIGURED
I Depend On: jboss.jca:service=ManagedConnectionPool,name=DefaultDS
jboss.jca:service=CachedConnectionManager
jboss.security:service=JaasSecurityManager
jboss:service=TransactionManager

Depends On Me: , 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: ]
16:22:13,218 INFO [URLDeploymentScanner] Started
16:22:13,218 INFO [MainDeployer] Deployed package: file:/C:/jboss-3.2.2RC3_jett
y-4.2.11/server/jms_minimal/conf/jboss-service.xml
16:22:13,218 INFO [Server] JBoss (MX MicroKernel) [3.2.2RC3 (build: CVSTag=JBos
s_3_2_2_RC3 date=200308241317)] Started in 5s:562ms

[jeroly]

1. Could somebody please update the modifications required to have a standalone distribution of JBossMQ under 3.2.2 RC4?

2. I'm interested in running JBossMQ on an XBox running Debian Linux.

--> a. Is anybody else out there doing this?
--> b. The XBox only has 64MB RAM. Does anybody out there have a feel as to whether performance will be acceptable with this level of RAM?

Thanks in advance,
Jerry Paulson

[juha]

The jmx-console servlet is not finding a deployer (that's the first issue), did you remove the servlet container from your config?

-- Juha