[
https://issues.apache.org/jira/browse/AMQ-1990?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13063926#comment-13063926
]
Justin Pitts commented on AMQ-1990:
-----------------------------------
Can someone point me to a clear, unambiguous statement regarding the policy on
versioning and back-porting bugs? At what point does a version become
unsupported? So far as I can tell, M.m becomes unsupported the moment M.m+1 is
released. This is frustrating because, as I mentioned, we embed the broker in
our product, and in the past upgrading minor versions has required significant
developer and QA resources to validate. That's a surprise to me.
> Failing network connectors randomly log SEVERE message : Could not accept
> connection : java.lang.Object cannot be cast to
> org.apache.activemq.command.Command
> -------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: AMQ-1990
> URL: https://issues.apache.org/jira/browse/AMQ-1990
> Project: ActiveMQ
> Issue Type: Bug
> Components: Broker
> Affects Versions: 5.1.0
> Environment: Linux, Windows XP, Mac OSX 10.5.1
> Reporter: Justin Pitts
> Fix For: 5.6.0
>
> Attachments: CouldNotAcceptConnection.java
>
>
> I have an application which embeds the broker service. A common deployment
> scenario is a sometimes-connected network of these applications.
> Unfortunately, I don't have many situations where I can use discovery, so the
> network connectors are static configurations. Randomly, when these network
> connections are unable to connect, I see the following exception trace:
> 30 Sep 2008 18:36:18 ERROR [ActiveMQ Transport Initiator: vm://instance-2#2]
> (TransportConnector.java:234) - Could not accept connection :
> java.lang.Object cannot be cast to org.apache.activemq.command.Command
> These errors seem like they might be the result of a race condition during
> start or stop of a network connector. I will attach a sample application
> which demonstrates the problem. You may have to run the application a couple
> times to provoke it.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
