You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@activemq.apache.org by "Dejan Bosanac (JIRA)" <ji...@apache.org> on 2010/12/02 14:14:12 UTC

[jira] Updated: (AMQ-1990) Failing network connectors randomly log SEVERE message : Could not accept connection : java.lang.Object cannot be cast to org.apache.activemq.command.Command

     [ https://issues.apache.org/jira/browse/AMQ-1990?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Dejan Bosanac updated AMQ-1990:
-------------------------------

    Fix Version/s:     (was: 5.4.2)
                   5.5.0

> 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.5.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.
-
You can reply to this email to add a comment to the issue online.