I looked over the examples and did not find one for Sybase.
I did get the datasource configured and I can connect without any issues, but
when ActiveMQ starts it performs a SELECT FOR UPDATE which causes an exception.
I'll try the useDatabaseLock=false and see if it resolves it, but what are the
ramifications if I do this? The row will not be locked so will there be
contention?
I just downloaded the 4.1.2 build. I haven't retrieved the
latest source. Is it stable enough to work in a production
environment?
From: "James Strachan" <[EMAIL PROTECTED]> [mailto:"James Strachan" <[EMAIL PROTECTED]>]
Sent: Tuesday, March 13, 2007 7:37 AM
To: users@activemq.apache.org
Subject: Re: ActiveMQ with Sybase for persistence
<[EMAIL PROTECTED]>wrote:
>
>
> Does anyone have a working example of using ActiveMQ with Sybase ASE as the
> persistence store?
The activemq.xml includes examples of configuring with various JDBC
drivers; it should be a matter of just tweaking those...
> The online docs make mention that Sybase is supported but
> ASE does not support SELECT FOR UPDATE and I was wondering how to configure
> ActiveMQ so it will work.
I've recently patched the 4.2 trunk to work better with TransactSQL
databases (SQLServer / Sybase) to use the 'select * from with XLOCK"
syntax instead...
http://issues.apache.org/activemq/browse/AMQ-1191
you could try using the 4.2-SNAPSHOT distro and seeing if that works for you.
(As a workaround you can add the useDatabaseLock="false" attribute to
the XML element for the database configuration).
--
James
-------
http://radio.weblogs.com/0112098/
