Gary Tully wrote:
>
> in transacted mode, who is managing the transaction demarcation? In
> other words, where is the session.commit() call?
>
it turns out that this issue was not related to the other issues in this
thread.
i had failed to make the message-producers commit and this was respon
gregory.guibert wrote:
>
> Thank you for the link on OpenDS, it looks great and seems to solve half
> my
> problem (alignment of data) :-)
> ...
> When using a jndi.properties file to create an initial context, the file
> looks like this:
> java.naming.factory.initial = com.sun.jndi.ldap.LdapCtx
Gary Tully wrote:
>
> in transacted mode, who is managing the transaction demarcation? In
> other words, where is the session.commit() call?
>
This is a session based transaction as opposed to an external JTA operation.
The COMMIT is, therefore, made against the jms session object.
The call
at least one in the thread mentioned persistence and i wonder if my problem
is related.
i am newbie/retarded and cannot get my embedded broker to deliver transacted
messages to my async client in my ActiveMQ 5.2 environment.
connection.createSession(false, Session.AUTO_ACKNOWLEDGE) works: messag
gregory.guibert wrote:
>
> In addition to the JMS-related objects, I need to bind/lookup other kinds
> of
> objects, so, the JNDI provider does not exactly fits my needs.
> Using ActiveMQ with failover mechanism, I am searching for a JNDI
> implementation with an equivalent *failover *mechanism
