I believe I was told there was some kind of multi-step upgrade path
from old 4.x releases to new 4.x releases (if you want to upgrade the
server and multiple clients with minimal down time), but as far as I
know the folks who worked that process out haven't gone to 5.x. I can
try to get more details if the upgrades within the 4.x series are
still of interest.
Thanks,
Aaron
On Mon, Jul 7, 2008 at 11:47 AM, Bruce Snyder <[EMAIL PROTECTED]> wrote:
> On Mon, Jun 30, 2008 at 4:59 PM, allenb <[EMAIL PROTECTED]> wrote:
>>
>> Hello,
>>
>> I'm currently running a 4.0.1 server with 4.0.1 clients. I'd like to
>> upgrade everything to 5.1.0, but not at the same time. Ideally, I'd do a 2
>> stage upgrade where I first bump the server to 5.1.0 and then the clients.
>>
>> Are there any known compatibility issue between a 4.0.1 client and a 5.1.0
>> server? I ask because in my testing there appears to be some problems. I'm
>> running 4.0.1 clients against a 5.1.0 server and see errors similar to the
>> following in the servers log over and over and eventually run out of heap.
>>
>> ERROR Service - Async error occurred:
>> java.lang.NullPointerException
>> java.lang.NullPointerException
>> at org.apache.activemq.command.SessionId.<init>(SessionId.java:39)
>> at
>> org.apache.activemq.command.SessionInfo.<init>(SessionInfo.java:37)
>> at
>> org.apache.activemq.state.ConnectionState.<init>(ConnectionState.java:47)
>> at
>> org.apache.activemq.broker.TransportConnectionState.<init>(TransportConnectionState.java:35)
>> at
>> org.apache.activemq.broker.TransportConnection.processAddConnection(TransportConnection.java:619)
>> at
>> org.apache.activemq.command.ConnectionInfo.visit(ConnectionInfo.java:125)
>> at
>> org.apache.activemq.broker.TransportConnection.service(TransportConnection.java:292)
>> at
>> org.apache.activemq.broker.TransportConnection$1.onCommand(TransportConnection.java:180)
>> at
>> org.apache.activemq.transport.TransportFilter.onCommand(TransportFilter.java:68)
>> at
>> org.apache.activemq.transport.WireFormatNegotiator.onCommand(WireFormatNegotiator.java:143)
>> at
>> org.apache.activemq.transport.InactivityMonitor.onCommand(InactivityMonitor.java:206)
>> at
>> org.apache.activemq.transport.TransportSupport.doConsume(TransportSupport.java:84)
>> at
>> org.apache.activemq.transport.tcp.TcpTransport.doRun(TcpTransport.java:196)
>> at
>> org.apache.activemq.transport.tcp.TcpTransport.run(TcpTransport.java:183)
>> at java.lang.Thread.run(Unknown Source)
>>
>>
>> Does anyone have any input on this? Is there a recommended upgrade path or
>> a client/server compatibility matrix floating around?
>
> Chances are there are some sizable incompatibilities between ActiveMQ
> 4.0.1 and 5.1 simply because the time between those releases is about
> 18 months. If you're going to upgrade the broker to 5.1 then I'd
> recommend upgrading the clients at the same time.
>
> Bruce
> --
> perl -e 'print unpack("u30","D0G)[EMAIL
> PROTECTED]&5R\"F)R=6-E+G-N>61E<D\!G;6%I;\"YC;VT*"
> );'
>
> Apache ActiveMQ - http://activemq.org/
> Apache Camel - http://activemq.org/camel/
> Apache ServiceMix - http://servicemix.org/
>
> Blog: http://bruceblog.org/
>
>
