[clebert.suconic]

I don't see 1.2.1.SP1, only 1.2.0.SP1, which I already have (jboss-messaging-1.2.0.SP1.zip).

I meant 1.2.0.SP1. Typo!

I tried both 4.0.4.GA and 4.0.5.GA.. and got same results!

Such as? Am I supposed to say a few Hail Mary's? ;)

But seriously, could someone answer the question as to whether these jbossmq-*.jar's or DestinationManager references in the xml files should or shouldn't be there? Maybe I just need to get rid of or alter some files that are interfering?

Can you try running the examples first? It will be better dealing with one problem at a time.

[clebert.suconic]

After running release-admin, the only reference I see to mq is at:

./messaging/deploy/cache-invalidation-service.xml
... Which is commented out.

<!--
 <mbean code="org.jboss.mq.server.jmx.Topic"
 name="jboss.mq.destination:service=Topic,name=JMSCacheInvalidationBridge">
 <depends optional-attribute-name="DestinationManager">jboss.mq:service=DestinationManager</depends>
 <depends optional-attribute-name="SecurityManager">jboss.mq:service=SecurityManager</depends>
 </mbean>

 <mbean code="org.jboss.cache.invalidation.bridges.JMSCacheInvalidationBridge"
 name="jboss.cache:service=InvalidationBridge,type=JavaGroups">
 <depends>jboss.cache:service=InvalidationManager</depends>
 <depends>jboss.mq.destination:service=Topic,name=JMSCacheInvalidationBridge</depends>
 <attribute name="InvalidationManager">jboss.cache:service=InvalidationManager</attribute>
 <attribute name="ConnectionFactoryName">java:/ConnectionFactory</attribute>
 <attribute name="TopicName">topic/JMSCacheInvalidationBridge</attribute>
 <attribute name="PropagationMode">1</attribute>
 </mbean>
-->

And ./messaging/conf/jboss-service.xml, which is being ignored (not affecting anything)

You could do this check yourself:

$ cd $JBOSS_HOME/server/messaging
$ find . -name \*xml -exec grep -H mq {} \;

[clebert.suconic]

You shouldn't make any reference to MQ... look at messaging/deploy/jboss-messaging.sar/destinations-service.xml for information about how to create topics.

[tamaluna]

In conf\jboss-service.xml there's

<mbean code="org.jboss.management.j2ee.LocalJBossServerDomain"
name="jboss.management.local:j2eeType=J2EEDomain,name=Manager">
...
 <attribute name="JMSService">jboss.mq:service=DestinationManager</attribute>
...

In conf\login-config.xml there's

<!-- Security domain for JBossMQ -->
 <application-policy name = "jbossmq">
 <authentication>
 <login-module code = "org.jboss.security.auth.spi.DatabaseServerLoginModule"
 flag = "required">
 <module-option name = "unauthenticatedIdentity">guest</module-option>
 <module-option name = "dsJndiName">java:/DefaultDS</module-option>
 <module-option name = "principalsQuery">SELECT PASSWD FROM JMS_USERS WHERE USERID=?</module-option>
 <module-option name = "rolesQuery">SELECT ROLEID, 'Roles' FROM JMS_ROLES WHERE USERID=?</module-option>
 </login-module>
 </authentication>
 </application-policy>

In conf\standardjboss.xml there are two instances, like this:

<invoker-proxy-binding>
 <name>singleton-message-driven-bean</name>
 <invoker-mbean>default</invoker-mbean>
 <proxy-factory>org.jboss.ejb.plugins.jms.JMSContainerInvoker</proxy-factory>
 <proxy-factory-config>
 <JMSProviderAdapterJNDI>DefaultJMSProvider</JMSProviderAdapterJNDI>
 <ServerSessionPoolFactoryJNDI>StdJMSPool</ServerSessionPoolFactoryJNDI>
 <CreateJBossMQDestination>true</CreateJBossMQDestination>
...

And of course there's lib\jbossmq.jar

What can I do about this?

~PT

[clebert.suconic]

I don't understand what problem those are causing...

You could pretty much ignore them.

The first one is a JSR-77 (management) reference

second one.. is login-config.. which is not being used.


The third one are just invokers configurations... not used by messaging.



You are confusing everybody.. we didn't understand what's your problem until now.

I don't know if you are trying to understand about those references, if your examples are not working, or if you have your own ear which is not working.


Lets start again...


Can you tell us what's going on?

[tamaluna]

My problem initially was that my MDB was not binding, as evidenced by their absence in the jmx-console. I deduced that it was because of the errors I was seeing in the server log.

Well, after re-installing today, I can now see my MDB EJB in the jmx-console. I thought it was still breaking, because I could still see the errors in the server log, and I neglected to look at the jmx-console. Let me do some testing and see if it's working as advertised; maybe those errors were just red herrings.

[timfox]

JBM is a raw JMS provider, it doesnoe handle deployment of MDBs.

Anything to do with MDB deployment is handled by the MDB container which is managed as a separate project by different people.

If you're having problems with MDB deployment, e..g problems getting the descriptors right etc, then you should try posting in the "Messaging, JMS, and JBoss MQ" forum (yes, sorry I know the names are confusing :) ).

Thanks.

[tamaluna]

Ok, I posted my issue on the other forum (http://www.jboss.com/index.html?module=bb&op=viewtopic&t=108476). It has some new information that I didn't have yet when I posted to this forum, so you might have a look and see if you happen to recognize the issue right off the bat. I'm sure all that debug output means a lot more to you guys than it does to me. ;)

~PT