Re: [Springframework-developer] JMS questions

[<sk...@fe...>]

There was an email today, from Juergen,  saying that JMS support would
"most likely" be in by the end of July? I don't recall what release that
cooresponds to not 1.1 final I believe it must have been some 1.2 version.
Check the archives from today for details, see Juergen post on releases.

By transactions and JMS I assume you mean a transacted JMS Session with
some support for that in the P2pTemplate or the PubSubTemplate for commits
and rollbacks. I don't see that level of support in there currently.

In general it sounds like your "auto-commit" option works with some
exceptions and your transacted JMS session does not work. BTW the ack mode
doesn't mean much for a transacted session. One generally passes in -1 or 0
to show that. Now that your telling the JMS Session to be transacted your
going to have to have some transaction code in there, commit or rollback
for example. It also matters where your transacted session is setup on the
sender or the receiver. I can't really tell but it sounds like you have
setup a transacted session when you send the message only and the session
is waiting for that commit to actually send the message. One would use this
type of functionality to send a group of messages atomically I would think.

But really it sounds to me like you need to manage event propagation with
some type of bean transaction. Iff, if and only if, your transacted bean
does something good put a message on a JMS Destination. It doesn't sound to
me like your having JMS problems but general transaction flow problems.
That is your, messages were being sent fine, until you started tweaking the
nobs, but are being sent at the wrong time in a transactions lifecycle.
FWIW.

SKroah





|---------+----------------------------------------------------->
|         |           "Les A. Hazlewood" <le...@ha...>    |
|         |           Sent by:                                  |
|         |           spr...@li...|
|         |           ceforge.net                               |
|         |                                                     |
|         |                                                     |
|         |           06/28/2004 03:18 PM                       |
|         |           Please respond to                         |
|         |           springframework-developer                 |
|         |                                                     |
|---------+----------------------------------------------------->
  >----------------------------------------------------------------------------------------------|
  |                                                                                              |
  |       To:       spr...@li...                              |
  |       cc:                                                                                    |
  |       Subject:  [Springframework-developer] JMS questions                                    |
  >----------------------------------------------------------------------------------------------|




Hiya folks,

I was wondering if anyone had any thoughts on when the JMS components would
be
integrated into a Spring release?  I'm not looking for any specific
dates...just a ballpark figure (and yes, I know that this is an Open Source
product, so I take ballpark figures with a grain of salt...I'm just looking
for
something, anything).

Also, I was wondering if anyone could help me out with some insight....

Here's my issue:

An EJB method is called from a remote client.  In response to that method
call,
some data is processed, saved back to the db, and then a JMS message is
published to all clients who care about that data.  The data is not
committed
until the end of the transaction.

The JMS message is received by a client which then immediately requests the
data
that was just updated.

Occasionally, when the client requests this data, it doesn't get what it
expects.  The reason for this is that we think the client is making a
request
for the data before the first transaction has had a chance to commit/flush.

So, basically, we'd like to sync the JMS sending to only send upon
transaction
commit, to ensure that the data will be in the db by the time the clients
request it.

I tried setting the JMS transacted attribute to true when creating a topic
session,
i.e.

topicSession =
    topicConnection.createTopicSession(true, Session.AUTO_ACKNOWLEDGE );


After reading the JMS spec, this is all that should be necessary when
participating in transactions in a J2EE container.

However, we're seeing that the client's don't receive _any_ messages from
the
server when set to true.  When set to false, the messages are being sent,
but
that synchronization issue pops its head up.

Does anyone have any insights on why this is happening?

Also, does the Spring JMS support in the sandbox already work with
integrating
into transactions, like the Spring Hibernate support does?

Any ideas would be graciously received.

Regards,

Les


-------------------------------------------------------
This SF.Net email sponsored by Black Hat Briefings & Training.
Attend Black Hat Briefings & Training, Las Vegas July 24-29 -
digital self defense, top technical experts, no vendor pitches,
unmatched networking opportunities. Visit www.blackhat.com
_______________________________________________
Springframework-developer mailing list
Spr...@li...
https://lists.sourceforge.net/lists/listinfo/springframework-developer