4.1 has been released.
-Brian
On Dec 18, 2006, at 11:40 AM, sileshi wrote:
Is 4.1 released? If not, what is rlelease plans?
-Sileshi
Hiram Chirino wrote:
On 10/4/06, yaussy <[EMAIL PROTECTED]> wrote:
Sorry about that. I'd forgotten about the wireformat stuff.
Looks like
you
can set AMQ 4.1 minimum wire format to 1 and then it will connect
to AMQ
4.0.2 (still breaks with AMQ 4.0.1, but 4.0.1 and 4.0.2 work
together).
This gives me the rollout path we need.
Since 4.0.2 has not been officially released, which 4.0.2 versin are
you using? RC4 ?
I think 4.0.2 RC 4 should be able to connecto the 4.1 without any
config changes. A small bug in 4.0 was fixed in 4.0.2 that fixes
auto
wirefomat versin negociation.
Two things though:
1) I could not get multiple connection properties on the TCP
connectors,
such as
tcp://perfgc1a::5112?
minmumWireFormatVersion=1&connectionTimeout=5000.
The
XML parser complained. How should this look??
in XML you need replace all the '&' with '&'
2) Even with minmumWireFormatVersion=1, will two AMQ 4.1 brokers
connect
using their newer v2 format?
Hum they should. Sees odd that the default is not 1... it should be
1. I'll double check.
Thanks for testing this stuff out!
yaussy wrote:
I put a post in the user forum for this, but thought I'd add
something
to
this thread. I'm concerned about backward compatibility. I've
got a
test
environment with all brokers at 4.0.1, except one I'm upgrading
to 4.1.
This would be how our production environment would be upgraded - a
machine
or so at a time.
However, the 4.0.1 brokers will not connect to the 4.1 broker,
giving
the
following exception:
Exception in thread "ActiveMQ Transport: tcp:///
170.137.15.160:34695"
java.lang.IllegalArgumentException: Invalid version: 2, could not l
oad org.apache.activemq.openwire.v2.MarshallerFactory
at
org.apache.activemq.openwire.OpenWireFormat.setVersion
(OpenWireFormat.java:329)
at
org.apache.activemq.openwire.OpenWireFormat.renegociatWireFormat
(OpenWireFormat.java:569)
at
org.apache.activemq.transport.WireFormatNegotiator.onCommand
(WireFormatNegotiator.java:100)
at
org.apache.activemq.transport.InactivityMonitor.onCommand
(InactivityMonitor.java:122)
at
org.apache.activemq.transport.TransportSupport.doConsume
(TransportSupport.java:87)
at
org.apache.activemq.transport.tcp.TcpTransport.run
(TcpTransport.java:143)
at java.lang.Thread.run(Thread.java:595)
Caused by: java.lang.ClassNotFoundException:
org.apache.activemq.openwire.v2.MarshallerFactory
at
org.apache.activemq.util.ClassLoading.loadClass
(ClassLoading.java:104)
at
org.apache.activemq.openwire.OpenWireFormat.setVersion
(OpenWireFormat.java:327)
... 6 more
There must be an upgrade path for 4.1. If that means I have to
go to
4.0.2 (which I did not try yet), that is OK. But, I can't possibly
tell
my management that I have to upgrade the AMQ version on all 50
or so
machines we have in production.
Hiram Chirino wrote:
I'm starting to work on the first release candidate for 4.1..
please let me know if I should hold off!
On 10/3/06, Vadim Pesochinsky <[EMAIL PROTECTED]>
wrote:
Hi James,
It looks like this is changed now with 4.0.3. Any idea when
4.1 is
going
to
be out? Thanks.
--
View this message in context:
http://www.nabble.com/Release-schedule-tf2124265.html#a6630219
Sent from the ActiveMQ - Dev mailing list archive at Nabble.com.
--
Regards,
Hiram
Blog: http://hiramchirino.com
--
View this message in context:
http://www.nabble.com/Release-schedule-tf2124265.html#a6647640
Sent from the ActiveMQ - Dev mailing list archive at Nabble.com.
--
Regards,
Hiram
Blog: http://hiramchirino.com
--
View this message in context: http://www.nabble.com/Release-
schedule-tf2124265.html#a7935126
Sent from the ActiveMQ - Dev mailing list archive at Nabble.com.
