activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Justin Pitts (JIRA)" <j...@apache.org>
Subject [jira] Commented: (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
Date Mon, 03 Nov 2008 19:37:05 GMT

    [ https://issues.apache.org/activemq/browse/AMQ-1990?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=47032#action_47032
] 

Justin Pitts commented on AMQ-1990:
-----------------------------------

I have not verified in anything but 5.1. Our product is currently shipping with 5.1. Should
I not expect this issue to be addressed in 5.1?

> 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/activemq/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
>         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.


Mime
View raw message