JBoss 3.2.3 JMS Q for A

[northwhite]

Browsing all kind of forums and official JBoss document, we still cannot find answes for certain questions. Please help.

1. jms-ds.xml

The JMS provider is configured as


DefaultJMSProvider

org.jboss.jms.jndi.JBossMQProvider

java:/XAConnectionFactory
java:/XAConnectionFactory


The question is what's the purpose of attribute name="QueueFactoryRef">java:/XAConnectionFactory ?

2. Transacted JMS

It's said that by using java:/JmsXA, we'll have transacted JMS. The question is which IL is being used by the connection pool refered by java:/JmsXA


3. Pooled connections

We have an application which sends messages within session beans to MDBs. Whenever we want to send a message, we have to go thru open connection, ..., send, ..., close connection. Is there a way to use pooled connections. The reason is that seems constantly open/close connection is causing JMS hang (after certain (large) number of messages).

[adrian.brock]

Didn't look very hard did you. I know all these questions are answered in this
forum, because I answered them.

I'm surprised you couldn't figure out the first two questions from the FAQ topic
where it explains how to configure jms-ds.xml for remote access.

You also didn't "READ THIS FIRST" or at least missed the part where it
says "One question, one topic"

You are already in my bad books.

1) It is the jndi reference of the real connection factory

2) The one in question 1

3) No, you have probably misconfigured the cache and JBossMQ is spending most of
its time moving messages to and from disk.
The other alternative is that an internal error has occurred in JBossMQ (probably because you are using hsqldb). See the "READ ME FIRST" for how to debug this.

[northwhite]

Thanks for providing "definite" answers.

For question 3, we are using MySQL as persistence manager, and water marks are set properly (350/400) I think for Xmx1024.

[adrian.brock]

????

So at 400M you have no messages in memory and 600M of free heap.

Regards,
Adrian

[adrian.brock]

That should be:

You potentially have no messages in memory at 400M if that 400M of heap
is used by something other than JBossMQ

[northwhite]

Or, the most part of 400M are messages, then processing logic kick in which begins to comsume the heap left.

[adrian.brock]

???

JBossMQ does not know what is messages and what is other. It doesn't do any book
keeping to say I have this many bytes of messages in memory. It just uses the JVM
heap size.

http://jboss.org/wiki/Wiki.jsp?page=MessageSoftening

Regards,
Adrian