On 23/01/2008, b_w <[EMAIL PROTECTED]> wrote:
>
> Hi James
>
> AMQ 5.0 successfully implemented with Spring 2.5.1 and Hibernate 3.2.5
>
> Took a while to get all the dependencies ironed out as well as modify a few
> deprecated options but
> got there in the end.
>
> The most noteworthy options to c
Hi James
AMQ 5.0 successfully implemented with Spring 2.5.1 and Hibernate 3.2.5
Took a while to get all the dependencies ironed out as well as modify a few
deprecated options but
got there in the end.
The most noteworthy options to change were:
replacing usageManger with systemUsage
Hi James
AMQ 5.0 successfully implemented with Spring 2.5.1 and Hibernate 3.2.5
Took a while to get all the dependencies ironed out as well as modify a few
deprecated options but
got there in the end.
The most noteworthy options to change were:
replacing usageManger with systemUsage
On 22/01/2008, b_w <[EMAIL PROTECTED]> wrote:
>
> At the bottom of this page under the BACKGROUND section:
> http://activemq.apache.org/version-5-xml-configuration.html
>
> So we use the Spring XML configuration file format
>
> The link from Spring XML gives a 404.
Link now fixed
http://cwiki.apac
At the bottom of this page under the BACKGROUND section:
http://activemq.apache.org/version-5-xml-configuration.html
So we use the Spring XML configuration file format
The link from Spring XML gives a 404.
Thanks for the feedback and I'll let you know if we make any progress with
the Spring 2.5
On 22/01/2008, b_w <[EMAIL PROTECTED]> wrote:
>
> Thanks James.
>
> If you don't mind, a couple more questions. The builds we are using are:
> AMQ 5.0.0
> Spring 2.5.1
> Tomcat 5.5.25
> Java 1.5.0
> Hibernate 3.2.5 (any risk of conflicting libs?)
We've not yet tried Spring 2.5.x with ActiveMQ/xbe
Thanks James.
If you don't mind, a couple more questions. The builds we are using are:
AMQ 5.0.0
Spring 2.5.1
Tomcat 5.5.25
Java 1.5.0
Hibernate 3.2.5 (any risk of conflicting libs?)
Does this jive?
And, the url in the documentation linking to a sample Spring 2 XML is http
404. Believe it was
I'm not sure - but there's no real point using failover with the vm
transport and specifying maxInactivityDuration. If you are using VM
then the broker is always in RAM and there's no chance of sockets
failing. So change your URL to just
vm://localhost?brokerConfig=xbean:/activemq.xml
On 22/01/20
