Hi,
I am using JBoss-2.4.9, J2SDK1.4.1, WinXP SP1.
Changed configs:
- in jmboss.jcml I changed the persistence manager to
"org.jboss.mq.pm.file.PersistenceManager"
- in standardjboss.xml I've changed the "Standard Message Driven
Bean" container param <MaximumSize>1</MaximumSize>
I know that jms-1.0.2b states (section 4.4.10) that the "JMS defines
that messages sent by a session to a destination must be received in the
order in witch they where sent ..." and further "The only ordering that
is visible to receiving clients is the order of messages a session send
to a particular destination."
Given a SINGLE PRODUCER - SINGLE CONSUMER - ONE DESTINATION design:
- the producer could be a separate JVM connecting to JBossMQ
over OIL or a SLSB using JVM protocol with transactional JMS delivery
- the consumer can be MDB or a separate JVM client
- the messages can be sent as goups(one group per QueueSession)
but always by only one thread.
Question:does JBossMQ guarantee in any way that I will have a FIFO
behaviour? BTW, this knowledge is almost fatal for our app. cause if the
order of delivery is not kept we are in big trouble.
Thanks,
Horia
-------------------------------------------------------
This SF.NET email is sponsored by:
SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See!
http://www.vasoftware.com
_______________________________________________
JBoss-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-user
- [JBoss-user] Strange Exception: JMS -> MDB -> Session ... joerg maier
- Re: [JBoss-user] Strange Exception: JMS -> MDB ->... Scott M Stark
- Re: [JBoss-user] Strange Exception: JMS -> MDB -... joerg maier
- Re: [JBoss-user] Strange Exception: JMS -> M... Scott M Stark
- Re: [JBoss-user] Strange Exception: JMS -&g... joerg maier
- Re: [JBoss-user] Strange Exception: JM... Scott M Stark
- Muntean Horia