Hi,
I would recommend you use the activemq-core.jar file instead since that
version of the jar file does not include the dependencies like derby.
Regards,
Hiram
Andrew Norman-3 wrote:
>
> We have found the problem, we think. The ActiveMQ project uses derby and
> contains the contents of derby
tabase home is with
> > system properties. So all uses of Derby within a given VM must access
> > the same database home and use the same system-wide configuration.
> >
> > David
> >
> > Hiram Chirino wrote:
> >> Hi Everybody,
> >>
> >> A
Hi Everybody,
ActiveMQ makes extensive use of Derby for storage of it's persistent
messages. You have have done a great job with Derby! Thanks for the
hard work!
One of the things that ActiveMQ supports is running multiple brokers
on 1 JVM. In that case we would actually like to run 2 derby
in
Doh! I had a previous derby version in my classpath! It absolutely
works in 10.1.1.0. Sorry for the noise!
Regards,
Hiram
On Oct 13, 2005, at 9:54 AM, Hiram Chirino wrote:
Hi Dan,
Yep! It was against 10.1.1.0!
Regards,
Hiram
On Oct 13, 2005, at 5:43 AM, Daniel John Debrunner wrote
Hi Dan,
Yep! It was against 10.1.1.0!
Regards,
Hiram
On Oct 13, 2005, at 5:43 AM, Daniel John Debrunner wrote:
Hiram Chirino wrote:
Hi Guys,
Any ideas why http://issues.apache.org/jira/browse/DERBY-621 is
happening to me?
Looks like the same as DERBY-217 which is meant to be fixed in
Hi Guys,
Any ideas why http://issues.apache.org/jira/browse/DERBY-621 is
happening to me?
Regards,
Hiram