JBoss 5.1.0GA with JBM2.0.0. b3

[guntherv]

Hi

I've integrated JBM 2.0.0 Beta 3 with JBoss AS 5.1.0GA using the Ant script provided with JBM. This worked fine but somehow I fail to register a custom queue on the system.

I copied the files delivered with JBM (config\jboss-as\non-clustered) to the JBOSS\server\default-with-jbm2 profile and get errors about beans that are already present. If I skip the jbm-jboss-beans.xml file, no errors are shown but I fail to find my custom defined queue.

As a JBM newbie I don't understand why I get this error? Somehow JBM must already be there. And if it is active, I wonder why I can't find my queue using the Admin Console? I'm sure I'm missing something crucial here.

I simply registered 2 queues in the jbm-jms.xml file.

<configuration xmlns="urn:jboss:messaging"
 xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
 xsi:schemaLocation="urn:jboss:messaging /schema/jbm-jms.xsd">

 <connection-factory name="ConnectionFactory">
 <connector-ref connector-name="netty"/>
 <entries>
 <entry name="ConnectionFactory"/>
 </entries>
 </connection-factory>

 <queue name="pbRequestQueue">
 <entry name="/queue/pbRequestQueue"/>
 </queue>
 <queue name="pbResponseQueue">
 <entry name="/queue/pbResponseQueue"/>
 </queue>

</configuration>

Thank you in advance for your reply.

[timfox]

Hi Gunther-

If you run the ant install script as mentioned in the quick start guide (after setting JBOSS_HOME) as described in http://labs.jboss.com/file-access/default/members/jbossmessaging/freezone/docs/quickstart-2.0.0.beta2/html/installation.html#installation.jboss then it should create a default-with-jbm2 profile and you don't need to manually copy any other files over.

To validate that JBM 2.0 was installed correctly you can try running the javaee examples as explained in the examples chapter. If these examples run ok you know you installed JBM alright. Otherwise it's likely it's a botched install, in which case I suggest starting the installation again with a fresh download of JBoss AS and JBM 2.0.

[ataylor]

firstly, you shouldn't need to copy any files the install script does this for you.

also, can you use the jmx console not the admin console. have you tried sending messages to the queue?

[timfox]

"ataylor" wrote:
firstly, you shouldn't need to copy any files the install script does this for you.

also, can you use the jmx console not the admin console. have you tried sending messages to the queue?

+1. JBM 2.0 *as yet* is not managed by the JBoss AS 5 admin console.

[guntherv]

First, thank you for your quick replies.

I ran the JBM JEE samples which integrate with JBoss and they all run fine. So that is good news. Next I tried to find the testQueue of the MDB sample using the JMX console as pointed out by ataylor, but I fail to find the MBean.
Also I still don't understand where/how you need to register your queues and stuff. For example the server config files delivered with the samples, where are they put under the server profile?

Can someone please shed some light here ;-), cause I'm getting a bit confused.

Thank you in advance

[ataylor]

have a look at http://labs.jboss.com/file-access/default/members/jbossmessaging/freezone/docs/usermanual-2.0.0.beta3/html_single/index.html#predefined.queues

[guntherv]

Tx, Andy

Do you customize the default-with-jbm2/deploy/messaging.sar/jbm-jms.xml file or can you just a well drop-in your own jbm-jms.xml file in the deploy folder or a subfolder? Is the filename fixed or can you choose your own name?

[ataylor]

"guntherv" wrote:
Tx, Andy

Do you customize the default-with-jbm2/deploy/messaging.sar/jbm-jms.xml file or can you just a well drop-in your own jbm-jms.xml file in the deploy folder or a subfolder? Is the filename fixed or can you choose your own name?

what ever is easiest for you, the filename is fixed tho'

[jmesnil]

"guntherv" wrote:
Next I tried to find the testQueue of the MDB sample using the JMX console as pointed out by ataylor, but I fail to find the MBean.

There is a bug in JBM 2.0.0.Beta3 which prevents its MBeans to show up in AS 5 JMX console.
The bug is fixed in the trunk and there is a workaround for Beta3, see http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4240363

[simon_temple]

I performed the workaround for BETA3 and can see the org.jboss.messaging node in the JMX console.

Why didn't you use the jboss.messaging name that already exists in JBAS5.1?