From my highly osgi-centric viewpoint this seems like a good use of running
activemq in an osgi environment exposing services that can be used by e.g. your
REST stuff to publish them externally. Adding servlets would be easy using the
http whiteboard service….
thanks
david jencks
On Apr 17
Maybe the redelivery counter is transactional so if the xa tx rolls back and
redelivery is needed the counter gets reset? this is speculation but might
explain your result.
david jencks
On Oct 16, 2014, at 10:45 AM, Xander Uiterlinden wrote:
> Hi,
>
> I'm trying to implement
Using activemq with a jta transaction manager and using the appropriate xa
interfaces (such as through the resource adapter) will guarantee that a message
is delivered exactly once. Many people prefer to use idempotent messages to
avoid the xa overhead.
david jencks
On Feb 24, 2014, at 6:45
You should ask on appropriate lists for each of those projects, about support
for specific versions.
I know tomcat provides maintenance releases, sometimes including security
fixes, for some major versions other than the latest.
david jencks
On Dec 12, 2013, at 9:39 AM, Ross Dukeshier wrote
the destinations in ldap?
I'm not trying to tell you what you should or shouldn't do, but I'd
like to understand how ldap actually meets your needs... and not
getting it.
thanks
david jencks
On Mar 18, 2009, at 9:56 AM, janylj wrote:
Hello Huntc,
I read your blog especiall
ts as now for client auth
Once you've done this however it looks like there is the same number
of places you'd have secure info on disk as with the plain user/pw +
ldap solution, although the info would be certs rather than passwords.
thanks
david jencks
Kind regards,
Christophe
disk.
Maybe I'm misunderstanding what you are proposing
david jencks
To further aid security I would disallow all but SSL based
communication
with the broker.
Does the strategy make sense? Is there a better way of avoiding
storing
usernames and passwords in the clear?
Than
so
most likely it is fixed well enough for most situations.
thanks
david jencks
On Jan 27, 2009, at 12:16 PM, Rob Davies wrote:
I believe this is fixed in 5.3 - (trunk) - which will be released in
the next few weeks or so
On 27 Jan 2009, at 20:14, MaenXe wrote:
Can I bump my own thread?
Is this the first or second (or later) time your app requests a
connection in this particular xa transaction?
Does the jencks pooling do transaction caching, i.e. make sure the
same connection is always supplied when you request a connection
within an xa tx?
thanks
david jencks
On Jan
cause problems. You might also be able to configure
each test to use a different directory. Or find a way to use the
MemoryPersistenceAdapter. Unfortunately I don't know how to do any of
these things.
thanks
david jencks
My understanding was that there is no possibility of messages
b
You might be looking for something a lot more complicated than
necessary for ActiveMQ. What exactly do you want to look up that
can't be configured in jndi.properties?
thanks
david jencks
On Dec 24, 2008, at 7:15 AM, KLA2008 wrote:
Hello Joe,
jndi.properties file is used by c
le duplicate messages.
There may be other ways to deal with this...
thanks
david jencks
On Nov 28, 2008, at 8:21 AM, Rob Davies wrote:
This is handled by the ActiveMQ failover transport (the default in
5.1 onwards).
It replays messages on your behalf that haven't been acknowledged -
there
12 matches
Mail list logo
